GNOME Bugzilla – Bug 539568
crash in Home Folder: I tried to connect to a ...
Last modified: 2008-06-22 12:14:41 UTC
What were you doing when the application crashed? I tried to connect to a Samba share on a NAS server I set up on my network, and to open a directory there. Usernames are different ("test" on local machine, "axel" on remote server). 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: 85508096 vsize: 85508096 resident: 29581312 share: 17121280 rss: 29581312 rss_rlim: 4294967295 CPU usage: start_time: 1214128437 rtime: 511 utime: 474 stime: 37 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 0xb6b5d720 (LWP 3651)] [New Thread 0xb54ffb90 (LWP 3670)] (no debugging symbols found) 0xb72a7f91 in waitpid () from /lib/libpthread.so.0
+ Trace 201065
Thread 1 (Thread 0xb6b5d720 (LWP 3651))
----------- .xsession-errors (61 sec old) --------------------- connection_message_func(): Callback CALLBACK: save-authentication!!! Initializing nautilus-open-terminal extension seahorse nautilus module initialized Initializing gnome-mount extension ** (nautilus:3651): WARNING **: Keine Beschreibung für MIME-Type »x-directory/smb-share« gefunden (Datei ist »familie«), teilen Sie dies der gnome-vfs-Mailingliste mit. 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: save-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 ***