Chrome OS changing timezone added manually to network geo location. |
||||
Issue descriptionChrome Version: Google Chrome 55.0.2883.105 (32-bit) Chrome OS Version: 8872.76.0 Chrome OS Platform: Chromebook Samsung XE303C12 SNOW Network info: Tested on WPA/WAP2 network Steps To Reproduce: 1-Turn Chromebook on 2-Sign in 3-Change Timezone manually and unchecked 'Set timezone automatically using your location' 4- after turning off and turning back on the device, the timezone gets changed in relation with the network, not respecting selection made at settings Expected Result: Device should respect timezone setting and keep timezone selected manually Actual Result: Device changing the timezone as soon as connecting to network How frequently does this problem reproduce? Always that device gets rebooted, powered off/on or user signs out. What is the impact to the user, and is there a workaround? If so, what is it? User network or ISP provider is located on a different timezone than where the device is physically, he has to change the timezone every single time manually to match with his physical location. This happens on both managed and unmanaged devices, workaround on managed devices is to define or enforce timezone policies, this is not possible on unmanaged devices. Please provide any additional information below. Attach a screen shot or log if possible. **Noticed this issue only happens on Chromebooks running 32 Bit OS version, Tried reproducing on Chromebooks such as HP14 or Dell Chromebook 13, issue does not happen there**
,
May 17 2018
,
Dec 7
Hello! This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time. - If you are currently working on this bug, please provide an update. - If you are currently affected by this bug, please update with your current symptoms and relevant logs. If there has been no updates provided by EOD Wednesday, 12/12/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary. Thank you!
,
Dec 13
Bulk-assigning unassigned status area bugs to me.
,
Dec 17
Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information. |
||||
►
Sign in to add a comment |
||||
Comment 1 by mkarkada@chromium.org
, Nov 3 2017Components: UI>Settings UI>Shell>StatusArea
Status: Untriaged (was: Unconfirmed)