gio - cifs mount smb not possible "Location is not mountable"

Thank you for your bug report, could report it upstream as well on https://gitlab.gnome.org/GNOME/glib ?

Opened

[https://gitlab.gnome.org/GNOME/glib/-/issues/2090](https://gitlab.gnome.org/GNOME/glib/-/issues/2090)

as requested, with additional comments that it works in Ubuntu 19.10 up to kernel 5.6.3 (I use both Ubuntu and newest linux kernel).

Checked the (working) Ubuntu 19.04 package:

$ apt-cache policy libglib2.0-bin
libglib2.0-bin:
  Installed: 2.62.4-1~ubuntu19.10.2
  Candidate: 2.62.4-1~ubuntu19.10.2
  Version table:
 *** 2.62.4-1~ubuntu19.10.2 500
        500 http://de.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages
        100 /var/lib/dpkg/status
     2.62.1-1 500
        500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

It seems, that the package is newer at Ubuntu 19.10???

$ lsb_release -rd
Description: Ubuntu 19.10
Release: 19.10

Sorry, should put my reading glasses on, 20:04beta's version 2.64.1-1 is newer than 19.10's version 2.62.4-1.

I wished, I could correct messages here, unless someone else is on the top ;-)

Thanks!

Could you get a debug log from gvfs following the steps in https://wiki.gnome.org/Projects/gvfs/debugging ?

Comments on
https://gitlab.gnome.org/GNOME/glib/-/issues/2090
showed, that there is this file `/usr/share/gvfs/mounts/smb.mount`
in Ubuntu 19.10, which is not there in Ubuntu 20.04 beta.

Inside of this file, there was a reference to the file
`/usr/lib/gvfs/gvfsd-smb`. Also a file `/usr/libexec/gvfsd-smb`
cannot be found.

I did not get any debug logs, I think because the prerequisites
are missing.

I found out, that I had to install the package `gvfs-backends` to get `gvfsd-smb`:

`$ find /usr -name 'gvfsd-smb' -exec ls -l '{}' \; 2>/dev/null`
`-rwxr-xr-x 1 root root 59704 Mär 11 17:23 /usr/libexec/gvfsd-smb`
`lrwxrwxrwx 1 root root 23 Mär 11 17:23 /usr/lib/gvfs/gvfsd-smb -> ../../libexec/gvfsd-smb`

After installing it, I got:

`$ gio mount smb://192.168.178.1/PathName`
`gio: smb://192.168.178.1/PathName/: Failed to mount Windows share: Software caused connection abort`
`gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse` `(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)`

I will reboot the machine to look if there is another result afterwards.

After installing package `gvfs-backends` and reboot, I got the follow error:

`$ gio mount smb://192.168.178.1/PathName`
`gio: smb://192.168.178.1/PathName/: Failed to mount Windows share: Software caused connection abort`
`gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)`

The debug logs look like the following:

`smb: g_vfs_backend_smb_init: default workgroup = 'NULL'`
`smb: Added new job source 0x55e4166bc080 (GVfsBackendSmb)`
`smb: Queued new job 0x55e4166bd940 (GVfsJobMount)`
`smb: do_mount - URI = smb://192.168.178.1/PathName`
`smb: do_mount - try #0 `
`smb: auth_callback - kerberos pass`
`smb: auth_callback - out: last_user = 'UserName', last_domain = 'WORKGROUP'`
`smb: do_mount - [smb://192.168.178.1/fritz7490; 0] res = -1, cancelled = 0, errno = [103] 'Software caused connection abort' `
`smb: do_mount - (errno != EPERM && errno != EACCES), cancelled = 0, breaking`
`smb: send_reply(0x55e4166bd940), failed=1 (Failed to mount Windows share: Software caused connection abort)`

The question is now, if a new bug should be opened, because of the reason is different and the description should be changed.

Weird that you didn't have gvfs-backends installed, it should be there on a default installation. How did you install your system?

The new issue seems worth debugging, it's fine to repurpose the bug here, maybe ask upstream what they prefer on gitlab though?

The error is similar to https://gitlab.gnome.org/GNOME/glib/-/issues/2090 so maybe reusing that one makes sense

I updated my Ubuntu 19.10 laptop with "sudo update-manager -d" to 20.04 beta. I always mount a small local drive in my network, because I have there my private git repo, which is then easily available to my laptops and to may raspberries.

I did not delete the package on my own, but there were some hickups during installation.

Remark: In Ubuntu 19.04, if the user/domain/password is not piped, `gio mount` requests
the `user/domain/password`:

`$ gio mount smb://192.168.178.1/Fritz7490`
`Password required for share fritz7490 on 192.168.178.1
`User [SessionUserName]: NewUserIfDifferent
`Domain [WORKGROUP]: NewDomainIfDifferent
`Password: PassWord

Again: gvfs-backends is installed (it was removed without my knowledge during the update from Ubuntu 19.10 to 20.04 beta). Perhaps you should not install a beta version on a productive
system ;-)

When I want to mount the drive as in Ubuntu 19.10, I get:

$ gio mount smb://192.168.178.1/sharename
Password required for share sharename on 192.168.178.1
User [SessionUserName]: NewUserIfDifferent
Domain [WORKGROUP]: NewDomainIfDifferent
Password: PassWord

In Ubuntu 20.04 beta I still get (after manual installation of `gvfs-backends`, which was removed during the update from 19.10 to the beta

$ gio mount smb://192.168.178.1/sharename
gio: smb://192.168.178.1/sharename/: Failed to mount Windows share: Software caused connection abort

So, Ubuntu 20.04 does not request to enter the user, domain/workgroup, password at all.

Remark: I could mount the drive via "sudo mount -t cifs ..." using the "vers=1.0" switch in all Ubuntu versions, also in 20.04 beta.

Should I open a new bug? The error and it's error message is now different. That the beta installer did remove the package `gvfs-backends`, I will not test again, because I have only productive 19.10 systems. I had several small glitches during the installation, so also the repositories were grilled away but one - I am doing this since 2008 at least twice a year on at least 2 laptops, mostly I start with the beta version.

Thanks Dirk, a new report would probably better to avoid confusion.

Can you see the content of that same mount doing
$ smbclient //192.168.178.1/sharename ?
if it fails could you add --debuglevel=10 and attach the log to the report? (and ideally reporting upstream gvfs would make sense)

I just saw, that it is not Ubuntu 20.04 beta, it is the real Ubuntu 20.04 now.

The release is next week, the title is just being updated in preparation, it doesn't matter really

I dream of a world where after next lts upgrade my samba shares are still mountable!
This isn't the first time, you know

Looks like the secondary problem is here is the same as https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1880305

is anyone still having that issue?