GNOME Bugzilla – Bug 535715
crash in File Browser: Tentando di leggere il c...
Last modified: 2008-05-30 11:17:26 UTC
Version: 2.20.0 What were you doing when the application crashed? Tentando di leggere il contenuto di una cartella di rete windows Distribution: Unknown Gnome Release: 2.22.1 2008-04-29 (Hymera) BugBuddy Version: 2.22.0 System: Linux 2.6.24.6-hymera-686 #2 SMP Tue May 20 17:50:57 CEST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Hymera Icon Theme: Hymera Memory status: size: 137785344 vsize: 137785344 resident: 32358400 share: 21299200 rss: 32358400 rss_rlim: 4294967295 CPU usage: start_time: 1212138815 rtime: 709 utime: 662 stime: 47 cutime:3 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b63720 (LWP 6220)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 199142
Thread 1 (Thread 0xb6b63720 (LWP 6220))
----------- .xsession-errors (5182 sec old) --------------------- File "/home/hymera/.screenlets/Netmonitor/NetmonitorScreenlet.py", line 278, in on_draw self.get_load() File "/home/hymera/.screenlets/Netmonitor/NetmonitorScreenlet.py", line 112, in get_load data = data.split(':')[1]; IndexError: list index out of range Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/screenlets/__init__.py", line 1688, in expose self.on_draw(ctx) File "/home/hymera/.screenlets/Netmonitor/NetmonitorScreenlet.py", line 278, in on_draw self.get_load() File "/home/hymera/.screenlets/Netmonitor/NetmonitorScreenlet.py", line 112, in get_load data = data.split(':')[1]; IndexError: list index out of range ...Too much output, ignoring rest... --------------------------------------------------
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 522534 ***