-
-
Notifications
You must be signed in to change notification settings - Fork 65
Correctly label pointing device as absolute, not relative #228
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
Conversation
c3bce0c
to
a1219fc
Compare
a1219fc
to
5947c79
Compare
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2025052803-4.3&flavor=pull-requests Test run included the following:
New failures, excluding unstableCompared to: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2025031804-4.3&flavor=update
Failed tests47 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/132953#dependencies 14 fixed
Unstable tests
Performance TestsPerformance degradation:12 performance degradations
Remaining performance tests:52 tests
|
The input device actually reports absolute events, not relative. Interestingly it worked before, probably because of InitAbsoluteClassDeviceStruct, but some applications were confused about mismatching mode. Adjust also min/max values based on max resolution supported by the qubes dummy driver. Fixes QubesOS/qubes-issues#7316
The input device actually reports absolute events, not relative.
Interestingly it worked before, probably because of
InitAbsoluteClassDeviceStruct, but some applications were confused about
mismatching mode.
Fixes QubesOS/qubes-issues#7316