Bug 203324 - randr rotated second display effects cursor orientation and location on first display
Summary: randr rotated second display effects cursor orientation and location on first...
Status: RESOLVED WORKSFORME
Alias: None
Product: krandr
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Gustavo Pichorim Boiko
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-10 16:43 UTC by Jaakko Kantojärvi
Modified: 2012-06-20 08:01 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jaakko Kantojärvi 2009-08-10 16:43:30 UTC
Version:            (using KDE 4.3.0)
OS:                Linux
Installed from:    Debian testing/unstable Packages

 ** Situation
I have two screens with ati setup using xrandr in Xsetup:
 randr --output DFP1 --auto --primary \
       --output DFP2 --auto --rotate left --right-of DFP1

This worked well on kde 4.2

Now cursor is rotated left in DFP1.

DFP1 is 1920x1200 and DFP2 is 1200x1600 (rotated).

Cursor rotation happens in area 1600x1200 in DFP1.
Cursor is in correct orientation on second monitor (no flip while going from DFP1 to DFP2 (as expected)).

 ** Possible reason:
This can be reflected from wrong handling of multiple monitors, because in "Display settings -> size & orientation" green display images are above each others instead of being side by side. Also cursor rotating area is size of DFP2.

 ** Notes:
 - ATI (I prefer nvidia, but I didn't bought this machine)
 - randr works correctly
 - KDE 4.2 worked correctly (for cursor)
Comment 1 Jaakko Kantojärvi 2009-08-10 19:04:43 UTC
Correction. Reverted from 4.3 to 4.2 and problem was here too. Have to do checks that nothing from kde 4.3 is still installed.

Anyway now the cursor orientation change happens between screens.

Also forget to mention that cursor icon is ~40pixels below actual cursor location (place where clicks go).
Comment 2 Jakob Schröter 2009-10-22 16:14:02 UTC
I had a similar issue at some point (early 4.3.x, I think) but I'm using the intel driver. However, it is fixed for me now (in the driver or in kwin, dunno) in Kubuntu Karmic beta with latest packages.
Comment 3 Thomas Lübking 2012-03-16 22:53:18 UTC
In case this is still a problem it's (likely) somewhere in krandr or a feature lack in xinput, unable to --set-prop per screen - kwin does not manage the pointer
Comment 4 Myriam Schweingruber 2012-06-20 07:49:57 UTC
Closing based on comment #2
Comment 5 Myriam Schweingruber 2012-06-20 08:01:27 UTC
Setting status correctly, sorry for the noise.