8000 Keyboard layout mismatch · Issue #1433 · pop-os/cosmic-comp · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Keyboard layout mismatch #1433

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
zanaviska opened this issue May 25, 2025 · 1 comment
Open

Keyboard layout mismatch #1433

zanaviska opened this issue May 25, 2025 · 1 comment

Comments

@zanaviska
Copy link

I am using Pop-os! 24.04 since alpha 1. Back in the days the only way to change keyboard layout with keyboard shortcut, was to modify .config/cosmic/com.system76.CosmicComp/v1/xkb_config. So I added shortcut for "win + space" shortcut to modify layout. Time has passed, and now "win + space" is native shortcut for keyboard layout change.

Bug

On my system there are 2 different shortcuts binded to "win + space":

  • native shortcut for keyboard layout change
  • custom shortcut for keyboard layout change

As a result for that displayed(in applets and settings) language could be language1, but actual input layout map is taken from language2.

steps to reproduce

  1. add "win+space" shortcut(options: Some(",grp:win_space_toggle"),) into .config/cosmic/com.system76.CosmicComp/v1/xkb_config
  2. add english keyboard as primary
  3. add another keyboard as alternative(let's say ukrainian(ua))
  4. activate ukrainian keyboard via appets
  5. restart OS
  6. press "win +space".
  7. try to type text somewhere. Text will be different from expected

workaround

remove custom shortcut from .config/cosmic/com.system76.CosmicComp/v1/xkb_config

thoughts about

Even thou, I found a workaround, bug still exist. It shouldn't be high on priority list, but it indicates, that system have incorrect behaviour in some case
1 additional reason to post is to have a written solution for everyone who was struggling with it as me
@zanaviska
Copy link
Author

Well, since there is a workaround, maintainers could close the issue, or keep it open, if they want fix it themselves. I couldn't fix it myself, so I found a workaround

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zanaviska
0