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

Issue 768466 link

Starred by 5 users

Issue metadata

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



Sign in to add a comment

Not able to switch between VT1 and VT2

Project Member Reported by sontis@chromium.org, Sep 25 2017

Issue description

Chrome Version: 9765.71.0
OS: ChromeOS

What steps will reproduce the problem?
(1) Boot the device in Dev mode.
(2) Sign in to the device.
(3) Try to switch between VT2 (Alt + Ctrl +F2) and VT1 (Alt+Ctrl+F1).

What is the expected result?
User should able to switch between VT2 and VT1.

What happens instead?
Not able to switch between VT2 and VT1.


Note: Able to access shell from crosh.

Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

 

Comment 1 by sontis@chromium.org, Sep 25 2017

Cc: sdantul...@chromium.org marc...@chromium.org
Logs are present at https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cros/768466?debugUI=CLOUD


No issue on previous beta build 9765.70.0, 61.0.3163.101

Comment 3 by ka...@chromium.org, Sep 25 2017

Owner: dbehr@chromium.org
Status: Assigned (was: Untriaged)
the results from graphics_VTSwitch show the issue comes with R61-9765.71.0 build: 
https://wmatrix.googleplex.com/unfiltered?suites=bvt-perbuild&tests=graphics_VTSwitch&releases=61&days_back=30&hide_missing=True

Per diff at https://crosland.corp.google.com/log/9765.70.0..9765.71.0 it could be b/c of
https://chromium-review.googlesource.com/c/chromiumos/platform/frecon/+/677060

+dbehr

Comment 4 by la...@chromium.org, Sep 27 2017

It looks like frecon change http://crrev.com/c/677060 was merged to 61 without the matching chromium change https://crrev.com/c/583853

dbehr: Easiest fix is likely to revert frecon: https://crrev.com/c/687954

Comment 5 by mlight@chromium.org, Sep 27 2017

Cc: mlight@chromium.org

Comment 6 by felixe@google.com, Sep 27 2017

Issue 769247 has been merged into this issue.
Cc: hansberry@chromium.org mxt@chromium.org vbendeb@chromium.org derat@chromium.org snanda@chromium.org khorimoto@chromium.org chinyue@chromium.org michae...@chromium.org jhawkins@chromium.org steve...@chromium.org dbehr@chromium.org r...@chromium.org
 Issue 769371  has been merged into this issue.
Labels: -Pri-1 Pri-0
P0 since this is blocking M-61 testing.

Comment 9 by son...@google.com, Sep 27 2017

@khorimoto, Is this a beta blocker for M61?
This is a pretty severe regression, so I would say yes. However, that decision is probably up to the TPMs instead of me.
Cc: keta...@chromium.org

Comment 12 by la...@chromium.org, Sep 27 2017

I believe https://crrev.com/c/687954 will resolve this; please verify that it has landed on the right branch.
61 patches are here: https://chromium.googlesource.com/chromium/src/+log/refs/branch-heads/3163

Does not look like that CL has been merged to M-61. Can you please merge it?

Comment 14 by la...@chromium.org, Sep 27 2017

It isn't a fix against chromium, it's a fix against frecon. I am unsure how to verify M61's version of frecon.

Comment 15 by dbehr@google.com, Sep 27 2017

This revert https://crrev.com/c/687954 has been committed.
Thanks Dbehr@
Project Member

Comment 17 by sheriffbot@chromium.org, Oct 10 2017

Pri-0 bugs are critical regressions or serious emergencies, and this bug has not been updated in three days. Could you please provide an update, or adjust the priority to a more appropriate level if applicable?

If a fix is in active development, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: -vbendeb@chromium.org
Status: Fixed (was: Assigned)
marking as fixed for verification since revert is in 9765.73.0+


Status: Verified (was: Fixed)
This issue no longer exists. Verified on M64 dev build (10115.0.0, 64.0.3264.0).

Sign in to add a comment