GNOME Bugzilla – Bug 374889
crash in Computer: on "Network" folder, I d...
Last modified: 2006-11-14 09:22:52 UTC
Version: 2.16.2 What were you doing when the application crashed? on "Network" folder, I double clicked a folder that said "root's files on localhost.localdomain" Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:34:46 EST 2006 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors --------------------- closing closing Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x1611b88 (Network); these messages lack timestamps and therefore suck. ** (nautilus:3166): CRITICAL **: nautilus_directory_ref: assertion `NAUTILUS_IS_DIRECTORY (directory)' failed ** (bug-buddy:7859): WARNING **: Couldn't load icon for Open Folder Initializing nautilus-flac-converter extension Initializing nautilus-search-tool extension Initializing nautilus-image-converter extension Initializing nautilus-open-terminal extension ** (nautilus:7875): CRITICAL **: nautilus_directory_ref: assertion `NAUTILUS_IS_DIRECTORY (directory)' failed ** (bug-buddy:7912): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 492351488 vsize: 492351488 resident: 29683712 share: 13754368 rss: 29683712 rss_rlim: -1 CPU usage: start_time: 1163455942 rtime: 279 utime: 262 stime: 17 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496396272 (LWP 7875)] (no debugging symbols found) 0x0000003a5e80d96f in waitpid () from /lib64/libpthread.so.0
+ Trace 86201
Thread 1 (Thread 46912496396272 (LWP 7875))
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 372471 ***
*** This bug has been marked as a duplicate of 373697 ***