GNOME Bugzilla – Bug 534197
crash in Computer: Ouverture d'un dossier s...
Last modified: 2008-05-21 23:27:49 UTC
Version: 2.20.0 What were you doing when the application crashed? Ouverture d'un dossier sur un partage windows Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-486 #1 Fri Apr 18 23:53:06 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: 87576576 vsize: 87576576 resident: 23773184 share: 15654912 rss: 23773184 rss_rlim: 4294967295 CPU usage: start_time: 1211372010 rtime: 590 utime: 561 stime: 29 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 0xb6bc2720 (LWP 10123)] (no debugging symbols found) 0xb7601f91 in waitpid () from /lib/libpthread.so.0
+ Trace 198309
Thread 1 (Thread 0xb6bc2720 (LWP 10123))
----------- .xsession-errors (16 sec old) --------------------- ** (gnome-settings-daemon:10100): WARNING **: Failed to open file '/etc/gnome/config/General.ad': Aucun fichier ou répertoire de ce type Avertissement du gestionnaire de fenêtres : Initializing gnome-mount extension La lecture du fichier de session enregistré /home/yann/.metacity/sessions/default0.ms a échoué : Failed to open file '/home/yann/.metacity/sessions/default0.ms': Aucun fichier ou répertoire de ce seahorse nautilus module initialized (gnome-panel:10119): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24 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: full-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 ***