SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Has anybody else encountered this: copying files from samba-shares freeze after a couple of files?
It only seems to happen on my Slackware laptop.
I can still browse the shared directories with Thunar, but the file copying freezes, and pushing cancel-button just shows "cancelling" but nothing happens. The "copying"-popup still stays there.
I tried to look at the logs (put log level to 8), but didn't find any clear reason.
Any suggestions how to proceed with debugging this?
Slackware is 14.1 with samba-4.1.0-i486-2.txz
The machine that has the samba-shares is Debian Jessie.
I have a question for you. Practically every day we see here support requests for failing CIFS/Samba transfers between two Linux machines. Why are you attempting to use a Windows protocol between two *nix machines?
Because there are two Windows-machines involved too - mine, and those Windows-machines my children have and which they use when visiting me.
Between two other Linux-machines (Sabayon, Debian) and the two Windows-machines (Vista, Windows7) that problem doesn't occur. (OK, win7 forgets the rights for accesses after an hour or so, but that's different problem .)
Last edited by turboscrew; 01-31-2016 at 12:53 PM.
How are Windows machines relevant? Oh ... I get it. People think when they share a volume over Samba it "locks it down"? I have news for you, you can share it also over NFS, and FTP, and HTTP for read-only access, and whatever network filesharing protocol you need - simultaneously!
What version of XFCE/Thunar is your Sabayon system using? Thinking in terms of the Sabayon version may be newer which may have fixed some bugs leading to the issue.
Another thing to try is running Thunar from a terminal and see if you get any useful info when it hangs.
What version of XFCE/Thunar is your Sabayon system using? Thinking in terms of the Sabayon version may be newer which may have fixed some bugs leading to the issue.
Another thing to try is running Thunar from a terminal and see if you get any useful info when it hangs.
I don't remember the Sabayon version, and I haven't used that machine for a while.
But yes, running Thunar from console may reveal something. Thanks.
From what I am seeing other folks have had the same issue. For them gvfs-smb is hanging which in turn causes Thunar to hang. If they whack the gvfs-smb process, Thunar comes back to life. However that does nothing to help with your situation. Depending on where you look some people have said the gvfs issue was supposed to be fixed in 1.16.3 (the version included with 14.1). Looking at this bug report from ubuntu, things were supposedly fixed in gvfs 1.18. They mention a workaround using cifs from the kernel. May be worth a shot.
From what I am seeing other folks have had the same issue. For them gvfs-smb is hanging which in turn causes Thunar to hang. If they whack the gvfs-smb process, Thunar comes back to life. However that does nothing to help with your situation. Depending on where you look some people have said the gvfs issue was supposed to be fixed in 1.16.3 (the version included with 14.1). Looking at this bug report from ubuntu, things were supposedly fixed in gvfs 1.18. They mention a workaround using cifs from the kernel. May be worth a shot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.