New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 606010 link

Starred by 5 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

User pods missing on Sign-in screen

Project Member Reported by sdantul...@chromium.org, Apr 22 2016

Issue description

Google Chrome	51.0.2704.23 (Official Build) dev (32-bit)
Revision	0
Platform	8172.9.0 (Official Build) dev-channel x86-alex

What steps will reproduce the problem?
1. Make sure there is more than 1 account on the device. AU to 8172.9.0
2. Only owner account is visible at first. On clicking anywhere else on the screen, owner user pod also disappears. 

Seen only on Alex.
 
Cc: x...@chromium.org
Attached screenshots.
IMG_20160422_123217.jpg
2.5 MB View Download
IMG_20160422_123223.jpg
2.5 MB View Download

Comment 3 by x...@chromium.org, Apr 22 2016

Cc: xiy...@chromium.org osh...@chromium.org

Comment 4 by osh...@chromium.org, Apr 22 2016

Cc: piman@chromium.org marc...@chromium.org
If this happens only on alex (or specific devie), it could be graphics/compositor related?

Comment 5 by piman@chromium.org, Apr 22 2016

More likely driver-related?

Can anyone bisect?

Comment 6 by marcheu@google.com, Apr 22 2016

Cc: dbehr@chromium.org gurcheta...@chromium.org h...@chromium.org
I don't know if that's worth bisecting (I think it's been happening forever) but it should probably be fixed.
Cc: sdantul...@chromium.org
 Issue 614782  has been merged into this issue.
I did a bisect across available x86-alex images, last good image was R51-8036.0.0	on Chrome 50.0.2657.0, first bad image was R51-8049.0.0 on Chrome 51.0.2672.0. I also tried an old build of Chrome on a new image but this still had the issue which leads me to believe it's a CrOS issue - so it should be one of the commits in this list:

https://crosland.corp.google.com/log/8046.0.0..8049.0.0
Sorry, the correct link for the changes is this: https://crosland.corp.google.com/log/8036.0.0..8049.0.0
Components: -Services>SignIn UI>Shell>StartScreen
Labels: -Pri-2 Pri-1
Owner: alemate@chromium.org
Status: Assigned (was: Untriaged)
 Issue 619340  has been merged into this issue.
Owner: marc...@chromium.org
Status: Started (was: Assigned)
Project Member

Comment 14 by bugdroid1@chromium.org, Oct 12 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/8f1068163c553150c58ea9864174584aacfa34a3

commit 8f1068163c553150c58ea9864174584aacfa34a3
Author: Stéphane Marchesin <marcheu@chromium.org>
Date: Tue Oct 11 01:31:13 2016

media-libs/mesa: i915g: Backport change to fix gl_FragCoord issues

This is causing different instances of corruption in our UI

BUG= chromium:606010 ,  chromium:624310 
TEST=run on zgb, no more corruption

Change-Id: I6949e687bf989ddc440af3bcb42cabde67bfa3cf
Reviewed-on: https://chromium-review.googlesource.com/396520
Commit-Ready: Stéphane Marchesin <marcheu@chromium.org>
Tested-by: Stéphane Marchesin <marcheu@chromium.org>
Reviewed-by: Haixia Shi <hshi@chromium.org>

[add] https://crrev.com/8f1068163c553150c58ea9864174584aacfa34a3/media-libs/mesa/files/12.1-i915g-fix-incorrect-gl_FragCoord-value.patch
[modify] https://crrev.com/8f1068163c553150c58ea9864174584aacfa34a3/media-libs/mesa/mesa-9999.ebuild
[modify] https://crrev.com/8f1068163c553150c58ea9864174584aacfa34a3/media-libs/mesa/mesa-12.1.0.ebuild
[rename] https://crrev.com/8f1068163c553150c58ea9864174584aacfa34a3/media-libs/mesa/mesa-12.1.0-r6.ebuild

Project Member

Comment 15 by bugdroid1@chromium.org, Oct 12 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/8f1068163c553150c58ea9864174584aacfa34a3

commit 8f1068163c553150c58ea9864174584aacfa34a3
Author: Stéphane Marchesin <marcheu@chromium.org>
Date: Tue Oct 11 01:31:13 2016

media-libs/mesa: i915g: Backport change to fix gl_FragCoord issues

This is causing different instances of corruption in our UI

BUG= chromium:606010 ,  chromium:624310 
TEST=run on zgb, no more corruption

Change-Id: I6949e687bf989ddc440af3bcb42cabde67bfa3cf
Reviewed-on: https://chromium-review.googlesource.com/396520
Commit-Ready: Stéphane Marchesin <marcheu@chromium.org>
Tested-by: Stéphane Marchesin <marcheu@chromium.org>
Reviewed-by: Haixia Shi <hshi@chromium.org>

[add] https://crrev.com/8f1068163c553150c58ea9864174584aacfa34a3/media-libs/mesa/files/12.1-i915g-fix-incorrect-gl_FragCoord-value.patch
[modify] https://crrev.com/8f1068163c553150c58ea9864174584aacfa34a3/media-libs/mesa/mesa-9999.ebuild
[modify] https://crrev.com/8f1068163c553150c58ea9864174584aacfa34a3/media-libs/mesa/mesa-12.1.0.ebuild
[rename] https://crrev.com/8f1068163c553150c58ea9864174584aacfa34a3/media-libs/mesa/mesa-12.1.0-r6.ebuild

Status: Fixed (was: Started)
Status: Verified (was: Fixed)
Verified on ChromeOS 8932.0.0, 56.0.2899.0 dev-channel x86-alex

Sign in to add a comment