gnome-calendar crashed with SIGSEGV in get_start_of_week()

Bug #1666205 reported by Trafex
102
This bug affects 22 people
Affects Status Importance Assigned to Milestone
gnome-calendar (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Trying to start Gnome Calendar immediately crashed.

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: gnome-calendar 3.23.90-0ubuntu2
ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
Uname: Linux 4.9.0-15-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Feb 20 13:30:24 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-calendar
InstallationDate: Installed on 2016-08-30 (174 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x561074b4ac65 <get_start_of_week+37>: mov 0x0(%rbp),%r12d
 PC (0x561074b4ac65) ok
 source "0x0(%rbp)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%r12d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
 get_start_of_week ()
 gcal_week_header_add_event ()
 ?? ()
 ?? ()
 e_cal_data_model_subscribe ()
Title: gnome-calendar crashed with SIGSEGV in get_start_of_week()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo

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

StacktraceTop:
 get_start_of_week (date=0x0) at gcal-utils.c:534
 gcal_week_header_add_event (self=0x5610786fa140, event=0x561078987dc0) at views/gcal-week-header.c:1580
 cal_data_model_add_to_subscriber (data_model=data_model@entry=0x56107617c1c0, client=<optimized out>, id=<optimized out>, component=<optimized out>, instance_start=<optimized out>, instance_end=<optimized out>, user_data=0x56107634d350) at e-cal-data-model.c:1740
 cal_data_model_foreach_component (data_model=data_model@entry=0x56107617c1c0, in_range_start=in_range_start@entry=1486940400, in_range_end=in_range_end@entry=1487545200, func=func@entry=0x561074b1cd40 <cal_data_model_add_to_subscriber>, user_data=user_data@entry=0x56107634d350, include_lost_components=include_lost_components@entry=1) at e-cal-data-model.c:2565
 e_cal_data_model_subscribe (data_model=0x56107617c1c0, subscriber=0x56107634d350, range_start=1486940400, range_end=1487545200) at e-cal-data-model.c:2761

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
tags: removed: need-amd64-retrace
Jeremy Bícha (jbicha)
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-calendar (Ubuntu):
status: New → Confirmed
Revision history for this message
Brains (brains) wrote :

I subsequently ran it from the terminal. The application started faultlessly. It seems to do now including from the dash or the application overview.

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.