This bug was fixed in the package mutter - 3.36.6-1ubuntu0.20.04.2
---------------
mutter (3.36.6-1ubuntu0.20.04.2) focal; urgency=medium
* xrandr-scaling: Never try to set invalid screen sizes (again!)
Looks like this change (introduced to fix LP:1889090) got lost while
rebasing previous fixes, gbp has been a bad guy this time! (LP: #1896818)
mutter (3.36.6-1ubuntu0.20.04.1) focal; urgency=medium
* Merge with debian, containing new stable release (LP: #1896332)
* debian/patches:
- Refresh patches and drop applied ones
- Don't set the font-dpi on clutter-backend-x11 (LP: #1892440)
- Cherry-pick upstream night-switch fixes for 3.36 branch
- Cherry-pick upstream fixes for handling X11 devices removal
(LP: #1558886)
* xrandr-scaling: Don't update UI scale factor on xrandr-manager creation
(LP: #1892440)
* debian/control: Revert pipewire version bumping
* Remaining changes with debian:
- debian/control:
+ Update VCS flags to point to ubuntu salsa branch
- debian/gbp.conf: update branch to point to ubuntu/master
- debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
+ X11: Add support for fractional scaling using Randr
mutter (3.36.6-1) unstable; urgency=medium
* Team upload
* New upstream release
* Update symbols file
* d/control.in, d/rules: Enable Pipewire on Debian (but not Ubuntu).
Now that we have Pipewire 0.3, we can enable screencasting and remote
desktop support again.
mutter (3.36.5-1) unstable; urgency=medium
* Team upload
* New upstream release
- Screencast fixes and improvements
- Fix glitches when subsurfaces extend outside the toplevel
- Improve background display in overview workspace switcher
- Fix wine copy & paste
- Plug memory leaks
* Drop patches that were applied upstream
mutter (3.36.4-1) unstable; urgency=medium
* New upstream stable release (LP: #1887998)
- Fix crash on area screenshots with fractional scaling
- Do not paint textures of fully obscured windows
- Turn off CRTCs as well when enabling DPMS
- Improve selection support
- Use a more appropriate combine function on opaque areas
- Fix remote desktop being broken without screencast session
- Fix popovers disappearing on wayland and HiDPI
- Fixed crashes (LP: #1870867, LP: #1857947)
- Plugged memory leaks
* d/p/screen-cast-Let-the-reason-for-recording-determine-what-t.patch,
d/p/screen-cast-src-Add-flag-to-maybe_record.patch,
d/p/screen-cast-src-Fix-signedness-of-timestamp-field.patch,
d/p/screen-cast-src-Make-record-functions-return-an-error-whe.patch,
d/p/screen-cast-src-Make-the-two-record-vfuncs-more-similarly.patch,
d/p/screen-cast-src-Record-follow-up-frame-after-timeout.patch,
d/p/screen-cast-src-Remove-follow-up-timeout-source-on-disabl.patch,
d/p/screen-cast-src-Use-G_USEC_PER_SEC-instead-of-1000000.patch,
d/p/screen-cast-window-stream-src-Fix-indentation.patch:
- Import more fixes for screencasting and remote desktop
-- Marco Trevisan (Treviño) <[email protected]> Wed, 23 Sep 2020
22:03:53 +0200
** Changed in: mutter (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1896818
Title:
Gnome-shell crash after turn display off in mutter
3.36.6-ubuntu0.20.04.1 (NVIDIA)
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Focal:
Fix Released
Bug description:
In Ubuntu 20.04.1 [focal-proposed]:
[ Impact ]
GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1.
With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2),
all works fine.
[ Test case ]
Steps to reproduce the error:
1) Lock screen;
2) Turn off the display;
3) Turn on the display;
And the Gnome Shell crash and show us a blank screen with the message:
"Oh no! Something has gone wrong."
[ Regression potential ]
This very fix was already handled as part of bug #1889090 and we had no
regression report,.
However, one possible is that the screen size is not set properly for
the session, or that panning is enabled.
[ Workaround ]
Downgrade the libmutter package temporarily.
ProblemType: BugDistroRelease: Ubuntu 20.04
Package: mutter 3.36.6-1ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65
Uname: Linux 5.4.0-49-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 23 15:57:17 2020
InstallationDate: Installed on 2020-08-15 (38 days ago)
InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa"
(20200815)SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2020-08-15T17:44:36
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
