GNOME Bugzilla – Bug 172831
gnome-volume-manager crashed while running apt-get upgrade
Last modified: 2005-04-06 17:12:36 UTC
Distribution: Debian 3.1 Package: gnome-volume-manager Severity: normal Version: GNOME2.10.0 1.2.x Gnome-Distributor: Ubuntu Synopsis: gnome-volume-manager crashed while running apt-get upgrade Bugzilla-Product: gnome-volume-manager Bugzilla-Component: general Bugzilla-Version: 1.2.x BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: unknown cause Steps to reproduce the crash: ran apt-get upgrade for the first time on a new ubuntu hoary (5.04) system and the volume manager crashed at somepoint after that. I'm not sure it is related to running apt-get install. How often does this happen? has only happened once. Debugging Information: Backtrace was generated from '/usr/bin/gnome-volume-manager' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (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 -1221838112 (LWP 7294)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 57790
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-06 12:33 ------- 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 brandon@faloona.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. Matches the stack trace in bug 172644, which has been marked as a duplicate of 170894. *** This bug has been marked as a duplicate of 170894 ***