[Chrome OS] Users profile pictures invisible in sign-in screen (Alex Chromebooks) |
||||||
Issue descriptionVersion: 53.0.2785.144 Stable OS: Chrome OS only. Affected Chromebook model: Samsung Series 5 XE500C21 Hardware ID: SAMS ALEX2 KAPPA-US 0325 What steps will reproduce the problem? (1) Turn the device ON (2) When it gets to the sign in screen, profiles pictures won’t be shown. What is the expected output? Profile pictures should be shown for users to click on them and sign in. What do you see instead? The system wallpaper is shown. The pictures do not show up, but if you hover the mouse over the center of the screen, where profile pictures should be shown, the cursor will turn from the arrow to a hand, if you click on them, you’ll see the profile picture and will be able to put the password for the given profile and sign in. Additional information. * It has nothing to do with the ‘DeviceShowUserNamesOnSignin’ policy, since the policy is set to always show pictures in the sign in screen. Reports from affected users say that this problem started after v51. * Issue is reproducible in current Beta/Dev channels. * Issue is isolated to this particular make/model. Device logs, and video showing the issue from an affected Chromebook at https://drive.google.com/open?id=0Bxg-rTzA58PeLVlja1poZE1Bdzg. Timestamp when issue was reproduced between 12:00 - 12:30 CST 10/4/2016. //Google restricted access.
,
Oct 8 2016
Moving to 54 and requesting stable so that this gets triaged. Feel free to move once its triaged.
,
Oct 9 2016
That sounds reasonable. Thanks for the heads up royans@.
,
Oct 10 2016
Abert, can you evaluate/re assign this one? removeing rbs but we can consider for merge if safe fix available in time
,
Oct 11 2016
,
Oct 12 2016
Is this specific only to alex? I tried to repro on samus with both 55.0.2878.0 and ToT @ 56.0.2889.0 and couldn't.
,
Oct 12 2016
Yes, this is specific to Alex.
,
Oct 18 2016
Issue 656017 has been merged into this issue.
,
Nov 2 2016
,
Nov 2 2016
I tried to repro on 56.0.2903.0 x86-alex and couldn't! * Does the issue still happen? * Is the device enrolled? * Is there a minimum number of users that should be added to the device for the issue to repro? (I tried with only 2 accounts).
,
Nov 2 2016
Going through the logs sent in the bug description, I can't see anything that stands out.
,
Nov 2 2016
Hello, I am actually one of (if not the only) people that reported this bug. I just finished moving a few of our Chromebooks over to the Developer channel and I am happy to report that it does seem the bug has been squashed in 56.0.2903.0. I appreciate the effort that has been given to this issue and look forward to the solution being rolled out to a stable channel build. Thank you for your time and hard work; our staff and students appreciate you too!
,
Nov 2 2016
I actually just checked this today and to my enjoyment and surprise, I saw that it was fixed. I'm so happy about that. How long does the dev channel usually take until it rolls out to the stable channel? I imagine it could be different with a device that's technically EOL.
,
Nov 3 2016
Already fixed. Please reopen if it comes up again. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by roy...@google.com
, Oct 7 2016Owner: keta...@chromium.org