GNOME Bugzilla – Bug 115419
gnome-panel segfaults when gconfd can't be started
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-panel Severity: critical Version: 2.2.0.1 Synopsis: gnome-panel segfaults when gconfd can't be started Bugzilla-Product: gnome-panel Bugzilla-Component: Panel BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: My machine crashed and left things in a bad state. The primary symptom which I haven't resolved is that gconfd won't start (several "resolved address xxxx to read-only source position" errors). Several apps die ungracefully as a result, including gnome-panel. I presume that this is actually the fault of an underlying library, but this was the only stage at which bug buddy worked for me. In short, I know this probably isn't a gnome-panel problem, but I don't know how else to get it logged. Steps to reproduce the problem: 1. install rh9 (in my hands, much more finnicky and unstable than previous versions) 2. install ximian desktop 3. yank cord from wall 4. repeat until it crashes hard enough Actual Results: Many programs crash ungracefully during gnome session startup, including gnome-panel. For some reason, bug buddy won't come up on earlier crashes. Expected Results: gnome2 bliss How often does this happen? everytime, several users I've tried mv'ing ~/.gnome* ~/.gconf* elsewhere and cleaning /tmp/ of orbit leftovers, etc, but this doesn't change the outcome substantially. Additional Information: - I've attached gdb to several of the crashed gconfs. The all have backtraces like (as in the full backtrace below): #0 waitpid #1 libgnomeui_module_info_get #2 __pthread_sighandler #3 <sighandler called> #4 FAMclose() #5 FAMMonitorDirectory() - I just noticed that bugbuddy caused errors that indicate bad XML input: ... initialowner=" othertag="..." ... i.e., initialowner contains an unmatched "... I suspect that the crash has left several files in horrible states (this is ext3). 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 16384 (LWP 13621)] 0x40927567 in waitpid () from /lib/i686/libpthread.so.0
+ Trace 37919
Thread 1 (Thread 16384 (LWP 13621))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-06-18 00:03 ------- Reassigning to the default owner of the component, gnome-panel-maint@bugzilla.gnome.org.
Matches the stack trace in bug 113828, and bug 113828 has been marked as a duplicate of bug 111147. Bug 111147 has links to packages which should fix this problem for you. *** This bug has been marked as a duplicate of 111147 ***