New issue
Advanced search Search tips

Issue 628689 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Jul 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

unable to login

Project Member Reported by osh...@chromium.org, Jul 15 2016

Issue description

Chrome Build: ToT(405749)
OS: 8588.0.0-16.07.15

bisecting now
 

Comment 1 by osh...@chromium.org, Jul 15 2016

Owner: ljusten@chromium.org
Status: Assigned (was: Started)
Bisected to:

https://codereview.chromium.org/2150603002

ljusten@, can you look into it?

Comment 2 by osh...@chromium.org, Jul 15 2016

here is the log

[8443:8549:0715/125038:ERROR:cloud_policy_validator.cc(472)] Empty device id encountered - expected: 
[8563:8570:0715/125038:ERROR:drm_device_manager.cc(53)] Could not initialize DRM device for /sys/devices/platform/vgem/drm/card1
[8443:8443:0715/125038:ERROR:session_manager_operation.cc(200)] Policy validation failed: 12
[8443:8443:0715/125038:ERROR:device_settings_service.cc(263)] Session manager operation failed: 6
[8443:8443:0715/125038:ERROR:device_settings_provider.cc(834)] Failed to retrieve cros policies. Reason: 6
[8443:8549:0715/125038:ERROR:cloud_policy_validator.cc(472)] Empty device id encountered - expected: 
[8443:8443:0715/125038:ERROR:session_manager_operation.cc(200)] Policy validation failed: 12
[8443:8443:0715/125038:ERROR:device_settings_service.cc(263)] Session manager operation failed: 6
[8443:8443:0715/125038:ERROR:device_settings_provider.cc(834)] Failed to retrieve cros policies. Reason: 6
[8443:8555:0715/125038:ERROR:theme_source.cc(150)] NOTREACHED() hit.
[1:1:0715/125039:ERROR:PlatformKeyboardEvent.cpp(93)] Not implemented reached in static bool blink::PlatformKeyboardEvent::currentCapsLockState()
[8443:8443:0715/125049:ERROR:core_oobe_handler.cc(197)] CoreOobeHandler::ShowSignInError: error_text=Sign-in failed, please connect to the internet and try again.
[8443:8443:0715/125049:ERROR:base_screen_handler_utils.cc(70)] Failed to deserialize 'motestc1@gmail.com'
Labels: ReleaseBlock-Dev
Any update on this issue?
Labels: -Pri-0 -ReleaseBlock-Dev Pri-3
The cl that caused this issue got reverted, so it isn't a blocker anymore. An adjusted version of the cl is sitting in review, but I got a higher priority issue I have to work on first and I'm not sure if the adjusted cl will land in M-54. I still want to keep this bug alive for verification when the cl lands, so in the mean time I'll remove the release block label and reduce priority.
Labels: -M-54

Comment 6 by osh...@chromium.org, Jul 26 2016

Status: WontFix (was: Assigned)
let's close this if it's reverted. Just make sure to test the login on device before you land.

Sign in to add a comment