Cinnamon Clock does not update time

[Lucas]

The Cinnamon Clock does not update the displayed time in the panel unless you open the time/calendar settings and change something there (for instance clicking on the checkbox for week numbers in the calendar).

It is a fresh install of Mint13 Maya 64bit with Cinnamon showing the traditional desktop (panel on top and bottom). I've changed the time display format but changing it back does not help.

[Lukas Schink (lukas-schink)]

I have the same issue. The clock worked for some time after installing Mint13 but somehow it doesn't update the time in the cinnamon panel now. The time is shown correct in the 'date and time setting' and on console using 'date' command.
On login and on time format change for the panel clock the current time is set in the panel clock, but then it is not updated any further and stays at the time of login or when the settings were changed.

[Tasha Six (tashasix6)]

Same issue..

[Ander (ander5151)]

Yes, this just happened to us when I was setting up Mint 14 Cinnamon on my son's PC.

Unbeknownst to me, my son opened the Date and Time Settings and changed the customizable format variables (in the "Date and time format for the panel" box). He didn't want the date to appear on his panel, only only the time—so he removed the date variables. From that point on, the clock refused to update.

When we restored some date variables, that fixed it. So apparently the app expects both date and time variables in that string, no matter what.

[BenR (benregier)]

@Ander - Could you post the date and time variables that are working for you? I don't think I ever modified mine, and the time is not updating for me.

These are the formats I'm using:
Date format for the panel: %a %b %e, %l:%m %p
Date format inside the applet: %A %B %e, %Y

[Lukas Schink (lukas-schink)]

While my Clock was working well in Mint14 with customized formats. Now in Mint15 the Issue is back for me. It appeared after changing the format string. Switching it back doesn't solve the problem. But I can't believe, that it is only so few people experiencing this problem. I hope somebody will find out what is happening here it is quite annoying to look at the clock showing the wrong time...

[Karthik Chandraraj (ckarthik17)]

I am also getting the problem in Linux Mint 15 Cinnamon.

Format I am trying to use
%l:%M %p

[HDJones (1hdjones1+ubuntuone)]

Well, it didn't take long to find others with this same issue. :) I installed Mint 13 Cinnamon 3 or 4 nights ago, but I think this behavior of the clock seizing didn't show up until tonight-- I think I would have noticed it previously. In my case the clock updates to the correct time at 8 minutes past each hour and then doesn't advance any further until another hour has passed and it sets itself correct again.

My format strings are
panel: %a %b %e %l:%m %p
inside date applet: %A %B %e, %Y

[comintern (brent-mckibbin)]

I can confirm this as well, and strangely mine stops at 8 minutes after the hour also and has the same behaviour of updating only the hour after the minutes freeze. I'm running Mint 15 Cinnamon (64) bit.

The format strings I'm using are:
panel: %b %e %l:%m %p
applet:%b %e %l:%m %p

[Brombomb (brombomb)]

Wanted to point out that a lot of people are using %m for the Minutes, which is incorrect. %M is for minutes, and %m is for month number.

For a valid clock time either %l:%M (12 hour) or %H:%M (24 hour), with %S being seconds

It is shown in this thread for a few users, but I wanted to point out the specific confusion.

[Mindaugas (mslavikas)]

I have the same issue. While my Clock was working well in Mint 15 Cinnamon (64) bit with customized formats.

I'm using time format:
%H:%M

How to fix this problem?

[Mindaugas (mslavikas)]

Problem solved. Clock workin. Just changed back (from Lithuanian) in Regional Settings -> Format -> United States (Englis) and rebooted.

[Mike Reid (we0h-mike)]

This is what fixed my clock so it showed the correct time:
For a valid clock time either %l:%M (12 hour) or %H:%M (24 hour), with %S being seconds

I was using a lower case m which showed several minutes lagging and changed it to a upper case M then it showed the correct time.

Mike