I'm long time KDE user (since 1.x) but for the last years I was using mostly debian/ubuntu.

In there, in system settings, under shortcuts, I had "Custom shortcuts" settings, which allowed me to add shortcuts to arbitrary things - command, dbus calls, and so on.

Lately I got laptop with newest Fedora (36). Based on "about this system" it has:

• KDE Plasma version 5.25.4
• KDE Frameworks Version 5.97.0
• QT Version 5.15.5

and it runs on Wayland (not sure if it matters).

The thing is that the whole "custom shortcuts" part is missing.

I made screenshots from both systems to show the problem, not sure if I can post links here, but here it goes: https://imgur.com/a/koJorvX - it has both version of the settings from Fedora and from Ubuntu. In case the link got censored, it's: 'imgur, dot, com, slash, "a", slash, koJorvX' over https.

Do I need to install something? Enable something? What am I missing?

It seems like someone has already have a similar problem on Fedora. Did you try this solution?.

Code: Select all

dnf install khotkeys

Let me know if it worked.

Unfortunately it didn't - I had khotkeys installed before, have it now, rebooted, but still no config.

Code: Select all

=# rpm -qa | grep -i hotk
khotkeys-5.25.4-1.fc36.x86_64


The suggested solution says about trying

Code: Select all

kcmshell5 khotkeys

, for me it doesn't do anything too interesting either:

Code: Select all

=$ kcmshell5 khotkeys
QSocketNotifier: Can only be used with threads started with QThread
Could not find module 'khotkeys'. See kcmshell5 --list for the full list of modules.


fill list is long, but searching for key shows:

Code: Select all

=# ksmshell5 --list | grep -i key
kcm_keyboard                   - Keyboard Hardware and Layout
kcm_keys                       - Configure Keyboard Shortcuts
kcm_virtualkeyboard            - Select which virtual keyboard to use
webshortcuts                   - Configure web search keywords
kcm_hotkeys                    - Configure Input Actions settings
webshortcuts                   - Configure web search keywords


According to this reply, the line

Code: Select all

QSocketNotifier: Can only be used with threads started with QThread

seems harmless. But the line

Code: Select all

Could not find module 'khotkeys'. See kcmshell5 --list for the full list of modules.

says that for some reason it can't execute the module although it is present.

kcmshell5 khotkeys --> Calls --> kcm_hotkeys

chiefbromden wrote:According to this reply, the line

Code: Select all

QSocketNotifier: Can only be used with threads started with QThread

seems harmless. But the line

Code: Select all

Could not find module 'khotkeys'. See kcmshell5 --list for the full list of modules.

says that for some reason it can't execute the module although it is present.

kcmshell5 khotkeys --> Calls --> kcm_hotkeys

Yeah, but it clearly is there in the list.

Any idea on how to debug it further?

You can ask the developers or report an issue here.
You will have to explain the problem again.

Let me know if you fix it.

Filled a bug https://invent.kde.org/plasma/kde-cli-tools/-/issues/2 - but I'm kinda confused - why should it be in kde-CLI-tools? isn't CLI "command line interface"?

So, I was told that it is intentional: https://bugs.kde.org/show_bug.cgi?id=455444

But it leads to next question: How do I create script shortcut "assignment"?

In the bug there is this statement:

> You make a script file and then assign a global shortcut to run it. It's a little clumsy, I know. We will improve it in the future.

I can write any script I want, no problem, but where/how do I make this assignment?

OK. Nate replied in the bugs thread with this info:

> Click the "Add Application" button on the Shortcuts page, click the "open file dialog" button in the dialog that appears, and navigate to the script file.

Link: https://invent.kde.org/plasma/kde-cli-t ... ote_514583

Hi @depesz

Sorry I lead you to the wrong place, I'm pretty new around here. I read both threads and I understand Nathan's position, sometimes you have to be wise and understand that not every complain has to be satisfied: on one side, the developer has frustrated users; on the other implementation decisions. Xorg is a well established technology; Wayland, on the other hand is relatively new. The latter is meant to be the replacement of the former, so these "missing functionality" problems can be common on the transition.

I'm glad that you fix your problem.

Cheers.