Ubuntu
indicator-datetime package

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

Bug #1215215 reported by Yabulda on 2013-08-22

This bug report is a duplicate of: Bug #1215003: indicator-datetime-service crashed with SIGSEGV in g_date_time_to_unix(). Edit Remove

This bug affects 9 people

Affects		Status	Importance	Assigned to	Milestone
	indicator-datetime (Ubuntu)	Fix Committed	High	Unassigned

Bug Description

happened after logging into desktop

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: indicator-datetime 12.10.3+13.10.20130731-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Wed Aug 21 21:08:36 2013
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
InstallationDate: Installed on 2013-06-03 (79 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
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=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f2ff042d764: mov 0x10(%rdi),%esi
PC (0x7f2ff042d764) 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:
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_date_time_to_unix () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? ()
indicator_datetime_planner_get_appointments ()
?? ()
Title: indicator-datetime-service crashed with SIGSEGV in g_date_time_to_unix()
UpgradeStatus: Upgraded to saucy on 2013-07-08 (44 days ago)
UserGroups:

Tags:

Revision history for this message

Yabulda (yabulda) wrote on 2013-08-22:

Dependencies.txt Edit (9.1 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (647 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (68.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (796 bytes, text/plain; charset="utf-8")
Registers.txt Edit (695 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (6.3 KiB, text/plain; charset="utf-8")

information type:

Private → Public

Revision history for this message

Apport retracing service (apport) wrote on 2013-08-22:

Stacktrace:
#0 0x00007f2ff042d764 in g_date_get_sunday_weeks_in_year (year=<optimized out>) at /build/buildd/glib2.0-2.37.5/./glib/gdate.c:1874
         d = {julian_days = 25483296, julian = 0, dmy = 0, day = 0, month = 0, year = 0}
         __PRETTY_FUNCTION__ = "g_date_get_sunday_weeks_in_year"
#1 0x0000000000000000 in ?? ()
No symbol table info available.
StacktraceSource:
#0 0x00007f2ff042d764 in g_date_get_sunday_weeks_in_year (year=<optimized out>) at /build/buildd/glib2.0-2.37.5/./glib/gdate.c:1874
   [Error: /build/buildd/glib2.0-2.37.5/./glib/gdate.c was not found in source tree]
#1 0x0000000000000000 in ?? ()
StacktraceTop:
g_date_get_sunday_weeks_in_year (year=<optimized out>) at /build/buildd/glib2.0-2.37.5/./glib/gdate.c:1874
?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2013-08-22: ThreadStacktrace.txt

ThreadStacktrace.txt Edit (3.2 KiB, text/plain)

Changed in indicator-datetime (Ubuntu):
status:	New → Invalid

Revision history for this message

Apport retracing service (apport) wrote on 2013-08-22: Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libglapi-mesa version 9.2.0~git20130729+9.2.9b8ad643-0ubuntu0sarvatt required, but 9.1.6-2ubuntu2 is available
libglib2.0-data version 2.37.6-1ubuntu1 required, but 2.37.5-1ubuntu1 is available
libdrm-nouveau2 version 2.4.46+git20130702.c6d73cfe-0ubuntu0sarvatt required, but 2.4.46-1 is available
libglib2.0-0 version 2.37.6-1ubuntu1 required, but 2.37.5-1ubuntu1 is available
outdated debug symbol package for libgcr-3-1: package version 3.8.2-4 dbgsym version 3.6.2-0ubuntu2
libdrm-intel1 version 2.4.46+git20130702.c6d73cfe-0ubuntu0sarvatt required, but 2.4.46-1 is available
libgl1-mesa-dri version 9.2.0~git20130729+9.2.9b8ad643-0ubuntu0sarvatt required, but 9.1.6-2ubuntu2 is available
libgl1-mesa-glx version 9.2.0~git20130729+9.2.9b8ad643-0ubuntu0sarvatt required, but 9.1.6-2ubuntu2 is available
libdrm-radeon1 version 2.4.46+git20130702.c6d73cfe-0ubuntu0sarvatt required, but 2.4.46-1 is available
libdrm2 version 2.4.46+git20130702.c6d73cfe-0ubuntu0sarvatt required, but 2.4.46-1 is available
outdated debug symbol package for libexpat1: package version 2.1.0-4 dbgsym version 2.1.0-2

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags:

removed: need-amd64-retrace

Revision history for this message

Pavol Klačanský (pavolzetor-deactivatedaccount) wrote on 2013-08-22:

why is it invalid, I got same error in saucy

Revision history for this message

Mikhail Paulyshka (pavlyshko) wrote on 2013-08-22:

Same error, bug is valid.

Revision history for this message

Sebastien Bacher (seb128) wrote on 2013-08-22:

That's an issue for those running saucy-proposed's glib version, please don't run saucy-proposed it's made for automatic testing and transitions, not for users...

The bug is fixed with https://code.launchpad.net/~laney/indicator-datetime/valid-day-of-month/+merge/181501 in any case