GNOME Bugzilla – Bug 552044
crash in File Browser:
Last modified: 2008-09-13 09:44:44 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 Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Lush Icon Theme: Lush Memory status: size: 78163968 vsize: 78163968 resident: 23547904 share: 15532032 rss: 23547904 rss_rlim: 4294967295 CPU usage: start_time: 1221264479 rtime: 431 utime: 409 stime: 22 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 0xb6c00720 (LWP 4120)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 206708
Thread 1 (Thread 0xb6c00720 (LWP 4120))
----------- .xsession-errors (33 sec old) --------------------- ** (gnome-settings-daemon:4097): WARNING **: Error in setting horizontal scroll ** (gnome-settings-daemon:4097): 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”. ** (gksu:4281): WARNING **: Lock taken by pid: 4275. Exiting. /usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet warnings.warn("apt API not stable yet", FutureWarning) 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 ***