--scale and --panning options do not resize the mouse area accordingly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libxrandr (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I just installed Xubuntu 11.10 Oneiric on my netbook, a MSI Wind U100.
On my previous OS (Jolicloud 1.0, derived from Ubuntu Jaunty), I used an applet relying on xrandr to expand the screen resolution when needed.
Indeed, my screen is 1024*600, and some programs and dialogs are higher than 600px. So when needed I used xrandr to resize it to 1024*768 with panning.
On Oneiric, however, this no longer works.
I can still run xrandr, and the display is resized correctly, but the area in which I can move the mouse stays the same 1024*600 box.
1) When using panning mode
I start panning mode with the following command :
xrandr --fb 1024x768 --output LVDS1 --mode 1024x600 --panning 1024x768 --scale 1x1
In that case, the display is resized (all windows become higher than the screen, etc).
However, I cannot pan to the bottom : my mouse cursor cannot go lower than the lower bound of my screen, so I can only pan by 1 or 2 pixels.
2) When using scale mode
I start scale mode with the following command :
xrandr --output LVDS1 --mode 1024x600 --scale 1.28x1.28 --fb 0x0 --panning 0x0
In that case, the display is resized so that a 1311x768 display fits on my screen.
However, I cannot move the cursor on the whole screen : it cannot go lower than the "virtual" 600px (actually 469 after resize), nor more to the right than the "virtual" 1024px (actually 800).
This basically makes xrandr unusable, which can be a real problem on such small screens.
Also, this bug isn't specific to Ubuntu : I found other bug reports elsewhere.
https:/
https:/
From my research, it looks like it was introduced in libxrandr 1.3.1.
Also, this bug was apparently already reported for Ubuntu but on an incorrect package, and I don't know how to move it.
See it declared as a compiz bug here : https:/
Feel free to ask more information about my system if you think it might help.
Thanks.
Status changed to 'Confirmed' because the bug affects multiple users.