When a share is mounted either manually or via fstab using samba protocol 2.1, Thunar is not able to copy a directory or multiple files from the share. To reproduce: Open terminal sudo mount -t cifs //servershare /mountpoint -o vers=2.1,username=xxx,uid=xxxx Open Thunar, navigate to mount point and select a directory, copy, paste into a local directory. Result: Thunar hangs while trying to copy the first file. Using cp from the terminal, files are copied correctly. Mounting the same share using vers=1.0 allows Thunar to copy the files.
Can you reproduce this problem with any other gvfs-based file manager (e.g. Nautilus, Nemo)? Sorry, but right now I can't easily test this, but I suspect it may possibly be a gvfs issue.
Same result with Nautilus. It hangs as well.
It took me a bit of work, but a shared folder from a Windows 7 machine is working fine here, however I used the following command to mount it: sudo mount -t cifs //servershare /mountpoint -o vers=2.1,username=user,password=pass,rw,uid=0,file_mode=0777,dir_mode=0777 If the shared folder host supports, try vers=3.0. I'm using gvfs 1.36.2, which version do you have installed?
Still fails with the extra parameters under vers=2.1 and vers=3.0. Here are some additional details: File server is running Debian 9.5(Stretch) and up to date XFCE/Thunar is running Ubuntu 18.04 (updated right before this test). gvfs is 1.36.1 (Your updated version may be the solution?) When mounted under 2.1 or 3.0, Thunar can browse the share directories, open a file, save a file, copy multiple files TO the share, copy a single file FROM the share. It just can not copy multiple files FROM the share. Perhaps the 1.36.1 vs 1.36.2 is the resolution. I can try to set up a Debian 10 / sid / 18.10 test machine to see if it still occurs.
Follow up: Same problem occurs with Buster (version 1.36.2 of gvfs) as well as unstable (version 1.38.0 of gvfs)
Just a longshot: Do you have "libsmbclient", "gvfs-backends" and "gvfs-fuse" installed ? Will try to reproduce it next week @work. @home there are no samba servers for me.
On my previous attempt I tried to create, copy, move or delete single files, I tried again with multiple files (4 with a few megabytes) still no hangs. I mean Thunar hangs very briefly while loading folder contents, but nothing terrible. The UI shortly freezing while browsing remote locations is known shortcoming, in future versions we hope to make the UI "immune" to high latency operations. Hopefully Alex is able to reproduce this bug, since he also uses Debian.
It seems to be looking more like a upstream Debian issue that I should somehow report to them rather than you. The 16.04 and 9.5 clients work fine with the vers=2.1. I did also set up a new fresh 9.5 file server with the defaults just to rule out server setup and the problem persisted for the Buster / 18.04 clients. Finally, I did try adding the backends and fuse (libsmbclient was already installed) and that didn't resolve it.
Ok, I took a try @work: schwinn@belpc077:~$ thunar -V Thunar 1.6.11 (Xfce 4.12) schwinn@belpc077:~$ cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 9 (stretch)" ... First tried to enter the smb location via smbclient: smbclient -U aschwinn -W campus //winscratch/scratch Now I took a try with thunar: smb://winscratch/scratch/ Multi file/folders copy to local folder works fine. Now I mounted the samba share: sudo mount -t cifs //winscratch/scratch /sambatest -o vers=3.0,username=aschwinn,rw,uid=0,file_mode=0777,dir_mode=0777,rw,uid=0,file_mode=0777,dir_mode=0777 Another try with thunar, using the mountpoint: /sambatest Multi file/folders copy to local folder works fine as well. You maybe know how I can check the smb-version of the server ? ( Read that "smbstatus" in smbclient should list the protocol version, but I only get "smbstatus: command not found" ) When I mount with "vers=3.0", I would assume that the mount would fail if the server does not support v3.0, is that correct ? As a next step I could try to build thunar from source to see if that changes anything ... but yes, possibly it is only related to buster. Actually I could move to buster/testing ... would be the next next step ;)
As nautilus shows the same issue for you, I as well think it is not a thunar problem. So I will close the bug for now. Please feel free add a links to upstream bugs ! When I get any news, I as well will post here.