Looks like this only ever affected 17.10: https://errors.ubuntu.com/problem/dcc31c919387fa75990e48e30880c3ec9bf46e18
** Description changed: + https://errors.ubuntu.com/problem/dcc31c919387fa75990e48e30880c3ec9bf46e18 + + --- + This bug was collected by Apport and so I don't know all the details. I just installed Ubuntu 17.10 and I have had problems with all my programs being closed (it looks as if the computer had been rebooted) after the screen had been locked. I then changed from Wayland to Xorg, just before this bug was reported, but I am uncertain if the bug report pertains to this problem, or if the bug was for the Wayland or Xorg state. I'm happy to provide more information, I just need to know what to look for. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Mon Oct 23 14:06:31 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: - + InstallationDate: Installed on 2017-10-23 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR=<set> - LANG=da_DK.UTF-8 - SHELL=/bin/false + PATH=(custom, no user) + XDG_RUNTIME_DIR=<set> + LANG=da_DK.UTF-8 + SHELL=/bin/false SegvAnalysis: - Segfault happened at: 0x7fb3f4c56233: mov 0x200(%rax),%rax - PC (0x7fb3f4c56233) ok - source "0x200(%rax)" (0x706e692f7665662f) not located in a known VMA region (needed readable region)! - destination "%rax" ok + Segfault happened at: 0x7fb3f4c56233: mov 0x200(%rax),%rax + PC (0x7fb3f4c56233) ok + source "0x200(%rax)" (0x706e692f7665662f) not located in a known VMA region (needed readable region)! + destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: - ?? () from /usr/lib/x86_64-linux-gnu/libgbm.so.1 - ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so - ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so - ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so - ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so + ?? () from /usr/lib/x86_64-linux-gnu/libgbm.so.1 + ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so + ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so + ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so + ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Released ** Changed in: mesa (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1726850 Title: gnome-shell crashed with SIGSEGV in image_get_buffers() from intel_update_image_buffers() [i965] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726850/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
