https://bugs.kde.org/show_bug.cgi?id=432460
--- Comment #5 from Fabian Vogt <fab...@ritter-vogt.de> --- I enabled the ksmserver logging category in "production" builds and fortunately it did actually fail in one of the openQA runs! In one test, a click on "Ok" to confirm log out works (https://openqa.opensuse.org/tests/1628813#step/start_wayland_plasma5/15): Feb 13 02:01:27.715302 susetest dbus-daemon[1102]: [session uid=1000 pid=1102] Activating service name='org.kde.Shutdown' requested by ':1.33' (uid=1000 pid=2423 comm="/usr/lib64/libexec/ksmserver-logout-greeter ") Feb 13 02:01:27.796281 susetest dbus-daemon[1102]: [session uid=1000 pid=1102] Successfully activated service 'org.kde.Shutdown' Feb 13 02:01:27.798859 susetest ksmserver[1246]: org.kde.kf5.ksmserver: saveSession is true Feb 13 02:01:27.804912 susetest ksmserver[1246]: org.kde.kf5.ksmserver: Saving legacy session apps Feb 13 02:01:27.818564 susetest ksmserver[1246]: org.kde.kf5.ksmserver: Done saving 0 legacy session apps ... In another test, a click on the "shutdown" button did nothing: https://openqa.opensuse.org/tests/1628811#step/shutdown/5 Feb 13 01:59:47.923856 susetest dbus-daemon[1095]: [session uid=1000 pid=1095] Activating service name='org.kde.Shutdown' requested by ':1.33' (uid=1000 pid=2361 comm="/usr/lib64/libexec/ksmserver-logout-greeter ") Feb 13 01:59:48.094592 susetest dbus-daemon[1095]: [session uid=1000 pid=1095] Successfully activated service 'org.kde.Shutdown' Feb 13 02:00:18.774911 susetest systemd[1]: Started Timeline of Snapper Snapshots. ... Apparently the call to org.kde.Shutdown didn't reach ksmserver at all? -- You are receiving this mail because: You are watching all bug changes.
