GNOME Bugzilla – Bug 541082
crash in Open Folder: connecting to a share on...
Last modified: 2008-07-01 18:06:14 UTC
Version: 2.20.0 What were you doing when the application crashed? connecting to a share on a server on the other end of a VPN connection. I can see the folder on my desktop, but every time i access it get this error Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 377290752 vsize: 377290752 resident: 30740480 share: 17219584 rss: 30740480 rss_rlim: 18446744073709551615 CPU usage: start_time: 1214920214 rtime: 286 utime: 260 stime: 26 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2b7217247220 (LWP 7361)] (no debugging symbols found) 0x00002b7210216edf in waitpid () from /lib/libpthread.so.0
+ Trace 201834
Thread 1 (Thread 0x2b7217247220 (LWP 7361))
----------- .xsession-errors (103 sec old) --------------------- ** 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) connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! Initializing gnome-mount extension seahorse nautilus module initialized Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:7361): WARNING **: No description found for mime type "x-directory/smb-share" (file is "bob"), 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 ***