GNOME Bugzilla – Bug 541041
crash in Open Folder: Browsing ssh connected s...
Last modified: 2008-07-01 10:50:30 UTC
Version: 2.20.0 What were you doing when the application crashed? Browsing ssh connected samba share from server Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24 #1 SMP Sat Jun 28 18:02:54 CEST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: oxy-gnome Memory status: size: 98607104 vsize: 98607104 resident: 28327936 share: 19787776 rss: 28327936 rss_rlim: 4294967295 CPU usage: start_time: 1214896929 rtime: 1382 utime: 1229 stime: 153 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 0xb6b7f940 (LWP 3908)] [New Thread 0xb3b4eb90 (LWP 19210)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 201812
Thread 1 (Thread 0xb6b7f940 (LWP 3908))
----------- .xsession-errors (163 sec old) --------------------- You have to set 'SHMConfig' 'true' in xorg.conf or XFree86.conf to use GSynaptics Conky: desktop window (13b) is root window Conky: window type - normal Conky: drawing to created window (1400001) Conky: drawing to double buffer seahorse nautilus module initialized Initializing gnome-mount extension kbuildsycoca running... DCOP Cleaning up dead connections. Unable to open desktop file /home/mkocka/Desktop/iceweasel.desktop for panel launcher: No such file or directory Unable to open desktop file /home/mkocka/Desktop/gnome-terminal.desktop for panel launcher: No such file or directory connection_message_func(): Callback CALLBACK: fill-authentication!!! kbuildsycoca running... Reusing existing ksycoca --------------------------------------------------
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 ***