Yes every time. I changed method and used Power/Automatic suspend instead, which actually is more convenient.
2018-04-24 23:12 GMT+02:00 Marco Trevisan (Treviño) <m...@3v1n0.net>: > Great to hear, were you getting this regularly? > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1760485). > 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: > Fix Released > Status in mutter package in Ubuntu: > Fix Released > Status in gnome-shell source package in Bionic: > Fix Released > Status in mutter source package in Bionic: > Fix Released > > Bug description: > https://errors.ubuntu.com/problem/3e662975e4b7e6829b9d68d1c2b06f > 429e44c854 > > --- > > 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 > -- Skickat från min nya mailadress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter 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() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724439/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
