GNOME Bugzilla – Bug 507679
crash in File Browser: Intentar leer el espacio...
Last modified: 2008-01-07 13:32:02 UTC
Version: 2.18.3 What were you doing when the application crashed? Intentar leer el espacio vacio de una targeta de memoria 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: 70000000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks-Visto Icon Theme: Gion Memory status: size: 84840448 vsize: 84840448 resident: 30752768 share: 16863232 rss: 30752768 rss_rlim: 4294967295 CPU usage: start_time: 1199634857 rtime: 160 utime: 147 stime: 13 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 0xb6d3b6b0 (LWP 22678)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 184285
Thread 1 (Thread 0xb6d3b6b0 (LWP 22678))
----------- .xsession-errors --------------------- ** 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 ** Message: drive = 0 ** Message: volume = 0 /home/guillem/.themes/Clearlooks-Visto/gtk-2.0/gtkrc:54: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored. /home/guillem/.themes/Clearlooks-Visto/gtk-2.0/gtkrc:55: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored. /home/guillem/.themes/Clearlooks-Visto/gtk-2.0/gtkrc:56: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. --------------------------------------------------
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 ***