New issue
Advanced search Search tips

Issue 788895 link

Starred by 6 users

Issue metadata

Status: Verified
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

ChromeOS issue: Avatar and wallpaper not loaded on first login.

Project Member Reported by llinares@chromium.org, Nov 27 2017

Issue description

Version of Google Chrome (Wrench-> About Google Chrome): 62.0.3202.97 
Using group policy settings? Yes

What steps will reproduce the problem?
(1) Configure UserAvatarImage and WallpaperImage policies.
(2) Do a first time login on a Chrome device.


What is the expected result?
-Managed avatar and wallpaper should be loaded on first login.

What happens instead?
-Session displays user's avatar and wallpaper instead of managed one.


Additional information
-Avatar and wallaper are not loaded even after reloading policies at chrome://policy
-The issue happens randomly, sometimes the avatar and wallpaper will load on first login.
-The Avatar and wallpaper are always loaded correctly on second login, once the user profile has been created locally.
-We were able to replicate the issue. Logs and test user can be found below. 
https://drive.google.com/open?id=1rN55jt18ikfNjC4vU0a5ckBBy8Jy3YyF

-Issue replicated on first login at 14:22 where avatar and wallpaper were not loaded.
-On sencond login at 14:24, everything loaded as expected.


 
Cc: jayhlee@google.com pmarko@chromium.org josa...@google.com
Labels: Hotlist-Enterprise M-62
Summary: ChromeOS issue: Avatar and wallpaper not loaded on first login. (was: Avatar and wallpaper not loaded on first login.)
Possibly WAI

pmarko@, can you please take a look?

Comment 2 by pmarko@chromium.org, Nov 29 2017

Cc: x...@chromium.org
Thanks! I'll take a look tomorrow, I'm currently busy with another issue :)
Doesn't sound like WAI anyway.

Does it randomly load wallpaper and randomly load avater, or either both or none?

+xdai maybe you have any idea / have seen such a behavior at least w.r.t. the wallpaper part? I recall you've been working on some managed wallpaper issue recently.
Requested information by @ykrychala@chromium.org :

Case #13897257
SN: G6NXCX00R628231
Model: ASUS Chromebook C202SA

Now regarding the questions from @pmarko@chromium.org 
Neither the Wallpaper nor the Avatar are loading just in the initial log in. In order to repro we had to wipe the device every time. When you log in the second time, everything loads as expected. 

Please let me know if this answers your questions or if there's anything else we can help you with.

Comment 4 by x...@chromium.org, Nov 29 2017

It sounds like a race condition to me, especially it only happens on first login. I'll try to repro on my device.
Owner: pmarko@chromium.org
Assigning to me to try to repro on current ToT.

Comment 6 by pmarko@chromium.org, Dec 11 2017

I could not reproduce this on 62.0.3202.97 or on ToT despite several attempts, and I couldn't see anything suspicious in the logs (except that an invalid Authority certificate was delivered, but this should be unrelated).

There are errors which look like
[1774:1774:1127/122350.011881:ERROR:gl_image_native_pixmap.cc(240)] Failed to flush rendering
I don't think these are related because they're also reported on the second sign-in attempt where avatar+wallpaper works.

