GNOME Bugzilla – Bug 791583
screen layout and primary screen settings not saved between sessions
Last modified: 2021-06-14 18:22:09 UTC
Every time I log in to the latest Ubuntu 17.10, I need to restore manually in the settings window my screen layout and primary screen configuration. The bug has been submitted on Ubuntu launchpad (https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726538).
I'm also experiencing this on Fedora 27
This bug also affects me on Ubuntu 17.10 on the Gnome desktop with xorg. Unity session works perfectly well.
can confirm this Bug for Ubuntu 17.10 with an Lenovo x270 on a Dockingstation and 2 external Monitors.
WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome-screensaver ERROR(syslog) = "Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist" gnome-shell[3007]: JS ERROR: Exception in callback for signal: loaded: TypeError: monitor is null#012_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:653:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:608:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:512:17 CAUSE = clean install of Ubuntu 18.10(4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux), attach VGA as primary monitor and HDMI(wireless Tx) as secondary to projector and then apply custom monitor positioning using g-c-c "Displays" panel. RESULT = correct positioning and working of multiple displays until reboot or shutdown, then--problems until HDMI cable is unseated and rebooted again. Downstream bug report: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1820423
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version of gnome-session, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-session/-/issues/ Thank you for your understanding and your help.