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

Issue 870115 link

Starred by 2 users
Status: Started
Owner:
domlasko...@chromium.org
Cc:
sdantul...@chromium.org
afakhry@chromium.org
█ lpique@chromium.org
dhadd...@chromium.org
osh...@chromium.org
abod...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

ARC++ app window turns black in primary after exiting clamshell

Project Member Reported by mkarkada@chromium.org, Aug 2 
Chrome OS version: 10718.71.0, 68.0.3440.87 beta channel caroline

What steps will reproduce the problem?
1. Connect device to external monitor
2. Close the device lid (i.e. device in clamshell mode)
3. Open any ARC++ app in full screen in external display
4. Open the device lid back

What happens instead?
ARC++ app window is in Black in primary display. If the same app is selected again from shelf, app regains its position back in primary.

Comment 1 by mkarkada@chromium.org, Aug 2

Components: -OS>Kernel>Display UI>Shell>ExtendedDesktop
Labels: -Pri-2 ReleaseBlock-Stable Pri-1
Repro video in this link:
https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/870115/

Comment 2 by mkarkada@chromium.org, Aug 2 

In the above scenario, after step 4,
Step 5: Minimize the app (i.e click on minimize button)
Step 6: Close the device lid again to enter clamshell

Observed a corrupted window on external display. Attached screenshot for this.
IMG-3547.JPG
2.2 MB View Download

Comment 3 by osh...@chromium.org, Aug 2

Cc: domdaskowski@chromium.org domlasko...@chromium.org
Dom is working on fixing these multi display related issues.

This is a tricky issue due to the lack of wayland API, and
it's unlikely to be able to fix this correctly in 68.

Comment 4 by bhthompson@google.com, Aug 2 

Should this not block 68 stable then?

Comment 5 by domlasko...@chromium.org, Aug 2

Cc: -domlasko...@chromium.org -domdaskowski@chromium.org
Labels: -ReleaseBlock-Stable -M-68 M-69
Owner: domlasko...@chromium.org
Status: Assigned (was: Untriaged)
Yes, this will be fixed in M69.

Comment 6 by mkarkada@chromium.org, Aug 14

Labels: ReleaseBlock-Stable
This is still happening on M69 (10895.21.0, 69.0.3497.35). Playstore app window is seen in black on extended display while exiting clamshell mode. App didn't move back to primary. Attached screenshot.
Screenshot 2018-08-13 at 5.04.29 PM - Display 2.png
57.1 KB View Download

Comment 7 by cindyb@chromium.org, Aug 31 

Is this reproducible in the latest M69?

Comment 8 by mkarkada@chromium.org, Aug 31 

Yes, this is still reproducible on M69 (10895.40.0, 69.0.3497.73) beta.

Comment 9 by afakhry@chromium.org, Sep 1

Cc: lpique@chromium.org

Comment 10 by domlasko...@chromium.org, Sep 5

Status: Started (was: Assigned)
I've been working on b/77972398, because I had assumed it was a prerequisite to fix this bug. However, that would require merging all of those CLs plus a few more Android CLs yet to be reviewed, so I will instead prepare a single Android CL as a workaround for M69.

Comment 11 by domlasko...@chromium.org, Sep 5

Labels: -Pri-1 -ReleaseBlock-Stable -M-69 M-70 Pri-2
After taking a closer look, there are two bugs here:

1) Window shows up at unexpected position. This is due to b/77972398 and will be fixed in M70.

2) Window content is black. Interestingly, this only happens when entering/exiting docked mode (as opposed to connecting/disconnecting an external display) and not all the time. I thought this was caused by recent cropping changes, but it seems to be a race with applying the display configuration change. Sometimes, instead of black content, the window ends up with an incorrect layout, i.e. based on the workspace of a different display.

I don't think the second issue should be a stable blocker, so retargeting to M70.
►

Sign in to add a comment