indicator-datetime-service crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-datetime (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Happened on login after update and restart
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: indicator-datetime 12.10.3+
ProcVersionSign
Uname: Linux 3.11.0-2-generic x86_64
NonfreeKernelMo
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Sat Aug 17 14:59:14 2013
ExecutablePath: /usr/lib/
ExecutableTimes
InstallationDate: Installed on 2013-03-28 (141 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130328)
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcCwd: /home/boteeka
ProcEnviron:
XDG_RUNTIME_
SHELL=/bin/bash
LANGUAGE=en_IE:en
PATH=(custom, no user)
LANG=en_IE.UTF-8
SegvAnalysis:
Segfault happened at: 0x7ffe5ea9df90 <_IO_vfprintf_
PC (0x7ffe5ea9df90) ok
source "%es:(%rdi)" (0x00000001) not located in a known VMA region (needed readable region)!
destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
g_signal_emit () from /usr/lib/
?? () from /usr/lib/
Title: indicator-
UpgradeStatus: Upgraded to saucy on 2013-08-17 (0 days ago)
UserGroups: adm lpadmin sambashare sudo
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 #1195874, 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.