Your message dated Sat, 22 Nov 2025 17:07:01 -0500
with message-id
<CAAajCMZLtJrp1SUzBJgWDM-HzB63TOk5ry=oq6pNVqB6=c_...@mail.gmail.com>
and subject line closing old mutter bugs
has caused the Debian Bug report #927275,
regarding gnome-shell - Intel GPU - monitors.xml is ignored and settings are
not applied after suspend/reboot
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
927275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927275
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-shell
Version: 3.30.2-3
Severity: serious
Device: Thinkpad L390
Debian Version: Buster with latest updates
After a fresh install, arranging all monitors in gnome-settings and
saving the changes the setup works on both sides (office and home) with
two same dockingstations (Thinkpad Thunderbolt 3 Dock Gen 2) and
different monitor settings at each side. All monitors are placed
correctly and the internal screen is off, as it was defined in gnome
settings before, see attached monitors.xml
But after disconnecting the dockingstation, suspend the laptop and
change the location, wake it up and connecting to the other dock, the
settings are not applied again, just the default display arrangement
(all three in one row, from left to right). Even a reboot, or another
suspend while beeing connected to the dockingstation is not solving it.
There is no way to get the correct saved options applied again which
have been working before.
It seems gnome-shell is not reading in the monitors.xml where the
correct settings are applied and stored for each side after a suspend
or even a reboot.
Any idea what is causing this issue and what could be a workaround for
now to trigger a manual reading of the monitors.xml so that it can be
applied manually as a temporary fix?
best regards
Christian Höffer
monitors.xml
Description: XML document
--- End Message ---
--- Begin Message ---
There have been many changes to Debian since this bug was originally
reported. If you are still experiencing this issue with Debian 13 (or
with Debian 12 or Testing or Unstable), please report a new bug.
Thank you,
Jeremy Bícha
--- End Message ---
