GNOME Bugzilla – Bug 361951
Wrong URI browsing samba shares
Last modified: 2006-12-24 11:09:39 UTC
Please describe the problem: correct URI to browse a samba share is smb://NETWORK@COMPUTER/SHARE Nautilus is malforming the URI Steps to reproduce: Open Resources > Network server (name may vary, localized version here) and select your Windows network (from now on, NETWORK) - icon is white, as here http://bugzilla.gnome.org/show_bug.cgi?id=323467 Nautilus will try to open "smb:///NETWORK" (three slashes). Of course path does not exists leading to "position is not a directory" error; even typing in the location bar (ctrl+l) "smb://mshome" manually you won't still be able to browse a computer because nautilus will try to open "smb://network/computer" instead of "smb://network@computer" (slash instead of at) leading to the same error above (icon still white). typing smb://NETWORK@COMPUTER will work, but I think this is a serious usability issue which in my opinino should be fixed as soon as possible on the other hand, "mounting" the share using "Resources > Connect to server" will create a link with the correct syntax Actual results: Expected results: Does this happen every time? Other information: bug already filed in ubuntu launchpad, but probably gnome-related https://launchpad.net/distros/ubuntu/+source/nautilus/+bug/65136 SCREENSHOT here: http://librarian.launchpad.net/4735610/Schermata-1.png bug http://bugzilla.gnome.org/show_bug.cgi?id=323467 should be probably marked as a duplicate of this one. I preferred to file a new one, because I think I've found the workaround
I've found an easy fix: instead of smb:/// the uri must be just smb:// and all will work as expected; please fix this
I have to correct myself; this bug seems more random than I thought; the fix sometimes work sometimes does not; hitting refresh may work as well
I think you meant bug 356093, not bug 323467. But why not just post the workaround the the original bug? Doesn't it just make more work to mark one a dupe?
well I meant both; they look like they are part of the same issue; and sorry for the duplicate, you're right ...
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 356093 ***