GNOME Bugzilla – Bug 610080
crash in Home Folder: ouverture d'un fichier R...
Last modified: 2010-02-16 09:29:13 UTC
What were you doing when the application crashed? ouverture d'un fichier RTF 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 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10704000 Selinux: No Accessibility: Disabled GTK+ Theme: Wasp Icon Theme: Wasp GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 149164032 vsize: 149164032 resident: 72478720 share: 31363072 rss: 72478720 rss_rlim: 18446744073709551615 CPU usage: start_time: 1266303788 rtime: 5359 utime: 4910 stime: 449 cutime:15 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xb0bffb70 (LWP 19588)] 0xb7814424 in __kernel_vsyscall ()
+ Trace 220593
Thread 1 (Thread 0xb669f760 (LWP 3675))
Inferior 1 [process 3675] 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 (4920 sec old) --------------------- (firefox-bin:5217): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:5217): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:5217): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:5217): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:5217): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:5217): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:5217): 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 ***