GNOME Bugzilla – Bug 134395
gnome-panel segfauls at startup
Last modified: 2009-08-15 18:40:50 UTC
Distribution: Debian testing/unstable Package: gnome-panel Severity: blocker Version: GNOME2.4.1 2.4.x Gnome-Distributor: Debian Synopsis: gnome-panel segfauls at startup Bugzilla-Product: gnome-panel Bugzilla-Component: Panel Bugzilla-Version: 2.4.x BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: When starting gnome (through starting metacity) gnome-panel crashes, and after dismissing the message the X-Session is terminated. Gnome can no longer used on my machine. Steps to reproduce the crash: I don't know how anybody can get this situation on his machine. I simply start metacity as X-Session. Expected Results: :) How often does this happen? Every time metacity is started 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)...(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)...[New Thread 1081895648 (LWP 10585)] (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)...0x405ac3ee in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 44179
Thread 1 (Thread 1081895648 (LWP 10585))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-02-14 13:19 ------- Reassigning to the default owner of the component, gnome-panel-maint@bugzilla.gnome.org.
correction: after dismissing (Close) the error-message gnome-panel is restarted immediately, crashing again. I have to terminate X with CTRL-ALT-Backspace.
You need to update FAM - see bug #111147 *** This bug has been marked as a duplicate of 111147 ***
$ dpkg -l libgnomevfs2-common libgnomevfs2-0 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-=========================================-=========================================-================================================================================================== ii libgnomevfs2-common 2.4.1-4.1 The GNOME virtual file-system library common files (for GNOME2) ii libgnomevfs2-0 2.4.1-4.1 The GNOME virtual file-system libraries (for GNOME2) I'm already on newest version with FAM, I think. But the problem is still there. Are you sure that this is a duplicate with #111147? If so, what should I do to fix it?
Please, help me finding a solution for this problem. I don't think that this should be a duplicate bug, because the problem is not solvable by updating FAM, as far as I can see. Additionally, the system with the problem is somewhat important for me, and it now doesn't work any more for over a week. So, if you can give me any hint, tell what I could do.
Try renaming ~/.recently-used to something else. And if it works, please send me this file. Thanks
OK, I had the same kind of problem: Gnome-panel craches at startup whith segfault. Removing (moving at least) the .recently-used file seemed to solve it. (I did not restart yet) If someone want it for debugging needs, I saved my .recently-used file. nathaelp@hotmail.com
shouldn't this bug now be reopened, perhaps with lower severity? Or is this still related to Bug #111147?
I'm working with a gnome-vfs maintainer right now on this bug. We'll open a bug if we don't find a fix (note that this does not crash on HEAD: the problem only occurs on debian).
*** Bug 145857 has been marked as a duplicate of this bug. ***
*** Bug 147024 has been marked as a duplicate of this bug. ***
*** Bug 146495 has been marked as a duplicate of this bug. ***
*** Bug 147397 has been marked as a duplicate of this bug. ***
*** Bug 149766 has been marked as a duplicate of this bug. ***
*** Bug 149980 has been marked as a duplicate of this bug. ***
*** Bug 148206 has been marked as a duplicate of this bug. ***
*** Bug 153956 has been marked as a duplicate of this bug. ***
*** Bug 158937 has been marked as a duplicate of this bug. ***
*** Bug 162468 has been marked as a duplicate of this bug. ***
*** Bug 163642 has been marked as a duplicate of this bug. ***
*** Bug 164107 has been marked as a duplicate of this bug. ***
*** Bug 172457 has been marked as a duplicate of this bug. ***
*** Bug 304730 has been marked as a duplicate of this bug. ***
*** Bug 304731 has been marked as a duplicate of this bug. ***