gnome-system-log crashed with SIGSEGV in g_time_zone_get_abbreviation()

Bug #1507332 reported by Dario Bertero
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-system-log (Ubuntu)
New
Medium
Unassigned

Bug Description

As in title. Tried to start gnome-system-log, it displayed immediately the crash dialog.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: gnome-system-log 3.9.90-3
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Oct 19 00:01:13 2015
ExecutablePath: /usr/bin/gnome-system-log
InstallationDate: Installed on 2015-08-22 (57 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/bin/gnome-system-log
ProcEnviron:
 LANGUAGE=en_HK:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_HK.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f363bc0c0f4 <g_time_zone_get_abbreviation+4>: mov 0x10(%rdi),%rax
 PC (0x7f363bc0c0f4) ok
 source "0x10(%rdi)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-system-log
StacktraceTop:
 g_time_zone_get_abbreviation () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_date_time_format () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
Title: gnome-system-log crashed with SIGSEGV in g_time_zone_get_abbreviation()
UpgradeStatus: Upgraded to wily on 2015-10-16 (2 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Dario Bertero (anrvrx) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_time_zone_get_abbreviation (tz=0x0, interval=70) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gtimezone.c:1782
 g_date_time_format_locale (datetime=<optimized out>, format=0x7f363268f31a <error: Cannot access memory at address 0x7f363268f31a>, outstr=0xa3e2e0, locale_is_utf8=<optimized out>) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gdatetime.c:2484
 g_date_time_format_locale (datetime=datetime@entry=0xad5780, format=0x41455a "", format@entry=0x414558 "%X", outstr=outstr@entry=0xa3e2e0, locale_is_utf8=locale_is_utf8@entry=1) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gdatetime.c:2459
 g_date_time_format (datetime=datetime@entry=0xad5780, format=format@entry=0x414558 "%X") at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gdatetime.c:2637
 logview_update_header (logview=logview@entry=0xb52320, active=active@entry=0xc6a6e0, selected_day=selected_day@entry=0x0) at logview-window.c:204

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-system-log (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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