Bug 769140 - xrandr --scale doesn't change pointer area
Summary: xrandr --scale doesn't change pointer area
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-20 02:45 UTC by Bill Nottingham
Modified: 2014-03-17 03:29 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 21:02:28 UTC
Type: ---


Attachments (Terms of Use)
ye olde X log (42.13 KB, text/plain)
2011-12-20 02:45 UTC, Bill Nottingham
no flags Details
kernel messages (81.16 KB, text/plain)
2011-12-20 02:46 UTC, Bill Nottingham
no flags Details

Description Bill Nottingham 2011-12-20 02:45:36 UTC
Created attachment 548731 [details]
ye olde X log

Description of problem:

Gen3 (atom)

Using xrandr --scale does not change the active pointer area - the pointer is restricted to the original resolution.

Happens with both built-in touchpad and attached usb mouse/keyboard combo.

Version-Release number of selected component (if applicable):

xorg-x11-server-Xorg-1.11.2-3.fc16.i686
xorg-x11-drv-synaptics-1.5.0-2.fc16.i686
xorg-x11-drv-evdev-2.6.99-3.20110601giteaf202531.fc16.i686
xorg-x11-drv-intel-2.17.0-4.fc16.i686

How reproducible:

100%

Steps to Reproduce:
1. xrandr --output LVDS1 --scale 1.333333x1.333333 --auto
  
Actual results:

Screen is resized. Pointer active area is not.

Expected results:

Screen is resized. Pointer active area is also.

Additional info:

00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 02)
02:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

Comment 1 Bill Nottingham 2011-12-20 02:46:25 UTC
Created attachment 548732 [details]
kernel messages

Comment 2 Karim 2012-03-14 09:14:03 UTC
Same problem.

When I scale my screen with xrandr, the pointer area do not change.

Comment 3 Leho Kraav 2012-07-27 14:35:57 UTC
It's probably [1]

 [1]: https://bugs.freedesktop.org/show_bug.cgi?id=39949

Comment 4 masanari iida 2012-08-14 01:26:08 UTC
Same problem exist on Fedora 17.
xorg-x11-server-Xorg-1.12.2-4.fc17.i686

See comment#21 of the id=39949.
The guy reported that patched the source of F17, and fixed the symptom.

Comment 5 masanari iida 2012-08-21 12:26:08 UTC
I have reverted following patch, and the scale and panning problem
has fixed. 
 
http://cgit.freedesktop.org/xorg/xserver/commit/?id=56c90e29f04727c903bd0f084d23bf44eb1a0a11

Comment 6 Fedora End Of Life 2013-01-16 16:54:15 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Fedora End Of Life 2013-02-13 21:02:32 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.