GNOME Bugzilla – Bug 530639
crash in File Browser:
Last modified: 2008-04-30 08:56:40 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-3-k7 #1 SMP Sun Feb 10 21:04:14 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: MacOS-X Icon Theme: Mac4Lin_Icons_v0.3a Memory status: size: 85962752 vsize: 85962752 resident: 29523968 share: 17276928 rss: 29523968 rss_rlim: 4294967295 CPU usage: start_time: 1209508254 rtime: 221 utime: 209 stime: 12 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 0xb6bc4720 (LWP 3399)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 196483
Thread 1 (Thread 0xb6bc4720 (LWP 3399))
----------- .xsession-errors --------------------- compiz.real (core) - Error: no 'text' plugin with ABI version '20080421' loaded compiz.real (shift) - Warn: No compatible text plugin loaded. (gnome-panel:3130): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -20 and height 24 connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:3131): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «pokemon»), avise a la lista de correo de gnome-vfs. Initializing gnome-mount extension seahorse nautilus module initialized Cutting log (size: 100389, max: 100000) ** (nautilus:3399): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «pokemon»), avise a la lista de correo de 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 ***