GNOME Bugzilla – Bug 541205
crash in File Browser: trying to connect to a r...
Last modified: 2008-07-02 12:20:42 UTC
Version: 2.20.0 What were you doing when the application crashed? trying to connect to a remote samba server share Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Gorilla Icon Theme: Gorilla Memory status: size: 76025856 vsize: 76025856 resident: 24092672 share: 15044608 rss: 24092672 rss_rlim: 4294967295 CPU usage: start_time: 1214991653 rtime: 335 utime: 314 stime: 21 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 0xb6bc6940 (LWP 2847)] (no debugging symbols found) 0xb732df91 in waitpid () from /lib/libpthread.so.0
+ Trace 201891
Thread 1 (Thread 0xb6bc6940 (LWP 2847))
----------- .xsession-errors --------------------- ** (gnome-settings-daemon:2824): WARNING **: Failed to open file '/etc/gnome/config/General.ad': No such file or directory Avviso del window manager: Lettura del file della sessione /home/stefano/.metacity/sessions/default0.ms fallita: Failed to open file '/home/stefano/.metacity/sessions/default0.ms': No such file or dir seahorse nautilus module initialized Initializing gnome-mount extension system-config-printer-applet: failed to start NewPrinterNotification service 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!!! 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 ***