https://bugs.kde.org/show_bug.cgi?id=522581
Bug ID: 522581
Summary: kglobalaccel does not stay running at session start →
global shortcuts non-functional (ctrl ,alt ,ESC ,
DEL..)
Classification: Plasma
Product: plasmashell
Version First 6.7.0
Reported In:
Platform: Neon
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Keyboard Indicator widget
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: 1.0
Created attachment 193988
--> https://bugs.kde.org/attachment.cgi?id=193988&action=edit
auto-generated by CLAUDE via SSH , because i can't see anything into MONITOR
(until RE-BOOT)
## Issue 3 — `kglobalaccel` does not stay running at session start → global
shortcuts non-functional
**Component:** `kglobalaccel` / `plasma-workspace`
### Summary
`plasma-kglobalaccel.service` (Type=dbus, `BusName=org.kde.kglobalaccel`)
starts and
**immediately exits with `status=0/SUCCESS`** at session start (within ~21 ms
CPU). The
bus name `org.kde.kglobalaccel` is never registered, so no global shortcuts
work
(Alt+Tab, Meta/KRunner, Ctrl+Alt+Del, etc.) for the entire session.
### Steps to reproduce
1. Log in to a Plasma Wayland session on the setup above.
2. Observe: `systemctl --user status plasma-kglobalaccel.service` →
`Active: inactive (dead) ... code=exited, status=0/SUCCESS`.
3. Try any global shortcut (Alt+Tab, Meta, Ctrl+Alt+Del) → nothing happens.
### Expected
`kglobalacceld` runs for the whole session and registers
`org.kde.kglobalaccel`; global
shortcuts work.
### Actual
```
$ systemctl --user status plasma-kglobalaccel.service
○ plasma-kglobalaccel.service - KDE Global Shortcuts Server
Loaded: loaded (.../plasma-kglobalaccel.service; static)
Active: inactive (dead) ... code=exited, status=0/SUCCESS
Process: <PID> ExecStart=.../kglobalacceld (code=exited, status=0/SUCCESS)
CPU: 21ms
```
Manual launch keeps the daemon alive (it does not self-exit), suggesting the
failure is in
systemd activation/environment, not the daemon itself. Likely
`WAYLAND_DISPLAY`/`DISPLAY` are
not present in the systemd user manager environment at dbus-activation time
(`systemctl --user import-environment` is needed before the unit can acquire
the bus name).
### Workaround
`systemctl --user import-environment DISPLAY WAYLAND_DISPLAY XDG_SESSION_TYPE`
then start the
unit — but this only helps if done before `kwin` starts; a session already
running without
`kglobalaccel` does not regain shortcuts without a fresh login.
---
## How the issues were discovered (context, not part of the bug)
An Electron-based IDE (`antigravity-ide`, Google Antigravity) running under the
Wayland
session entered a state where the cursor was hidden and keyboard input / global
shortcuts
stopped working (pointer/keyboard grab not released). While attempting
recovery, the
maintainer restarted `plasma-kwin_wayland.service` via systemctl, which
triggered
**Issue 1** (session crash), which exposed **Issue 2** (black-screen login) and
**Issue 3** (kglobalaccel). The Electron app's grab behavior itself is not a
KDE bug, but it
was the trigger that surfaced the three KDE-side defects above.
---
## Useful commands to attach to the reports
```bash
# Versions
plasmashell --version; kwin_wayland --version; uname -r; cat /etc/lsb-release
# DRM / GPU layout
lspci | grep -iE 'VGA.*AMD'
for c in /sys/class/drm/card*-*; do
n=$(basename "$c"); echo "$n status=$(cat $c/status) enabled=$(cat
$c/enabled)"
done
sudo fuser -v /dev/dri/card2 # who holds DRM master
# kglobalaccel
systemctl --user status plasma-kglobalaccel.service
gdbus call --session --dest org.freedesktop.DBus --object-path / \
--method org.freedesktop.DBus.ListNames | tr ',' '\n' | grep -i kglobalaccel
# Logs
journalctl --user -b --since "today" | grep -iE
'kwin|kglobalaccel|sddm|drm|core-dump'
journalctl -b | grep -iE 'sddm|drm|amdgpu'
coredumpctl list
```
--
You are receiving this mail because:
You are watching all bug changes.
