GNOME Bugzilla – Bug 535691
crash in File Browser: I was opening a windows ...
Last modified: 2008-05-30 09:47:57 UTC
Version: 2.20.0 What were you doing when the application crashed? I was opening a windows shared folder Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-gio #1 SMP Tue Feb 19 19:27:18 CET 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Noia Memory status: size: 154615808 vsize: 154615808 resident: 29966336 share: 18812928 rss: 29966336 rss_rlim: 4294967295 CPU usage: start_time: 1212138068 rtime: 205 utime: 196 stime: 9 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 0xb6bff720 (LWP 4409)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 199123
Thread 1 (Thread 0xb6bff720 (LWP 4409))
----------- .xsession-errors --------------------- Initializing gnome-mount extension xrdb: "*Label.background" on line 220 overrides entry on line 150 xrdb: "*Text.background" on line 226 overrides entry on line 191 xrdb: "*Label.foreground" on line 232 overrides entry on line 151 xrdb: "*Text.foreground" on line 238 overrides entry on line 192 seahorse nautilus module initialized connection_message_func(): Callback CALLBACK: fill-authentication!!! Initializing gnome-mount extension seahorse nautilus module initialized *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. ** (nautilus:4409): WARNING **: Non è stata trovata alcuna descrizione per il tipo MIME «x-directory/smb-share» (relativa al file «Tutti»); avvisare cortesemente la mailing list di gnome-vfs. --------------------------------------------------
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 ***