GNOME Bugzilla – Bug 105268
gnome-theme-manager crashes at start ([gnome_theme_save_show_dialog] after [libgnomeui_module_info_get])
Last modified: 2009-08-15 18:40:50 UTC
Package: control-center Severity: critical Version: GNOME2.2.0 2.2.0.1 os_details: Gnome.Org Synopsis: gnome-theme-manager crashes at start Bugzilla-Product: control-center Bugzilla-Component: theme-manager BugBuddy-GnomeVersion: 2.0 (2.2.0) Description: gnome-theme-manager from recent versions of control-center (including 2.2.0.1) always crashes at start. It happens also with user which have not any configuration files (new user). I use gnome 2.2 compiled by me on Slackware 8.1. Debugging Information: Backtrace was generated from '/opt/gnome2/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 1024 (LWP 26447)] 0x40ae6089 in __wait4 () from /lib/libc.so.6
+ Trace 33498
Thread 1 (Thread 1024 (LWP 26447))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-04 23:43 ------- Reassigning to the default owner of the component, control-center-maint@bugzilla.gnome.org.
Apparently a unique stack trace. Setting version->2.2.x, marking priority->high (it's a crasher), adding GNOMEVER2.1 (GNOMEVER2.2 keyword still doesn't exist yet, though it should) and bugsquad keywords and marking as new.
*** Bug 105411 has been marked as a duplicate of this bug. ***
We had a similar report on Gentoo Bugzilla: http://bugs.gentoo.org/show_bug.cgi?id=18077 We finally nailed it down to the GConf key for default themes being unset or empty. According to the bug reporter, it was set as an int rather than a string. The GConf key in question is: /desktop/gnome/interface/gtk_theme The bug reporter fixed it by setting the key to type String and with a non-null value.
*** Bug 109745 has been marked as a duplicate of this bug. ***
*** Bug 107986 has been marked as a duplicate of this bug. ***
*** Bug 110058 has been marked as a duplicate of this bug. ***
*** Bug 110332 has been marked as a duplicate of this bug. ***
*** Bug 110952 has been marked as a duplicate of this bug. ***
*** Bug 110917 has been marked as a duplicate of this bug. ***
Changing the type of that key still causes a crash in latest CVS, but with a different trace. Backtrace was generated from '/gnome/install/bin/gnome-theme-manager' [New Thread 1085845952 (LWP 629)] 0xffffe002 in ?? ()
+ Trace 36527
Thread 1 (Thread 1085845952 (LWP 629))
*** Bug 114200 has been marked as a duplicate of this bug. ***
*** Bug 115406 has been marked as a duplicate of this bug. ***
*** Bug 116021 has been marked as a duplicate of this bug. ***
Is bug 115034 a duplicate of this bug?
*** Bug 123799 has been marked as a duplicate of this bug. ***
*** Bug 122574 has been marked as a duplicate of this bug. ***
Does this bug still occur? It looks like that strcmp won't crash anymore.
No response and no more dups--assuming that it doesn't still occur and I'm closing. Feel free to reopen if that's in error.