Issue metadata
Sign in to add a comment
|
Android Apps do not work when plugged into a USB-C Dock
Reported by
joe.ro...@sunrun.com,
Apr 16 2018
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 10539.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3383.0 Safari/537.36 Platform: 10539.0.0 (Official Build) dev-channel eve Steps to reproduce the problem: 1. Plug Chromebook into a USB-C Dock (we use a Plugable UD-CAM) 2. Click on the launcher for the Play Store or any Android App 3. Watch the "loading" animation forever What is the expected behavior? On Chrome OS 67 Android Apps opened and worked properly when docked What went wrong? Now they don't. Our organization uses USB-C docks so that Chromebook users can plug into ethernet and utilize multiple monitors. If this isn't fixed before Beta/Stable they will not be able to perform their jobs. Did this work before? Yes 66 Chrome version: 67.0.3383.0 Channel: dev OS Version: 10539.0.0 Flash Version: When undocked (just using the Chromebook by itself) Android Apps work properly. As soon as you plug into a dock they crash and cannot be re-opened.
,
Apr 25 2018
,
Apr 25 2018
Link to spreadsheet with debug logs customer provided - https://docs.google.com/spreadsheets/d/15pJKRTyZLVLCI4o6BJYG0kg3bRtlr4wHY0_apJwI2kA/edit?usp=sharing Video of the issue - https://drive.google.com/file/d/1uZW5vs7fZdDyNGWvOV2xLT5wk20XsbLX/view?usp=sharing
,
Apr 25 2018
+Dom, are we supposed to hit those not-implemented paths? (from ui.20180424-120716 debug-logs_20180424-125703.tgz) [1135:1135:0424/120940.352462:ERROR:server.cc(1915)] Not implemented reached in void exo::wayland::(anonymous namespace)::remote_surface_set_rectangular_shadow_background_opacity_DEPRECATED(wl_client *, wl_resource *, wl_fixed_t) [1135:1135:0424/120940.353650:ERROR:multi_user_window_manager_stub.cc(17)] Not implemented reached in virtual void MultiUserWindowManagerStub::SetWindowOwner(aura::Window *, const AccountId &)
,
Apr 26 2018
The next update (Chrome OS 10543.0.0, ARC 4696445) should fix this. The NOTIMPLEMENTED in Exo is harmless, and is also fixed in recent releases.
,
May 22 2018
Is this fix completed and tested? Need an updates status/owner to plan and validate that this is RBS issue.
,
May 22 2018
Yes, internal bug is b/77328081.
,
May 22 2018
[Auto-generated comment by a script] We noticed that this issue is targeted for M-67; 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-67 label, otherwise remove Merge-TBD label. Thanks.
,
May 22 2018
Merge is not required because this was an Android fix. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by joe.ro...@sunrun.com
, Apr 16 2018