Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access based share enumeration = yes'

Bug #1828606 reported by Sean McBride
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gvfs
New
Unknown
gvfs (Ubuntu)
Low
Unassigned

Bug Description

From Ubuntu 18.04's GUI, if I open the "Files" app and go to "Other Locations", I see my samba/SMB server. If I double click it, it then lists *some* of my shares. Specifically, it lists those where I didn't use Samba's 'access based share enumeration = yes'[1] (which allows some shares to be made completely invisible to some users). Note that Ubuntu has *not* yet asked me to authenticate, so it makes sense that I shouldn't yet be able to see shares I'm not entitled to.

The bug is: even after I authenticate (and let it remember my password), then go back to Other Locations>MyServer, it *still* doesn't show the other shares. In fact, I can't find *any* way to see the other shares.

Contrast this with macOS Finder. If I navigate to MyServer in the share list, it doesn't show *any* shares until I authenticate, then it shows *all* shares that the user has access to (and none of the shares the user doesn't have access to).

Ubuntu could either:
 - adopt macOS Finder behaviour and get authentication first, or
 - update the share list after authentication is performed.

Its current behaviour makes some shares totally inaccessible (the crux of the bug).

I doubt it matters, but my server is: FreeNAS 11.2-U4 (current newest) using ZFS, running samba 4.9.6. Other users on the FreeNAS forum see the same behaviour[2], so it's not particular to my setup.

[1] https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html
[2] https://www.ixsystems.com/community/threads/accessing-smb-shares-from-ubuntu-18-04-doesnt-show-all-shares-in-gui.75961/

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1828606/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Sean McBride (seanmcb) wrote :

OK, I used "ubuntu-bug -w" and the package seems to be "nautilus 1:3.26.4-0~ubuntu18.04.4"

affects: ubuntu → nautilus (Ubuntu)
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, the issue looks like an upsream one though, maybe you could report it to them on https://gitlab.gnome.org/GNOME/gvfs/issues ?

affects: nautilus (Ubuntu) → gvfs (Ubuntu)
Changed in gvfs (Ubuntu):
importance: Undecided → Low
Revision history for this message
Sean McBride (seanmcb) wrote :
Changed in gvfs:
status: Unknown → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks

Changed in gvfs (Ubuntu):
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.