GNOME Bugzilla – Bug 159638
gnome volume manager won't start
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 3 (Heidelberg) Package: gnome-volume-manager Severity: blocker Version: GNOME2.8.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: gnome volume manager won't start Bugzilla-Product: gnome-volume-manager Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Just pops an error dialog saying it has unexpectedly quit, and will not restart. If started from the command-line, it does the same thing, and there is not additional information in the shell on standard output or error. Steps to reproduce the crash: 1. Just log in. 2. 3. Expected Results: Should start. It started up without issue before I applied all the fedora core three patches. How often does this happen? Everytime. Additional Information: This problem is probably related to the fedora core 3 patches that I applied. To get all the patches applied I had to install many of the 386 libraries for GNOME, along side the 64-bit libraries. Maybe the volume manager is trying to load the 32-bit libraries instead of the 64-bit libraries. 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 182894222176 (LWP 10571)] (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)...0x000000390760bf44 in waitpid () from /lib64/tls/libpthread.so.0
+ Trace 52747
Thread 1 (Thread 182894222176 (LWP 10571))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-27 11:44 ------- 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 andrig.t.miller@comcast.net. 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.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 158733 ***