gnome-shell crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
this is happenning quite often after the recent gnome-shell update
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.25.91-0ubuntu2
ProcVersionSign
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sun Sep 3 01:12:05 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2017-07-08 (56 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7f40d8e31a80: mov 0x80(%rdi),%eax
PC (0x7f40d8e31a80) ok
source "0x80(%rdi)" (0x00000080) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
() at /usr/lib/
() at /usr/lib/
st_theme_
st_widget_
() at /usr/lib/
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: Upgraded to artful on 2017-07-19 (46 days ago)
UserGroups: adm bluetooth cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape users vboxusers
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 #1714542, 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.