UserAgent: Mozilla/5.0 (X11; CrOS aarch64 9901.77.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.97 Safari/537.36

Steps to reproduce the problem:
1. Try to either allow shared access to a new Linux account, or look up existing sessions that were created in the past.
2. For existing sessions, it'll either show that the session was last active sometime in the past, or it shows that the session is associated with a different Google account (that's bound to be a bogus error message!)
3. For newly created accounts, the operation never gets past the point of selecting a new PIN. After a long while, it finally times out though.

What is the expected behavior?
Apart from  bug 793045 , which always presented a minor hurdle, it used to be pretty easy to set up Chrome Remote Desktop connections to Linux hosts. As of recent switch to remotedesktop.google.com, this no longer seems to be the case.

What went wrong?
Attempts to activate Chrome Remote Desktop now always time out after I have picked a new PIN.

Interestingly though, if I look at my process list, it appears as if the session has actually started. It simply doesn't allow me to connect to it.

Did this work before? Yes About two days ago (not sure which version). This was before the switch to remotedesktop.google.com

Chrome version: 62.0.3202.75  Channel: n/a
OS Version: Ubuntu 16.04
Flash Version: