You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This has been driving me crazy for a long time. Just got annoyed enough when it did it again today.
Context
I regularly use 2 keyboard layouts, and use Alt+Capslock to toggle between them.
Current Behavior
In unknown, but frequent circumstances, my Alt+Capslock shortcut stops working. Opening lxqt-config-input --show-page Keyboard Layout shows that the settings have reverted to the default : US layout only, no shortcut. I have to enter my settings again, apply & save, then continue working until it decides to forget my settings again.
Yet, even when it's reset and the shortcut is broken, my .config/lxqt/session.conf still has this section :
It also happens to me, although in my case it happens when a new package is installed using Pacman or something get upgraded, it's not just the keyboard, but display resolution and touchpad settings.
Here is my System Information
Distribution & Version: Arch Linux
Kernel: 6.5.7
Qt Version: 5.15.11
liblxqt Version: 1.3.0-2
lxqt-config 1.3.0-1
This has been driving me crazy for a long time. Just got annoyed enough when it did it again today.
Context
I regularly use 2 keyboard layouts, and use
Alt+Capslock
to toggle between them.Current Behavior
In unknown, but frequent circumstances, my Alt+Capslock shortcut stops working. Opening
lxqt-config-input --show-page Keyboard Layout
shows that the settings have reverted to the default : US layout only, no shortcut. I have to enter my settings again, apply & save, then continue working until it decides to forget my settings again.Yet, even when it's reset and the shortcut is broken, my
.config/lxqt/session.conf
still has this section :just as it should. I don't know why suddenly the shortcut stops working. I'm not even sure how I could set a 'breakpoint' on this...
Steps to Reproduce (for bugs)
I'm sorry, there's no clear steps to reproduce this. It just happens very often, at unknown times.
System Information
The text was updated successfully, but these errors were encountered: