Bug 436415 - Shortcut added to toggle "Do not disturb" mode stops working when KCM is closed, and then only starts working again after kglobalaccel5 is restarted
Summary: Shortcut added to toggle "Do not disturb" mode stops working when KCM is clos...
Status: CONFIRMED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_notify (show other bugs)
Version: 5.21.4
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Kai Uwe Broulik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-30 18:47 UTC by Víctor
Modified: 2021-05-04 00:40 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Víctor 2021-04-30 18:47:06 UTC 
SUMMARY

I have set up a keyboard shortcut to toggle “Do not disturb” mode in notifications. When I set any combination of keys, apparently works. But, after close the settings window, the shortcut stop to work.


STEPS TO REPRODUCE
1. Open Notifications settings page in System Settings.
2. Set up a shortcut for toggle “Do not disturb” mode (Ctrl+Shift+F4, by example).
3. Try the new shortcut combination.The toggle works.
4. Close System Settings window.
5. Try again new shortcut combination. The toggle does not work.

OBSERVED RESULT
After close System Settings window, the shortcut does not work. 

EXPECTED RESULT
Shortcut would be work in any situation when is invoked.

SOFTWARE/OS VERSIONS
Operating System: KDE neon Testing Edition
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2021-05-03 20:47:35 UTC 
Wow, can confirm. We're probably registering it as a local shortcut rather than a global shortcut.
Comment 2 Nate Graham 2021-05-04 00:25:30 UTC 
HMm, it actually stops working the moment you leave the page, and doesn't start working again if you return. But the KCM still lists the shortcut.
Comment 3 Nate Graham 2021-05-04 00:26:15 UTC 
The shortcut is written into the config file properly though, and restarting kglobalaccel5 makes it start working.

So maybe we're somehow  not telling kglobalaccel about the new shortcut we've added?
Comment 4 Nate Graham 2021-05-04 00:36:24 UTC 
Seems like closing the KCM wipes out the shortcut change until kglobalaccel is restarted, basically.