GNOME Bugzilla – Bug 541062
crash in Open Folder: I am accessing windows n...
Last modified: 2008-07-01 18:02:31 UTC
Version: 2.20.0 What were you doing when the application crashed? I am accessing windows network from the debian system 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: Industrial Icon Theme: gnome Memory status: size: 99893248 vsize: 99893248 resident: 32227328 share: 16154624 rss: 32227328 rss_rlim: 4294967295 CPU usage: start_time: 1214923066 rtime: 4381 utime: 4059 stime: 322 cutime:5 cstime: 15 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 0xb6b90940 (LWP 2827)] [New Thread 0xb4356b90 (LWP 2962)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 201823
Thread 1 (Thread 0xb6b90940 (LWP 2827))
----------- .xsession-errors --------------------- CALLBACK: full-authentication!!! ** (nautilus:2827): WARNING **: Hit unhandled case 31 (Operation cancelled) in fm_report_error_loading_directory connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! --------------------------------------------------
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 ***