Description of problem: Nautilus hangs when copy folders with files from (smb) share. There seems to be no problem with single or large files. Those "hangs" are some kind of random. There is no error message. Also there is no problem by copying those folders on command line (terminal). Nautilus itself does not freeze, but the copy process never ends. Version-Release number of selected component (if applicable): nautilus-3.26.2-1.fc27.x86_64 samba-client-4.7.3-3.fc27.x86_64 gvfs-smb-1.34.1-1.fc27.x86_64 How reproducible: Mostly Steps to Reproduce: 1. Copy folder with files from command line (No problem) 2. Copy folder with files with nautilus (It mostly hangs) 3. Actual results: Nautilus hangs when copy folders from (smb) share Expected results: Nautilus should not hang and copy this folders Additional info:
This bug does not affect copying to the share.
Please see also here: https://bugzilla.gnome.org/show_bug.cgi?id=792169
Created attachment 1377919 [details] $ strace -o output.txt gio copy * /home/sysop/foo/
No changes in samba 4.7.4-2. Is anyone using samba out there?
We either needs logfiles or better a reproducer with libsmbclient. Can you reproduce it with smbget?
No, I can not reproduce it with smbget. With smbget it is working.
(In reply to Steve from comment #6) > No, I can not reproduce it with smbget. With smbget it is working. Because smbget cannot copy directories recursively.
It has been a long time since I looked in libsmbclient and I do not have any deep knowledge about Gvfs, however two things came to mind you may want to check: 1) I do not think libsmbclient can handle more than one operation at a time on the same smb_context 2) Gfvs uses a single smb_context per backend 3) In the Gvfs "smb driver" I have seen no locking or serialization So if all of these are true and Gfvs can issues multiple operations concurrently (I think FUSe is thraded ??) then you may definitely run into issues where operations get mixed on the same context with unpredictable reults. My 2c, HTH
But "GNOME" says, this bug is NOTGNOME: https://bugzilla.gnome.org/show_bug.cgi?id=792169 What can I do to give You the right informations to fix this bug (I'm not a developer)?
Steve, that Gnome bug is unrelated to the problem you have. That Gnome bug is about Glib doing suff on a CIFS mount using the kerbel cifs.ko client. Gvfs instead (AFAICS) uses libsmbclient via a FUSE mount. Completely different situation.
This seem to be a major samba bug. I see this also in Ubuntu 17.10, samba-4.6.7.
> (In reply to Steve from comment #6) > > No, I can not reproduce it with smbget. With smbget it is working. > > Because smbget cannot copy directories recursively. bin/smbget --help | grep recursive -R, --recursive Recursively download files
> bin/smbget --help | grep recursive > -R, --recursive Recursively download files Also when recursively downloading folders with smbget I cannot reproduce this bug. This bug only happens with GUI's: https://bugzilla.samba.org/show_bug.cgi?id=13252
Then I would argue it is a GVFS issue using the libsmbclient API incorrectly, see comment #8.
The bug persists in gvfs-smb-1.34.2.1-1.fc27.x86_64.
The bug persists in Fedora 28, gvfs-smb-1.36.1-1.fc28.x86_64.
Please note: I no longer use samba. Because we have a productive system, samba is useless. I think that's a pity and I'm sorry. Please keep in mind that I can no longer help here.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.