https://bugs.kde.org/show_bug.cgi?id=390288
--- Comment #2 from Valdo <woualere.agn...@laposte.net> --- Hi Dominik, yes I can reproduce this issue systematically. A/ Test case avoiding the bug: I can create an empty text file in the remote Samba share with Dolphin. Then open that empty file with Kate, feed it with some text and save it: no issue. B/ Test case hitting the bug: Launch Kate, type in some text, then click Save, navigate to the "Network" shortcut, then double-clicking "Samba shares": Kate crashes in less than a second. By reading the first part of bug #190535, I had the idea to launch Kate from Konsole. As soon as I click Save (to select a destination folder), this information displays in Konsole: kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "" kf5.kio.core: KSambaShare: Could not find smb.conf! Each time I navigate to a new local subfolder, I get this information: kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "" Then clicking the "Network" shortcut to the left of the Save window: kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "" As soon as I double-click "Samba shares" to the right, I get this in Konsole: kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "" kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "" kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "" kf5.kio.widgets: Items emitted in directory QUrl("smb://") but that directory isn't in KDirModel! Root directory: QUrl("smb:///") Item: QUrl("smb://workgroup") KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kate path = /usr/bin pid = 1779 KCrash: Arguments: /usr/bin/kate KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 [2]+ ArrĂȘtĂ© kate $ Remember my Samba share is hosted on a Linux Mint 18.3 machine. On that machine, when right-clicking the folder shared with Samba and selecting option "Sharing options" (or equivalent English translation), I can notice that message: "The share name is too long" (or equivalent English translation). In my case, the share name is "Partage Mint-land". I hope this helps. Feel free to ask for more details if needed. And thanks for your investigation. -- You are receiving this mail because: You are watching all bug changes.