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
Just freshly installed Ubuntu 18.04LTS Daily Build
Was clicking on the dash, then clicked back to the desktop without opening anything.
gnome-shell crashed but didn't cause any loss of functionality. The end user would not notice this crash other than the Apport report.
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
Codename: bionic
gnome-shell:
Installed: 3.28.0-0ubuntu1
Candidate: 3.28.0-0ubuntu1
Version table:
*** 3.28.0-0ubuntu1 500
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.0-0ubuntu1
ProcVersionSign
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Tue Mar 27 17:38:53 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/
GsettingsChanges:
InstallationDate: Installed on 2018-03-27 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
JournalErrors:
-- Logs begin at Tue 2018-03-27 17:36:28 CEST, end at Tue 2018-03-27 17:41:57 CEST. --
mrt 27 17:39:59 hostname spice-vdagent[921]: Cannot access vdagent virtio channel /dev/virtio-
mrt 27 17:40:12 hostname spice-vdagent[
mrt 27 17:40:23 hostname pulseaudio[1217]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop
ProcCmdline: /usr/bin/
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: No upgrade log present (probably fresh install)
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.