GNOME Bugzilla – Bug 531448
crash in Home Folder:
Last modified: 2008-05-04 23:03:00 UTC
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.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Snow-Apple Memory status: size: 70279168 vsize: 70279168 resident: 31920128 share: 16551936 rss: 31920128 rss_rlim: 4294967295 CPU usage: start_time: 1209937940 rtime: 271 utime: 253 stime: 18 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 0xb6b51720 (LWP 4287)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 196869
Thread 1 (Thread 0xb6b51720 (LWP 4287))
----------- .xsession-errors --------------------- ** (nautilus:3346): WARNING **: Não foi encontrada descrição para o tipo MIME "x-directory/smb-share" (o arquivo é "Imagem"), por favor notifique a lista de discussão do gnome-vfs. (bug-buddy:4268): Gtk-WARNING **: Theme directory 48x48/mimetypes of theme Snow-Apple has no size field seahorse nautilus module initialized Initializing gnome-mount extension (nautilus:4287): Gtk-WARNING **: Theme directory 48x48/mimetypes of theme Snow-Apple has no size field Aviso do gerenciador de janelas: Received a _NET_WM_MOVERESIZE message for 0x16000a8 (eduardo); these messages lack timestamps and therefore suck. ** (nautilus:4287): WARNING **: Não foi encontrada descrição para o tipo MIME "x-directory/smb-share" (o arquivo é "imagem"), por favor notifique a lista de discussão do gnome-vfs. (bug-buddy:4299): Gtk-WARNING **: Theme directory 48x48/mimetypes of theme Snow-Apple has no size field --------------------------------------------------
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 ***