indicator-datetime-service crashed with SIGSEGV in g_date_time_to_instant()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-datetime (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Thread 1 (Thread 0x7ffff7fce840 (LWP 4099)):
#0 g_date_
#1 0x00007ffff6be5659 in g_date_time_to_unix (datetime=
#2 0x0000000000405c3f in my_get_appointments (planner=0x61f820, begin_datetime=
#3 0x000000000040541f in indicator_
#4 0x000000000040671b in get_all_
#5 create_
#6 0x0000000000408783 in init_gactions (self=0x61d0e0) at service.c:1459
#7 indicator_
#8 0x00007ffff6ee4d7b in g_type_
#9 0x00007ffff6ec8475 in g_object_
#10 0x00007ffff6eca27d in g_object_newv (object_
#11 0x00007ffff6ecaa2c in g_object_new (object_
#12 0x0000000000408cd2 in indicator_
#13 0x0000000000404f52 in main (argc=<optimised out>, argv=<optimised out>) at main.c:53
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: indicator-datetime 12.10.3+
ProcVersionSign
Uname: Linux 3.11.0-3-generic x86_64
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Thu Aug 22 19:46:05 2013
ExecutablePath: /usr/lib/
MarkForUpload: True
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7fd2f5814764 <g_date_
PC (0x7fd2f5814764) 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_
g_date_
my_get_
indicator_
get_all_
Title: indicator-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout libvirtd lpadmin netdev plugdev sambashare users video
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.