Global keyboard shortcuts not working in KDE Plasma 6

morganmay · 2024-03-07 02:30:42

I took the plunge and updated to Plasma 6 today. After the update, global keyboard shortcuts like Alt-Tab are broken. (Per-application shortcuts still work, and Meta launches the application menu as expected.) When I open the Keyboard > Shortcuts tab of System Settings, no shortcuts are displayed and there's an error message:

Failed to communicate with global shortcuts daemon

I haven't been able to find any documentation regarding this error. Searching for the message brought up some old posts indicating that the culprit might be kglobalaccel5. When I tried running kglobalaccel5, I got the error:

kglobalaccel5 may be found in the following packages:
  extra/kglobalaccel 5.35.0-1   /usr/bin/kglobalaccel5

I already have the packages kglobalaccel5 5.115.0-3, kglobalaccel 6.0.0-1, and kglobalacceld 6.0.1-1 installed. None of them actually provide /usr/bin/kglobalaccel5. I tried reinstalling them in case the file was just missing from my system, but no luck. There's no /usr/bin/kglobalaccel or /usr/bin/kglobalacceld, either.

kglobalacceld provides an autostart file (/etc/xdg/autostart/kglobalacceld.desktop) that runs /usr/lib/kglobalacceld. Running this manually accomplishes nothing that I can see. It also provides a service file, /usr/lib/systemd/user/plasma-kglobalaccel.service. Starting this service didn't seem to accomplish anything, either.

I'm stumped. I can't tell if this is a problem with my system or with the current Arch release of Plasma 6. If anyone has any insights to offer, I would really appreciate them. Thanks!

pezz · 2024-03-07 05:00:53

Seeing the same here. kglobalacceld is running but some shortcuts I set simply don't work.

V1del · 2024-03-07 10:13:56

Did you reboot after updating? If you just updated and haven't rebooted or at least restarted plasma yet a bunch of libs will still look for the old dependencies.

morganmay · 2024-03-07 18:31:32

V1del wrote:

Did you reboot after updating? If you just updated and haven't rebooted or at least restarted plasma yet a bunch of libs will still look for the old dependencies.

Yes, I have rebooted multiple times in the process of troubleshooting this.

seth · 2024-03-07 21:35:41

Any suspective processes in https://wiki.archlinux.org/title/Core_d … _core_dump or the system journal?

There's no /usr/bin/kglobalaccel or /usr/bin/kglobalacceld, either.

https://archlinux.org/packages/extra/x8 … balacceld/

pacman -Qikk kglobalacceld
sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files'

aocab · 2024-03-08 14:23:04

Not sure if it is related but I just ran into this when I re-enabled sddm.
I disabled it because the machine was locking up after the screen turned off after a recent update.
I re-enabled to test when I saw sddm was updated.
After disabling sddm the global keyboard shortcuts are working again.

V1del · 2024-03-08 14:49:49

SDDM has absolutely no relation on this once the session has started. Unless you have some very funky sddm config.

seth · 2024-03-08 15:09:53

The way the session is started might impact the running state of kglobalacceld?
How did you start KDE when not using SDDM and what's its status w/ and w/o using SDDM?

aocab · 2024-03-08 15:19:37

No funky sddm config. I only added a background image to the config file.

KDE was started using startx from .bash_profile after logging in at the terminal.

