GNOME Bugzilla – Bug 113027
gnome-panel segfaults repeatedly
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-panel Severity: major Version: 2.2.0.1 Synopsis: gnome-panel segfaults repeatedly Bugzilla-Product: gnome-panel Bugzilla-Component: Panel BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: RH9 crashed; when it came back up, there were numerous errors that gnome settings couldn't be restored. Everyone (gnome-panel, nautilus, gnome-terminal) are all having trouble... sigh. This almost certainly isn't a gnome-panel issue per se, but it happens to be the app that keeps failing. Steps to reproduce the problem: 1. install RH9 2. crash 3. repeat (sorry I couldn't be more helpful here) Actual Results: gnome-panel gets restarted (by session mgmt?) repeatedly and segfaults every time. Expected Results: no segv, for any reason, even after a crash. How often does this happen? once; unable (unwilling) to crash my machine repeatedly. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (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 1086409632 (LWP 6777)] 0xffffe002 in ?? ()
+ Trace 36895
Thread 1 (Thread 1086409632 (LWP 6777))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-05-15 00:13 ------- Reassigning to the default owner of the component, gnome-panel-maint@bugzilla.gnome.org.
By "gnome settings couldn't be restored", I really mean that gnome complains that the gnome-settings-daemon couldn't be started. FYI, This occurred after I powered off (no shutdown... box was unresponsive). ext3 recovered the journal and I expected I'd be fine.
This is a duplicate of bug 10711, which really isn't going to help you much since that bug was marked as NOTGNOME. I'll try to give you a pointer on what you might try, though. It sounds like your system somehow got messed up. One way I've checked for this before on my RedHat systems (I have power outages here all the time which caused lots of unclean shutdowns before I got a UPS so I had to learn this trick) is to run the following command as root: rpm -Va > verify_all_packages.txt Then wait about an hour for it to finish (it checks the integrity of each and every file installed via rpm on your machine) and look through the resulting file. Mostly, you can search for the string "missing", although the other changes may be relevant too (see 'man rpm' for a description of the other fields). Note that, the most relevant verification to do would probably be rpm -V fam so if you're impatient, you can just run that--hopefully that would give some insights. If this doesn't work for you, I have no clue what to tell you other than perhaps reinstall or try to contact the FAM developers. *** This bug has been marked as a duplicate of 107111 ***