GNOME Bugzilla – Bug 605422
crash in Computer: copied the name of a fil...
Last modified: 2009-12-26 02:13:14 UTC
Version: 2.28.1 What were you doing when the application crashed? copied the name of a file. While the name of the file was still open to edit(?), I ran a commad that had about 1000 output textfiles in teh same directory. Clicked on the white space to close the name-editing "box". Those 1000 files weren't shown yen in nautilus. Distribution: Debian 5.0.3 Gnome Release: 2.28.0 2009-11-21 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.32-trunk-686 #1 SMP Thu Dec 17 00:26:04 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 138469376 vsize: 138469376 resident: 49459200 share: 24338432 rss: 49459200 rss_rlim: 18446744073709551615 CPU usage: start_time: 1261686239 rtime: 20503 utime: 18851 stime: 1652 cutime:632 cstime: 84 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xb53feb70 (LWP 7973)] 0xb7830424 in __kernel_vsyscall ()
+ Trace 219770
Thread 1 (Thread 0xb66c0950 (LWP 5238))
Inferior 1 [process 5238] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (51497 sec old) --------------------- (firefox-bin:4794): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:4794): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:4794): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:4794): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:4794): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:4794): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:4794): 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 602613 ***