GNOME Bugzilla – Bug 543188
crash in Computer: I was opening a smb view...
Last modified: 2008-07-16 07:53:50 UTC
Version: 2.20.0 What were you doing when the application crashed? I was opening a smb view to a win xp host Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 445231104 vsize: 445231104 resident: 30187520 share: 16429056 rss: 30187520 rss_rlim: 18446744073709551615 CPU usage: start_time: 1216157612 rtime: 60 utime: 54 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2b3016d5eb60 (LWP 3481)] (no debugging symbols found) 0x00002b300f8efedf in waitpid () from /lib/libpthread.so.0
+ Trace 202940
Thread 1 (Thread 0x2b3016d5eb60 (LWP 3481))
----------- .xsession-errors (25 sec old) --------------------- /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/puhti:/tmp/.ICE-unix/3395 ** Message: another SSH agent is running at: /tmp/ssh-CWPARD3395/agent.3395 ** (gnome-settings-daemon:3456): WARNING **: Failed to open file '/etc/gnome/config/General.ad': Tiedostoa tai hakemistoa ei ole Ikkunointiohjelman varoitus:Tallennetun istuntotiedoston "/home/mika/.metacity/sessions/default0.ms" luku epäonnistui: Failed to open file '/home/mika/.metacity/sessions/default0.ms': Tiedostoa tai h Initializing gnome-mount extension seahorse nautilus module initialized 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 ***