Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#66577 - [samba] incorrectly reported stat info breaking gvfs

Attached to Project: Arch Linux
Opened by Maciek Borzecki (bboozzoo) - Thursday, 07 May 2020, 12:28 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 17 August 2020, 09:24 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jelle van der Waa (jelly)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

Issue originally reported to gvfs https://gitlab.gnome.org/GNOME/gvfs/-/issues/470 (includes full logs and details)

Opening files via smbclient works, but gvfs incorrectly reports files in smb shares as directories.

Additional info:
* package versions:
gvfs-smb 1.44.1-3
gvfs 1.44.1-3
smbclient 4.12.2-3

The bug was also present in Fedora. As a fix they have cherry-picked this commit from upstream: https://github.com/samba-team/samba/commit/39c910fd9cba3caf7414274b678b9eee33d7e20b

Steps to reproduce:
- use gvfs to mount a share
- try to open a file
- smb returns with ET_STATUS_OBJECT_PATH_NOT_FOUND, or ENOENT once translated to corresponding errno
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Monday, 17 August 2020, 09:24 GMT
Reason for closing:  Fixed
Additional comments about closing:  4.12.3-1
Comment by Andrea Cisternino (acisternino) - Sunday, 10 May 2020, 08:06 GMT
Same error in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1872476
Comment by Martin Miller (martinm1000) - Thursday, 21 May 2020, 16:06 GMT
I just want to add that this also prevent deleting files and not just viewing them.
Comment by Maciek Borzecki (bboozzoo) - Saturday, 23 May 2020, 10:36 GMT
I think this can be marked as fixed now. With an update to 4.12.3-1 things are working well again.
Comment by Martin Miller (martinm1000) - Saturday, 23 May 2020, 20:25 GMT
Yes, thank you it does work after updating !

Loading...