Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#36106 - Gnome 3.8's Clock won't display AM/PM
Attached to Project:
Arch Linux
Opened by Larry Bolan (ratdude747) - Thursday, 11 July 2013, 17:59 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 21 July 2013, 21:32 GMT
Opened by Larry Bolan (ratdude747) - Thursday, 11 July 2013, 17:59 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 21 July 2013, 21:32 GMT
|
DetailsDescription:
When Customizing a New Install of Arch, I found that whenever I try to change the clock from 24 hour to Am/PM, the clock doesn't change. In fact, the clock display freezes (as time passes, the time doesn't update). The clock in the settings menu works properly (see attached screenshot). Switching the time back to 24 hour mode unfreezes the clock. Additional info: Under the most recent Gnome 3.8. Steps to reproduce: 1. open up time settings 2. switch clock from 24 hour to AM/PM 3. Notice that while the time in the tiem settings window changes to AM/PM, the clock at top of the screen does not. 4. Notice that the clock at the top of the screen doesn't change it's displayed value as time goes by. 5. Switch the time back to 24 hour mode. Note that thee clock unfreezes. |
This task depends upon
Comment by Larry Bolan (ratdude747) -
Thursday, 11 July 2013, 18:04 GMT
Forgot to add: in the screenshot, I rolled back the time in the settings menu, which also didn't update the clock.
Comment by Larry Bolan (ratdude747) -
Thursday, 11 July 2013, 18:35 GMT
Just installed a couple fresh updates, rebooted, working. I'd say the bug is history if to doesn't come back within the next few days.
Screenshot from 2013-07-11 13...