GNOME Bugzilla – Bug 106648
gnome theme manager crashes on BrushedGnome
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: gnome theme manager Bugzilla-Product: control-center Bugzilla-Component: theme-manager BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: Loading brushedgnome theme crashes it Steps to reproduce the problem: 1. just load BrushedGnome 2. 3. Actual Results: Expected Results: How often does this happen? every single time I've tried it Additional Information: Debugging Information: Backtrace was generated from '/usr/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)...[New Thread 16384 (LWP 16078)] (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)... 0x40b503d9 in wait4 () from /lib/libc.so.6
+ Trace 34080
Thread 1 (Thread 16384 (LWP 16078))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-20 17:28 ------- The original reporter (webmaster@quantumz.net) 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.
Thanks for the bug report. This appears to be a new stack trace.
On the advice of Andrew Sobala, I am moving my bug info from # 106314 to this one. Sorry for the previous mistake. Here is the info pasted from bug buddy. For your info (just in case) I am running gentoo. Subject: theme-manager crashes Package: control-center Severity: critical Version: GNOME2.2.0 2.2.0.1 os_details: Gnome.Org Synopsis: theme-manager crashes 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. login 2. start theme manager 3. Actual Results: theme manager has a seg fault Expected Results: theme manager should open properly and allow selecting themes How often does this happen? Every time. Additional Information: I have tried deleteing all of the .gnome* and .gconf directories in /root (I am running as root). I would also try re-installing the theme manager but I dont know which package that is in? Debugging Information: Backtrace was generated from '/usr/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)...[New Thread 16384 (LWP 7167)] (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)... 0x403c69e5 in waitpid () from /lib/libpthread.so.0
+ Trace 34261
Thread 1 (Thread 16384 (LWP 7167))
Can you reproduce this with the latest release of control-center?
*** Bug 112693 has been marked as a duplicate of this bug. ***
dup from 2.2.1
I was not able to reproduce this with 2.5 HEAD build. Request the reporter to reconfirm.
Although it's hard to tell without line numbers, I thinkg this bug was fixed a while ago. Looking at all instances of strcmp in the code, I don't see where it could be crashing.