Hello Rachel, or anyone else affected, Accepted mutter into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: mutter (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1723615 Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution() Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Committed Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/130 https://errors.ubuntu.com/problem/84e05b052e88b79520a684d6113084e9be8bc339 --- [ Description ] This happened while I was away from the computer. By the timing it should have been well after the time it should have gone *into* displaysleep, and was also about 45min before I returned, so certainly wasn't the wake-up process either. What I observed when I did return: My 4K monitor didn't wake up (that's a known problem with this monitor, Dell P2715Q), the second monitor (Dell U2711) did wake up, showing the login screen. So although I've considered my Dell 4K problem a problem with waking up, I wonder if it might be actually a problem with it apparently going away completely after a longer displaysleep (it's usually fine if I just do a short sleep of a minute or two). Another possibility is the cat stepped on the keyboard and thus triggered an attempted display-wake. But that would actually be out of character (for the cat). Either way is a bug because the session should survive monitor shenanigans... :-) In some not known conditions, g-s might crash while computing global resolution for monitors. [ Test case ] There's really no test case for this bug, a part that g-s should not crash with this stacktrace. Unforuntaltey this is quite hard to reproduce, it might happen while resetting the crtc when setting up a (new) monitor or at wake up, but so far nobody has reported a way for reproducing this. [ Regression potential ] Global scale for attached monitors could not be properly computed, and thus if attaching an HiDPI device, the UI could not be scaled properly --- ProblemType: CrashDistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Oct 14 15:39:50 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-07-30 (75 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_GB.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7fae20ab44a0 <meta_monitor_mode_get_resolution>: mov 0x8(%rdi),%eax PC (0x7fae20ab44a0) ok source "0x8(%rdi)" (0x00000008) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: gnome-shell StacktraceTop: meta_monitor_mode_get_resolution () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_monitor_calculate_mode_scale () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_monitor_manager_update_logical_state_derived () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_monitor_manager_rebuild_derived () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_monitor_manager_xrandr_handle_xevent () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution() UpgradeStatus: Upgraded to artful on 2017-08-22 (53 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
