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

Bug #1215038 reported by siucdude
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
indicator-datetime (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

New Bug on 13.10 Beta

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
NonfreeKernelModules: nvidia
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Wed Aug 21 07:40:37 2013
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
InstallationDate: Installed on 2011-04-03 (870 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
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: 0x7fc6fe8f6764: mov 0x10(%rdi),%esi
 PC (0x7fc6fe8f6764) 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: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
siucdude (siucdude) wrote :
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in indicator-datetime (Ubuntu):
status: New → Confirmed
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

tags: removed: need-amd64-retrace
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.