I get this on un-secured shares. I am puzzled that samba has been updated today (August 18th) without any apparent change in the situation. It seems that this is not a samba bug, at any rate.
Is this a gvfs bug? Is it a seahorse bug (as suggested above by fishor)? Or is it something else? It is certainly, for me at least, unique to Intrepid - the same machines connect just fine using hardy. zoidberg - that's right - you need to run gvfs-mount smb://server/share to get the folder to appear in ~/.gvfs Once it is there you can cd into it and see, and copy, files. It still won't open using nautilus, though there is an icon on the desktop. -- Intrepid Ibex: Cannot access samba share "Unable to mount location" https://bugs.launchpad.net/bugs/241139 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
