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

[Nicolas Devillers]

Indicator-datetime-service crash on start since a recent update.

crash is at: g_date_time_to_instant (datetime=0x0) at /build/buildd/glib2.0-2.37.6/./glib/gdatetime.c:503

and always reproducible:

nicolas@omega:~$ /usr/lib/x86_64-linux-gnu/indicator-datetime-service
Erreur de segmentation (core dumped)

I didn't figure an ubuntu package providing it's debugging symbol but let me know if there is one.

Nicolas

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: indicator-datetime 12.10.3+13.10.20130731-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6
Uname: Linux 3.11.0-3-generic x86_64
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Thu Aug 22 09:43:05 2013
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
InstallationDate: Installed on 2013-04-08 (135 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
ProcEnviron:
 SHELL=/bin/false
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fea98465764 <g_date_time_to_instant+4>: mov 0x10(%rdi),%esi
 PC (0x7fea98465764) 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: indicator-datetime
StacktraceTop:
 g_date_time_to_instant (datetime=0x0) at /build/buildd/glib2.0-2.37.6/./glib/gdatetime.c:503
 g_date_time_to_unix (datetime=<optimized out>) at /build/buildd/glib2.0-2.37.6/./glib/gdatetime.c:1899
 ?? ()
 indicator_datetime_planner_get_appointments ()
 ?? ()
Title: indicator-datetime-service crashed with SIGSEGV in g_date_time_to_instant()
UpgradeStatus: Upgraded to saucy on 2013-06-24 (58 days ago)
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1215003, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.