GNOME Bugzilla – Bug 544341
crash in Open Folder: Opening SAMBA share on l...
Last modified: 2008-07-23 17:43:45 UTC
Version: 2.20.0 What were you doing when the application crashed? Opening SAMBA share on local Windows computer Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 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: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Nuvola Memory status: size: 83288064 vsize: 83288064 resident: 29487104 share: 16556032 rss: 29487104 rss_rlim: 4294967295 CPU usage: start_time: 1216817520 rtime: 349 utime: 319 stime: 30 cutime:6 cstime: 1 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 0xb6c33720 (LWP 3912)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 203575
Thread 1 (Thread 0xb6c33720 (LWP 3912))
----------- .xsession-errors --------------------- ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) sh: acroread: command not found connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:3912): WARNING **: No description found for mime type "x-directory/smb-share" (file is "SharedDocs"), please tell the gnome-vfs mailing list. --------------------------------------------------
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 ***