GNOME Bugzilla – Bug 472764
crash in Open Folder: Deleted a file with shif...
Last modified: 2007-10-21 16:56:09 UTC
Version: 2.18.3 What were you doing when the application crashed? Deleted a file with shift+delete then quickly closed the window by Ctrl+W Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.18-3-k7 #1 SMP Mon Dec 4 17:23:11 UTC 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Industrial Memory status: size: 107745280 vsize: 107745280 resident: 39759872 share: 15523840 rss: 39759872 rss_rlim: 4294967295 CPU usage: start_time: 1188523384 rtime: 21060 utime: 18231 stime: 2829 cutime:1 cstime: 14 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 -1226827584 (LWP 6543)] [New Thread -1304429680 (LWP 19910)] (no debugging symbols found) 0xb763abf1 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 159779
Thread 1 (Thread -1226827584 (LWP 6543))
----------- .xsession-errors (191771 sec old) --------------------- ** 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 ...Too much output, ignoring rest... --------------------------------------------------
(In reply to comment #0) > Version: 2.18.3 > > What were you doing when the application crashed? > Deleted a file with shift+delete then quickly closed the window by Ctrl+W > I've been unable to reproduce the effect so far.
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 461139 ***