GNOME Bugzilla – Bug 535632
crash in Open Folder: Trying to open a windows...
Last modified: 2008-05-30 11:18:16 UTC
Version: 2.20.0 What were you doing when the application crashed? Trying to open a windows smb share on a windows XP machine Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-compy386 #3 SMP PREEMPT Wed May 28 12:29:56 EST 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 520536064 vsize: 520536064 resident: 37830656 share: 17571840 rss: 37830656 rss_rlim: 18446744073709551615 CPU usage: start_time: 1212109332 rtime: 222 utime: 206 stime: 16 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x7f79937067a0 (LWP 6561)] (no debugging symbols found) 0x00007f798e851edf in waitpid () from /lib/libpthread.so.0
+ Trace 199081
Thread 1 (Thread 0x7f79937067a0 (LWP 6561))
----------- .xsession-errors (6 sec old) --------------------- Initializing gnome-mount extension seahorse nautilus module initialized Initializing gnome-mount extension seahorse nautilus module initialized Initializing gnome-mount extension 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!!! ** (nautilus:6561): WARNING **: Hit unhandled case 31 (Operation cancelled) in fm_report_error_loading_directory --------------------------------------------------
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 ***