https://bugs.kde.org/show_bug.cgi?id=498683
--- Comment #6 from Raphael Kubo da Costa <rak...@freebsd.org> --- Git commit 702a8fe3e75b04c376ed2db95ed39b0b29a9ff17 by Raphael Kubo da Costa. Committed on 21/01/2025 at 22:57. Pushed by rkcosta into branch 'master'. ksldapp: Set componentDisplayName property for global Lock Session action This is used by kglobalacceld as the "friendly name" of a given component, which kcm_keys then uses as a name in the Shortcuts KCM list. When not set, the application name is used. Although different plugins and libraries (e.g. plasma-workspace's startkde/session-shortcuts and KScreenLockerSettings here) register global shortcuts for the "ksmserver" component with the "Session Management" display name, KSldApp::initialize() might be the first to register a ksmserver global shortcut. When testing the latest Neon stable release (neon-user-20250119-0743) with a new installation, kwin_wayland would often be the first to call KSldApp::initialize(), so we would end up with a new component called "ksmserver" with a friendly name of "KWin". In practice, we would end up with two KWin components in the Shortcuts KCM, the real one and the one that should be called "Session Management", which has "Lock Session", "Log Out" etc. M +3 -0 ksldapp.cpp https://invent.kde.org/plasma/kscreenlocker/-/commit/702a8fe3e75b04c376ed2db95ed39b0b29a9ff17 -- You are receiving this mail because: You are watching all bug changes.
