gnome-shell crashed with signal 5 in g_log_default_handler()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Error came up shortly after login, first login after a reboot, immediately following this morning's updates. gnome-shell did not receive an update this time around, nor anything else very specifically gnome, but kernel did. Apart from apport giving me an error to report, I didn't actually notice any wrong or failed behaviour (except I suppose maybe a delay) so presumably it recovered by itself.
I've often reported from a desktop with gnome-shell issues connected by displayport to a dell monitor. This is not that machine (it's a 2015 macbook pro) and no external monitor (or anything) is attached. I don't generally get gnome-shell errors on this machine, so it's not one of my usuals.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.0-0ubuntu1
ProcVersionSign
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.9-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Tue Mar 27 08:58:44 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/
GsettingsChanges:
InstallationDate: Installed on 2017-08-07 (231 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_GB.UTF-8
SHELL=/bin/false
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
?? () from /lib/x86_
g_log_
?? ()
g_logv () from /lib/x86_
g_log () from /lib/x86_
Title: gnome-shell crashed with signal 5 in g_log_default_
UpgradeStatus: Upgraded to bionic on 2018-03-10 (16 days ago)
UserGroups:
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 #1748450, 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.