[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && exec startx

did you mean the status of the user session when not using sddm?

$ loginctl show-session $XDG_SESSION_ID
Id=1
User=1000
Name=alpha
Timestamp=Fri 2024-03-08 08:16:34 CST
TimestampMonotonic=12327595
VTNr=1
Seat=seat0
TTY=tty1
Remote=no
Service=login
Scope=session-1.scope
Leader=506
Audit=1
Type=tty
Class=user
Active=yes
State=active
IdleHint=yes
IdleSinceHint=1709907394000000
IdleSinceHintMonotonic=11748059
LockedHint=no

status of the user session when using sddm

$ loginctl show-session $XDG_SESSION_ID
Id=2
User=1000
Name=alpha
Timestamp=Fri 2024-03-08 09:20:38 CST
TimestampMonotonic=8915597
VTNr=1
Seat=seat0
TTY=tty1
Remote=no
Service=sddm
Desktop=KDE
Scope=session-2.scope
Leader=636
Audit=2
Type=wayland
Class=user
Active=yes
State=active
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0
LockedHint=no

PS. just noticed type=wayland on the user session status when using sddm.
Logged out and made sure to select X11 and the issue is gone.

Last edited by aocab (2024-03-08 15:26:33)

seth · 2024-03-08 15:36:38

Logged out and made sure to select X11 and the issue is gone.

What explains the different behavior, but I meant whether the kglobalaccel process is running (on plasma/wayland)

aocab · 2024-03-08 17:42:39

kglobalacceld is not running on plasma/wayland. It is running on plasma/x11.

I did come across this old article (2015) about global shortcut handling in a plasma/wayland
have not read it yet. and not sure if the info still applies

https://blog.martin-graesslin.com/blog/ … d-session/

seth · 2024-03-08 22:09:30

If the WM is supposed to handle the global shortcuts, it'll be the disfunctional part.
Can you explicitly start kglobalacceld in a wayland session (preferably from an interactive shell so it can yell errors at you)
There's an xdg autostart entry and it limits KDE, nothing about wayland. And it's a hard dep of kwin

morganmay · 2024-03-09 01:48:29

Things I have learned since my last post:

It's more than just global hotkeys that aren't working. Other issues include multi-display settings not working, the system tray not appearing (causing many of the apps that use it to crash), and kdeconnect refusing to pair.
These problems go away when I log in using X11, so it's definitely a Wayland-related problem.
journalctl shows a bunch of different processes throwing variations of this error message:
```
Failed to create wl_display (No such file or directory)
```
Some have the additional message:
```
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: minimalegl, minimal, offscreen, linuxfb, wayland-egl, wayland, vkkhrdisplay, xcb, vnc, eglfs.
```
Affected processes include kcminit_startup, kded6, plasmashell, kactivitymanagerd, org_kde_powerdevil, xdg-desktop-portal-kde, polkit-kde-authentication-agent-1, kscreen_backend_launcher, kdeconnectd, DiscoverNotifier, and kalendarac.

Several processes also threw this error:

Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name is not activatable")

I reinstalled every package that was surfaced by
```
sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files'
```
This didn't seem to fix anything.

seth · 2024-03-09 08:06:40

What's the output of

printenv

Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name is not activatable")

That's your global shortcuts.

pezz · 2024-03-09 08:51:49

seth wrote:

What's the output of
printenv
That's your global shortcuts.

Hey seth, love your work.

But can you explain what you're getting at here?

I just want a single shortcut for Meta + Z to expose workspaces so I can move windows around, but the hotkey handling seems broken except for some built-in things.

seth · 2024-03-09 08:59:47

This application failed to start because no Qt platform plugin could be initialized.

Might be because one is enforced by an environment variable (notably QT_QPA_PLATFORM, but there might be other issues - the "unknown unknowns")

The xdg autostart and apparently various clients try to start kglobalacceld but it seems to fail (for unkown reasons)
The global shortcut feature might or not be duplicated in kwin in a wayland session (what sounds dumb) or exists just partly in the compositor and kglobalaccled still plays a major role.
That's why

seth wrote:

Can you explicitly start kglobalacceld in a wayland session (preferably from an interactive shell so it can yell errors at you)

Edit

I just want a single shortcut for Meta + Z to expose workspaces

Does the feature still exist in X11?
https://bbs.archlinux.org/viewtopic.php?id=293522

Last edited by seth (2024-03-09 09:00:55)

pezz · 2024-03-09 09:15:33

Maybe I missed something, but I'm not sure how that other thread helps.

I can actually choose / have chosen the same shortcut I had before Plasma 6 but now it just doesn't work.

https://i.imgur.com/hp8dhkK.png

seth · 2024-03-09 09:34:08

It was just to illustrate that some features might have gone for good.

https://i.imgur.com/hp8dhkK.png

That's a kwin thing, I even doubt it uses global shortcuts for this.
Do other global shortcuts (eg. to open krunner or so) still work?
Have you tried a different activation (hot corner, shortcut that does not involve "Meta" and, in case you're not using a US QWERTY layout (are australian keyboards simply upside down? ) a qwerty-safe shortcut (eg. "Z" and "Y" are prominently swapped on qwertz)

pezz · 2024-03-09 10:04:13

seth wrote:

It was just to illustrate that some features might have gone for good.
(are australian keyboards simply upside down? )

Oi! You havin' a go at me? Heh.

But other keyboard commands like Meta + Shift + Ctrl + (Down or Up arrow) to move maximised windows to another workspace work.

Just nothing I seem to set myself works, and it used to work fine.

Would just like to know how I can achieve the same function now.

seth · 2024-03-09 12:47:34

Did you check that you actually still have multiple workspaces and try whether you can trigger the feature by other means?
(mouse corner and it might have a dbus interface)
Finally a different shortcut.

There're three stages where this can fall apart:
1. the physical keys you press don't produce the expected shortcut (keyboard layout issue)
2. the shortcut isn't handled (possibly kglobalacceld issue, did you check whether the process runs or whether you can start it?)
3. the activated feature doesn exist/malfunctions

You want to run some checks and tests to figure which stage is failing (different activation to rule out 3, kglobalacceld status and a different shortcut - idk what your layout is, but there even different qwerty ones and a main differece is the key left of the "z")

Edit: for all I know you're living in a magical wonderland where the toilets flush the wrong direction, people farm crocogators and battle dropbears on their way to school and work.
I'd never mess around with Aussies

Last edited by seth (2024-03-09 12:48:51)

seth · 2024-03-11 21:27:33

https://bbs.archlinux.org/viewtopic.php … 2#p2156642 alleges that the feature has indeed been scrapped

nicenemo · 2024-03-12 22:18:53

I don't think this is a X11 or wayland issue.
I am running into a similar problem. I am configuring a ZMK firmware based 40% keyboard with official HID specification compliant application launch layer.
The key for calculator did work on Plasma 5 it no longer works under 6. It is not even recognized if you try to register it in the shortcuts configuration. Some other keys like Messenger or Browser are recognized.
It does not matter if you run Plasma 6 under X11 or Wayland. The calculator key is authomatically recognized under Windows 10.
Showkeys from the console shows the correct codes.
The Calculator key is also recognized in the QMK online keyboard tester. Most other keys are not recognized when I use the Chrome or Firefox browser.
Those keys are mapped to code 0. in both browsers while showkeys shows the correct codes.

QMK keyboard tester:https://config.qmk.fm/#/test
Over 400 different application lauch keys that I can configure: https://github.com/zmkfirmware/zmk/blob … id_usage.h
Aliases as defined by ZMK https://github.com/zmkfirmware/zmk/blob … zmk/keys.h
My custom keymap for my Cornish-Zen https://github.com/nicenemo/zmk-config/ … zen.keymap

seth · 2024-03-12 22:28:28

Just to be clear, you're only concerning the behavior of the calculator (which doesn't seem to be bound nor be bindable to a global shotcut), b/c "other keys are not recognized when I use the Chrome or Firefox browser" is perfectly expectable if those are bound to global shortcuts, but where an unrelated problem if they're not (and your keyboard just doesn't work in general)

