SUMMARY When I press Shift + PrtScr then Spectacle does the printscreen just fine, but when I change the default shortcut to Ctrl + PrtScr, Apply and press the shortcut combination, the Spectacle doesn’t make what it just previously did with NO errors within the logs. When I revert Ctrl + PrtScr back to Flameshot and check the logs, this is what pops up every time I press this particular shortcut combination: 18 Aug 2021 10:56:31 kstart5 QApplication: invalid style override 'gtk' passed, ignoring it. Available styles: Breeze, kvantum-dark, kvantum, qt5ct-style, Windows, Fusion 18 Aug 2021 10:56:32 kstart5 qt.svg: link #path2410 is undefined! 18 Aug 2021 10:56:32 kglobalaccel5 kstart: Unknown option 'delay'. When I press PrtScr it triggers ksnip (another app for screenshots), but unfortunately it doesn’t create a screenshot. The log throws the following sausage instead: 19 Aug 2021 17:39:42 kstart5 QApplication: invalid style override 'gtk' passed, ignoring it. Available styles: Breeze, kvantum-dark, kvantum, qt5ct-style, Windows, Fusion 19 Aug 2021 17:39:42 kstart5 qt.svg: link #path2410 is undefined! 19 Aug 2021 17:39:42 kglobalaccel5 kstart: Unknown option 'r'. STEPS TO REPRODUCE 1. Install Flameshot and ksnip 2. Assign Ctrl + PrtScr to make a screenshot with Flameshot 3. Assign PrtScr to make a screenshot with ksnip 4. Try different combinations of taking screenshots and check your logs OBSERVED RESULT Not possible to use the Ctrl+PrtScr keys combinations. Not possible to use Flameshot and ksnip. EXPECTED RESULT Self explanatory. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.10.59-1-MANJARO (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION
This is related to the most recent change of marking `kinit` as an orphan package, so it was missing from my system. To resolve this issue, one should install the package manually.
I can't reproduce this issue; do you still see it?
(In reply to Ahmad Samir from comment #2) > I can't reproduce this issue; do you still see it? You may reproduce this issue as long as you don't have the `kinit` package missing. Once you have it installed, everything behaves alright.
What's the exact command that the shortcut is used to launch?
(In reply to Ahmad Samir from comment #4) > What's the exact command that the shortcut is used to launch? https://i.imgur.com/vnFm3GX.png