https://bugs.kde.org/show_bug.cgi?id=504232
Bug ID: 504232
Summary: Adding custom commands block themselves from being
seen in shortcuts
Classification: Applications
Product: systemsettings
Version: 6.3.5
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: kcm_keys
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected],
[email protected]
Target Milestone: ---
Created attachment 181302
--> https://bugs.kde.org/attachment.cgi?id=181302&action=edit
Error seen in settings gui
SUMMARY
When adding a custom command/script as a keyboard shortcut, plasma will create
a .desktop file with the "NoDisplay" attribute set to True. This is fine, as it
is expected not to be displayed in any launcher menus. However, after setting
the command and name, you get this error
"Error while communicating with the global shortcuts service"
If you view the journalctl logs, you see this
org.kde.kcm_keys: "Error while calling objectPath of added
applicationnet.local.<generated name>.desktop"
org.kde.kcm_keys: "org.kde.kglobalaccel.NoSuchComponent" "The component
'net.local.<generated name>.desktop' doesn't exist."
kcm keys cannot find the entry.
If you manually remove the "NoDisplay" attribute, and add the generated desktop
file as an application, it correctly enters the "Commands" section as a custom
command would
STEPS TO REPRODUCE
1. Open systemsettings
2. Navigate to Keyboard > Shortcuts
3. Click Add New, and select "Command or script..."
4. Fill out details for a script
5. *** Observe error adding script
OBSERVED RESULT
Command/Script not added to shortcuts menu
EXPECTED RESULT
Command/script added to shortcuts menu as expected
SOFTWARE/OS VERSIONS
Linux: Arch, kernel 6.14.6-arch1-1
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
--
You are receiving this mail because:
You are watching all bug changes.
