indicator-datetime-service crashed with SIGSEGV in icaltimezone_ensure_coverage()

[Pete Goodall]

Just updated today. Indicator-date-time crashed as soon as I logged in. Wasn't doing anything in particular. Will see if this repeats on every login and/or reboot.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-datetime 0.3.90-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94-0ubuntu2
Architecture: amd64
Date: Wed Mar 7 13:19:39 2012
ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f07fd47b710: cmpq $0x0,0x28(%rdi)
 PC (0x7f07fd47b710) ok
 source "$0x0" ok
 destination "0x28(%rdi)" (0x7f07000004d9) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
 ?? () from /usr/lib/libical.so.0
 icaltimezone_get_utc_offset () from /usr/lib/libical.so.0
 icaltimezone_convert_time () from /usr/lib/libical.so.0
 icaltime_as_timet_with_zone () from /usr/lib/libical.so.0
 ?? () from /usr/lib/libecal-1.2.so.10
Title: indicator-datetime-service crashed with SIGSEGV in icaltimezone_get_utc_offset()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 icaltimezone_ensure_coverage (zone=0x7f07000004b1, end_year=2011) at /build/buildd/libical-0.44/src/libical/icaltimezone.c:485
 icaltimezone_get_utc_offset (zone=0x7f07000004b1, tt=0x7fff3c6d7590, is_daylight=0x0) at /build/buildd/libical-0.44/src/libical/icaltimezone.c:834
 icaltimezone_convert_time (tt=0x7fff3c6d7590, from_zone=0xb1be70, to_zone=0x7f07fd69c440) at /build/buildd/libical-0.44/src/libical/icaltimezone.c:789
 icaltime_as_timet_with_zone (tt=..., zone=0xb1be70) at /build/buildd/libical-0.44/src/libical/icaltime.c:409
 e_cal_recur_generate_instances_of_rule (comp=0x7f07cc0014e0, prop=0x0, start=1331126361, end=1333891161, cb=0x7f07fd6b7d20 <add_instance>, cb_data=0xb2a500, tz_cb=0x7f07fd6bb020 <e_cal_resolve_tzid_cb>, tz_cb_data=0xace2e0, default_timezone=0xb1be70) at e-cal-recur.c:714

[Charles Kerr (charlesk)]

This is an odd ticket... I don't see anything suspicious in the indicator-datetime code that calls ecal, and the crash is occurring down inside libical functions called by ecal.

I do notice that Ubuntu's upgraded libical from 0.44 to 0.48 in the time since this bug report was filed. Pete, did this crash ever happen again for you, and if so is it repeatable?

[Launchpad Janitor (janitor)]

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

[hamed mosavian (sahmosavian)]

this bug is bothering me since I upgraded my Ubuntu. What I do is just after logging in,
open a System Monitor,
check indicator-datetime-service's ID number and remember it,
press Alt+Ctrl+F1, log in again and
use the command kill -STOP "indicator-datetime-service's ID #"