gnome-shell crashed with signal 5 in g_log_default_handler()

Bug #1630218 reported by ubuntu38 on 2016-10-04
52
This bug affects 11 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Medium
Unassigned

Bug Description

The system is reporting this issue when I get logged into GNOME X11 session and I can't speak for if it is same using the Wayland session.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: gnome-shell 3.20.3-1ubuntu2
Uname: Linux 4.8.0-17-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat Oct 1 18:55:43 2016
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2015-10-26 (344 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20151017.1)
LocalLibraries: /usr/local/lib/libfreetype.so.6.12.2
ProcCmdline: /usr/bin/gnome-shell
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter.so.0
 ?? ()
 ?? ()
 g_log_writer_journald () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with signal 5 in g_log_default_handler()
UpgradeStatus: Upgraded to yakkety on 2016-10-01 (2 days ago)
UserGroups:

ubuntu38 (ubuntu38) wrote :

StacktraceTop:
 g_log_default_handler () from /tmp/apport_sandbox_bsyJwC/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /tmp/apport_sandbox_bsyJwC/usr/lib/x86_64-linux-gnu/libmutter.so.0
 ?? ()
 default_log_handler (log_domain=0xba4f654f48e14700 <error: Cannot access memory at address 0xba4f654f48e14700>, log_level=627046208, message=0x5592255ff740 "Connection to xwayland lost", data=0x559224f45ad0) at main.c:313
 g_log_writer_journald () from /tmp/apport_sandbox_bsyJwC/lib/x86_64-linux-gnu/libglib-2.0.so.0

Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test.

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-shell (Ubuntu):
status: Incomplete → Expired

my real distro release is Ubuntu 18.04 LTS Bionic Beaver Alpha 1

stinger (dev-t) on 2017-11-16
Changed in gnome-shell (Ubuntu):
status: Expired → New
status: New → Confirmed
Per-Inge (per-inge-hallin) wrote :

I suppose it's this bug even if I'm on Ubuntu 18.04 with kernel 4.15-RC3

Doug McMahon (mc3man) on 2017-12-31
tags: added: bionic
removed: yakkety
Daniel van Vugt (vanvugt) wrote :

This bug should have been kept as Expired ideally, especially since the original reporter has not yet replied to comment #6. And users of newer Ubuntu releases should log new bugs in future, please.

That all said, looking at the attached Stacktrace.txt and StacktraceSource.txt, I can tell this is actually a duplicate of the most common gnome-shell crash; bug 1505409

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers