GNOME Bugzilla – Bug 515827
crash in Computer: looking hhd properties
Last modified: 2008-02-11 20:17:00 UTC
Version: 2.18.3 What were you doing when the application crashed? looking hhd properties Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 98373632 vsize: 98373632 resident: 39735296 share: 16646144 rss: 39735296 rss_rlim: 4294967295 CPU usage: start_time: 1202744946 rtime: 60856 utime: 36465 stime: 24391 cutime:512 cstime: 124 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6ce46b0 (LWP 2975)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 188853
Thread 1 (Thread 0xb6ce46b0 (LWP 2975))
----------- .xsession-errors (45 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 (nautilus:2975): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 29: Element 'markup' was closed, but the currently open element is 'b' (nautilus:2975): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 29: Element 'markup' was closed, but the currently open element is 'b' --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 355018 ***