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

[Bruce Pieterse]

Occurred after applying today's updates. Crashed after logging in.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: indicator-datetime 12.10.3+13.10.20130822.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Wed Aug 28 13:17:41 2013
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
ExecutableTimestamp: 1377208642
InstallationDate: Installed on 2013-03-11 (169 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime-service
ProcCwd: /home/bruce
SegvAnalysis:
 Segfault happened at: 0x7faa9c27df90 <_IO_vfprintf_internal+14352>: repnz scas %es:(%rdi),%al
 PC (0x7faa9c27df90) 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/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
Title: indicator-datetime-service crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to saucy on 2013-08-24 (3 days ago)
UserGroups: adm lpadmin sambashare sudo vboxusers www-data

[Apport retracing service (apport)]

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.