GNOME Bugzilla – Bug 534250
crash in Home Folder: doppelklick auf einem or...
Last modified: 2008-05-21 23:22:57 UTC
What were you doing when the application crashed? doppelklick auf einem ordner Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-3-486 #1 Mon Nov 12 07:53:08 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 85704704 vsize: 85704704 resident: 22921216 share: 15593472 rss: 22921216 rss_rlim: 4294967295 CPU usage: start_time: 1211401815 rtime: 575 utime: 526 stime: 49 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 0xb6c52720 (LWP 3057)] (no debugging symbols found) 0xb7691f91 in waitpid () from /lib/libpthread.so.0
+ Trace 198341
Thread 1 (Thread 0xb6c52720 (LWP 3057))
----------- .xsession-errors (6 sec old) --------------------- ** (gnome-settings-daemon:3036): WARNING **: Datei »/etc/gnome/config/General.ad« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden Fenstermanager-Warnung:Gespeicherte Sitzungsdatei /home/timor/.metacity/sessions/default0.ms konnte nicht gelesen werden: Datei »/home/timor/.metacity/sessions/default0.ms« konnte nicht geöffnet we seahorse nautilus module initialized Initializing gnome-mount extension 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!!! --------------------------------------------------
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 ***