FS#45572 - [xf86-video-intel] corrupt/inaccurate mouse pointer on scaled displays

Attached to Project: Arch Linux
Opened by Henry Lajoie (htl2001) - Monday, 06 July 2015, 20:39 GMT
Last edited by Laurent Carlier (lordheavy) - Saturday, 10 October 2015, 12:51 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Andreas Radke (AndyRTR)
Laurent Carlier (lordheavy)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description: when using xrandr --scale 2x2 on external monitor (hidpi laptop w/ regular external monitor) mouse cursor gets corrupted and is inaccurate on the 2nd monitor. The inaccuracy may be present on the non-scaled display, but is small - pointer appears slightly up and to the right of the actual locations).

The previous version does not have this issue, apparently because the mouse cursor did not respect the scaling config - cursor was the same size at --scale 1x1 and --scale 2x2, while with the new version, it shrinks to the size expected.


Additional info:
* package version(s): 1:2.99.917+364+gb24e758-1
* occurs with or without scaling patch to xorg-server (bug: https://bugs.freedesktop.org/show_bug.cgi?id=39949 patch: https://bugs.freedesktop.org/attachment.cgi?id=94929 )

Steps to reproduce:
1. scale a display with xrandr:
$ xrandr --output HDMI1 --scale 2x2
2. move mouse over a button, edge of a window, etc
This task depends upon

Closed by  Laurent Carlier (lordheavy)
Saturday, 10 October 2015, 12:51 GMT
Reason for closing:  Fixed
Additional comments about closing:  xf86-video-intel-1:2.99.917+478+gdf72bc5 -1
Comment by Henry Lajoie (htl2001) - Monday, 06 July 2015, 20:45 GMT
Sorry, I can't find a way to edit and I made a mistake, the inaccuracy is pointer up and to the LEFT of the actual position. And it is definitely present on un-scaled displays but only a few pixels.
Comment by Alex Bruce (manghoti) - Thursday, 27 August 2015, 18:58 GMT
I've been effected by this as well, using a Lenovo y-50 with monitor. To be honest I don't think this is under arch's purview though. Seems like this is more an Xorg bug.

Though it's worth noting that I am using the xf86-video-intel drivers as well.
Comment by Henry Lajoie (htl2001) - Thursday, 27 August 2015, 20:33 GMT
Correct... but this is with an update and the version number makes me think its out of band for xorg

The initial inaccuracy is still a thing on the "working" version though, its just that at 1x1 scale its minor. Considering how long taking for the scale bounding box fix to be taken upstream I was thinking here would be better, or someone else with more technical knowledge of this specific section could be of more help reporting upstream
Comment by Laurent Carlier (lordheavy) - Sunday, 27 September 2015, 07:33 GMT
Should be fixed with xf86-video-intel-1:2.99.917+472+gf0fd4d5-1 in testing
Comment by Lukas Fleischer (lfleischer) - Tuesday, 29 September 2015, 13:33 GMT
Seems like the same issue now occurs when you rotate the screen, i.e. after running `xrandr --rotate inverted`.
Comment by Martin Peres (MuPuF) - Tuesday, 29 September 2015, 14:53 GMT
Yes Lukas, I am looking into this. Will try to propose a fix today to Chris Wilson.
Comment by Henry Lajoie (htl2001) - Tuesday, 29 September 2015, 20:02 GMT
This update did fix the inaccuracy, but has not fixed corruption. Unfortunately I have to post photos as screenshots show the pointer without corruption: http://imgur.com/a/ZuXiq

In order to reproduce this, you need a program that doesn't work 100% correctly with hidpi, in my case here its HipChat.

Actually it also works when you attempt to highlight and drag something in chromium (in cinnamon) which also has its own issues (displacement from top left is 2x as far away as the actual mouse pointer)
Comment by Laurent Carlier (lordheavy) - Friday, 09 October 2015, 15:14 GMT
Please check xf86-video-intel-1:2.99.917+478+gdf72bc5-1 in testing
Comment by Lukas Fleischer (lfleischer) - Friday, 09 October 2015, 16:34 GMT
Works fine for me now.

Loading...