GNOME Bugzilla – Bug 300116
Gnome Volumen Manager quit during Synaptic update
Last modified: 2005-04-10 19:00:03 UTC
Distribution: Debian 3.1 Package: gnome-volume-manager Severity: normal Version: GNOME2.10.0 unspecified Gnome-Distributor: Ubuntu Synopsis: Gnome Volumen Manager quit during Synaptic update Bugzilla-Product: gnome-volume-manager Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: During a general update via Synaptic, the dialog box came up about Gnome Volumne Manager quitting unexpectedly. I was using gFTP at the same time. Steps to reproduce the crash: 1. Open Synaptic Package Manager 2. Apply all updates 3. Open gFTP, connect to a server, and upload files Expected Results: No Gnome Volumne Manager crash How often does this happen? First time Additional Information: 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 -1221973280 (LWP 8129)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (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 57992
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-10 14:53 ------- 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 nyondo@customjuju.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.
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 ***