gnome-calendar crashed with SIGSEGV in pvl_head()

Bug #1725689 reported by Fabio Rizzioli
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-calendar (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Sometimes login fails

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-calendar 3.26.2-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 21 15:20:37 2017
ExecutablePath: /usr/bin/gnome-calendar
InstallationDate: Installed on 2017-05-19 (154 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f1e4a9482e0 <pvl_head>: mov 0x8(%rdi),%rax
 PC (0x7f1e4a9482e0) ok
 source "0x8(%rdi)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
 pvl_head () from /usr/lib/x86_64-linux-gnu/libical.so.2
 icalproperty_get_first_parameter () from /usr/lib/x86_64-linux-gnu/libical.so.2
 e_cal_component_alarm_get_trigger () from /usr/lib/x86_64-linux-gnu/libecal-1.2.so.19
 get_alarm_trigger_minutes ()
 ?? ()
Title: gnome-calendar crashed with SIGSEGV in pvl_head()
UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Fabio Rizzioli (crotalone) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 pvl_head (L=0x0) at ./src/libical/pvl.c:484
 icalproperty_get_first_parameter (p=0x564db9c38bc0, kind=ICAL_VALUE_PARAMETER) at ./src/libical/icalproperty.c:750
 e_cal_component_alarm_get_trigger (alarm=alarm@entry=0x564dba053410, trigger=trigger@entry=0x7ffcf635da50) at ./src/calendar/libecal/e-cal-component.c:6080
 get_alarm_trigger_minutes (event=event@entry=0x564db97946a0, alarm=alarm@entry=0x564dba053410) at ../src/gcal-utils.c:1064
 remove_button_clicked (button=<optimized out>, row=0x564db982aef0) at ../src/gcal-edit-dialog.c:930

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
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

information type: Private → Public
Changed in gnome-calendar (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-calendar (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-calendar (Ubuntu):
status: Incomplete → Expired
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.