GNOME Bugzilla – Bug 173133
I ran a dist-upgrade through synaptic, with very low free hard disk memory
Last modified: 2005-04-10 15:52:34 UTC
Distribution: Debian 3.1 Package: control-center Severity: normal Version: GNOME2.10.0 2.10.x Gnome-Distributor: Ubuntu Synopsis: I ran a dist-upgrade through synaptic, with very low free hard disk memory Bugzilla-Product: control-center Bugzilla-Component: other capplets Bugzilla-Version: 2.10.x BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: I ran a dist-upgrade through synaptic, with very low free hard disk memory: it was required 360Mb of disk space, aprox, and I had just about 400Mb left at hda2, where linux system was installed. Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? 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 -1221977376 (LWP 8558)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (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 57912
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-09 02:39 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "control-center". 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 xavidp@confluencia.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 ***