Log into a plasma/X11 session (wayland won't work for this) and run "xev -event keyboard", press the calculator key and post the output.

nicenemo · 2024-03-13 16:48:57

The calculator key, an example, was bindable in the latest Plasma 5 version.

What makes you think my keyboard does not work? It seems to work fine for the normal alpha number and many other keys on multiple operating systems, both on bluetooth and via USB.

I logged into Plasma X11. The xev tools was not installed. I installed xorg-xev first.
I ran xev -event keyboard

Pressing the calculator key gives the XF86Calculator keycodes for pressed an released as it should.

KeyPress event, serial 32, synthetic NO, window 0x4800001,
root 0x52b, subw 0x4800002, time 9436256, (33,43), root:(903,485),
state 0x0, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0x4800001,
root 0x52b, subw 0x4800002, time 9436312, (33,43), root:(903,485),
state 0x0, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES,
XLookupString gives 0 bytes: XFilterEvent returns: False

Update: it cannot be bound in Plasma 6.x under X11 either.
Anything else I can do to help?

Last edited by nicenemo (2024-03-13 16:51:26)

seth · 2024-03-13 17:00:28

What makes you think my keyboard does not work?

Doesn't - I just pointed out that global shortcuts won't show up in clients systematically, but if you cannot record a whole bunch of keys that are not bound to anything, there might be an issue w/ the keyboard.

The calculator key however shows up perfectly fine, so this would be a pure KDE issue.
=> bugs.kde.org
(It btw. should™ not if it was bound to anything anywhere somehow)

Can you bind Ctrl+XF86Calculator ? (Just trying to understand where the bug might be)

Arch Linux

#1 2024-03-07 02:30:42

Global keyboard shortcuts not working in KDE Plasma 6

#2 2024-03-07 05:00:53

Re: Global keyboard shortcuts not working in KDE Plasma 6

#3 2024-03-07 10:13:56

Re: Global keyboard shortcuts not working in KDE Plasma 6

#4 2024-03-07 18:31:32

Re: Global keyboard shortcuts not working in KDE Plasma 6

#5 2024-03-07 21:35:41

Re: Global keyboard shortcuts not working in KDE Plasma 6

#6 2024-03-08 14:23:04

Re: Global keyboard shortcuts not working in KDE Plasma 6

#7 2024-03-08 14:49:49

Re: Global keyboard shortcuts not working in KDE Plasma 6

#8 2024-03-08 15:09:53

Re: Global keyboard shortcuts not working in KDE Plasma 6

#9 2024-03-08 15:19:37

Re: Global keyboard shortcuts not working in KDE Plasma 6

#10 2024-03-08 15:36:38

Re: Global keyboard shortcuts not working in KDE Plasma 6

#11 2024-03-08 17:42:39

Re: Global keyboard shortcuts not working in KDE Plasma 6

#12 2024-03-08 22:09:30

Re: Global keyboard shortcuts not working in KDE Plasma 6

#13 2024-03-09 01:48:29

Re: Global keyboard shortcuts not working in KDE Plasma 6

#14 2024-03-09 08:06:40

Re: Global keyboard shortcuts not working in KDE Plasma 6

#15 2024-03-09 08:51:49

Re: Global keyboard shortcuts not working in KDE Plasma 6

#16 2024-03-09 08:59:47

Re: Global keyboard shortcuts not working in KDE Plasma 6

#17 2024-03-09 09:15:33

Re: Global keyboard shortcuts not working in KDE Plasma 6

#18 2024-03-09 09:34:08

Re: Global keyboard shortcuts not working in KDE Plasma 6

#19 2024-03-09 10:04:13

Re: Global keyboard shortcuts not working in KDE Plasma 6

#20 2024-03-09 12:47:34

Re: Global keyboard shortcuts not working in KDE Plasma 6

#21 2024-03-11 21:27:33

Re: Global keyboard shortcuts not working in KDE Plasma 6

#22 2024-03-12 22:18:53

Re: Global keyboard shortcuts not working in KDE Plasma 6

#23 2024-03-12 22:28:28

Re: Global keyboard shortcuts not working in KDE Plasma 6

#24 2024-03-13 16:48:57

Re: Global keyboard shortcuts not working in KDE Plasma 6

#25 2024-03-13 17:00:28

Re: Global keyboard shortcuts not working in KDE Plasma 6

Board footer