Latest Update seemed to make Shift or Control clicking not work anymore.
When I hold shift and left click on the mouse, or hold control and left click on the mouse (to select multiple items) on a remote PC, it no longer works for me, anyone else?
I noticed it broke update before this last one, but thought I would wait for another one to come out to report it.
- 10 replies
- Michael Lynch @michael2021-03-22 19:26:10.867Z
Can you try updating once more? There was an bad update on Friday that broke input forwarding.
If you're still seeing this after updating to the latest version, can you share your logs from System > View Logs?
Today 23.3 I launched the upgrade TinyPilot latest version 1.4.1. then I did a reboot.
The TinyPilot not responding to the mouse and keyboard.
Chromium still displays the screen in the web browser.
Fortunately I made an image of the sd card ver 1.4.0
- Michael Lynch @michael2021-03-25 20:51:29.710Z
Hmm, it doesn't look like there are any errors in your logs.
What I think happened was that your browser had cached the old version of the socket.io library after you updated. You should be able to solve it with a hard refresh (Ctrl+F5) in your browser.
- AIn reply toAmerisun⬆:John Amerisun @Amerisun2021-03-22 20:46:19.943Z
Yes, I actually updated after the bad update apparently, as I did not receive that. Link to logs are here: https://logs.tinypilotkvm.com/YGVf6QIO
- Michael Lynch @michael2021-03-23 22:22:25.459Z
Well, this is embarrassing...
I was updating the log sharing service this weekend and accidentally disabled data replication for three days, so I lost your log.
Would it be possible for you to re-upload the logs?
Also, what OS is your target computer?
No problem. https://logs.tinypilotkvm.com/hCPCJxGg
OS of target computer is Windows 10. I can hold shift or control and hit left arrow / right arrow and it works fine in text (word / text editor), it doesn't work with the mouse click though when trying to choose more than one file.
- Michael Lynch @michael2021-03-24 19:32:17.182Z
Oh, I see what you're saying. I can reproduce this behavior. I've filed a bug to track this:
Did this work at some point? Looking at the code, I can't tell what would have changed to break it.
It was working before the last two major updates. The first update (with the new update UI) was when it first occurred, but I was going to let it go another patch before I reported it. Then the second update came with a better looking UI, and that's when I reported it.