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
Windows start/win key 'sticks' after switching between Windows virtual desktops #1578
Comments
It took me a few attempts, but I was finally able to see what you mean here. I misunderstood that you meant that the Win key got stuck in the session (a common bug), not that it was stuck locally on the client. There must be something in our keyboard grab code that confuses Windows. I assume it doesn't happen if "Send system keys..." is disabled? Does the RealVNC client have the feature to grab the keyboard? Have you tried any other client that can grab the keyboard, but doesn't trigger this bug? |
Yes, if I disable 'Send system keys...' the issue does not occur. But of course I then get Windows responding to the keys as well as the server. I believe that the RealVNC client grabs the keyboard. Its default setting is to send all keys (except audio/volume controls) directly to the VNC server. I have also tried the UltraVNC client, which does not exhibit this bug. |
RealVNC is unfortunately proprietary, so we can't see how they handle the keyboard grab. I had a look at UltraVNC. They use the same system hooks, but they have a very different approach to handling the events. Someone will unfortunately need to dig in to this a bit and try to figure out the details of where it goes wrong. |
This occurs on Ubuntu 22.04 + i3 window manger + single monitor. Windows key is grabbed after full screen. Tested with client version "v1.13.1" connection to the tigervncserver v 1.11.0 running on debian machine. |
The issue reported here is very specific for a Windows client. If you are seeing something similar on Linux, then please open a new issue for that. |
Describe the bug
When I have TigerVNC open full screen on its own Windows virtual desktop, switching to another desktop and back via Ctl-Win-arrow keys causes the Win key to behave as if it is stuck down. It can be 'unstuck' by sending a valid Win-key combination through to Windows then returning focus to the TigerVNC display.
To Reproduce
Note that to perform steps 3 and 6 you might need a second display in which TigerVNC is not running, so that you can click on the Windows desktop to give input focus back for Windows to receive the Win-key combinations. Minimising TigerVNC to perform these steps does not trigger the bug.
The behaviour does not occur if TigerVNC is minimised, or running in a Window rather than full screen. The behaviour does not occur in other VNC clients (e.g. Real VNC vncviewer).
Expected behavior
Keyboard behaviour should not change after switching between virtual desktops.
Screenshots
N/A
Client (please complete the following information):
Server (please complete the following information):
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: