Bug 442925

Summary: Clipboard keyboard shortcuts are tied to panel instance
Product: [Plasma] plasmashell Reporter: David <david.cortes.rivera>
Component: Clipboard widget & pop-upAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate, programmer.pesesoft+kde
Priority: NOR    
Version: 5.22.90   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=423625
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description David 2021-09-25 02:26:14 UTC 
SUMMARY
If I set custom keyboard shortcuts for the clipboard, and then remove the panel that has the systray and put it again, those keyboard shortcuts will be lost.

STEPS TO REPRODUCE
1. Add a latte dock with system tray, and remove any current plasma panel.
2. Copy something to the clipboard so as to make it show a tray icon.
3. Right-click the clipboard icon, configure custom keyboard shortcuts.
4. Remove latte dock and put a plasma panel with a system tray.
5. Restart the computer just in case.
6. Try using the keyboard shortcuts that were set for the clipboard.

OBSERVED RESULT
Configured keyboard shortcuts are gone.

EXPECTED RESULT
Keyboard shortcuts should not be tied to a panel instance.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2021-09-27 21:21:42 UTC 
Indeed, because the shortcuts live in the Clipboard applet, and each applet lives somewhere. We would have to make the shortcuts get set elsewhere. See also:

- Bug 391578 for the Audio Volume applet
- Bug 409190 for the Media Player applet
- Bug 423625 for the Clipboard applet but in a different context
Comment 2 Nate Graham 2022-06-09 15:38:35 UTC 
*** Bug 455039 has been marked as a duplicate of this bug. ***
Comment 3 Nate Graham 2023-04-27 23:20:13 UTC 
Ultimately the same as Bug 423625.
Comment 4 Nate Graham 2024-03-16 15:53:21 UTC 

*** This bug has been marked as a duplicate of bug 423625 ***