GNOME Bugzilla – Bug 544866
crash in File Browser: open folfer trought netw...
Last modified: 2008-07-27 09:58:34 UTC
Version: 2.20.0 What were you doing when the application crashed? open folfer trought network Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (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: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 83546112 vsize: 83546112 resident: 30736384 share: 16420864 rss: 30736384 rss_rlim: 4294967295 CPU usage: start_time: 1217092548 rtime: 1331 utime: 1241 stime: 90 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 0xb6b35720 (LWP 3537)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 203851
Thread 1 (Thread 0xb6b35720 (LWP 3537))
----------- .xsession-errors (203 sec old) --------------------- /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/inspiron:/tmp/.ICE-unix/3455 ** (gnome-settings-daemon:3514): WARNING **: Failed to open file '/etc/gnome/config/General.ad': No existe el fichero o el directorio Advertencia del gestor de ventanas: Ocurrió un error al leer el archivo de sesión guardado /home/davilajc/.metacity/sessions/default0.ms: Failed to open file '/home/davilajc/.metacity/sessions/defau Traceback (most recent call last): File "/usr/bin/system-config-printer-applet", line 25, in <module> from cupsutils.debug import * ImportError: No module named cupsutils.debug seahorse nautilus module initialized Initializing gnome-mount extension ** (nautilus:3537): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «compartido»), 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 ***