Settings for external monitor are deleted after reboot, suspension, log out

[Jeremie Tamburini]

New Gnome Settings on Ubuntu 17.10

Settings for external monitor are working but after reboot/suspension/log-out log-in, the system will not remember the setup.

Example:
1- open Gnome Settings and select "Devices → Displays"
2- set the external monitor as "Single Display" and click on "Apply"
3- log-out

After log-in the laptop monitor will be set as default instead of the external monitor.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Olivier Tilloy (osomon)]

Reported upstream: https://bugzilla.gnome.org/show_bug.cgi?id=787629

[Sebastien Bacher (seb128)]

g-c-c does send the config changes correctly, the issue is rather with g-s-d or gnome-shell

[Daniel van Vugt (vanvugt)]

Consider de-duplicating with bug 1292398?

[Daniel van Vugt (vanvugt)]

For gnome-shell I don't think this is "regression-release" because gnome-shell has not regressed any worse than previous gnome-shell releases. You can always go back to Unity if it was working better for you:

  sudo apt install unity-session

and select it on the login screen.

[Jonathan Kamens (jik)]

I think this is regression-release because the default display manager in Ubuntu 17.04 was not broken in this way and the default display manager in Ubuntu 17.10 is.

But hey, what do I know, I'm just an end user.

[Daniel van Vugt (vanvugt)]

Absolutely it's a regression in the overall product, and one that we have developers working on.

However that tag is only appropriate if the bug covers components where the problem did not exist in a previous version of those components. And AFAIK this bug probably did exist in previous gnome-shell versions (?)

Technically you could add a generic "Ubuntu" task up top and then it would then qualify as regression-release for general "Ubuntu", but I've never seen anyone do that. A generic "Ubuntu" task usually just means no one has yet figured out what component the bug is in.

[Sebastien Bacher (seb128)]

the issue there was fixed in 3.26.1 before 17.10, if you still have problems please report a new reports with detailed steps and log

[Sebastien Bacher (seb128)]

bug #1726538 was recent and from 3.26.1, unduplicated it so it can sent upstream and used for the new issue

[Calin (calinuswork)]

Is not clear to me if this was fixed or not?

I have the same issue on a brand new 17.10 installation.

[Dmitrii Shcherbakov (dmitriis)]

Hmm, for my installation upgraded from 17.04 it got fixed - I no longer experience the issue.

[Chris (toefel)]

I still experience the issue as of today on 17.10 after updating.

gnome-control-center/artful-updates,now 1:3.26.1-0ubuntu5 amd64 [installed,automatic]

[Dmitrii Shcherbakov (dmitriis)]

Chris, out of curiosity, do you have a dual-monitor setup?

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726538

For me it works fine with a laptop monitor disabled + single monitor as a primary.

[Andreas Vinsander (andreas-vinsander)]

I use two external monitors with my Lenovo Thinkpad t430s sitting in a Lenovo docking station. The external monitors are connected through DVI and DisplayPort to the docking station. I see the problem both when using Wayland and Xorg. The laptop lid is closed and the internal screen is not used when sitting in the dock. My seconday display is positioned to the left of the primary display when everything is correct. But those settings does not persist over reboots.

[Daniel van Vugt (vanvugt)]

This bug is closed. So regardless of whether that's right or wrong, please keep the discussion in a bug that is still open, like bug 1292398 or bug 1726538.