GNOME Bugzilla – Bug 115380
control center crashes on startup
Last modified: 2004-12-22 21:47:04 UTC
Package: control-center Severity: normal Version: GNOME2.2.2 2.2.1 os_details: Ximian, Inc. Synopsis: control center crashes on startup Bugzilla-Product: control-center Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: Approximately every other time I start the control center, it crashes immediately. If I start it again, it usually works. Crash dump should be attached. Seemed to die in FAM call. RH9 + Ximian 2 desktop. NFS mounted home directory. Steps to reproduce the problem: 1. 2. 3. Actual Results: Expected Results: How often does this happen? 50% Additional Information: RH9 + Ximian 2 desktop. NFS mounted home directory. Debugging Information: Backtrace was generated from '/usr/bin/gnome-control-center' (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 27780)] (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)...(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)...(no debugging symbols found)... 0x402e21a7 in waitpid () from /lib/libpthread.so.0
+ Trace 37892
Thread 1 (Thread 16384 (LWP 27780))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-06-17 12:35 ------- The original reporter (steve@ageia.com) 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.
I believe this is a duplicate of 111147 (though I'm not completely sure). From Alex's comment in that bug: Can you please try these: http://people.redhat.com/alexl/RPMS/gnome-vfs2-2.2.2-4.1famfix.i386.rpm http://people.redhat.com/alexl/RPMS/gnome-vfs2-debuginfo-2.2.2-4.1famfix.i386.rpm and see if the crash is fixed? I'll let someone else decide whether this is a dup or not and whether to mark it...
From email: The packages you suggested seem to have fixed the crashes. But it's an ugly fix for my purposes because the RPM package versions mismatch with the rest of Ximian GNOME2. Well, that at least means that this really is a duplicate of bug 111147, so we know the basics of how to fix it. I agree that if it conflicts with Ximian Gnome2 then it's an ugly solution. I'm not sure whether that belongs here, or in Ximian's bugzilla, though. So I'll leave off the bugsquad keyword and keep the bug open, but add the GNOMEVER2.2 keyword.
I'm resolving this. The fam fix will go downstream to Ximian once we have tarballs incorporating it and they package those into RPMs. Since the fix is in CVS, that will happen eventually.
Doh! *** This bug has been marked as a duplicate of 111147 ***