487962 2024-06-03 14:06:19 +0000 Audio Volume Widget shortcut does not function correctly Plasma 6. 2024-06-11 08:02:36 +0000 1 1 4 Plasma plasmashell System Tray widget master Other Linux RESOLVED DUPLICATE 488332 NOR normal 1.0 1 randy.rah.harp plasma-bugs-null akselmo materka 0 oldest_to_newest 2324187 0 randy.rah.harp 2024-06-03 14:06:19 +0000 SUMMARY I cannot get the Audio Volume Widget shortcut to function. It will save in the config file, and in the keyboard shortcut settings. It will still not actually come up if I input the shortcut. I searched for users with a similar issue and found one Reddit post https://www.reddit.com/r/kde/comments/1byxxmq/cant_apply_shortcut_to_audio_volume_widget/ that had the same issue with no response. This has only happened to me on Plasma 6, and I never had this issue with Plasma 5. The shortcut I use is Meta+G. The shortcut did work for a few days before breaking within the last 48 hours. STEPS TO REPRODUCE 1. Add Meta+G as shortcut for Audio Volume Control 2. Input Shortcut 3. OBSERVED RESULT Audio Volume Widget does not respond to shortcut. If in text box will type the G from Meta+G. EXPECTED RESULT Audio Volume Widget to respond to shortcut. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 40 (available in About System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION 2326472 1 akselmo 2024-06-11 08:02:05 +0000 Is the audio widget inside system tray for you? Does it work if you add as separate widget? Seems that some of the widgets that are inside system tray by default have lost their shortcut ability for some reason. I can't even find the setting to add a shortcut, so I think this is confirmed. Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.80 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.1 Kernel Version: 6.8.11-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 6600 2326473 2 akselmo 2024-06-11 08:02:36 +0000 *** This bug has been marked as a duplicate of bug 488332 ***