GNOME Bugzilla – Bug 106683
Unable to install meta-themes
Last modified: 2004-12-22 21:47:04 UTC
Package: control-center Severity: critical Version: GNOME2.2.0 2.2.0.1 os_details: Gnome.Org Synopsis: Unable to install meta-themes Bugzilla-Product: control-center Bugzilla-Component: theme-manager BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: Steps to reproduce the problem: 1. 2. 3. Actual Results: Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/X11R6/bin/gnome-theme-manager' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... [Switching to Process 18751, Thread 1] 0x28b1bab3 in poll () from /usr/lib/libc.so.5
+ Trace 34097
Thread 1 (Process 18751, Thread 1)
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-21 01:58 ------- The original reporter (andreyf@gsnet.ru) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, control-center-maint@bugzilla.gnome.org.
Looks like this is a duplicte of bug 105706, but I'll not mark it as such so that we might be able to get some questions answered: This trace seems incomplete. Can you get us a more complete one? (See http://bugzilla.gnome.org/getting-traces.cgi for more information on this). Also, Luis thought bug 105706 (which is a report nearly identical to this one) was probably related to FreeBSD. Are you running on that platform?
I apologize for the spam, but in talking to David Kennedy on #bugs we decided that it might be useful for me to add a comment to a lot of bugs that have nearly identical stack traces that aren't very useful. (It took me a while because I gave up on several bugzilla queries that simply hung). Anyway, I may have caught some bugs with this query that aren't relevant, so I apologize again if this bug is one of those. If not: The following comment from 100709 may be relevant: "It turns out this was an accidental FreeBSD ABI change during the import of gcc-3.2.1. div(), a structure returning function, was the culprit."
Closing then. *** This bug has been marked as a duplicate of 100709 ***