GNOME Bugzilla – Bug 544537
crash in File Browser: Opening smb share in win...
Last modified: 2008-07-24 13:14:48 UTC
Version: 2.20.0 What were you doing when the application crashed? Opening smb share in win domain Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-686 #1 SMP Fri Jul 18 17:46:56 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 79966208 vsize: 79966208 resident: 28700672 share: 16498688 rss: 28700672 rss_rlim: 4294967295 CPU usage: start_time: 1216903230 rtime: 308 utime: 289 stime: 19 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6ad2720 (LWP 6117)] [New Thread 0xb40fdb90 (LWP 6633)] (no debugging symbols found) 0xb7ef9424 in __kernel_vsyscall ()
+ Trace 203675
Thread 1 (Thread 0xb6ad2720 (LWP 6117))
----------- .xsession-errors --------------------- Resource id: 0xe6fd3a Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x69 non valido per 0x20001c5 (Twinkle - ). Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x69 non valido per 0x2001c3c (Twinkle - ). ** (nautilus:6117): WARNING **: Non è stata trovata alcuna descrizione per il tipo MIME «x-directory/smb-share» (relativa al file «home»); avvisare cortesemente la mailing list di gnome-vfs. 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 ***