GNOME Bugzilla – Bug 531938
crash in File Browser:
Last modified: 2008-05-07 14:08:52 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: Wasp Icon Theme: Wasp Memory status: size: 77774848 vsize: 77774848 resident: 22102016 share: 15106048 rss: 22102016 rss_rlim: 4294967295 CPU usage: start_time: 1210168032 rtime: 114 utime: 101 stime: 13 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 0xb6bc3720 (LWP 3506)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 197124
Thread 1 (Thread 0xb6bc3720 (LWP 3506))
----------- .xsession-errors (12 sec old) --------------------- ** (gnome-settings-daemon:3482): WARNING **: Error in setting vertical scroll ** (gnome-settings-daemon:3482): WARNING **: Error in setting horizontal scroll xrdb: "*Label.background" on line 220 overrides entry on line 150 xrdb: "*Text.background" on line 226 overrides entry on line 191 xrdb: "*Label.foreground" on line 232 overrides entry on line 151 xrdb: "*Text.foreground" on line 238 overrides entry on line 192 Avviso del window manager: Lettura del file della sessione /home/stefano/.metacity/sessions/default0.ms fallita: Failed to open file '/home/stefano/.metacity/sessions/default0.ms': No such file or dir 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 ***