Bug 510498 - Shortcut capture on X11 inserts imaginary Meta
Summary: Shortcut capture on X11 inserts imaginary Meta
Status: RESOLVED UNMAINTAINED
Alias: None
Product: systemsettings
Classification: Applications
Component: general (other bugs)
Version First Reported In: 6.3.6
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-10-11 16:19 UTC by Kyle Rose
Modified: 2025-10-11 16:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kyle Rose 2025-10-11 16:19:36 UTC
When I try to capture a shortcut like "Alt-v" or "Alt-{" (i.e., Alt-Shift-[), the capture process pulls an extra Meta modifier out of nowhere. I have Meta mapped to Win, and while X11 modifiers and XKB are different beasts, Meta and Alt are on different modifiers (Mod4 and Mod1, respectively). I confirmed with xkbwatch that Alt, Meta, and Shift are completely separate states. This does not happen on Wayland, which correctly sees "Alt-v" or "Alt-{".

STEPS TO REPRODUCE
0. Make sure you have Alt and Meta mapped separately (e.g., with system-settings / Keyboard / Key Bindings / Alt and Win behavior / "Meta is mapped to Left Win")
1. Start Plasma on X11
2. Start system-settings
3. Go to Keyboard -> Shortcuts -> Navigation -> Activate Next Tab
4. Click "+Add"
5. Start with either Shift or Alt, and then hit the other one, and then "["

OBSERVED RESULT
A "Meta+" will appear out of nowhere in the middle of this process.

EXPECTED RESULT
"Alt-{"

SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux 13
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2
Comment 1 Bug Janitor Service 2025-10-11 16:33:40 UTC
Thank you for the bug report!

Debian advises users to not submit bugs upstream (https://www.debian.org/Bugs/Reporting), and Plasma 6.3.6 is no longer eligible for support or maintenance from KDE. It's possible that the issue exists only in Debian at this point.

Could you report the bug to Debian using the report bug utility (https://packages.debian.org/stable/utils/reportbug)? If necessary, the maintainer of the package will forward the bug upstream.
Thanks for understanding!

Thanks again!