After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 772709 - X11 and Wayland screen configurations disagree
X11 and Wayland screen configurations disagree
Status: RESOLVED DUPLICATE of bug 774135
Product: mutter
Classification: Core
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2016-10-10 15:43 UTC by Jan Alexander Steffens (heftig)
Modified: 2016-11-09 18:34 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jan Alexander Steffens (heftig) 2016-10-10 15:43:16 UTC 
Putting my monitors into the right order on X11 generated the following configuration:

  <configuration>
    <clone>no</clone>
    <output name="HDMI1">
      <vendor>GSM</vendor>
      <product>E2251</product>
      <serial>112LTEN3A836</serial>
      <width>1920</width>
      <height>1080</height>
      <rate>60</rate>
      <x>1920</x>
      <y>0</y>
      <rotation>normal</rotation>
      <reflect_x>no</reflect_x>
      <reflect_y>no</reflect_y>
      <primary>yes</primary>
      <presentation>no</presentation>
      <underscanning>no</underscanning>
    </output>
    <output name="HDMI2">
      <vendor>GSM</vendor>
      <product>E2251</product>
      <serial>112LTXX39834</serial>
      <width>1920</width>
      <height>1080</height>
      <rate>60</rate>
      <x>3840</x>
      <y>0</y>
      <rotation>normal</rotation>
      <reflect_x>no</reflect_x>
      <reflect_y>no</reflect_y>
      <primary>no</primary>
      <presentation>no</presentation>
      <underscanning>no</underscanning>
    </output>
    <output name="HDMI3">
      <vendor>GSM</vendor>
      <product>E2251</product>
      <serial>112LTLM3L976</serial>
      <width>1920</width>
      <height>1080</height>
      <rate>60</rate>
      <x>0</x>
      <y>0</y>
      <rotation>normal</rotation>
      <reflect_x>no</reflect_x>
      <reflect_y>no</reflect_y>
      <primary>no</primary>
      <presentation>no</presentation>
      <underscanning>no</underscanning>
    </output>
  </configuration>

Moving to a Wayland session then used the default, wrong, configuration again. Fixing it generated this configuration:

   <configuration>
    <clone>no</clone>
    <output name="HDMI-1">
      <vendor>GSM</vendor>
      <product>E2251</product>
      <serial>112LTEN3A836</serial>
      <width>1920</width>
      <height>1080</height>
      <rate>60.000495910644531</rate>
      <x>1920</x>
      <y>0</y>
      <rotation>normal</rotation>
      <reflect_x>no</reflect_x>
      <reflect_y>no</reflect_y>
      <primary>yes</primary>
      <presentation>no</presentation>
      <underscanning>no</underscanning>
    </output>
    <output name="HDMI-2">
      <vendor>GSM</vendor>
      <product>E2251</product>
      <serial>112LTXX39834</serial>
      <width>1920</width>
      <height>1080</height>
      <rate>60.000495910644531</rate>
      <x>3840</x>
      <y>0</y>
      <rotation>normal</rotation>
      <reflect_x>no</reflect_x>
      <reflect_y>no</reflect_y>
      <primary>no</primary>
      <presentation>no</presentation>
      <underscanning>no</underscanning>
    </output>
    <output name="HDMI-3">
      <vendor>GSM</vendor>
      <product>E2251</product>
      <serial>112LTLM3L976</serial>
      <width>1920</width>
      <height>1080</height>
      <rate>60.000495910644531</rate>
      <x>0</x>
      <y>0</y>
      <rotation>normal</rotation>
      <reflect_x>no</reflect_x>
      <reflect_y>no</reflect_y>
      <primary>no</primary>
      <presentation>no</presentation>
      <underscanning>no</underscanning>
    </output>
  </configuration>
Comment 1 Giovanni Campagna 2016-10-10 18:31:03 UTC 
This is unfortunately somewhat to be expected: in X11 the output naming is left to the drivers, and different drivers have different convention.

The default should be at least consistent with the intel or the modesetting driver, though, and it isn't because of that dash.
Comment 2 Jan Alexander Steffens (heftig) 2016-10-11 17:09:34 UTC 
The modesetting ddx (as opposed to the intel ddx) uses names with a dash. So this might solve itself eventually, at least for intel graphics.
Comment 3 Rui Matos 2016-11-09 18:34:12 UTC 
I had a feeling this was already filed... anyway attached a patch to bug 774135 for this.

*** This bug has been marked as a duplicate of bug 774135 ***