Created attachment 183408 [details] Logs and debug output for kglobalaccel issue (strace + env setup) After upgrading to Plasma 6 (currently 6.4.3 on Arch Linux), the KDE Global Shortcuts server (`kglobalaccel`) does not work under my main user account. Observed Behavior: - `plasma-kglobalaccel.service` shows as inactive (dead) immediately after starting, even though it returns `SUCCESS`. - Global shortcuts do not function at all (e.g., volume keys, meta shortcuts, etc.). - No `kglobalaccel` process stays alive. - Starting manually with `/usr/lib/kglobalacceld --replace --nofork` exits silently with no visible effect. - Logs show no errors, even under debugging environment. - `~/.config/kglobalshortcutsrc` and related configs appear valid and were tested by copying from a working user. Troubleshooting Attempts: - Confirmed DBus address and environment are set correctly. - Compared working state with a new user account: new user has working `kglobalaccel`. - No `~/.local/share/kglobalaccel/` exists for either account. - Tried full reset of Plasma config (`~/.config/` files like `plasmarc`, `kdeglobals`, etc.) — issue persists. - Verified wallpaper and visual settings restored; panel restored manually. - Verified with `systemctl --user status plasma-kglobalaccel.service` that it is always inactive (dead). - Performed `strace` and captured session logs (see attachments). - The problem is fully reproducible every login under the main user. ### Versions: - plasmashell: `6.4.3` - kded6: `6.16.0` - Arch Linux kernel: `6.15.7-arch1-1` Attachments: I have attached a `.tar.gz` archive containing: - `kglobalaccel_strace.txt` (strace log of attempted manual start) - `debug_env.sh` (debug environment attempt) Let me know if further logs or a screencast would help. Thank you for your work on KDE!
The kglobalacceld process is not supposed to run on Wayland. That's unrelated to any shortcuts not working
Your shortcuts getting lost is likely fixed by https://invent.kde.org/plasma/kglobalacceld/-/merge_requests/72. Let us know if it ever happens again after you upgrade from Plasma 6.4.4 (or later) to any subsequent version of Plasma. Thanks!