Closed medanimohamedakram closed 3 months ago
Thanks for reporting!
Was it possibly caused by a still running, not updated keymapperd
instance being incompatible with the updated keymapper
instance? Or the other way round.
Could you stop both before installing the new version? (sudo systemctl stop keymapperd
, killall keymapper
)
I will add a version check, which should detect this problem and exit with an error message.
If that was not the cause, could you please start them manually with the verbose flag and post the output. (sudo keymapperd -v
, keymapper -v
).
Thanks!
I had a similar issue after upgrade which got fixed by restarting keymapperd
. This check sounds like a good idea. I don't know if this would be feasible, but I think even better would be if keymapperd
would be forced to restart after an upgrade. I realise this is not how upgrades are normally handled on Linux, but I could see this as an exception due to the tight coupling between the processes.
...after a bit of thinking, that would be a very bad idea as the upgrades could have breaking changes 😅. A warning is much better.
Thanks for reporting! Was it possibly caused by a still running, not updated
keymapperd
instance being incompatible with the updatedkeymapper
instance? Or the other way round. Could you stop both before installing the new version? (sudo systemctl stop keymapperd
,killall keymapper
) I will add a version check, which should detect this problem and exit with an error message. If that was not the cause, could you please start them manually with the verbose flag and post the output. (sudo keymapperd -v
,keymapper -v
). Thanks!
I tried this and it seems that was the issue So keymapper works fine now, Thanks
I will add a version check, which should detect this problem and exit
This is implemented now in 4.4.0.
when I upgraded to 4.2.0 Mouse and keyboard kept lagging and I noticed the numlock and Caps kept flashing as if connecting and disconnecting continously I downgraded to 4.1.3 and every turned back to normal
I tried building from source to the latest commit but the issue still persist