GNOME Bugzilla – Bug 530375
crash in Home Folder:
Last modified: 2008-04-28 18:06:01 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: Lush Icon Theme: Lush Memory status: size: 72904704 vsize: 72904704 resident: 26046464 share: 16392192 rss: 26046464 rss_rlim: 4294967295 CPU usage: start_time: 1209394517 rtime: 293 utime: 277 stime: 16 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 0xb6bf3720 (LWP 3905)] [New Thread 0xb4beeb90 (LWP 3931)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 196340
Thread 1 (Thread 0xb6bf3720 (LWP 3905))
----------- .xsession-errors (16 sec old) --------------------- Fenstermanager-Warnung:Gespeicherte Sitzungsdatei /home/schackenberg/.metacity/sessions/default0.ms konnte nicht gelesen werden: Failed to open file '/home/schackenberg/.metacity/sessions/default0.ms' Initializing gnome-mount extension seahorse nautilus module initialized connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nautilus:3751): WARNING **: Keine Beschreibung für MIME-Type »x-directory/smb-share« gefunden (Datei ist »backup_pool«), teilen Sie dies der gnome-vfs-Mailingliste mit. Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:3905): WARNING **: Keine Beschreibung für MIME-Type »x-directory/smb-share« gefunden (Datei ist »backup_pool«), 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 ***