https://bugs.kde.org/show_bug.cgi?id=435478
Harald Sitter <sit...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO |UPSTREAM
--- Comment #11 from Harald Sitter <sit...@kde.org> ---
Right. So...
What appears to be going on is that making multiple requests at the same time
results in failure, while making a single request works just fine.
This does rather point at the problem being server-side.
The way concurrency works on the KIO side is that for each request we start a
new worker process that executes that request in isolation.
For example when you start dolphin it will generally make a request to list the
directory but at roughly the same time it will also make a request to obtain
the free space on the remote drive. Since these are standalone processes they
both independently authenticate to the server. It's like multiple users from
the same computer try to access the server at the same time. What appears to
happen then is that both processes fail to authenticate.
When you ran kioclient manually it succeeded because it only had a single
request to make at that time. The script I provided made the same request 5
times concurrently and consequently failed again.
As mentioned, this pretty much means the server is to blame. There are two
options you have here:
a) file a bug with samba and reference this bug report from some background
https://bugzilla.samba.org/ they may be able to help you figure out what
exactly the server is doing that trips up authentication. Perhaps they might
even be able to do something about it.
b) you could take this to the manufacturer of your NAS directly. From the
behavior we have seen this is almost certainly a problem with the SMB server.
>From our end there's nothing we can do unfortunately.
--
You are receiving this mail because:
You are watching all bug changes.
