Description of problem:
At gdm screen at 00:12 local time, I see 12:12 which, presumably, 12 hour clock format
$ cat /etc/sysconfig/i18n
Version-Release number of selected component (if applicable):
I think the date and time formats in gdm are handled by the translations, but Fedora's fix-clock.patch broke that by merging the format strings (date and time format were translated separately, plus date or time first is handled by another translation).
I just rebuilt gdm-2.28.1-24.fc12 without applying fix-clock.patch, and got a 24-hour clock and a date that nicely matches gnome-panel, in en_GB.
Actually, I don't think fix-clock.patch was in gdm-2.28.0-6.fc12, the original report could be just due to the translation for "ru" not setting the 24-hour format.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
Running with LANG set to sv_SE.utf8, I also get a 12-hour clock.
The fix-clock.patch adds a lot of messages marked for translation, but there are no translations for them in any gdm.mo files. I tried to add the following to the Swedish gdm.mo file:
msgid "%a %l:%M %p"
msgstr "%a %H:%M"
That helps! Now I get a proper 24-hour clock! The analysis in comment 1 seems to be confirmed.
So either the fix-clock.patch could be dropped, leaving the original time format, or the additional messages added in this patch could be made available for translation. (I guess they aren't. Or are they?)
translate.fedoraproject.org could surely handle the translation if you want to go that way. But you would have to merge the additional translations with the original ones from upstreams. It sounds a bit messy, but I may be wrong.
Thank you for the bug report.
Fedora Bugzappers volunteer triage team
*** Bug 600778 has been marked as a duplicate of this bug. ***
Why exactly this patch can't be pushed upstream?
It was for 2.30 - http://git.gnome.org/browse/gdm/commit/?id=87248d5c3e0a90c3b0748c7be05a9e6eac231737
Oh, thanks then.
I don't think it is worthy to fix F12 (string freezes and such), but that's up to gdm maintainer.
move this to f14 for triaging as gdm-2.30 is already built for f13 and f14
This bug is fixed in F13 and F14.