GNOME Bugzilla – Bug 541241
crash in Home Folder: die Benutzerkennung für ...
Last modified: 2008-07-02 13:24:16 UTC
What were you doing when the application crashed? die Benutzerkennung für das Netzwerk eingegeben (Bunutzername,Domäne,Kennwort) Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24.7 #1 SMP PREEMPT Fri Jun 6 12:28:22 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Amaranth Icon Theme: Amaranth Memory status: size: 458076160 vsize: 458076160 resident: 32784384 share: 17711104 rss: 32784384 rss_rlim: 18446744073709551615 CPU usage: start_time: 1215011022 rtime: 133 utime: 122 stime: 11 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2ac39faa3240 (LWP 2931)] [New Thread 0x40800950 (LWP 2958)] (no debugging symbols found) 0x00002ac398f99edf in waitpid () from /lib/libpthread.so.0
+ Trace 201908
Thread 1 (Thread 0x2ac39faa3240 (LWP 2931))
----------- .xsession-errors --------------------- ** (nautilus:2740): WARNING **: Keine Beschreibung für MIME-Type »x-directory/smb-share« gefunden (Datei ist »Data«), teilen Sie dies der gnome-vfs-Mailingliste mit. connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:2931): WARNING **: Keine Beschreibung für MIME-Type »x-directory/smb-share« gefunden (Datei ist »Data«), 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 ***