GNOME Bugzilla – Bug 482917
crash in Open Folder: Going up a directory/fol...
Last modified: 2007-10-21 16:56:14 UTC
Version: 2.18.3 What were you doing when the application crashed? Going up a directory/folder using the button (not back or backspace or up but the button like folder A button | Folder B button | Folder C button and clicking on Folder B) then rapidly trying to enter a new directory/folder 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: 97931264 vsize: 97931264 resident: 33402880 share: 12505088 rss: 33402880 rss_rlim: 4294967295 CPU usage: start_time: 1190850403 rtime: 27220 utime: 24970 stime: 2250 cutime:0 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 -1226594112 (LWP 579)] (no debugging symbols found) 0xb7673bf1 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 167382
Thread 1 (Thread -1226594112 (LWP 579))
----------- .xsession-errors (866333 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... --------------------------------------------------
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 ***