kde-apps/ksystemlog requires the kdesu executable. That executable is available in kde-plasma/kde-cli-tools[kdesu]. Please see the linked KDE bug report: https://bugs.kde.org/show_bug.cgi?id=414971 I have installed kde-plasma/kde-cli-tools[kdesu] and this fixed the issue described, namely, that ksystemlog cannot be started through its desktop file. Reproducible: Always
Works fine from terminal, is caused by desktop file.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/kde.git/commit/?id=3f8ad6b2e4c131954ba2564664f0a5eccee5178d commit 3f8ad6b2e4c131954ba2564664f0a5eccee5178d Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2020-09-19 16:23:01 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2020-09-19 20:03:15 +0000 kde-apps/ksystemlog: Add IUSE=kdesu for X-only run-as-root option Keeping this disabled by default with accompanying pkg_postinst messages as a middle ground between hard-requiring X or being broken by default in Wayland. KDE-Bug: https://bugs.kde.org/show_bug.cgi?id=414971 KDE-Bug: https://bugs.kde.org/show_bug.cgi?id=227793 Reported-by: Erik Quaeghebeur <gentoo@e3q.eu> Bug: https://bugs.gentoo.org/743196 Package-Manager: Portage-3.0.7, Repoman-3.0.1 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> kde-apps/ksystemlog/ksystemlog-20.08.49.9999.ebuild | 16 +++++++++++++++- kde-apps/ksystemlog/ksystemlog-9999.ebuild | 20 ++++++++++++++++++-- kde-apps/ksystemlog/metadata.xml | 3 +++ 3 files changed, 36 insertions(+), 3 deletions(-)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0629e604123c478049295966edecf253b62feff1 commit 0629e604123c478049295966edecf253b62feff1 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2020-09-19 16:23:01 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2020-09-19 20:18:42 +0000 kde-apps/ksystemlog: Add IUSE=kdesu for X-only run-as-root option Keeping this disabled by default with accompanying pkg_postinst messages as a middle ground between hard-requiring X or being broken by default in Wayland. KDE-Bug: https://bugs.kde.org/show_bug.cgi?id=414971 KDE-Bug: https://bugs.kde.org/show_bug.cgi?id=227793 Reported-by: Erik Quaeghebeur <gentoo@e3q.eu> Closes: https://bugs.gentoo.org/743196 Package-Manager: Portage-3.0.7, Repoman-3.0.1 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> ...20.04.3.ebuild => ksystemlog-20.04.3-r1.ebuild} | 28 ++++++++++------------ ...20.08.1.ebuild => ksystemlog-20.08.1-r1.ebuild} | 16 ++++++++++++- kde-apps/ksystemlog/metadata.xml | 3 +++ 3 files changed, 31 insertions(+), 16 deletions(-)
I do not think this issue is fully fixed yet. I now get execvp: No such file or directory when trying to start from the menu or krunner. Starting from the console still works. I have '-kdesu'. I'm running stable KDE frameworks, plasma, and packages.
It certainly works for me. You'll have to be a bit more specific.
(In reply to Andreas Sturmlechner from comment #5) > It certainly works for me. You'll have to be a bit more specific. I do not really know how to provide more information… $ eix ksystemlog [I] kde-apps/ksystemlog Available versions: (5) 20.04.3-r1^t ~20.08.1-r1^t {debug +handbook kdesu systemd test} Installed versions: 20.04.3-r1(5)^t(13:49:50 20-09-20)(handbook systemd -debug -kdesu -test) Starting from the menu, from krunner, and from inside ksysguard (top-right ‘tools’ menu) gives that message. There is nothing to be found in the logs (journal) about this failure.
