gnome-shell crashed with SIGSEGV in g_time_zone_ref() from g_date_time_alloc() from g_date_time_from_instant() from g_date_time_new_from_timeval() from g_date_time_new_now()

Bug #1689828 reported by paregistrase
30
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gnome-desktop
Fix Released
Medium
gnome-desktop3 (Ubuntu)
Fix Released
Medium
Unassigned
gnome-shell (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

https://errors.ubuntu.com/problem/4deb8ab6e5fbe049ceb3c53e0e961e23126a0375

---

changing settings in gnome-tweak

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.24.1-0ubuntu3
Uname: Linux 4.11.0-041100-generic x86_64
ApportVersion: 2.20.4-0ubuntu6
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Wed May 10 16:09:14 2017
DisplayManager: lightdm
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2017-04-17 (22 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=es_ES
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fadafcb7830 <g_time_zone_ref>: mov 0x18(%rdi),%eax
 PC (0x7fadafcb7830) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 g_time_zone_ref () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_date_time_new_now () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgnome-desktop-3.so.12
Title: gnome-shell crashed with SIGSEGV in g_time_zone_ref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
paregistrase (paregistrase) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_time_zone_ref (tz=tz@entry=0x0) at ../../../../glib/gtimezone.c:267
 g_date_time_alloc (tz=tz@entry=0x0) at ../../../../glib/gdatetime.c:435
 g_date_time_from_instant (tz=tz@entry=0x0, instant=63630108554322603) at ../../../../glib/gdatetime.c:530
 g_date_time_new_from_timeval (tv=0x7ffe494cbdc0, tz=0x0) at ../../../../glib/gdatetime.c:653
 g_date_time_new_now (tz=0x0) at ../../../../glib/gdatetime.c:711

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
information type: Private → Public
summary: - gnome-shell crashed with SIGSEGV in g_time_zone_ref()
+ gnome-shell crashed with SIGSEGV in g_time_zone_ref() from
+ g_date_time_alloc() from g_date_time_from_instant() from
+ g_date_time_new_from_timeval() from g_date_time_new_now()
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
description: updated
Tim Lunn (darkxst)
Changed in gnome-desktop3 (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
no longer affects: gnome-shell
Changed in gnome-desktop:
importance: Unknown → Medium
status: Unknown → Confirmed
Changed in gnome-desktop:
status: Confirmed → Fix Released
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Fix Released, apparently. Zero reports of this crash after 17.10.

Changed in gnome-shell (Ubuntu):
status: Confirmed → Fix Released
Changed in gnome-desktop3 (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.