connecting to samba fileshare fails if smb1(now deprecated) is not supported by the server

Bug #2016046 reported by beadon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

When connecting with Nautilus to "smb://hostname.lan/" note - not the full path to the samba share, and this is a resolvable ".lan" name handled by the local DNS server - then gvfsd fails, and doesn't send a proper error back to nautilus. This display in Nautilus is simply "Folder is empty"

Apr 12 19:31:31 semiauto dbus-daemon[729]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1635' (uid=1000 pid=381751 comm="/usr/bin/nautilus --gapplication-service" label="unconfined")
Apr 12 19:31:31 semiauto gnome-shell[1916]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
Apr 12 19:31:31 semiauto systemd[1]: Starting Hostname Service...
Apr 12 19:31:31 semiauto dbus-daemon[729]: [system] Successfully activated service 'org.freedesktop.hostname1'
Apr 12 19:31:31 semiauto systemd[1]: Started Hostname Service.
Apr 12 19:31:42 semiauto nautilus[381751]: GtkText - did not receive a focus-out event.#012If you handle this event, you must return#012GDK_EVENT_PROPAGATE so the default handler#012gets the event as well
Apr 12 19:31:42 semiauto gvfsd[171389]: smbXcli_negprot_smb1_done: No compatible protocol selected by server.
Apr 12 19:32:01 semiauto systemd[1]: systemd-hostnamed.service: Deactivated successfully.

Since the client forces the server to use NT1 protocols, and the server is configured to NOT permit this, then hte client connection fails - ungracefully.

The solution is a few parts :

1. Negotatiate up to higher levels of encryption during connection time.
2. Gracefully provide a message back to nautilus that there is an error in connecting for X or Y reason (encryption related, specific to connection to this server )

It appears that this has been a known problem now for a few years, here is a reference to it in 2021 (but in Linux Mint):

https://forums.linuxmint.com/viewtopic.php?t=363511

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gvfs 1.48.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85
Uname: Linux 5.15.0-67-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed Apr 12 19:26:46 2023
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gvfs
UpgradeStatus: Upgraded to jammy on 2022-11-22 (141 days ago)

Revision history for this message
beadon (bryant-eadon) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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