New issue
Advanced search Search tips

Issue 677682 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 584388
Owner: ----
Closed: Jan 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Chrome Remote desktop connects and works, but does not display anything on the chromebook

Reported by corban...@gmail.com, Dec 31 2016

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 8872.73.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.103 Safari/537.36
Platform: 8872.73.0 (Official Build) stable-channel celes

Example URL:

Steps to reproduce the problem:
1. Connect to windows 10 pc w/ two different resolution monitors set in dual monitor mode (extended display, not eyefinity) with android device to ensure it works (nexus 6p connects and displays content fine while using chrome remote desktop)
2. disconnect phone and connect with samsung chromebook to the same computer
3. confirm everything works, but there is no content displayed on the chrombooks screen

What is the expected behavior?
the chrome book can control the pc with no problem.  mouse and keyboard work as normal. the problem is that there is nothing displayed on the chrome book screen.

What went wrong?
Chrome remote desktop dose not display content when connecting to pc with two monitors with different resolutions

Did this work before? N/A 

Chrome version: 55.0.2883.103  Channel: stable
OS Version: 8872.73.0
Flash Version: Shockwave Flash 24.0 r0
 

Comment 1 by corban...@gmail.com, Dec 31 2016

not sure if i reported this under the correct label, but i did my best ;) lol
Components: -Internals>Network Services>Chromoting
Mergedinto: 584388
Status: Duplicate (was: Unconfirmed)
Hi, Cor*@gmail.com,
Would you mind to share us the screen resolutions of your monitors? Two known issues may cause the issue. One is  http://crbug.com/584388 , i.e. hardware renderer won't work with a very large screen resolution. The bug has been resolved, which will be released through M56. The second is  http://crbug.com/632822 . It looks like a Pixel 2 specific issue, but we cannot quite tell whether similar issue happens on other machines.

Sign in to add a comment