indicator-datetime-service crashed with SIGSEGV in g_date_time_to_unix()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-datetime (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I don't know
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: indicator-datetime 12.10.3+
ProcVersionSign
Uname: Linux 3.11.0-1-generic x86_64
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Aug 22 14:41:35 2013
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-01-01 (232 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/false
XDG_RUNTIME_
PATH=(custom, no user)
LANG=ru_RU.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f97440b5764: mov 0x10(%rdi),%esi
PC (0x7f97440b5764) 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_
g_date_
?? ()
indicator_
?? ()
Title: indicator-
UpgradeStatus: Upgraded to saucy on 2013-07-23 (29 days ago)
UserGroups:
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.