-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
turning monitor off and on will revert keyboard settings #1293
Comments
I have the same issue sometimes. I use a regular desktop and have the keyboard plugged straight into the back of the pc. It also occasionally reverts after updating packages. |
Possibly related to #1265, I also have a problem where by I have to pull it out and plug it in twice for the remap settings to take affect. |
Interesting. I think this has happened to me since the It's not totally obvious to me what is going on. Perhaps when there is a udev update or a related package. As for why this happens with a USB monitor, I'm not sure either, or how to sidestep this problem. If someone with a USB monitor runs a |
I just wanted to clarify that I did not mean my monitor is only connected to my laptop using a USB. I suspect that the script may not be detecting the keyboard as a new device because it has already been connected once before, and the keyboard reverts to its original settings when the laptop is bought back from suspension. Perhaps there is a way we can make these keyboard settings permanent? Perhaps adding a hook that runs after the PC is bought back from suspension? If you let me know what I can do to further debug the problem I will be happy to report back |
Just want to add, in regards to having this issue after updating, the keyboard settings revert only when the device configuration manager is reloaded as part of the post-transaction hooks. |
Situation / Problem
remaps
andremapd
seem to revert.Reproducing this
remapd
script still running in the background.I want to note that I don't think the laptop is actually being put to sleep, I think it is just the monitor being put on stand by whenever the power button is pressed.
The text was updated successfully, but these errors were encountered: