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

Issue 758765 link

Starred by 2 users
Status: Archived
Owner:
weidongg@chromium.org
Closed: Aug 2017
Cc:
█ vadimt@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Launcher broken with multiple displays

Project Member Reported by abodenha@chromium.org, Aug 24 2017 
Google Chrome	61.0.3163.51 (Official Build) beta (64-bit)
Revision	0
Platform	9765.31.0 (Official Build) beta-channel samus

What steps will reproduce the problem?
(1) Have desktop extended over 2 displays
(2) Press search button

What is the expected result?
See a launcher, preferably the new launcher.

What happens instead?
There's a brief flash on the internal (non-primary) display then nothing.

Comment 1 by abodenha@chromium.org, Aug 24 2017 

I'd say this borders on P0 and beta blocking. If this is affecting everyone with multiple displays then launcher is completely broken for all multi-display users in beta now.

Comment 2 by xiy...@chromium.org, Aug 25 2017

Cc: vadimt@chromium.org
Owner: weidongg@chromium.org
Somewhat related to  issue 752166 . weidongg@, 61.0.3163.51 should have your fix. Could you double check?

Comment 3 by weidongg@chromium.org, Aug 25 2017 

I checked on golden eye, it seems the first build that includes my CL is 61.0.3163.53: https://chromium-review.googlesource.com/c/chromium/src/+/618400.

Comment 4 by gbranger...@gmail.com, Aug 26 2017 

I was having the same issue on the Lenovo Flex 11 extended to QuadHD Lenovo monitor. Latest Dev channel update appears to have fixed the issue.
Screenshot 2017-08-26 at 2.20.08 PM - Display 2.png
352 KB View Download

Comment 5 by gbranger...@gmail.com, Aug 26 2017 

Will test on Beta momentarily.

Comment 6 by weidongg@chromium.org, Aug 26 2017

Status: Fixed (was: Untriaged)
Thanks for the feedback, I tested build from ToT, the issue is fixed.
Project Member

Comment 7 by blocker...@chrome-infra-auth.iam.gserviceaccount.com, Aug 26 2017

Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-61; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-61 label, otherwise remove Merge-TBD label. Thanks.
Project Member

Comment 8 by sheriffbot@chromium.org, Oct 9 2017

Labels: -Merge-TBD

Comment 9 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)
►

Sign in to add a comment