clock is missing ~10% of the time

[Borim]

This bug is maybe related to Bug #1239710, as in comment #34 mentioned I created a new bug report.

After start of my pc the clock in the notification area is missing sometimes. When you kill the indicator-datetime the clock is displaying again:
sudo pkill -9 indicator-date

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-datetime 13.10.0+14.04.20140415.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic x86_64
NonfreeKernelModules: wl tbs6982fe tbs6680fe tbs6923fe tbs6985se tbs6928se tbs6982se tbs6991fe tbs6618fe tbs6983fe tbs6922fe tbs6928fe tbs6991se tbs6290fe
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Feb 14 10:26:41 2015
InstallationDate: Installed on 2014-03-30 (320 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140329)
SourcePackage: indicator-datetime
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

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

[Albert Astals Cid (aacid)]

When this happens the process is still around but it doesn't respond the the dbus calls

tsdgeos_work@xps:~$ gdbus call --session --dest com.canonical.indicator.datetime --object-path /com/canonical/indicator/datetime --method org.gtk.Actions.DescribeAll
S'ha produït un error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.indicator.datetime was not provided by any .service files
tsdgeos_work@xps:~$ gdbus call --session --dest com.canonical.indicator.datetime --object-path /com/canonical/indicator/datetime/desktop --method org.gtk.Menus.Start [0]
S'ha produït un error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.indicator.datetime was not provided by any .service files

[Lars Karlitski (larsu)]

indicator-datetime-service seems to do the right thing when it loses its name (exit the process). Maybe it gets stuck in a deadlock and doesn't respond to D-Bus calls anymore?

Can someone please attach a backtrace of the running process when this happens again?