Dennis HilkLinux Fix LabDE

Desktop, X11 & Wayland

Plasma global shortcuts stop responding

One broken shortcut can be a conflicting assignment; many broken shortcuts may reflect session integration. Inspect the affected component first.

Editorial source review: Start with the evidenceShare this guide
On this page
  1. Symptoms & scope
  2. Possible causes
  3. Diagnose safely
  4. Evidence-guided next steps
  5. References & review
  6. Related problems

Symptoms & scope

  • A global key combination no longer activates its assigned action.
  • Shortcuts work after leaving a VM or remote-desktop window.

Relevant environment

KDE Plasma; global shortcuts differ from application-local shortcuts, and a VM or remote desktop can capture input.

Possible causes

These are possible explanations, not a confirmed diagnosis. Several independent faults can coexist.

  • The shortcut may be assigned twice or disabled for its component.
  • Input capture or a missing user-bus component may prevent dispatch.

Diagnose safely

Run one command at a time in the relevant session. Read the explanation first. Uppercase placeholders need your own values; tools and privileges vary by distribution. These commands are displayed here and never executed by the website.

Check 1

Reads common component assignments; narrow the search to the affected action. The file can be absent before custom settings exist.

rg -n "krunner|kwin|plasmashell|Volume|mute|launch" "$HOME/.config/kglobalshortcutsrc"

Interpret the result: An empty or unexpected assignment supports a settings problem. This file alone does not show whether another application currently captures the keys.

Check 2

Reads existing user-bus service names as the Plasma account without altering services.

busctl --user list

Interpret the result: Look for the expected KDE session services. Presence does not prove shortcut delivery; if bus connectivity itself fails, diagnose the session bus before rebinding keys.

Evidence-guided next steps

Repair only the affected shortcut assignment

If the action’s assignment is missing or conflicts, export the current shortcut scheme in System Settings, then reset or reassign only that action in Shortcuts. Distinguish its global component entry from the application’s own shortcut dialog.

Precautions: Do not delete the entire kglobalshortcutsrc. Avoid overwriting familiar accessibility or assistive-tool bindings.

Recovery / rollback: Import the saved scheme or restore the recorded assignment for that one action.

Did this solution help you?

Share this solution#

Release input captured by a VM or remote session

If shortcuts fail only while a guest or remote window owns input, release its keyboard grab using that application’s documented host key and disable capture only where needed. If all applications remain affected and bus errors are present, save work and relogin to refresh the Plasma session.

Precautions: A session restart closes unsaved windows; a guest’s capture behavior is not repaired by global keyboard remapping.

Recovery / rollback: Reenable the original capture setting in the guest/remote application or restore the saved session-start configuration.

Did this solution help you?

Share this solution#

References & review

This guide was prepared from primary project or distribution sources and reviewed on the date shown. This is an editorial source check, not evidence that a fix was reproduced on your hardware. Diagnostic log examples are synthetic fixtures. Version-dependent details must be checked against your installed release.