GNOME Bugzilla – Bug 158733
gnome-volume-manager (and eggcups) crash unexpectedly at startup
Last modified: 2005-01-03 16:26:51 UTC
Distribution: Fedora Core release 3 (Heidelberg) Package: gnome-volume-manager Severity: normal Version: GNOME2.8.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: program reports crash after installing imagemagik also egg cups Bugzilla-Product: gnome-volume-manager Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Steps to reproduce the crash: 1. install imagemagik 2. log out then log in 3. after reboot Expected Results: How often does this happen? Always Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-volume-manager' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -151156512 (LWP 3191)] (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)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x003407a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 52216
Thread 1 (Thread -151156512 (LWP 3191))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-19 14:10 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-volume-manager". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was fletcher_dave@hotmail.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
May be a duplicate of bug 158697 (or even bug 141544) but it's hard to tell without a better stack trace. Reporter: Could you install the glib2, gtk2, hal, dbus, and gnome-volume-manager debuginfo rpms from http://download.fedora.redhat.com/pub/fedora/linux/core/3/i386/debug/, get the crash to happen again, and then paste the new stack trace into this bug report?
*** Bug 158746 has been marked as a duplicate of this bug. ***
*** Bug 158779 has been marked as a duplicate of this bug. ***
*** Bug 158778 has been marked as a duplicate of this bug. ***
*** Bug 158786 has been marked as a duplicate of this bug. ***
*** Bug 158813 has been marked as a duplicate of this bug. ***
*** Bug 158844 has been marked as a duplicate of this bug. ***
My Bug 158779 has been marked a duplicate of this bug. I installed the glib2, gtk2, hal, dbus, and gnome-volume-manager debuginfo rpms as suggested in Additional Comment #1 and rebooted. Here are the stack traces from the two (gnome-volume-manager AND eggcups) as requested. GNOME-VOLUME-MANAGER Backtrace was generated from '/usr/bin/gnome-volume-manager' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -151144768 (LWP 3220)] 0x0051e7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 52313
Thread 1 (Thread -151144768 (LWP 3220))
Awesome! Thanks for the stack traces. The eggcups one looks like bug 151703. I'll reopen this bug due to the gnome-volume-manager one.
err, I meant bug 151307. Chris: comment 13 of bug 151307 provided a workaround the eggcups crash. Does it also fix the gnome-volume-manager issue?
*** Bug 158912 has been marked as a duplicate of this bug. ***
*** Bug 158908 has been marked as a duplicate of this bug. ***
*** Bug 158911 has been marked as a duplicate of this bug. ***
Elijah, et al... I'd like to try out the fix suggested in bug 151307, comment 13 (use command: prelink /usr/lib/libdbus*so*), but the errors have mysteriously stopped occuring on my machine! The only thing I did recently was to reboot once using KDE instead of Gnome... I knew the gnome-volume-manager error wouldn't appear, but I was trying to see if the eggcups error would manifest itself when I used KDE. Could this have duplicated the prelink command? Anyway, I have rebooted three times this morning and have not gotten the errors - I'll try the prelink command if they crop up again. Hopefully, prelink is the solution to the errors - but what was the cause? It seems a lot of individuals have had this problem since running the November 20 Fedora Core 3 update.
*** Bug 158975 has been marked as a duplicate of this bug. ***
Chris: I have no idea, but maybe Colin does, since he suggested it in the first place...
*** Bug 159147 has been marked as a duplicate of this bug. ***
I was having this problem and the problem in bug 151307, and the solution was in comment 10. It fixed both issues.
*** Bug 159261 has been marked as a duplicate of this bug. ***
*** Bug 159267 has been marked as a duplicate of this bug. ***
*** Bug 159278 has been marked as a duplicate of this bug. ***
*** Bug 159313 has been marked as a duplicate of this bug. ***
*** Bug 159358 has been marked as a duplicate of this bug. ***
*** Bug 159372 has been marked as a duplicate of this bug. ***
*** Bug 159377 has been marked as a duplicate of this bug. ***
From bug 159358: when i yum updated, one of the gnome packages apparently required hal-gnome but did not enforce that dependency ( so yum didn't install it ). After installing hal-gnome, gnome-volumne-manager no longer crashes and all works well. So, this is a bug against one or many spec files for packages that are missing a require line for hal-gnome. So there might be something else involved, but perhaps that user ran prelink without knowing it...
*** Bug 159572 has been marked as a duplicate of this bug. ***
*** Bug 159585 has been marked as a duplicate of this bug. ***
*** Bug 159618 has been marked as a duplicate of this bug. ***
*** Bug 159638 has been marked as a duplicate of this bug. ***
*** Bug 159641 has been marked as a duplicate of this bug. ***
*** Bug 159642 has been marked as a duplicate of this bug. ***
*** Bug 159691 has been marked as a duplicate of this bug. ***
*** Bug 159694 has been marked as a duplicate of this bug. ***
*** Bug 159707 has been marked as a duplicate of this bug. ***
*** Bug 159725 has been marked as a duplicate of this bug. ***
*** Bug 159799 has been marked as a duplicate of this bug. ***
*** Bug 159868 has been marked as a duplicate of this bug. ***
*** Bug 159876 has been marked as a duplicate of this bug. ***
*** Bug 159891 has been marked as a duplicate of this bug. ***
*** Bug 159934 has been marked as a duplicate of this bug. ***
*** Bug 159953 has been marked as a duplicate of this bug. ***
*** Bug 160062 has been marked as a duplicate of this bug. ***
*** Bug 160241 has been marked as a duplicate of this bug. ***
We haven't gotten any more dups since Fedora updated prelink (and we used to get several, and at least a couple reporters said that manually running prelink fixed the issue...), so I'm going to go ahead and close. *** This bug has been marked as a duplicate of 160111 ***
*** Bug 162810 has been marked as a duplicate of this bug. ***