Launching chrome will not have indicator STEPS TO REPRODUCE 1. Set "Global Shortcuts > Application Launchers > Launch Google Chrome > Launch Google Chrome" to "Meta+W" (or any combination) 2. Do the key combination 3. Chrome will launch but without that jumping icon indicator OBSERVED RESULT Chrome will launch but without that jumping icon indicator EXPECTED RESULT Maybe for the first time it to show a jumping icon indicator, so user can understand that its launching. I am not sure about the second or so on times because they are pretty quick. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Pop!_OS 19.10 (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION
This was fixed in a later Plasma version.
Still not working on Plasma 5.18 beta. Tested chromium, dolphin and konsole.
You're right, I was testing wrong, sorry. Can confirm now.
From kglobalaccel: //we can't use KRun there as it depends from KIO and would create a circular dep nicofee is planning on resolving the kbookmarks being used from kio which would then resolve that and this becomes a simple fix.
I looked into it once and it appeared it would still create a launch feedback but it would use the binary name "dolphin" which doens't match "org.kde.dolphin". I'm pretty sure this worked at some point.
also affects wayland here Operating System: Gentoo Linux KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.10-gentoo (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-4810MQ CPU @ 2.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600
*** Bug 451160 has been marked as a duplicate of this bug. ***
On Wayland this was fixed by https://invent.kde.org/frameworks/kglobalaccel/-/commit/ce28705bc9e6e0192108382a1c6bfb4ff59fddd7
It also work fine for me on X11 FWIW
(In reply to David Edmundson from comment #4) > From kglobalaccel: > //we can't use KRun there as it depends from KIO and would create a circular > dep > > > nicofee is planning on resolving the kbookmarks being used from kio which > would then resolve that and this becomes a simple fix. This has meanwhile been resolved by splitting kglobalacceld into its own repo and porting to KIO::ApplicationLauncherJob. With that this should be properly fixed