ksystemlog cannot start from the menu and there's no error message. However, if I execute the ksystemlog from the console, the application can start normally with the following message logged in the console. ksystemlog: Log manager is not yet initialized STEPS TO REPRODUCE 1. Install ksystemlog version 19.08.3 on Plasma 5 DE 2. Open the start menu and search for ksystemlog 3. Click on the icon to start the application 3. OBSERVED RESULT Nothing happens EXPECTED RESULT The ksystemlog application should start. SOFTWARE/OS VERSIONS Windows: n/a macOS: n/a Linux/KDE Plasma: Gentoo 64 bit Plasma 5 (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.64.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION Full console log when starting ksystemlog from a console. Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 14: Having multiple <family> in <alias> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 14: Having multiple <family> in <alias> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 14: Having multiple <family> in <alias> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 14: Having multiple <family> in <alias> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 14: Having multiple <family> in <alias> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 14: Having multiple <family> in <alias> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 14: Having multiple <family> in <alias> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 26: Having multiple <family> in <alias> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 26: Having multiple <family> in <alias> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 26: Having multiple <family> in <alias> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 26: Having multiple <family> in <alias> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 26: Having multiple <family> in <alias> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 26: Having multiple <family> in <alias> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 26: Having multiple <family> in <alias> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 38: Having multiple <family> in <alias> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 38: Having multiple <family> in <alias> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 38: Having multiple <family> in <alias> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 38: Having multiple <family> in <alias> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 38: Having multiple <family> in <alias> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 38: Having multiple <family> in <alias> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 38: Having multiple <family> in <alias> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 92: Having multiple values in <test> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 106: Having multiple values in <test> isn't supported and may not work as expected Fontconfig warning: "/etc/fonts/conf.avail/69-odofonts.conf", line 125: Having multiple values in <test> isn't supported and may not work as expected ksystemlog: Log manager is not yet initialized
Same thing with ksystemlog 19.12.1 on Arch Linux.
I've tried to open KSystemlog 20.07.80 on Plasma Wayland in Arch Linux. It asks me for my root password. If I enter it, KSystemlog fails to start. Only if I click on ignore when asked for the root password, KSystemlog starts ok like from the terminal.
In my case I remember my problem is caused by the incorrect file permission of the file "~/.local/share/applications/org.kde.ksystemlog.desktop". After I changed the permission and make sure my account can access that file. I am able to start the system log from the menu.
I can confirm this issue. Still happens on neon with Plasma 5.19.5.
I can confirm this as well with 20.04.3 on Gentoo. It prints: “Kon het programma 'kdesu' niet vinden”, which is Dutch for: “Could not find the program 'kdesu'”. I also need to start it from a terminal.
Does it work if you install kdesu?
(In reply to Christoph Feck from comment #6) > Does it work if you install kdesu? I have the kdesu-5.70.0 package installed (Gentoo). However, there is no kdesu executable. The only exectutable-like files I have with kdesu in the name are /usr/lib64/libexec/kf5/kdesu_stub /usr/lib64/libexec/kf5/kdesud Should there be a kdesu executable?
On my system, 'kdesu' executable is provided by the 'kde-cli-tools5' package. Please ask in a forum of your distribution for exact package names.
(In reply to Christoph Feck from comment #8) > On my system, 'kdesu' executable is provided by the 'kde-cli-tools5' > package. Please ask in a forum of your distribution for exact package names. On Gentoo, it's kde-plasma/kde-cli-tools. It has a use flag kdesu which causes the executable kdesu to be compiled and installed. It is disabled by default. Enabling it fixes the startup issue for me. So this seems like a downstream issue. So unless others' issues described here are not solved by this, this can be marked RESOLVED DOWNSTREAM. Gentoo bug report: https://bugs.gentoo.org/show_bug.cgi?id=743196
This package seems to be the last one within KDE Release Service to be using "X-KDE-SubstituteUID=true" for startup. This solution is only for X, it will remain broken within Wayland until ported to kauth.
I use a full x-org session and still get this same broken behavoir. An error message would be helpful even if the port kauth is needed for final resolution.
When will KSystemLog work with Wayland? Is there another bug report for that?