It sounds like this bug is now fixed(?). If so then we don't need any
further investigation thanks.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: mutter (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you
For the confirmation, I'd need guidance. Which source/mutter link to
click to reinstall the prior version (or is it all of them?).
Since writing the above report, by reflex more Ubuntu updates have been
accepted (there have been very many this week - perhaps four or five) -
new dpkg.log
Curious.
xorg-server on 18.04 hasn't changed since last year so that can't be the
problem. The same goes for mutter, which would be the main package of
interest if you were using a Wayland session.
There was a kernel update at the end of April, so that's the only
candidate I can think of for
Although 'mutter' isn't mentioned in the attached 'dpkg.log'. That may
indicate the bug is not in mutter, or it may indicate that the assertion
of 'dpkg.log' containing the regressed package might be wrong.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You
Sorry, I misread the dates.
There was also a 'mutter' update at the end of April, so that may be the
problem. To confirm this, please try reinstalling the .deb files of the
prior version:
https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.1/+build/16422451
and then
** Summary changed:
- Reboot after dpkg update set invalid Graphics resolutions (Dual Monitor)
+ [regression] Reboot after dpkg update set invalid Graphics resolutions (Dual
Monitor) since ~7th/8th May
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Tags added: regression-update