llinares@, would you know how often this happens? (e.g. once in 3 attempts or much less often?
Also, if you are able to reproduce this easily, would you mind sharing the contents of chrome://policy page when it doesn't work?

xdai@ did you manage to repro / do you have an idea?

The next step would be reading the code for these policies and trying to find where it could silently break.
Hello pmarko@

I've capture the requested information and have attached it. I also want to mentioned that I've tested today on Beta 64.0.3282.24 and the issue is reproducible. 

Please let me know if there's anything else that we can assist with

Policies (1).pdf
52.5 KB Download
policies (2).json
10.3 KB View Download
Hello pmarko@

Do you have any updates on this issue? 
Sorry for the delay, I was busy with a release blocker and then on vacation. I'll re-try to repro this and see what else could go wrong here.
Re Comment #7: Do you still repro with the account mentioned in the issue description (https://drive.google.com/open?id=1rN55jt18ikfNjC4vU0a5ckBBy8Jy3YyF)? I'm asking because currently no wallpaper/avatar user policy seems to be served there.

Also, did you manage to repro on an enterprise-enrolled device or on a personally owned device?

@pmarko

Thank you for looking into this. Yes, I did test out with the same user, unfortunately, I did remove the settings some days ago since it's our test account. This can be repro with any user, however, I did apply again a wallpaper and avatar on that test user.

I did repro on a test device that was not manage. Please let me know if there's anything else that I can assist you with
Status: Started (was: Unconfirmed)
@christianelias:

Thanks, I've managed to reproduce it with that account.
Here's what happens:
(1) The wallpaper/avatar start loading.
(2) The policy-set cert import runs
(3) The policy-set cert import finishes, triggering a reset of all active connections
(4) The wallpaper/avatar loading code gets the -100 CONNECTIONC_CLOSED error and schedules a retry with an interval of 1 hour

So I guess the wallpaper would appear in 1 hour :)

(2) should not be happening, we want to delay the user session start until cert import is done. This is tracked in  bug 787602  and is high on my todo list.
(4) sounds like it could be made more robust too, we should reduce the initial backoff interval in these cases. I will track this change in this bug.

For future self reference: 
The backoff strategy is in [1] and is chosen in [2].
[1] https://cs.chromium.org/chromium/src/components/policy/core/common/cloud/external_policy_data_updater.cc?l=56&gs=kythe%253A%252F%252Fchromium%253Flang%253Dc%25252B%25252B%253Fpath%253Dsrc%252Fcomponents%252Fpolicy%252Fcore%252Fcommon%252Fcloud%252Fexternal_policy_data_updater.cc%2523OoEby8nFXCRJhfHsFxsIgMqBgWinTIY3Qm3LsdbvCD0%25253D&gsn=kRetryLaterPolicy&ct=xref_usages
[2] https://cs.chromium.org/chromium/src/components/policy/core/common/cloud/external_policy_data_updater.cc?rcl=30cf78450be041e3329a4d0f8c8a485724564b84&l=229
Project Member

Comment 13 by bugdroid1@chromium.org, Jan 17 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/0526ca8ccc76966a7c9aae4af003f698e4522314

commit 0526ca8ccc76966a7c9aae4af003f698e4522314
Author: Pavol Marko <pmarko@chromium.org>
Date: Wed Jan 17 18:27:55 2018

Retry failed external policy data fetches sooner

Shorten initial backoff intervals on external policy data fetches:
'Retry soon' mode: 1 minute -> 15 seconds.
'Retry later' mode: 1 hour -> 1 minutes.
Use the 'retry soon' mode also for ERR_CONNECTION_CLOSED(-100).

Bug:  788895 
Test: components_unittests --gtest_filter=*ExternalPolicyDataUpdaterTest*
Change-Id: I106442efd94b5b3441ecb8fe068c819b66eb6630
Reviewed-on: https://chromium-review.googlesource.com/870030
Commit-Queue: Pavol Marko <pmarko@chromium.org>
Reviewed-by: Drew Wilson <atwilson@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#529816}
[modify] https://crrev.com/0526ca8ccc76966a7c9aae4af003f698e4522314/components/policy/core/common/cloud/external_policy_data_fetcher.cc
[modify] https://crrev.com/0526ca8ccc76966a7c9aae4af003f698e4522314/components/policy/core/common/cloud/external_policy_data_updater.cc
[modify] https://crrev.com/0526ca8ccc76966a7c9aae4af003f698e4522314/components/policy/core/common/cloud/external_policy_data_updater_unittest.cc

Labels: -M-62 M-65
Status: Fixed (was: Started)
The avatar/wallpaper should work fine on M-65 now; only a slight delay should be noticeable at maximum due to the improved retry scheduling behavior.

The root cause fix is tracked in  bug 787602 .

Status: Verified (was: Fixed)
Verified, avatar and wallpaper are loaded on first login, however it takes about one minute.

Chrome OS: 10323.39.0
Chrome: 65.0.3325.89
Device: Kip

Sign in to add a comment