Skip to content
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.

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

Keyboard layout set in xkb-config doesn't get loaded until I open and save xkb-config manually #285

Closed
leviport opened this issue Jan 23, 2024 · 2 comments · Fixed by #286

Comments

@leviport
Copy link
Member

I've been setting my keyboard layout to Dvorak in .config/cosmic/com.system76.CosmicComp/v1/xkb-config with the following line:

(rules:"",model:"",layout:"us",variant:"dvorak",options:Some("altwin:swap_alt_win,caps:ctrl_modifier,compose:ralt"))

Fairly recently, I noticed that my keyboard was reverting to Qwerty after reboots. I also discovered that opening xkb-config in nano and simply writing the file without making changes re-activated my hipster layout.

@leviport
Copy link
Member Author

I forgot to add that I also recreated this issue on a fresh COSMIC DE install on a lab unit, and without all of the options: in the line above. I was suspicious that those might have been messing something up, but they do not appear to be a the cause.

ids1024 added a commit that referenced this issue Jan 23, 2024
It seems these two lines were omitted in
#254, so it was reading the
"xkb_config" settings at startup, then watching "xkb-config".

The other settings seem to be consistent.

This should fix #285 (though
it will also be necessary to edit "xkb_config", rather than the old
file.
ids1024 added a commit that referenced this issue Jan 23, 2024
It seems these two lines were omitted in
#254, so it was reading the
"xkb_config" settings at startup, then watching "xkb-config".

The other settings seem to be consistent.

This should fix #285 (though
it will also be necessary to edit "xkb_config", rather than the old
file.
@ids1024
Copy link
Member

ids1024 commented Jan 23, 2024

#254 renamed the setting to xkb_config so it could be used with CosmicConfigEntry, which assumes that naming. But it seems it was renamed in one place but not the other, so it was loading xkb_config at startup and then watching for changes in xkb-config.

It would be good to have config work in a more statically typed way to prevent that sort of discrepancy, but anyway, #286 should fix the inconsistency.

Drakulix pushed a commit that referenced this issue Jan 24, 2024
It seems these two lines were omitted in
#254, so it was reading the
"xkb_config" settings at startup, then watching "xkb-config".

The other settings seem to be consistent.

This should fix #285 (though
it will also be necessary to edit "xkb_config", rather than the old
file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants