GNOME Bugzilla – Bug 162304
Gnome-volume-manager crashed on log in
Last modified: 2004-12-27 16:54:38 UTC
Distribution: Fedora Core release 3 (Heidelberg) Package: gnome-volume-manager Severity: normal Version: GNOME2.8.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: Gnome-volume-manager crashed on log in Bugzilla-Product: gnome-volume-manager Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: error msg. when desktop is first displayed. egg-cups also crashes on login. Steps to reproduce the crash: 1. login 2. 3. Expected Results: no home or trash icons, file-browser won't start. How often does this happen?every time. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-volume-manager' (no debugging symbols found)...Using host libthread_db library "/lib64/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 182894279520 (LWP 9765)] (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)...0x00000030e510bf44 in waitpid () from /lib64/tls/libpthread.so.0
+ Trace 53895
Thread 1 (Thread 182894279520 (LWP 9765))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-12-27 04:06 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-volume-manager". Setting to default milestone for this product, '---' 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.
I believe this is the prelink issue. Getting the updated prelink rpm from Fedora should fix this problem for you. If it doesn't, let us know. *** This bug has been marked as a duplicate of 156388 ***