Bug 497577 - Global hotkeys are depended on keyboard language
Summary: Global hotkeys are depended on keyboard language
Status: RESOLVED DUPLICATE of bug 453661
Alias: None
Product: kwin
Classification: Plasma
Component: input (show other bugs)
Version: 6.2.4
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-16 21:24 UTC by Damglador
Modified: 2024-12-29 01:56 UTC (History)
3 users (show)

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 Damglador 2024-12-16 21:24:26 UTC
SUMMARY
Creating a global shortcut with a certain keyboard layout may determine if it'll actually activate if you hit the same keys, but with a different keyboard layout.

STEPS TO REPRODUCE
1. Get Ukrainian and English US keyboard layouts
2. Switch to Ukrainian layout
3. Go to shortcut settings of Plasma and add a custom keyboard shortcut, let's say Meta+S. It will display Meta+I
4. Switch to English US and try to activate this keyboard shortcut 

OBSERVED RESULT
The shortcut created on Ukrainian keyboard layout won't trigger if current layout is English

EXPECTED RESULT
Global shortcut shouldn't be dependend on keyboard layouts

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.2.4
KDE Frameworks Version:  6.8.0
Qt Version: 6.8.1

ADDITIONAL INFORMATION
This may be an intentionall behaviour, but imo it's pretty weird if it is. I would understand if it was persistent, but for example Meta+S with English layout will trigger on Ukrainian layout, but not the other way around. But for example Meta+` seems to be fully tied to keyboard layout, so I have to create one shortcut on Ukrainian and one on English for it to always work.
Comment 1 John Kizer 2024-12-29 01:56:50 UTC
Hi - I believe this issue falls under an overarching issue around how to handle hotkey/shortcut assignments when multiple keyboard layouts are involved, so I'm linking this into the Bugzilla ticket with the most context and activity (including references to upstream Qt work).

Thanks!

*** This bug has been marked as a duplicate of bug 453661 ***