New issue
Advanced search Search tips

Issue 614012 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 611251
Owner: ----
Closed: May 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

ctl alt delete not responding in Chrome remote desktop for Asus c1000 flipbook

Reported by dwolf...@baugo.org, May 23 2016

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS armv7l 7978.69.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36
Platform: 7978.69.0 (Official Build) stable-channel veyron_minnie

Steps to reproduce the problem:
1. Login to Asus c1000 flipbook
2. open chrome remote desktop
3. send ctl alt delete command

What is the expected behavior?
The command would open upu the windows pc you are trying to access

What went wrong?
When I or any of my staff at school are using their asus c1000 flipbook the ctl alt delete command is not responding.  It works perfectly on other chromebooks, but not the asus c1000 flipbook.

Did this work before? No 

Chrome version: 50.0.2661.94  Channel: n/a
OS Version: 7978.69.0
Flash Version: Shockwave Flash 21.0 r0

My district just purchased the flipbooks for our staff as the district is going 1-1 chromebooks next year.  We have some HP 14s laying around so we tried those.  Those work perfectly with Chrome remote desktop.  None of our flips work when trying to do the ctl alt delete command.
 
 Issue 614030  has been merged into this issue.
Components: Services>Chromoting
Adding this issue to Chromoting, see whether the chrome remote desktop team has any idea on this issue.

Comment 3 by dwolf...@baugo.org, May 23 2016

Sorry.  I did not fill the form out correctly.  I'm not sure how to update.  It's on the Stable Channel and it is the Asus c100pa flipbook.  I mistakenly typed the model number wrong previously.  Sorry!
Mergedinto: 611251
Status: Duplicate (was: Unconfirmed)
What version of Chrome Remote Desktop are you running (the easiest way to check is by visiting chrome://extensions). We recently had an update that broke this functionality, but we rolled it back. If you're still seeing it, the simplest fix is to remove the app and reinstall it.

Sign in to add a comment