STEPS TO REPRODUCE 1. open system settings > shortcuts 2. click on "+ Add application..." button, select any app and click on "Ok" button (notice "_launch:" instead of "<app>:" above "No default shortcuts") 3. click on "+ Add custom shortcut" button and assign a shortcut (I assigned meta+w) 4. test the just assigned shortcut OBSERVED RESULT nothing happens EXPECTED RESULT shortcut assigned in the step 3 should work SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.18.80 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2
I just tried it with kcalc and it worked. What application did you test with?
(In reply to David Redondo from comment #1) > I just tried it with kcalc and it worked. What application did you test with? Ark, Firefox and Opera internet browser. Also reproducible with kcalc.
Possibly related... I notice that if I have created a shortcut on the desktop and click on the icon it *appears* that the application is opened with the name of the whatever.desktop file as an argument. For example for a dolphin shortcut, clicking on the link opens Desktop/org.kde.dolphin.desktop/ folder and prompts "What do you want to do with this executable file" This behaviour has changed since Neon (Plasma 5.18.4, Framework 5.69.0), I see it on Neon Testing (Plasma 5.18.5, Framework 5.71.0)
Yes. Since Saturday 9 I noticed that when I try to open an app via an icon on desktop the app opens or tries to open its own .desktop file. For example, add Kate icon to desktop, launch Kate via its icon on desktop and Kate opens its own .desktop file. But I think it's a different issue. The issue with Global Shortcuts kcm is not recent, it exists since such kcm landed on my system.
Thanks! Created Bug 421364 with a reference to this one. Not sure where it "really lives", filed it under Dolphin :-/
Weird, works for me too.
humm, it's also working on Arch running plasma 5.19 beta. Operating System: Arch Linux KDE Plasma Version: 5.18.90 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 rc2
Last week I set up a completely new Arch system with Plasma 5.18 and Qt 5.14. I did not copy over any configs from my previous machine and instead set up everything from scratch because I did not want to take over cruft from years gone by. I’ve been using Meta+Letter shortcuts for many years. So I assigned a few shortcuts on the new system. But apart from Meta+E to launch Dolphin, which has been made a Plasma default a short wile ago, none of my own shortcuts worked. So I went back to my old machine and did some digging. I have an old shortcut for Krusader, Meta+R. It is listed in kglobalshortcutsrc in the [khotkeys] section as: {2fd04451-6cb6-4eda-82ca-9bf53c0e7235}=Meta+R,none,Krusader Now I go to the menu editor. The “current shortcut” widget in the menu editor says “None”. I click on the clear button next to it and save my settings. It warns me that the shortcut is assigned to Krusader in System settings. I apply it and save. Now the line I quoted above still exists in kglobalshortcutsrc, but has its Meta+R removed. Instead, a new section has been added in the rc with a _launch= line. And now the shortcut does not work anymore. So the workaround – until this has been resolved – is to go to Systemsettings → Shortcuts → Custom shortcuts („Eigene Kurzbefehle“ in German) and add them there under the KMenuEdit tree node.
*** Bug 422887 has been marked as a duplicate of this bug. ***
Seems like this is predominately affecting 3rd-party apps. Can reproduce with GIMP for example.
*** Bug 423089 has been marked as a duplicate of this bug. ***
*** Bug 422752 has been marked as a duplicate of this bug. ***
*** Bug 415183 has been marked as a duplicate of this bug. ***
*** Bug 413911 has been marked as a duplicate of this bug. ***
*** Bug 422913 has been marked as a duplicate of this bug. ***
*** Bug 418753 has been marked as a duplicate of this bug. ***
I can confirm that this is not working for 3rd-party apps whose launch shortcuts are set in the global shortcuts KCM.
I can confirm that global shortcuts thing happens here too, and I'd say that was back in Plasma 5.18 too. Using KMenuEdit to set those global shortcuts failed just the same.
A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kglobalaccel/-/merge_requests/2
As hinted in https://invent.kde.org/frameworks/kglobalaccel/-/merge_requests/2 after I created a ~/.local/share/kglobalaccel directory, on my machine everything started working fine! So until that merge request is accepted, you can manually create the ~/.local/share/kglobalaccel directory to try to fix the issue.
(In reply to Alexander Popel from comment #20) > As hinted in > https://invent.kde.org/frameworks/kglobalaccel/-/merge_requests/2 > after I created a ~/.local/share/kglobalaccel directory, on my machine > everything started working fine! > > So until that merge request is accepted, you can manually create the > ~/.local/share/kglobalaccel directory to try to fix the issue. I can confirn that your workaround works on neon unstable. Thank you.
*** Bug 417495 has been marked as a duplicate of this bug. ***
I can confirm as well that creating the ~/.local/share/kglobalaccel directory fixed everything for me - before this, I was getting a weird "_launch" text instead of the standard "Launch this program" and all of the other assignable shortcut things. I just had to do mkdir ~/.local/share/kglobalaccel and everything works as expected.
Git commit 215d325972c32f35ad004764ad0bccb40f3aba61 by Méven Car. Committed on 15/07/2020 at 13:43. Pushed by meven into branch 'master'. Resolve service files from applications folder This efficively makes installing desktop files to `prefix/share/kglobalaccel` unnecessary. FIXED-IN: 5.73 CC @marco @ngraham Bug was introduced in e5fa5cbc4fa7ebb96a2ec7803e2963038e3bf1a6 M +1 -1 src/runtime/kserviceactioncomponent.cpp https://invent.kde.org/frameworks/kglobalaccel/commit/215d325972c32f35ad004764ad0bccb40f3aba61
Git commit 3514beccfe8c71233d58ec51aa813112db8a03da by Méven Car. Committed on 15/07/2020 at 13:44. Pushed by meven into branch 'master'. kcm_keys: clean copying of desktop files to kglobalaccel data dir M +0 -2 kcms/keys/kcm_keys.cpp https://invent.kde.org/plasma/plasma-desktop/commit/3514beccfe8c71233d58ec51aa813112db8a03da
The merge request regressed on appllications that installed on share/kglobalaccel and will be reverted. Sorry about that. :/
Git commit cfdbf5e629391dd2475193495637df2919658b2b by Aleix Pol. Committed on 17/07/2020 at 18:32. Pushed by apol into branch 'master'. Revert "Resolve service files from applications folder" This reverts commit 215d325972c32f35ad004764ad0bccb40f3aba61. This stopped finding krunner.desktop which is currently in share/kglobalaccel. Installing it elsewhere wouldn't make a difference because we need to be backwards compatible. A good way around that would be to check both directories. M +1 -1 src/runtime/kserviceactioncomponent.cpp https://invent.kde.org/frameworks/kglobalaccel/commit/cfdbf5e629391dd2475193495637df2919658b2b
The suggestion to add kglobalaccel directory made no difference at all. Please address this issue. It is hard to believe that it was allowed to get through in the first place. Something that has worked flawlessly for years has suddenly stopped functioning. It almost seems deliberate. I report problems to you people and you do nothing but look for someone else to blame. FIX THE ISSUE! IT IS REAL! As I stated this is a fresh install. Brand new and broken.
*** Bug 424576 has been marked as a duplicate of this bug. ***
A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kglobalaccel/-/merge_requests/4
@cor People are working on free software, they are doing it for free, they want to do their best and their work helps many others. This is not how you "repay" them or motivate them. So, please, be considerate.
Can confirm creating the ~/.local/share/kglobalaccel directory resolves the issue for now. Thanks for the easy workaround @Alexander Popel. For anyone still having trouble, I needed to remove and re-add the applications and shortcuts before they started working.
*** Bug 425696 has been marked as a duplicate of this bug. ***
Why don't the developers revert the instructions since the shortcuts demon works perfectly?
Still reproducible on Plasma 5.19.4. It's been more than three months, but still not fixed :(
Git commit 628c0c40147338c2dcd53c1c56af1148204e5d2e by Méven Car. Committed on 23/08/2020 at 19:33. Pushed by ngraham into branch 'master'. Load service files for shortcuts for applications data dir as fallback FIXED-IN: 5.74 M +23 -13 src/runtime/kserviceactioncomponent.cpp M +1 -1 src/runtime/kserviceactioncomponent.h https://invent.kde.org/frameworks/kglobalaccel/commit/628c0c40147338c2dcd53c1c56af1148204e5d2e
I come from here: https://bugs.kde.org/show_bug.cgi?id=417495 Not only has this never been fixed, it is even worse. KDE Menu Editor won't even let me enter new combinations keys. So, what to do? Using KDE 5.76.0 from KDE Neon (Testing)
Works for me. I would recommend filing a new bug report.
It's still happening. I can't assign new custom shortcuts to 3rd party apps in a fresh install. SOFTWARE/OS VERSIONS Operating System: KDE neon User Edition KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2
Can you please file a new bug report? The fact that it works for me makes me think that you're affected by a different bug or else there is a local configuration issue at play.
Apparently the new problem that I have where it is not possible to enter new shortcuts is the same as this report: https://bugs.kde.org/show_bug.cgi?id=430388 Regarding previous reports where keyboard shortcuts for third-party apps/scripts do not work, some of the reports about it had been closed as duplicates to this one, but had never actually been resolved. When the new bug is fixed and I can continue testing, I may open a new report about the old problem if it continues to occur.
That bug report is about the "Custom Shortcuts" page in System Settings, not the system used by the "Shortcuts" page and KMenuEdit.
Had the same wrong behavior after a fresh - not further updated - install of KDE NEON 5.20 german version where I have not even been able to set a shortcut for a quickstart of an application, not in the menu editor and not in Settings > shortcuts: I activated the shortcut field but my keyboard input was not recorded. After install of all automatic upcoming updates now I have KDE-Plasma-Version: 5.20.5 KDE-Frameworks-Version: 5.78.0 QT-Version: 5.12.2 Kernel-Version: 5.4.0-58-generic and the problems are gone. For Kubuntu 20.04 LTS after a fresh install and after installing all updates the faulty behavior I had was - it is possible to setup a shortcut for an application in menu editor - and in Settings > Shortcuts - but the application does not start This error was with all kind of shortcut (Shift-x, Alt-X, Ctrl-x and kombinations). I received a hint in Kubuntuforums.net there was the same faulty behavior some years ago in an older version of Kubuntu and followed the resolve action: - not a must but best practice: delete all your already setup application shortcuts - go to "~/.config/kglobalshortcutsrc" and rename this e.g. to "~/.config/kglobalshortcutsrc_org" - reboot the system - check the file has been recreated and for me from the on on two differnts notebooks this fixed the problem. Hope this helps ...