Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2131723
| Summary: | Nautilus refuses to copy a complete directory to a Samba share... | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | antonraves |
| Component: | nautilus | Assignee: | Matthias Clasen <mclasen> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 37 | CC: | awilliam, caillon+fedoraproject, cosimo.cecchi, gary.buhrmaster, gnome-sig, kparal, mclasen, oholy, philip.wyett, rhughes, robatino, sandmann, sgallagh |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | RejectedBlocker | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-10-21 19:10:39 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2009540 | ||
|
Description
antonraves
2022-10-03 13:26:53 UTC
The Samba definition for this Nautilus problem: [share_name] path = /srv/samba/share_name valid users = fedora_user browsable = yes guest ok = no writable = yes hide dot files = yes hide files = /~$*/~*/ veto files = /._*/.DS_Store/ delete veto files = yes create mask = 0644 directory mask = 0755 veto oplock files = /*.doc/*.docx/*.xls/*.xlsx/ Proposed as a Blocker for 37-final by Fedora user bcotton using the blocker tracking app because: Arguably violates the Final criterion: For all release-blocking desktop / arch combinations, the following applications must start successfully and withstand a basic functionality test: file manager I can reproduce this problem in my home with nautilus-43.0-2.fc37.x86_64 and a SMB share provided by my router. Does copying a complete directory work from the command line? Can you run `cp -a /path/to/dir /path/to/smb/share` successfully? @sgallagh I tried as you asked and both with and without a "sudo" I got the error message "cp: cannot stat '/run/user/1000/gvfs/smb-share:server=34.235.198.240,share=share_name/ test_directory': Permission denied", this of course with the IP address of the Samba server, not redhat.com. well, this is likely really a gvfs issue, i.e. it's to do with how gvfs mounts the share when you discover a network location in Nautilus. With a manually configured smb share this works fine for me, I just tested. I can copy a folder to a manually mounted SMB share in nautilus no problem. This may (or may not) be related to https://bugzilla.redhat.com/show_bug.cgi?id=2127301 (fix available as of a few hours ago) and https://gitlab.gnome.org/GNOME/gvfs/-/issues/651 which suggests a samba issue. It might be worth seeing of the samba update resolves the issue. Yes, this is most probably related to Bug 2127301. Or are you able to reproduce this with samba-4.17.1-1.fc37 (https://bodhi.fedoraproject.org/updates/FEDORA-2022-1b0ba70aca)? If so, please provide debug log using the steps from https://wiki.gnome.org/Projects/gvfs/debugging#Getting_debug_logs with GVFS_SMB_DEBUG=10 envar set in the second step... With samba-4.17.1-1.fc37 installed a complete folder / directory can be copied to the Samba-share without any worries! Then it works! I can also confirm samba-4.17.1-1.fc37 fixed the issue for me. Rejected as an F37 blocker in https://pagure.io/fedora-qa/blocker-review/issue/979 . Since we've skipped, we have scope to pull this in as an FE, so proposing it. I think we can just make this a dupe of 2127301, right? *** This bug has been marked as a duplicate of bug 2127301 *** |