What I found is, when I'm saving my settings in monitors.xml, is have
the following:

 <configuration>
    <logicalmonitor>
      <x>0</x>
      <y>0</y>
      <scale>1</scale>
      <monitor>
        <monitorspec>
          <connector>HDMI-A-1</connector>
          <vendor>ACI</vendor>
          <product>ASUS PB278</product>
          <serial>D3LMTF056504</serial>
        </monitorspec>
        <mode>
          <width>2560</width>
          <height>1440</height>
          <rate>59.950550079345703</rate>
        </mode>
      </monitor>
    </logicalmonitor>
    <logicalmonitor>
      <x>5120</x>
      <y>0</y>
      <scale>1.5</scale>
      <primary>yes</primary>
      <monitor>
        <monitorspec>
          <connector>DisplayPort-1</connector>
          <vendor>ACI</vendor>
          <product>ASUS PB287Q</product>
          <serial>0x0001ecd2</serial>
        </monitorspec>
        <mode>
          <width>3840</width>
          <height>2160</height>
          <rate>59.996623992919922</rate>
        </mode>
      </monitor>
    </logicalmonitor>
  </configuration>

As you can see first one resolution is 2560x1440, but the second one by
position starts at x=5120, so 2560x2, as the second one is saved with
1.5 scale. But gnome-shell probably expects them to be adjacent, so
expects x=2560

So, when gnome-shell starts it looks like we are failing to pass the
adjacent check. And that's exactly what it's saying:

Apr 25 13:28:28 xxx gnome-shell[10304]: Failed to read monitors config
file '/home/xxx/.config/monitors.xml': Logical monitors not adjacent

To verify that I made x=2560 in monitors.xml and restarted gnome-shell,
all scaling remained in place as they saved and no errors from gnome-
shell anymore, but the right screen is half overridden by left one
(which is exactly how to position specified now for the scaled screen).

So it looks like config validator in gnome-shell needs to be fixed to
behave differently when logical monitors are scaled.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1825593

Title:
  Display: 100% scale not remembered when X11 Fractional Scaling is
  enabled

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 19.04, I enabled the experimental 'x11-randr-
  fractional-scaling' setting.  If I set scaling to 125, 150, or 200%,
  the setting is remembered and used the next time I log in.  If I set
  scaling to 100%, however, the next time I log in the scaling switches
  back to 200% automatically.  I only want to use fractional scaling for
  external monitors.

  Background: This is on a Dell XPS 9360 with a 1920x1080 ~168 DPI
  screen.  Pretty standard configuration.  I have my DisplaySize set to
  294x165 in Xorg.conf, Xft.dpi=168, GTK font scaling factor 1.0.

  I have been unable to find an appropriate combination of settings
  where 168 DPI is respected for accurate font rendering, while at the
  same time not scaling up the rest of the UI to unusable proportions.
  Fractional scaling seems to be the only way to adjust some Gnome UI
  elements.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1825593/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to