GNOME Bugzilla – Bug 534249
crash in Computer: tentative d'ouverture d'...
Last modified: 2008-05-21 23:23:03 UTC
Version: 2.20.0 What were you doing when the application crashed? tentative d'ouverture d'un volume Windows NTFS distant avec Samba 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 Thu May 8 02:16:39 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: 78020608 vsize: 78020608 resident: 23416832 share: 15638528 rss: 23416832 rss_rlim: 4294967295 CPU usage: start_time: 1211401056 rtime: 339 utime: 313 stime: 26 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 0xb6bcc720 (LWP 3209)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 198340
Thread 1 (Thread 0xb6bcc720 (LWP 3209))
----------- .xsession-errors --------------------- /etc/gdm/Xsession: Beginning session setup... Setting IM through im-switch for locale=fr_FR. Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default. SESSION_MANAGER=local/debian:/tmp/.ICE-unix/3123 ** Message: another SSH agent is running at: /tmp/ssh-QFVLdX3123/agent.3123 ** (gnome-settings-daemon:3186): 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/clodoald/.metacity/sessions/default0.ms a échoué : Failed to open file '/home/clodoald/.metacity/ses seahorse nautilus module initialized Initializing gnome-mount extension 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 ***