GNOME Bugzilla – Bug 538889
crash in Open Folder: Clicking the sub directo...
Last modified: 2008-06-18 12:19:54 UTC
Version: 2.20.0 What were you doing when the application crashed? Clicking the sub directory expansion triangle while browsing on a windows XP share. Did not have write permissions for base of share and crash occurred trying first and only subdir. Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 88604672 vsize: 88604672 resident: 22904832 share: 11350016 rss: 22904832 rss_rlim: 4294967295 CPU usage: start_time: 1213321037 rtime: 1886 utime: 1769 stime: 117 cutime:27 cstime: 4 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6bc1720 (LWP 4119)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200721
Thread 1 (Thread 0xb6bc1720 (LWP 4119))
----------- .xsession-errors (22 sec old) --------------------- connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nautilus:4119): WARNING **: Hit unhandled case 31 (Operation cancelled) in fm_report_error_loading_directory ** Message: Hit unexpected error "Access denied" while doing a file operation. --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 522534 ***