Scenario: - FreeBSD 12.0 latest patchlevel (releng/12.0) - Using portmaster to always upgrade to latest ports - Starting kde using sddm - A few days ago, upgraded plasma5 to 5.15.2 Result: - Since upgrading plasma to 5.15.2, when starting a KDE session, a red "crash" symbol appears in the system tray, indicating that kded5 has crashed - There are no immediately visible problems resulting from this [0]% grep -i kded .local/share/sddm/xorg-session.log kdeinit5: preparing to launch 'libkdeinit5_kded5' kdeinit5: Launched KDED, pid = 2091 result = 0 Initializing "kded_touchpad" : "kcminit_touchpad" KCrash: Attempting to start /usr/local/bin/kded5 from kdeinit kdeinit5: Got EXEC_NEW '/usr/local/bin/kded5' from wrapper. kdeinit5: preparing to launch '/usr/local/bin/kded5' KCrash: Application Name = kded5 path = /usr/local/bin pid = 2091 KCrash: Arguments: /usr/local/bin/kded5 print-manager.kded: unable to register service to dbus kscreen.kded: PowerDevil SuspendSession action not available! [0]%
Found this: https://github.com/NixOS/nixpkgs/issues/24563 last comment: After disabling session restore and restarting a KDE session, you can then re-enable session restore, and everything will behave just like before.
Don't if it solves, but maybe.
Hmmm... I tried this, and at least in this new session I have not had the crash. [0]% grep -i kded .local/share/sddm/xorg-session.log kdeinit5: preparing to launch 'libkdeinit5_kded5' kdeinit5: Launched KDED, pid = 9647 result = 0 print-manager.kded: unable to register service to dbus Initializing "kded_touchpad" : "kcminit_touchpad" kscreen.kded: PowerDevil SuspendSession action not available! [0]% grep -i crash .local/share/sddm/xorg-session.log [1]%
Thanks for the pointer. I'll watch this a little longer and then hopefully close this PR.
After the second reboot with session restore re-enabled, the crash has been re-enabled as well...
(In reply to Martin Birgmeier from comment #5) I cannot reproduce this on my desktop. I'll see if any other computer of mine behaves like this.
With one of the recent upgrades of plasma/KDE, this issue has vanished. -- Martin