New issue
Advanced search Search tips

Issue 876287 link

Starred by 1 user
Status: Assigned
Owner:
isandrk@chromium.org
Cc:
kathrelk...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

SystemUse24HourClock Works on Login, not in Public Session

Project Member Reported by mikewilusz@chromium.org, Aug 21 
Chrome Version: 67.0.3396.99
Chrome OS Version: 10575.58.0
Chrome OS Platform: Tested on Samus & Eve
Network info: N/A


Steps To Reproduce:
(1) Policy SystemUse24HourClock is set to "true"
(2) Login screen displays 24-hour clock
(3) Start public session and 24-hour clock no longer set

Expected Result:
SystemUse24HourClock should show 24 hour clock on both login screen and public session. According to https://www.chromium.org/administrators/policy-list-3#SystemUse24HourClock this should support both the login screen and public session kiosk.

Actual Result: 24 hour clock works on login screen, but not public session.

How frequently does this problem reproduce? Always

What is the impact to the user, and is there a workaround? If so, what is
it? The only workaround is to set it manually, but this doesn't persist for public session. One customer reporting the issue is a healthcare system, whom depends on 24 hour time for accurate time reporting.

Logs attached.
debug-logs_20180821-085148.tgz
317 KB Download

Comment 1 by zalcorn@chromium.org, Dec 12

Components: -UI>Shell>StartScreen UI>Shell>PublicAccounts

Comment 2 by chchakrapani@chromium.org, Dec 28

Cc: kathrelk...@chromium.org
Status: Untriaged (was: Unconfirmed)
Issue is reproducible on Google Chrome (73.0.3644.0,11476.0.0) nautilus via yaps.

Device time changes to 12-hour format in the public session and is shown in 24-hour format.

Attached logs.
debug-logs_20181227-163839.tgz
759 KB Download
policies.json
7.1 KB View Download
Screenshot 2018-12-27 at 4.38.25 PM.png
202 KB View Download

Comment 3 by atwilson@google.com, Jan 11

Labels: -Pri-1 Enterprise-Triaged Hotlist-GoodFirstBug Pri-2
Owner: isandrk@chromium.org

Comment 4 by benhenry@google.com, Jan 11

Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.
►

Sign in to add a comment