gnome-calendar crashed with SIGSEGV in g_date_time_to_instant()

Bug #1759387 reported by Marcello Nuccio
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-calendar (Ubuntu)
New
Medium
Unassigned

Bug Description

It crashed when I have clicked on the next month button in the toolbar.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-calendar 3.28.0-1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 27 22:45:15 2018
ExecutablePath: /usr/bin/gnome-calendar
InstallationDate: Installed on 2018-03-27 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325)
JournalErrors:
 -- Logs begin at Tue 2018-03-27 10:24:33 CEST, end at Tue 2018-03-27 22:48:44 CEST. --
 mar 27 11:04:14 hostname kernel: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later)
 mar 27 11:04:17 hostname spice-vdagent[952]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
 mar 27 11:04:23 hostname spice-vdagent[1407]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
 mar 27 11:04:41 hostname pulseaudio[1280]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=it_IT.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f0ed2bac3cc <g_date_time_to_timezone+12>: mov 0x10(%rdi),%esi
 PC (0x7f0ed2bac3cc) ok
 source "0x10(%rdi)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
 g_date_time_to_timezone () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_date_time_to_local () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 gcal_week_header_add_event ()
 gcal_week_header_set_date ()
 ?? ()
Title: gnome-calendar crashed with SIGSEGV in g_date_time_to_timezone()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Marcello Nuccio (marcenuc) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_date_time_to_instant (datetime=datetime@entry=0x0) at ../../../../glib/gdatetime.c:733
 g_date_time_to_timezone (datetime=datetime@entry=0x0, tz=tz@entry=0x562b158e2ec0) at ../../../../glib/gdatetime.c:2636
 g_date_time_to_local (datetime=0x0) at ../../../../glib/gdatetime.c:2660
 gcal_week_header_add_event (self=0x562b1679bd70, event=0x562b17fc9260) at ../src/views/gcal-week-header.c:1878
 update_unchanged_events (new_icaldt=<optimized out>, self=0x562b1679bd70) at ../src/views/gcal-week-header.c:892

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-calendar (Ubuntu):
importance: Undecided → Medium
summary: - gnome-calendar crashed with SIGSEGV in g_date_time_to_timezone()
+ gnome-calendar crashed with SIGSEGV in g_date_time_to_instant()
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.