STEPS TO REPRODUCE 1. download kmymoney binary build from https://binary-factory.kde.org/view/Windows%2064-bit/job/KMyMoney_Release_win64/ 2. download dbgview from https://docs.microsoft.com/en-us/sysinternals/downloads/debugview 3. start dbgview, then start kmymoney OBSERVED RESULT In the dbgview window you will find lines in the form kf5.kio.core: couldn't create slave: "Meldung von klauncher: Unbekanntes Protokoll „g“.\n" EXPECTED RESULT As this line indicate a problem with loading kio slave, the root cause should be fixed SOFTWARE/OS VERSIONS Windows: 10 KDE Frameworks Version: 5.83 Qt Version: 5.15
> kf5.kio.core: couldn't create slave: "Meldung von klauncher: Unbekanntes Protokoll „g“.\n" The term „g“ is the first character from the installation path "g:\..." on Windows, which probably indicates a problem in kio parsing a windows path url.
Is klauncher available on windows? IIRC kate explicitly runs on windows by forking the slaved (probably setting KDE_FORK_SLAVES=1).
(In reply to Ahmad Samir from comment #2) > Is klauncher available on windows? IIRC kate explicitly runs on windows by > forking the slaved (probably setting KDE_FORK_SLAVES=1). Builds from binary factory are not using klauncher by default, as on the cmake command line used to compile kio, KDE_FORK_SLAVES=1 is set. Also klauncher is not packaged.
(In reply to Ralf Habacker from comment #3) > (In reply to Ahmad Samir from comment #2) > > Is klauncher available on windows? IIRC kate explicitly runs on windows by > > forking the slaved (probably setting KDE_FORK_SLAVES=1). I remember Ahmad was going to look at it, but I haven't heard from him since.
(In reply to Ralf Habacker from comment #3) > (In reply to Ahmad Samir from comment #2) > > Is klauncher available on windows? IIRC kate explicitly runs on windows by > > forking the slaved (probably setting KDE_FORK_SLAVES=1). This problem is independent from klauncher.
The binary build system has been switched to the use of gitlab-CI/Craft. It should be checked whether this problem still exists.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.