GNOME Bugzilla – Bug 538115
crash in File Browser: navigavo nella lan
Last modified: 2008-06-13 08:49:29 UTC
Version: 2.20.0 What were you doing when the application crashed? navigavo nella lan Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (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: LeopardX_V3.1 Memory status: size: 73977856 vsize: 73977856 resident: 26861568 share: 15265792 rss: 26861568 rss_rlim: 4294967295 CPU usage: start_time: 1213346724 rtime: 151 utime: 137 stime: 14 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 0xb6b7a720 (LWP 14577)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200304
Thread 1 (Thread 0xb6b7a720 (LWP 14577))
----------- .xsession-errors (21 sec old) --------------------- /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/portatile:/tmp/.ICE-unix/3288 ** Message: another SSH agent is running at: /tmp/ssh-aCZKlb3288/agent.3288 ** (gnome-settings-daemon:3348): WARNING **: Failed to open file '/etc/gnome/config/General.ad': No such file or directory Avviso del window manager: Lettura del file della sessione /home/mauro/.metacity/sessions/default0.ms fallita: Failed to open file '/home/mauro/.metacity/sessions/default0.ms': No such file or directo seahorse nautilus module initialized Initializing gnome-mount extension Not a regular file: / Initialize default_framework extension. Initialize gtk_edit_element extension. Initialize gtkmoz_browser_element extension. Initialize gst_mediaplayer_element extension. Initialize gtk_system_framework extension. Initialize gst_audio_framework extension. Demarshal failed. Type dismatch, message type: --------------------------------------------------
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 ***