GNOME Bugzilla – Bug 534110
crash in File Browser:
Last modified: 2008-05-20 23:17:10 UTC
Version: 2.20.0 What were you doing when the application crashed? 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 Sat Apr 19 00:37:55 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Lush Icon Theme: Lush Memory status: size: 62824448 vsize: 62824448 resident: 24399872 share: 15880192 rss: 24399872 rss_rlim: 4294967295 CPU usage: start_time: 1211319083 rtime: 741 utime: 716 stime: 25 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 0xb6c25720 (LWP 3675)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 198263
Thread 1 (Thread 0xb6c25720 (LWP 3675))
----------- .xsession-errors (66 sec old) --------------------- ** (gnome-settings-daemon:3392): WARNING **: Error in setting vertical scroll ** (gnome-settings-daemon:3392): WARNING **: Error in setting horizontal scroll ** (gnome-settings-daemon:3392): 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/interservice/.metacity/sessions/default0.ms fallita: Failed to open file '/home/interservice/.metacity/sessions/default0.ms': No such f Initializing gnome-mount extension seahorse nautilus module initialized ** Message: <info> Si è ora connessi alla rete wireless “NETGEAR”. connection_message_func(): Callback CALLBACK: fill-authentication!!! Initializing gnome-mount extension seahorse nautilus module initialized --------------------------------------------------
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 ***