GNOME Bugzilla – Bug 508056
crash in File Browser: Nothing
Last modified: 2008-01-09 08:49:12 UTC
What were you doing when the application crashed? Nothing Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.18-4-686 #1 SMP Mon Mar 26 17:17:36 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 71614464 vsize: 71614464 resident: 21557248 share: 14225408 rss: 21557248 rss_rlim: 4294967295 CPU usage: start_time: 1199798279 rtime: 156 utime: 144 stime: 12 cutime:174 cstime: 21 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 0xb6e126b0 (LWP 25119)] (no debugging symbols found) 0xb768e321 in waitpid () from /lib/libpthread.so.0
+ Trace 184521
Thread 1 (Thread 0xb6e126b0 (LWP 25119))
----------- .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 /home/francesco/Desktop/Diagrama1.dia --> /tmp/.gnome_thumbnail.U5T24T /home/francesco/Cableado-Mesacavaca-Torres.dia --> /tmp/.gnome_thumbnail.7OFT4T ** ERROR **: file nautilus-navigation-window.c: line 723 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers)) aborting... /usr/share/themes/Glossy/gtk-2.0/gtkrc:62: error: unexpected identifier `colorize_scrollbar', expected character `}' Failed to read a valid object file image from memory. --------------------------------------------------
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 459221 ***