GNOME Bugzilla – Bug 534531
crash in File Browser: Abriendo una carpeta
Last modified: 2008-05-23 23:21:28 UTC
Version: 2.20.0 What were you doing when the application crashed? Abriendo una carpeta Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-686 #1 SMP Wed May 14 16:42:03 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: 82436096 vsize: 82436096 resident: 21458944 share: 13455360 rss: 21458944 rss_rlim: 4294967295 CPU usage: start_time: 1211561214 rtime: 2562 utime: 2238 stime: 324 cutime:8 cstime: 6 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 0xb6bcf720 (LWP 3068)] (no debugging symbols found) 0xb7f7e424 in __kernel_vsyscall ()
+ Trace 198480
Thread 1 (Thread 0xb6bcf720 (LWP 3068))
----------- .xsession-errors (19 sec old) --------------------- treeiter = self.model.get_iter( path ) ValueError: invalid tree path Traceback (most recent call last): File "/usr/share/wine-doors/src/ui.py", line 663, in fade_cell treeiter = self.model.get_iter( path ) ValueError: invalid tree path amidi-plug(i_backend.c:i_backend_unload:164): unloading backend 'alsa' amidi-plug(i_backend.c:i_backend_unload:167): backend 'alsa' unloaded LASTFM: (cleanup) Cleanup finished connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:3068): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «D»), 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 ***