Rachel, no need to switch to Mac to avoid this problem. What I ended up doing was this:
$ sudo add-apt-repository ppa:kubuntu-ppa/backports $ sudo apt update && sudo apt upgrade $ sudo apt install kubuntu-desktop -- Daniel Wilches On Thu, Mar 15, 2018 at 4:21 AM, Rachel Greenham <1724...@bugs.launchpad.net > wrote: > Well, my bug #1756036 just got (automatically-i-think) marked as a > duplicate of this one, and I'm on 18.04 (gnome-shell 3.27.92-0ubuntu1) > So that's one, Daniel. ;-) I'd been getting this on some mornings, but > the bug report was getting rejected because of outdated packages until > this morning. Interestingly it doesn't seem to happen again later in the > day, so, as noted before, length-of-sleep may be a factor. > > I reported a lot on these bugs in 17.10, until I eventually gave up and > just used my (half-the-speed) mac for a while. Freshly-installed 18.04 > and tried again, and I *am* having far less trouble. When it does go > wrong, it "fails better", in that it seems to recover reasonably well > and leave me with a working session, even if there are a couple of side- > effects (eg: having both dash-to-dock and the dash in > activities/applications) which clear on an orderly logout/login. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1724439 > > Title: > gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from > ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from > function_call() > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mutter/+bug/1724439/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724439 Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call() Status in Mutter: In Progress Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/3e662975e4b7e6829b9d68d1c2b06f429e44c854 --- left virtual box to update win10 came back and got error message ProblemType: Crash DistroRelease: 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 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 23:37:32 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-04-18 (182 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7feb2ed42d94 <meta_window_get_monitor+4>: mov 0x18(%rax),%eax PC (0x7feb2ed42d94) ok source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ?? () from /usr/lib/libgjs.so.0 ?? () from /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724439/+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
