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

Bug #1500806 reported by Abhishek
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
GNOME System Log
Fix Released
Medium
gnome-system-log (Debian)
Fix Released
Unknown
gnome-system-log (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Segfaults immediately after starting.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: gnome-system-log 3.9.90-3
Uname: Linux 4.0.9-040009-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Sep 29 15:40:09 2015
ExecutablePath: /usr/bin/gnome-system-log
InstallationDate: Installed on 2013-07-31 (790 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
ProcCmdline: gnome-system-log
SegvAnalysis: Failure: Unknown offset literal: [rdi+0x10]
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-09-25 (3 days ago)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo

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

StacktraceTop:
 g_time_zone_get_abbreviation (tz=0x0, interval=6) at /build/glib2.0-pRoDo9/glib2.0-2.46.0/./glib/gtimezone.c:1782
 g_date_time_format_locale (datetime=<optimized out>, format=0x7f180923a318 <error: Cannot access memory at address 0x7f180923a318>, outstr=0x1834ce0, locale_is_utf8=<optimized out>) at /build/glib2.0-pRoDo9/glib2.0-2.46.0/./glib/gdatetime.c:2484
 g_date_time_format_locale (datetime=datetime@entry=0x1834940, format=0x41455a "", format@entry=0x414558 "%X", outstr=outstr@entry=0x1834ce0, locale_is_utf8=locale_is_utf8@entry=1) at /build/glib2.0-pRoDo9/glib2.0-2.46.0/./glib/gdatetime.c:2459
 g_date_time_format (datetime=0x1834940, format=0x414558 "%X") at /build/glib2.0-pRoDo9/glib2.0-2.46.0/./glib/gdatetime.c:2637
 ?? ()

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
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-system-log (Ubuntu):
status: New → Confirmed
information type: Private → Public
Revision history for this message
Sebastien Bacher (seb128) wrote :

That should be fixed with https://git.gnome.org/browse/gnome-system-log/commit/?id=a09f87bafc833d199cfd8364dff72b4c2e812af8
I've sent a debdiff to Debian, the package is in sync so it would be good if they could include it, bugs.debian.org/cgi-bin/bugreport.cgi?bug=802326

Changed in gnome-system-log (Ubuntu):
status: Confirmed → Fix Committed
Changed in gnome-system-log (Debian):
status: Unknown → New
Changed in gnome-system-log:
importance: Unknown → Medium
status: Unknown → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-system-log - 3.9.90-4

---------------
gnome-system-log (3.9.90-4) unstable; urgency=medium

  [ Sebastien Bacher ]
  * debian/patches/03_git_invalid_unref.patch:
    - backport upstream commit to fix segfaults (lp: #1500806, Closes:
      #802326)

 -- Iain Lane <email address hidden> Mon, 19 Oct 2015 16:05:00 +0100

Changed in gnome-system-log (Ubuntu):
status: Fix Committed → Fix Released
Changed in gnome-system-log (Debian):
status: New → 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.