Version: unspecified (using KDE 4.6.2) OS: Linux When attempting to copy files between two smb shares on two remote machines using drag and drop, dolphin attempts to copy the file, but the job on the notification tray shows that the file's copy speed is 0B/s. While the file is "transferring" while not copying any actual data, dolphin is unable to read the contents of either smb share until the copy job is stopped, after which a 0B file is present where the file was attempted to be copied to. Reproducible: Always Steps to Reproduce: see above Actual Results: na Expected Results: na na
Is this really an smb problem? I would think that it is a dolphin problem because nautilus does not have the same problem when it is running on the same system.
The reassignment to kio/smb means that it's problem with the SMB kioslave, which is the part of KDE that Dolphin uses to interact with smb shares.
Why is this still unconfirmed?
(In reply to comment #3) > Why is this still unconfirmed? Ahhh... maybe because this is a volunteer effort and the number of people volunteering is way way smaller than the number of bugs people file ? Anyhow, please look for the protocol description file "smb.protocol" on your system, edit it as a super user (root), add the two properties listed below and tell us if it solves your problem: maxInstances=20 maxInstancesPerHost=5
Yes, this solves the problem for me. Maybe this should be included by default, as companies tend to have more than one (Windows) file server...
(In reply to comment #5) > Yes, this solves the problem for me. Maybe this should be included by default, > as companies tend to have more than one (Windows) file server... It is already done. See https://bugs.kde.org/show_bug.cgi?id=250882.
Dolphin is still extremely buggy when working with samba. eg: https://bugs.kde.org/show_bug.cgi?id=272500 https://bugs.kde.org/show_bug.cgi?id=284977 Are there any plans to fix these in 4.8?