Skip to content

CPVM: if special key is pressed down while window is closed, key is not release for next opening #9940

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

Open
borisstoyanov opened this issue Nov 18, 2024 · 1 comment · May be fixed by #10743

Comments

@borisstoyanov
Copy link
Contributor

ISSUE TYPE
  • Bug Report
COMPONENT NAME
CPVM, noVNC 
CLOUDSTACK VERSION
4.19
CONFIGURATION

This has been reproduced with VMware, but it might be related to other hypervisors.

SUMMARY

Let's say someone hit's the 'Shift.Down' button in the session window, starts typing in upper case then close the window without depressing in the 'Shift.Down' button, upon next opening of the same session the button is displayed depressed but console still types with up case characters.

STEPS TO REPRODUCE
1. Open CP session to a guest VM
2. Press the 'Shift.Down' special key buttons on the side of the window (any other special key also ) 
3. Start typing and close the CP window
4. Open the same session again from Cloudstack
5. Observe that the button is displayed a depressed as default, but console still produces upper case characters. 
EXPECTED RESULTS
Special keys should be reverted to default and it should type lower case in this scenario 
ACTUAL RESULTS
upper case characters printer while key is depressed. 
@vishesh92
Copy link
Member

I could reproduce the issue with vmware in Chromium browser. This bug doesn't occur in Firefox.
Not able to reproduce it for KVM.
Created a PR here: #10743 to reset the modifier keys when connection is created with the VM.

@vishesh92 vishesh92 moved this from Discuss to ready for Review in Apache CloudStack BugFest - Issues Apr 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ready for Review
Development

Successfully merging a pull request may close this issue.

4 participants