GNOME Bugzilla – Bug 506893
crash in Open Folder: properties of USB key
Last modified: 2008-01-02 21:00:30 UTC
Version: 2.18.3 What were you doing when the application crashed? properties of USB key Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22 #3 PREEMPT Sat Dec 22 15:46:45 CET 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 431001600 vsize: 431001600 resident: 34410496 share: 15749120 rss: 34410496 rss_rlim: 18446744073709551615 CPU usage: start_time: 1199294538 rtime: 2260 utime: 1946 stime: 314 cutime:2033 cstime: 558 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 0x2ad5b89bc540 (LWP 6902)] [New Thread 0x42804950 (LWP 13181)] [New Thread 0x40800950 (LWP 10300)] (no debugging symbols found) 0x00002ad5b1f4234f in waitpid () from /lib/libpthread.so.0
+ Trace 183823
Thread 1 (Thread 0x2ad5b89bc540 (LWP 6902))
----------- .xsession-errors (13 sec old) --------------------- ** 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 ** Message: drive = 0 ** Message: volume = 0 /usr/share/themes/ClearlooksClassic/gtk-2.0/gtkrc:61: error: unexpected identifier `colorize_scrollbar', expected character `}' --------------------------------------------------
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 ***