Closed mattiasJohnson closed 2 years ago
Hello, I have been pondering this issue for the last couple of days. Sadly, I cannot reproduce the described behaviour on my end and I do not know where the cause of the issue may lay.
Out of curiosity, do you have any clean VM (the newest Ubuntu or something similar, for example; if brave, Arch even) lying around, where you could test what the behaviour will be
Furthemore, trying a different keyboard for each of these test scenarios as well would be ideal. I am more inclined to believe the problem is directly connected to your system and/or HW restrictions, but that is only a guess here. I definitely do not recognize this issue. I see these tests as a way to exclude some possible causes and hopefully get closer to the real problem here. But I understand I am sending you on a rabbit hunt. Decide for yourself if this is worth it.
@donniebreve Any ideas? I am at a loss here.
Sorry I could not be of more help so far. Hope we can solve this together.
I sincerely apologise I've made a really clumsy mistake. Running cat /proc/bus/input/devices | less
I read AT Translated Set 2 keyboard
but it never crossed my mind that that wasn't the keyboard when I was looking for why it wasn't working. One page further down I found ITE Tech. Inc. ITE Device(8296) Keyboard
which was the correct entry and now everything of course works as it should.
Also thanks a lot for this amazing program, I've literally been using my six year older laptop just because I had it working there since it makes my workflow so much smoother.
No worries. I am glad the issue has been resolved and everything works for you once again. I am actually using my notebook with the AT Translated Set 2 keyboard
name for my integrated keyboard so I saw nothing wrong about it. It is good to know that this behaviour may occur when inserting a wrong name in specific cases, though. This way, I may hopefully recognize the issue later when anyone comes with the same problem.
I must agree. I cannot work without TouchCursor any more, too. When setting up a new system, TouchCursor is literally the first thing I set up, before I configure the system any further. Good luck and enjoy.
When I hold space I just write a lot of spaces even though I should have succesfully installed it and
systemctl --user status touchcursor.service
shows that it's running. Although checkingjournalctl
seems to indicate that it is constantly starting and stopping. I previously opened the issue #36 but I had a lot of work so stopped examining it and it got closed due to inactivity.Outputs
Running
systemctl --user status touchcursor.service
Running
systemctl --user restart touchcursor.service; sleep 10; journalctl -e -n8000
Ran the above command and cut out subsequent parts relating to touchcursor, marked gaps with a few blank lines.
Running
cat /proc/bus/input/devices | less
My keyboard (which I've of course then set in the config)
Virtual TouchCursor Keyboard:
Starting the binary
My system setup
I've got a Lenovo laptop of version
Legion S7 15ACH6
running Ubuntu 20.04. My kernel is5.11.0-40-generic
which might not be the newest one and if it would be likely to fix it I can try running a more recent kernel (no ubuntu wifi drivers for my laptop so a bit cumbersome process to upgrade kernel having to reinstall the custom drivers).