GNOME Bugzilla – Bug 536955
crash in Computer: trying to connect to a w...
Last modified: 2008-06-06 12:37:12 UTC
Version: 2.20.0 What were you doing when the application crashed? trying to connect to a windows remote computer using samba Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (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: 65323008 vsize: 65323008 resident: 27213824 share: 15613952 rss: 27213824 rss_rlim: 4294967295 CPU usage: start_time: 1212745011 rtime: 315 utime: 299 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6c28720 (LWP 6115)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 199713
Thread 1 (Thread 0xb6c28720 (LWP 6115))
----------- .xsession-errors (17 sec old) --------------------- (synaptic:3523): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed 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!!! 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 ***