FS#76158 - Permission denied calling SMBC_getatr when file not exists
Attached to Project:
Arch Linux
Opened by Stefan Mayer-Popp (smp) - Monday, 10 October 2022, 08:52 GMT
Last edited by Toolybird (Toolybird) - Monday, 10 October 2022, 21:00 GMT
Opened by Stefan Mayer-Popp (smp) - Monday, 10 October 2022, 08:52 GMT
Last edited by Toolybird (Toolybird) - Monday, 10 October 2022, 21:00 GMT
|
Details
Description:
Creating new folders or files (partially) via samba is currently not possible with gvfs via Nautilius as it returns `permission denied` when calling `SMBC_getatr` when a file does not exists. The error is already reported to several upstream bug trackers by Víctor Daniel Martínez O. Additional info: * package version(s) samba samba-4.17.0-1 gvfs-smb 1.50.2-1 smblcient 4.17.0-1 * config and/or log files etc. ``` smbc_stat(smb://nas/storage/test.txt) SMBC_getatr: sending qpathinfo map_errno_from_nt_status: 32 bit codes: code=c0000022 cli_status_to_errno: 0xc0000022 -> 13 smb: send_reply(0x7f0b10002400), failed=1 (Permission denied) ``` * link to upstream bug report, if any Samba: https://bugzilla.samba.org/show_bug.cgi?id=15195 Red Hat Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2127301 Related gvfs issues: https://gitlab.gnome.org/GNOME/gvfs/-/issues/649 https://gitlab.gnome.org/GNOME/gvfs/-/issues/651 Steps to reproduce: 1. Connect to any Samba share via Files (Nautilus) and try to move/create folders or files 2. An error should appear with `permission denied` |
This task depends upon
Closed by Toolybird (Toolybird)
Monday, 10 October 2022, 21:00 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#76087
Monday, 10 October 2022, 21:00 GMT
Reason for closing: Duplicate
Additional comments about closing:
Comment by
Stefan Mayer-Popp (smp) - Monday,
10 October 2022, 08:57 GMT
In this comment
https://bugzilla.samba.org/show_bug.cgi?id=15195#c2
a patch (
https://attachments.samba.org/attachment.cgi?id=17546
) is already provided by Jeremy Allison. Its not clear when it
will be officially released, but maybe in the meantime the patch
can be applied by the package maintainer?