gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
If I switch off my monitor or if it goes to sleep, with either Dash To Dock or the Ubuntu-flavored version of the plugin will crash and refuse to work until I reboot.
It doesn't seem to happen on Ubuntu 16.04 with gnome-shell and an Nvidia graphics card (I tested it with that hardware on another system), but seems to exhibit this behavior more often on my Intel integrated graphics.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.0-0ubuntu5
ProcVersionSign
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 12 16:14:07 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/
GsettingsChanges:
b'org.gnome.shell' b'enabled-
b'org.gnome.shell' b'had-bluetooth
b'org.gnome.shell' b'app-picker-view' b'uint32 1'
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.
InstallationDate: Installed on 2018-01-20 (81 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180120)
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7f0772664c24 <meta_window_
PC (0x7f0772664c24) 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_
ffi_call_unix64 () from /usr/lib/
ffi_call () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: gnome-shell crashed with SIGSEGV in meta_window_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1724439, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.