GNOME Bugzilla – Bug 611961
crash in Home Folder: thumbnail en constructio...
Last modified: 2010-03-08 03:39:18 UTC
What were you doing when the application crashed? thumbnail en construction Distribution: Debian squeeze/sid Gnome Release: 2.28.2 2009-12-18 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.32-trunk-686-bigmem #1 SMP Sun Jan 10 07:12:17 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10705000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 206958592 vsize: 206958592 resident: 104062976 share: 37789696 rss: 104062976 rss_rlim: 18446744073709551615 CPU usage: start_time: 1267815407 rtime: 13699 utime: 12935 stime: 764 cutime:5781 cstime: 446 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xabad1b70 (LWP 4002)] [New Thread 0xb533ab70 (LWP 1571)] 0xb7854424 in __kernel_vsyscall ()
+ Trace 220825
Thread 1 (Thread 0xb66d3760 (LWP 3931))
Inferior 1 [process 3931] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** nautilus **: nautilus_file_get_uri: assertion `NAUTILUS_IS_FILE (file)' failed ----------- .xsession-errors (3660 sec old) --------------------- (firefox-bin:5131): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:5131): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:5131): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:5131): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:5131): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:5131): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:5131): Gdk-WARNING **: XID collision, trouble ahead ...Too much output, ignoring rest... --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 602500 ***