gnome-shell crashed with SIGSEGV in g_settings_get_enum() from update_clock() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist()

Bug #1629822 reported by Cliff Carson
28
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Fix Released
High
Unassigned

Bug Description

https://errors.ubuntu.com/problem/924ae5ed07309bcf869deeac49211d615dd24b67

---

This crash occurred on first boot in the morning. The desktop initially flash up with the desktop ICONs on a total black background for several seconds then the normal desktop appear but a lower resolution than normal.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: gnome-shell 3.20.3-1ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Oct 3 05:55:39 2016
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2016-08-16 (47 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160813)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f9db6062a48 <g_settings_get_enum+40>: mov (%rbx),%rdx
 PC (0x7f9db6062a48) ok
 source "(%rbx)" (0x00005614) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 g_settings_get_enum () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgnome-desktop-3.so.12
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in g_settings_get_enum()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Cliff Carson (ccarson1) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_settings_get_enum () from /tmp/apport_sandbox_SwbrDq/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 update_clock (data=0x5646a2d3efa0) at gnome-wall-clock.c:345
 g_closure_invoke () from /tmp/apport_sandbox_SwbrDq/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 signal_emit_unlocked_R () from /tmp/apport_sandbox_SwbrDq/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /tmp/apport_sandbox_SwbrDq/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
tags: added: zesty
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: gnome-shell crashed with SIGSEGV in g_settings_get_enum()

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
information type: Private → Public
summary: - gnome-shell crashed with SIGSEGV in g_settings_get_enum()
+ gnome-shell crashed with SIGSEGV in g_settings_get_enum() from
+ update_clock() from g_closure_invoke() from signal_emit_unlocked_R()
+ from g_signal_emit_valist()
description: updated
Changed in gnome-shell (Ubuntu):
importance: Medium → High
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Fix released (zero crash reports after 17.04)

Changed in gnome-shell (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.