Does not respect 12/24-hour setting when not logged in

Bug #1054305 reported by forteller on 2012-09-21
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ayatana Design
Indicator Date and Time
unity-greeter (Ubuntu)

Bug Description

I installed English language Ubuntu, but otherwise with localization settings for Norway. That set the clock to a 24-hour setting (as it should). And this works great, when I'm logged in the clock shows me the time as being 21:30 right now. But after turning on the computer, and before logging in (that is, in the Unity Greeter), the setting is not respected and the clock says 9:30 PM.

The clock should have the same setting in Unity Greater as after logged in

What happens:
I have 12-hour setting in Unity Greeter, and 24h when logged in. The last one is correct.

Charles Kerr (charlesk) wrote :

Indicator-datetime uses per-user settings stored in dconf files in ~/.config/dconf/ ... in order to support this, we'd need a way for the greeter to set this configuration, and for unity-greeter to feed this configure info to the indicators.

It's not clear to me that this is desirable.

Adding also-affects for unity-greeter and to Ayatana for a Design opinion.

Changed in indicator-datetime:
importance: Undecided → Wishlist
status: New → Incomplete
Changed in unity-greeter:
status: New → Incomplete
forteller (forteller) wrote :

But it has to show either 12 or 24 hour, why is the default 12 hour? From Wikipedia article on the 24 hour clock: "This system is the most commonly used time notation in the world today,[1] and is the international standard (ISO 8601) notation for time of day"

affects: unity-greeter → unity-greeter (Ubuntu)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers