GNOME Bugzilla – Bug 506391
crash in Computer:
Last modified: 2007-12-30 11:27:36 UTC
Version: 2.18.3 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.23.9-vagner #1 SMP PREEMPT Tue Dec 25 22:44:56 TAHT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Nuvola Icon Theme: Nuvola Memory status: size: 93806592 vsize: 93806592 resident: 39915520 share: 22421504 rss: 39915520 rss_rlim: 4294967295 CPU usage: start_time: 1199002248 rtime: 1581 utime: 1442 stime: 139 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6df26b0 (LWP 4514)] (no debugging symbols found) 0xb7fa8410 in __kernel_vsyscall ()
+ Trace 183522
Thread 1 (Thread 0xb6df26b0 (LWP 4514))
----------- .xsession-errors --------------------- Traceback (most recent call last): File "/usr/lib/nautilus/extensions-1.0/python/bluetooth.py", line 16, in get_file_items file = files[0] IndexError: list index out of range Traceback (most recent call last): File "/usr/lib/nautilus/extensions-1.0/python/bluetooth.py", line 16, in get_file_items file = files[0] IndexError: list index out of range ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 sys:1: GtkWarning: 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 ***