[dolphin] [Bug 431050] SMB error: "There is not enough space on the disk to write smb://..."

[fdkde]

https://bugs.kde.org/show_bug.cgi?id=431050

--- Comment #23 from fdkde <fd483721kde at mailbox.org> ---
I hope that adds some more information which is helpful to track down the
issue:

While browsing through some smb shares and folders with the modified kio-extras
version I noticed some repeating error messages that Dolphin put out into the
terminal session where I started it from:

session setup failed: NT_STATUS_NO_MEMORY
Unable to follow dfs referral [path to smb share]
Couldn't resolve [path to the accessed folder, starting from the smb share]

Info: I had to redact the smb share path and folders for confidential reasons.

Unfortunately I was too busy today to test if I get the same error messages on
with my productive system without the modified kio-extras version. The problems
I had on the VM are gone on a physical system but I got a new error message
from LibreOffice when trying to write new files via smb:

Fehler beim Speichern des Dokuments Unbenannt 1:
Kein Zugriff auf Objekt.
Aufgrund fehlender Benutzerrechte kann auf das Objekt nicht zugegriffen werden.

Translated freely:

Error while saving the document Unbenannt 1:
No access on object.
It isn't possible to access the object due to missing user rights.

Saving existing file is working without problems. I don't know if the reason
for that is our infrastructure or something that can be fixed by KDE or
LibreOffice developers.
One thing I've noticed when trying the same with Kate is that the KDE file
pickers for LibreOffice and Kate look quite similar. But there is one detail
what catched my eye: The network/foreign devices section in the left pane of
the file picker for LibreOffice is/was missing.
Two question for better understanding: How are the file pickers are getting
created and configured? Can application developers decide if the KDE file
picker is showing/supporting the network/foreign section or not?

-- 
You are receiving this mail because:
You are on the CC list for the bug.