GNOME Bugzilla – Bug 530495
crash in Home Folder: Bei dem Zugriff auf eine...
Last modified: 2008-04-29 07:12:22 UTC
What were you doing when the application crashed? Bei dem Zugriff auf einen Ordner im lokalen Netzwerk kam es zum Absturz des filerollers... 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: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 84733952 vsize: 84733952 resident: 29679616 share: 16834560 rss: 29679616 rss_rlim: 4294967295 CPU usage: start_time: 1209450420 rtime: 398 utime: 358 stime: 40 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 0xb6b74720 (LWP 9043)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 196409
Thread 1 (Thread 0xb6b74720 (LWP 9043))
----------- .xsession-errors --------------------- closing gnome-mount 0.7 kbuildsycoca running... Reusing existing ksycoca kbuildsycoca running... Reusing existing ksycoca kbuildsycoca running... Reusing existing ksycoca kbuildsycoca running... Reusing existing ksycoca ** (nautilus:3035): WARNING **: Keine Beschreibung für MIME-Type »x-directory/smb-share« gefunden (Datei ist »bilder«), teilen Sie dies der gnome-vfs-Mailingliste mit. Initializing gnome-mount extension ** (nautilus:9043): WARNING **: Keine Beschreibung für MIME-Type »x-directory/smb-share« gefunden (Datei ist »bilder«), teilen Sie dies der gnome-vfs-Mailingliste mit. --------------------------------------------------
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 ***