GNOME Bugzilla – Bug 542913
crash in Open Folder: Viewing smb shared folde...
Last modified: 2008-07-14 15:06:47 UTC
Version: 2.20.0 What were you doing when the application crashed? Viewing smb shared folder containing a Makefile.am file leads to file browser crash. 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: Mist Icon Theme: Mist Memory status: size: 59387904 vsize: 59387904 resident: 25219072 share: 15028224 rss: 25219072 rss_rlim: 4294967295 CPU usage: start_time: 1216037967 rtime: 343 utime: 167 stime: 176 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 0xb6acb720 (LWP 1107)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 202782
Thread 1 (Thread 0xb6acb720 (LWP 1107))
----------- .xsession-errors (112 sec old) --------------------- Initializing gnome-mount extension seahorse nautilus module initialized Initializing gnome-mount extension seahorse nautilus module initialized Initializing gnome-mount extension seahorse nautilus module initialized Initializing gnome-mount extension seahorse nautilus module initialized Initializing gnome-mount extension seahorse nautilus module initialized Initializing gnome-mount extension seahorse nautilus module initialized Initializing gnome-mount extension seahorse nautilus module initialized Initializing gnome-mount extension --------------------------------------------------
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 ***