GNOME Bugzilla – Bug 104676
gnome-theme-manager crashes on start (fam)
Last modified: 2009-08-15 18:40:50 UTC
Package: control-center Severity: critical Version: 2.2.0 Synopsis: gnome-theme-manager crashes on start Bugzilla-Product: control-center Bugzilla-Component: theme-manager Description: Description of Problem: gnome-theme-manager crashes on start. Output in my term is many lines "FAMOpen failed, FAMErrno=0", then, gnome crash window. My system is quite old, based on a Debian 2.0, and often up to date (now on sid). Gnome 1.4 worked well, then when i first tried gnome2, nothing worked, then after many tries, it work fine using debian packages. I think the problem comes from themes installed months ago, and maybe deleted or something like that ... Steps to reproduce the problem: 1. install gnome2 on a 3 years old debian quite up to date 2. try to set up a theme with gnome-theme-manager 3. no tool to define a theme Actual Results: crash Expected Results: some tool to select a theme How often does this happen? always Additional Information: ------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-01-28 16:32 ------- The original reporter (francois.baudens@icam.fr) 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.
*** Bug 104677 has been marked as a duplicate of this bug. ***
We really need a stack trace from bug-buddy to find the cause of the crash. But, if you're running sid you're running an unreleased beta version of GNOME. The theme manager has a couple of open crasher bugs in this version, so it's likely you're seeing what's already been reported.
found the solution (not really the problem). I created the gconf key /desktop/gnome/interface/icon_theme and set to "gnome", verifying that /usr/share/icons/gnome exists and contains a set of icons (several directories with different size of icons "12x12" "24x24" "48x48" ...) then gnome-theme-manager launches .... ... the drag and drop of tar.bz2 themes doesn't work, but i can do without for the moment, i can detar files in ~/.themes or /usr/share/something_about_themes. Sorry for posting the bug twice.
I have a similar problem With FAM running, gnome-theme-manager will not load, no errors on console, but FAM debug shows a lot of odd querys With FAM disabled, gnome-theme-manager will load, spew FAM errors (as expected...) and work.
*** Bug 105236 has been marked as a duplicate of this bug. ***
Anyone still seeing this with the latest release or CVS?
Marking as NEEDINFO since crash reports need a stacktrace. See http://bugzilla.gnome.org/getting-traces.cgi for more details
Pre-emptively reopening, since I can see the future and people are still seeing this bug.
Apparently this still happens (at least on debian)
I'm seeing this with a (possibly bad?) theme (Germanik). Unfortunately, getting a core file is difficult. Looking at strace output, it looks like gnome-theme-manager does a fork() and sets up some signal handlers, then the child dies with a SEGV. At this point, the parent falls into an infinite loop with read(5, "", 600) = 0 This is using 2.2.1 on a stock Gentoo portage build. Workaround: change the theme manually (using gconf) to default.
It's very hard to catch bad themes. If the theme engine makes me crash, I'm going to crash. Can you confirm that that is the problem by setting the /desktop/gnome/interface/gtk_theme key in gconf to be Germanik. If that crashes your whole desktop, then we know the theme is bad.
Closing. No new information in a long time.