GNOME Bugzilla – Bug 539243
crash in Computer:
Last modified: 2008-06-20 10:19:06 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-486 #1 Thu May 8 01:29:10 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 76148736 vsize: 76148736 resident: 24559616 share: 15028224 rss: 24559616 rss_rlim: 4294967295 CPU usage: start_time: 1213952689 rtime: 274 utime: 253 stime: 21 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 0xb6be7720 (LWP 3327)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200910
Thread 1 (Thread 0xb6be7720 (LWP 3327))
----------- .xsession-errors (14 sec old) --------------------- SESSION_MANAGER=local/EusLib:/tmp/.ICE-unix/3239 ** Message: another SSH agent is running at: /tmp/ssh-gSKNVY3239/agent.3239 ** (gnome-settings-daemon:3307): WARNING **: Failed to open file '/etc/gnome/config/General.ad': Aucun fichier ou répertoire de ce type Avertissement du gestionnaire de fenêtres : La lecture du fichier de session enregistré /home/euslib/.metacity/sessions/default0.ms a échoué : Failed to open file '/home/euslib/.metacity/session ** (x-session-manager:3239): WARNING **: Host name lookup failure on localhost. seahorse nautilus module initialized Initializing gnome-mount extension ** (nautilus:3327): WARNING **: Hit unhandled case 38 (Service non disponible) in fm_report_error_loading_directory connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-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 ***