GNOME Bugzilla – Bug 537621
crash in Computer: Mapping to networkdrive ...
Last modified: 2008-06-10 19:08:35 UTC
Version: 2.20.0 What were you doing when the application crashed? Mapping to networkdrive Buffalo Linkstation. Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-486 #1 Thu May 8 01:29:10 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: 65626112 vsize: 65626112 resident: 27942912 share: 16506880 rss: 27942912 rss_rlim: 4294967295 CPU usage: start_time: 1213113036 rtime: 314 utime: 287 stime: 27 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6c22720 (LWP 3481)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200044
Thread 1 (Thread 0xb6c22720 (LWP 3481))
----------- .xsession-errors (73 sec old) --------------------- 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: save-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! seahorse nautilus module initialized Initializing gnome-mount extension seahorse nautilus module initialized Initializing gnome-mount extension --------------------------------------------------
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 ***