turning monitor off and on will revert keyboard settings

[yaaama]

Situation / Problem

• I have a monitor connected to my laptop using a USB cable.
• It allows for a keyboard to be plugged into my monitor instead of having to plug it into my laptop (makes moving my laptop around easier).
• Whenever I turn the monitor off and it is kept off for a while, the keyboard settings set by remaps and remapd seem to revert.

Reproducing this

1. Connect monitor to laptop using USB A to USB B cable (one of those printer cables).
2. Turn the monitor off using the power button (so it goes on stand by)
3. Wait for some time, it does not seem to happen instantly
4. Turn the monitor back on
5. Keyboard settings should magically disappear despite the 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.

[2084x]

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.

[rial1106]

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.

[LukeSmithxyz]

Interesting. I think this has happened to me since the remapd script was implemented when packages are updated every once in a while.

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 remapd script (without grep's -q option) we might be able to figure our when the script is ceasing to function.

[yaaama]

Interesting. I think this has happened to me since the remapd script was implemented when packages are updated every once in a while.

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 remapd script (without grep's -q option) we might be able to figure our when the script is ceasing to function.

I just wanted to clarify that I did not mean my monitor is only connected to my laptop using a USB. My monitor is connected using a HDMI cable and I have a USB cable connected to the monitor so that I can make use of the monitors USB hub feature (allows me to connect my keyboard straight into the monitor rather than having to connect it to the laptop).

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

[2084x]

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.