Issue metadata
Sign in to add a comment
|
[Bob,Kevin]: device stuck on welcome screen after system updated |
||||||||||||||||||||||
Issue descriptiongoogle Chrome 67.0.3381.0 (Official Build) dev Platform 10525.0.0 (Official Build) dev-channel JavaScript V8 6.7.170 Flash 29.0.0.134 What steps will reproduce the problem? (1)run autest to update system to latest ToT build 10525.0.0/67.0.3381.0 (2)after updating is done, reboot system (3)Observed the issue, system will stuck on welcome screen What is the expected result? It should not stuck and can continue to use What happens instead? system will stuck on welcome screen ********Note********* 1. It might be the same root cause as bug #826163 2. Kevin device will display as black screen 3. issue also reproduce by using USB disk to update system 4. issue reproduce on both dev mode and non-dev mode
,
Mar 29 2018
Mouse pointer is moving but no response after clicking on any button at welcome screen. and touch is also not working.
,
Mar 29 2018
The issue no reproduce on previous ToT build 10520.0.0/67.0.3376.0. It seems to be broken between 10520.0.0/67.0.3376.0 and 10525.0.0/67.0.3381.0
,
Mar 29 2018
I see two things in logs. These logs indicate a possible new issue. Owner to alemate@ to investigate. [1273:1273:0329/100611.981428:ERROR:CONSOLE(0)] "Unchecked runtime.lastError while running webViewInternal.executeScript: Cannot access contents of the page. Extension manifest must request permission to access the respective host.", source: chrome://oobe/oobe (0) [1273:1273:0329/100611.984127:ERROR:CONSOLE(0)] "Unchecked runtime.lastError while running webViewInternal.executeScript: Cannot access contents of the page. Extension manifest must request permission to access the respective host.", source: chrome://oobe/oobe (0) [1273:1273:0329/100611.985727:ERROR:CONSOLE(0)] "Unchecked runtime.lastError while running webViewInternal.executeScript: Cannot access contents of the page. Extension manifest must request permission to access the respective host.", source: chrome://oobe/oobe (0) [1273:1273:0329/100611.987305:ERROR:CONSOLE(0)] "Unchecked runtime.lastError while running webViewInternal.executeScript: Cannot access contents of the page. Extension manifest must request permission to access the respective host.", source: chrome://oobe/oobe (0) These logs indicate a potential duplicate of issue 826973. [1447:1447:0329/100608.614776:ERROR:gles2_cmd_decoder.cc(4677)] [.DisplayCompositor-0xc255880]GL ERROR :GL_INVALID_FRAMEBUFFER_OPERATION : glDrawElements: framebuffer incomplete [1447:1447:0329/100608.614886:ERROR:gles2_cmd_decoder.cc(12380)] [.DisplayCompositor-0xc255880]GL ERROR :GL_INVALID_VALUE : glScheduleOverlayPlaneCHROMIUM: unsupported texture format [1447:1447:0329/100608.628118:ERROR:gles2_cmd_decoder.cc(4677)] [.DisplayCompositor-0xc255880]GL ERROR :GL_INVALID_FRAMEBUFFER_OPERATION : glDrawElements: framebuffer incomplete [1447:1447:0329/100608.628240:ERROR:gles2_cmd_decoder.cc(4677)] [.DisplayCompositor-0xc255880]GL ERROR :GL_INVALID_FRAMEBUFFER_OPERATION : glDrawElements: framebuffer incomplete [1447:1447:0329/100608.628467:ERROR:gles2_cmd_decoder.cc(4677)] [.DisplayCompositor-0xc255880]GL ERROR :GL_INVALID_FRAMEBUFFER_OPERATION : glDrawElements: framebuffer incomplete [1447:1447:0329/100608.628665:ERROR:gles2_cmd_decoder.cc(4677)] [.DisplayCompositor-0xc255880]GL ERROR :GL_INVALID_FRAMEBUFFER_OPERATION : glDrawElements: framebuffer incomplete
,
Mar 29 2018
,
Mar 29 2018
alemate@ do we need to look into the webViewInternal.executeScript errors?
,
Mar 29 2018
Yes, we do. Basically this is what I was going to do yesterday and what turned into issue 826973 ;)
,
Mar 30 2018
Jacob, my debugging shows that it's the same issue 543861. It's been started for 2.5 years by now ;) |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by hsiangc@chromium.org
, Mar 29 2018