Summary: | kf5.kio.core: couldn't create slave: "Meldung von klauncher: Unbekanntes Protokoll „g“.\n" | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | Ralf Habacker <ralf.habacker> |
Component: | general | Assignee: | KIO Bugs <kio-bugs-null> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | a.samirh78, kdelibs-bugs, tbaumgart |
Priority: | NOR | ||
Version: | 5.83.0 | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=426448 | ||
Latest Commit: | Version Fixed In: | ||
Bug Depends on: | |||
Bug Blocks: | 426400 |
Description
Ralf Habacker
2021-07-15 06:45:52 UTC
> 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. |