GNOME Bugzilla – Bug 509421
crash in Computer: I wanted read the proper...
Last modified: 2008-01-14 23:51:10 UTC
Version: 2.18.3 What were you doing when the application crashed? I wanted read the properties of my floppy. Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (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: gartoon Memory status: size: 86999040 vsize: 86999040 resident: 28258304 share: 15511552 rss: 28258304 rss_rlim: 4294967295 CPU usage: start_time: 1200331252 rtime: 879 utime: 817 stime: 62 cutime:0 cstime: 0 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6e356b0 (LWP 5372)] (no debugging symbols found) 0xb768a321 in waitpid () from /lib/libpthread.so.0
+ Trace 185311
Thread 1 (Thread 0xb6e356b0 (LWP 5372))
----------- .xsession-errors (7 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:5372): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 43: Element 'markup' was closed, but the currently open element is 'b' (nautilus:5372): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 43: 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 ***