Skip to content
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

In BIOS screens, the KVM remove mouse cursor is not aligned with the local mouse cursor #866

Open
rgl opened this issue Jan 18, 2024 · 0 comments
Labels
known issue Issue is known but unable to be fixed or will take a long time to resolve

Comments

@rgl
Copy link

rgl commented Jan 18, 2024

Describe the bug 🪲

In BIOS screens, the KVM remove mouse cursor is not aligned with the local mouse cursor.

I'm testing with this hardware:

  • HP EliteDesk 800 G2 DM 35W
  • BIOS N21 Ver. 02.60
  • AMT 11.8.92

To Reproduce 🪜
Steps to reproduce the behavior:

  1. Boot the computer to the BIOS.
  2. Using the KVM UI control (or at the sample-web-ui), move the mouse.
  3. See that it has an odd offset. In the screenshot below, my local computer mouse cursor is the black one. the white one is the remote computer mouse cursor. As you can see, they are not aligned, and have an odd offset between them.

Please note that this only happens when in the BIOS screens. When the remote computer is at the OS desktop, the mouse cursor works as expected.

Expected behavior
I expected the remote mouse cursor to follow the local mouse cursor.

Screenshots 🖼️

Screenshot from 2024-01-18 18-20-38

Browser Information (please complete the following information): 🖥️

  • OS: Ubuntu 22.04 LTS
  • Browser and Version: Firefox 121.

Additional context

I'm not sure how the mouse is emulated in AMT. As a comparison, https://docs.pikvm.org/mouse/ talks about different mouse types: absolute or relative. Maybe there is something like this with AMT?

@bwendlandt-intel bwendlandt-intel added the known issue Issue is known but unable to be fixed or will take a long time to resolve label Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
known issue Issue is known but unable to be fixed or will take a long time to resolve
Projects
Status: No status
Development

No branches or pull requests

2 participants