Bug 103794 - Please set up RandR 1.5 monitors automatically as per the TILE properties
Summary: Please set up RandR 1.5 monitors automatically as per the TILE properties
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/Ext/RandR (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-17 14:26 UTC by Michael Stapelberg
Modified: 2018-12-13 18:33 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
xrandr --props (4.71 KB, text/plain)
2017-11-17 14:26 UTC, Michael Stapelberg
no flags Details

Description Michael Stapelberg 2017-11-17 14:26:07 UTC
Created attachment 135557 [details]
xrandr --props

I use X.Org 1.19.3 on Linux.

I use a Dell UP2414Q monitor, which exposes two outputs via Multi-Stream Transport (MST). I verified this issue is also present when using a display requiring multiple connections, e.g. the Dell UP3218K, which uses 2 DisplayPort connections.

When starting Xorg, the position of the individual outputs relative to each other is the wrong way around: instead of (left half, right half), I see (right half, left half) on my monitor.

Also, when using xrandr --listmonitors, I see 2 monitors instead of 1.

To fix this, I currently use the following in my ~/.xsession:

xrandr --output DP-5.8 --auto --right-of DP-5.9
xrandr --setmonitor up2414q auto DP-5.8,DP-5.9

I think it would be better if Xorg (specifically the RANDR extension, I suppose?) would look at the TILE property, arrange the outputs accordingly and create a monitor object accordingly.

I attached the output of xrandr --props.

Please let me know if you need any further details.

Thanks!
Comment 1 GitLab Migration User 2018-12-13 18:33:39 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/232.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.