I'm still not sure what to make of this bug. The fix linked upstream: https://gitlab.gnome.org/GNOME/mutter/-/issues/1345
is supposedly in mutter 3.35.2 but there are plenty of these crashes after that: https://errors.ubuntu.com/problem/fda12af21f79f7f1e23ab3cc830da47eca410baa So it seems like at least one of those should not be linked here. That said, if we don't see any more crashes in 3.36.6 and 3.38.1 then there's nothing left to do and resolving the confusion is not required. -- 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/1558886 Title: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info() Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Bug description: [ Impact ] Using Ubuntu 16.04 and 20.04 LTS Beta release. Was using gnome-shell and using Chrome web browser when computer became unresponsive to any commands or mouse clicks. About 3-4 minutes later a crash report popped up on my screen. I clicked report and now I am reporting this as a new bug as I have never had this happen before on previous versions of Ubuntu. I was attempting to copy and save an image from Google Chrome when this happened. Similar crash still happening, as per https://errors.ubuntu.com/problem/fda12af21f79f7f1e23ab3cc830da47eca410baa ---- [ Test case ] Run xinput and figure device IDs for your mouse. Run this evil script with 9 changed (be sure to change both) to your id: for ((;;)) do xinput disable 9; echo Disabled; xinput enable 9; echo Enabled; done While the script runs, open some context menu in some program. It may require a few clicks due to evil script enabling/disabling mouse. This will sometimes crash GTK programs due to a mirror bug in GTK. GNOME Shell should not crash [ Regression potential ] Devices might be not be properly recognized when plugged and unplugged ---- Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 lostprophet@DigitalDamage:~$ apt-cache policy google-chrome-stable google-chrome-stable: Installed: 49.0.2623.75-1 Candidate: 49.0.2623.75-1 Version table: *** 49.0.2623.75-1 100 100 /var/lib/dpkg/status ProblemType: CrashDistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 17 22:20:56 2016 DisplayManager: lightdm ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-02-24 (22 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f634ba78320: mov 0xe0(%rdi),%rax PC (0x7f634ba78320) ok source "0xe0(%rdi)" (0x000000e0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMASignal: 11SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 clutter_x11_handle_event () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/libmutter.so.0 Title: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event() UpgradeStatus: Upgraded to xenial on 2016-03-03 (14 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1558886/+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
