Bug 460436

Summary:	Global multimedia shortcuts randomly stop working
Product:	[Plasma] plasmashell	Reporter:	Dmitrii Chermnykh <chermnykh2001>
Component:	Media Player widget	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	chermnykh2001, kde, nate
Priority:	NOR
Version:	5.26.0
Target Milestone:	1.0
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Dmitrii Chermnykh 2022-10-14 14:36:26 UTC

SUMMARY
After some time or session restart some multimedia keys stop working. Sometimes play/pause shortcut breaks. Sometimes audio volume controls stop working. Any of those shortcuts may stop working independently from each other. 

When a shortcut stops working the corresponding dbus command (e.g. `qdbus org.kde.kglobalaccel /component/mediacontrol org.kde.kglobalaccel.Component.invokeShortcut playpausemedia`) also stops working.

Removing shortcut grop in system settings (e.g. media controller) and restarting the session helps, but some time later problem reappears. 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.26.0
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.6+kde+r180

Comment 1 Dmitrii Chermnykh 2022-10-14 20:41:19 UTC

One more note: only shortcuts stop working. The widget works fine

Comment 2 Dmitrii Chermnykh 2022-12-19 09:14:50 UTC

Seems like the issue emerges only when using multiple screen setup (I'm using hybrid amd+nvidia setup):

1. Connect 2nd screen 
2. Start plasma
3. Media keys are not working, volume keys are fine
4. Disconnect the 2nd screen
5. Volume keys break until the 2nd screen is reconnected

I'm also using 2 exactly same panels (one per each screen) with media control widget, volume control widget and system tray. I think it may have something to do with the issue.

Comment 3 Nate Graham 2022-12-23 22:10:30 UTC

Ah, so the two instances of the Media Player widget are fighting for control. It's ultimately the same issue as Bug 409190.

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