Package: ukui-screensaver Version: 4.20.0.3-1 Severity: normal Dear Maintainer,
ukui-screensaver-backend unconditionally creates an interface for org.kde.kglobalaccel, including when running in the LightDM greeter session. Creating the QDBusInterface is enough to activate org.kde.kglobalaccel, even before any global shortcut operation is performed. In the greeter session this starts plasma-kglobalaccel5.service. The service cannot connect to the display and exits, after which systemd restarts it repeatedly until the start limit is reached. Typical log output includes: systemd: Starting plasma-kglobalaccel5.service… kglobalaccel5: qt.qpa.xcb: could not connect to display systemd: plasma-kglobalaccel5.service: Main process exited systemd: Scheduled restart job This happens on every boot and may leave multiple core dumps behind. Global shortcut blocking is not needed in the greeter session, since it runs in its own LightDM display session. Expected result: When running in greeter mode, ukui-screensaver should not activate or contact org.kde.kglobalaccel. This is separate from the ukui-session-manager issue about the missing display environment in the simpleDesk activation environment. That issue affects services which legitimately need display access, while this issue is that kglobalaccel should not be started by the greeter in the first place. Regards,
