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

Issue 759902 link

Starred by 7 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

ChromeOS issue: web RDP app artifacts on Elm/Hana

Project Member Reported by vkhabarov@chromium.org, Aug 29 2017

Issue description

ChromeOS version: 60.0.3112.101
ChromeOS device model: Elm and Hana
Case#: 13379955

Description:
Since customer updated to Stable 60 on Acer R13 (CB5-312T-K7SP) devices the webbased remote solution called Ericom Access, has started to show some graphical issues. https://drive.google.com/a/google.com/file/d/0B7RXwPjBEiJ3Sy0teU9nRklrZjQ/view?usp=sharing

Steps to reproduce: 
1. Login to his Ericom Access on the Chromebook. 

Current Behavior / Reproduction: 
Having graphical issues on image 

Expected Behavior: 
Image should be observed normal 

Workaround:
Disabling Accelerated 2D canvas seems to fix the issue

We were able to reproduce on our Hana device in v59 and v60. Customer says that it was working fine on v52
 
Owner: abodenha@chromium.org
Albert, this seems a chrome platform issue, can you evaluate/confirm?
Cc: abodenha@chromium.org marc...@chromium.org
Components: -Blink>Canvas UI>GFX Blink>WebRTC>Video
Owner: ----
Adding a few people and components who might know more.
Labels: Restrict-View-Google
Do we know if Ericom Access uses WebRTC?

Searching for "WebRTC" on their website yields no hits. http://www.ericom.com/access-now/html5-rdp-client/
How do we reliably check?
We have their demo installed, but I can't find any mention of WebRTC.
Labels: -Restrict-View-Google
While running their app in Chrome, go to chrome://webrtc-internals and see if you see a PeerConnection running. If not, they are not using WebRTC.

(-RVG, which I added by mistake before.)
Nothing in chrome://webrtc-internals while it's running.
Cc: niklase@chromium.org
Ok, I think that would mean that the WebRTC renderer is not used. +niklase to confirm.

Comment 8 by woerd...@woerden.nl, Sep 15 2017

Hi guys, i asked ericom about WebRTC and here is the answer:
Hello,

AccessNow does not offer support for WebRTC and implementing it is not considered in the near future.

Kind regards,
Cristian Dinca
Customer Advocacy Engineer

--------------- Original Message ---------------
From: Ricardo [woerde.r@woerden.nl]
Sent: 9/15/2017 10:44 AM
To: ca@ericom.com
Subject: WebRTC Ericom Access now

Hi,
 
Can you tell me if ericom acces now uses webRTC?
If you can tell me google can progress with following issue:
https://code.google.com/p/chromium/issues/detail?id=759902

Thanks in advance!

Ricardo Woerde

Components: -Blink>WebRTC>Video
Thanks for confirming. Removing WebRTC component.
Hi all,

Do we have any updates on this issue?

Thanks!
Owner: djkurtz@chromium.org
Cc: drinkcat@chromium.org oak-img@chromium.org oak-mtk@chromium.org
Components: OS>Kernel>Graphics
Labels: M-59
Status: Started (was: Untriaged)
Summary: ChromeOS issue: web RDP app artifacts on Elm/Hana (was: ChromeOS issue: web RDP app artifacts on Elm)
vkhabarov,

It isn't clear from this ticket if we have tried to reproduce on other Chromebook types (besides elm or hana)?

Note: Since this apparantly did not occur in R52, our initial suspicion is that this might be a regression introduced by the IMG DDK update from 1.7 -> 1.8 which rolled out in R59.  If you can reproduce easily, can you try on older R58 elm image (anything before 9692.0.0)?

Comment 13 by ad...@woerden.nl, Oct 23 2017

I can reproduce the issue easily, and we have multiple devices in our company. But I don't know what to test. I can only reproduce it on acer R13 models.
Labels: M-61 M-58
@djkurtz
I couldn't repro the issue on other devices.
I just tried 9334.72.0 on Hana - still reproduces.
Do we have any instructions for how to reproduce the issue? Is there a demo account or similar?
@bhthompson
We installed demo version of this software on our test server and used it, I could share credentials to it.
Repro instructions are kind of vague, I just use Ericom own server config window and quickly switch between tabs, until I see artifacts (or won't see any)
Could we share the credentials with the Imagination folks whom can help with such GPU issues?

We can share them offline assuming they should not be posted to a public bug. 
Sent test credentials to bhthompson

Comment 19 by tho...@g.company, Nov 15 2017

Hi Guys,

Could you give a status update about this issue?

With kind regards,

Thomas van Latum
g-company
Hi Bernie,
Are there any news from Imagination?
Thanks!
Imagination folks (Afar?) can you comment on debug status here? IIRC this was reproducible with the credentials. 

Comment 22 by ad...@woerden.nl, Nov 27 2017

Hi guys,

This issue is staling since november 2th, is there any news?

Kind regards,

Ricardo Woerde
Gemeente Woerden

Comment 23 by tho...@g.company, Nov 29 2017

Hi Guys,

Could you update us about this issue?

Regards
Hi All,

I'm part of the Imagination support team has been looking at this issue. Firstly, apologies for the delay while we've been investigating this. 

The info we've found so far is pointing to an app synchronisation bug. We've taken a graphics trace of the OpenGL calls that are being used when running this app on the Chromebook and by playing the trace back on a PC (using a non-Imagination graphics stack) this issue is still reproducible. This leads us to believe that the issue is outside our GPU driver. 

We're working to provide more details over the next few days so this can be investigated further.

Many thanks,
Ian


Cc: bhthompson@chromium.org
Ian, are you able to reproduce on any other Chromebooks without Imagination graphics?
Oh, I just saw comment #14, it was noted that this issue does *not* reproduce on any other Chromebooks.

Also, from comment #1, the original report said that this issue was not reproducible on Imagination chromebooks on M52, but appeared in M58.

One next step would be to double check that this issue did indeed begin with the introduction of 1.8 driver.  Also, can you take an API trace with 1.7 and check whether it is the App or driver behaving differently between the two different driver versions.

Comment 27 by tho...@g.company, Jan 2 2018

Hi All,

Who needs to to double check if this issue began with the introduction of 1.8 driver?

Regards,

Hi,

Apologies for the delay. Our investigations are continuing although were delayed by the holiday period. 

I've been advised that the server credentials (IP, Username and Password) we were using for testing this app no longer work as of this week. 

Is it possible for someone to provide us with working credentials so we can continue looking at this?

Thanks,
Ian

Comment 29 by tho...@g.company, Jan 15 2018

Hi Guys,

We need a fix for this as soon as possible because we need to update our devices to fix the Meltdown bug.

Regards,

Thomas
Cc: marcore@chromium.org
@ian, I've sent you an email with Ip, username & password of the test server.
djkurtz@, is there any update to this issue? Please let us know if anything else is needed from customers.

Comment 32 by vsu...@google.com, Jan 25 2018

Cc: hsiangc@chromium.org

Comment 33 by tho...@g.company, Jan 26 2018

@All, Please update this case our customer needs to roll out the chrome devices.
Cc: marchuk@google.com
@imagination: do you have necessary access for testing?
Do we need buganizer bug for better tracking/communication?
Customer is constantly asking for news and updates
All,

I'm pleased to say our investigations have finally led us to a fix for this problem. We will provide this patch on Gerrit ASAP and post back here when we know which ChromeOS version will contain the fix.

Thanks for your patience,
Ian
Project Member

Comment 36 by bugdroid1@chromium.org, Feb 8 2018

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/vendor/img-ddk/+/74907127b6ba0113bea24366941a27b4eefac85d

commit 74907127b6ba0113bea24366941a27b4eefac85d
Author: Afar Lin <afar.lin@imgtec.com>
Date: Thu Feb 08 17:24:10 2018

Fix landed in R66-10386.0.0.

Who can double-check that the fix works? Then we can backport to R65 and maybe R64.
Labels: -M-58 -M-59 -M-60 -M-61 M-65
If someone can verify this fixed it on an R66 official build (canary channel today, dev channel later this week), we can pick this back to R65 (currently beta).

Comment 40 by tho...@g.company, Feb 16 2018

Hi,

Could someone explain to me how to update a chromebook to R66?
We would like to test to see if the issue is fixed.

Regards,

Thomas
I believe we are still serving R65 on dev channel, so one way would be to switch to canary channel (these instructions look correct: https://www.howtogeek.com/308602/how-to-switch-to-or-leave-the-canary-channel-on-your-chromebook/)
Hi,

I've switched one of our chromebooks to canary channel. Cannot reproduce the graphical glitch anymore so i think the problem is solved. Many thanks!!!
Hi,

 
I've switched one of our chromebooks to canary channel. Cannot reproduce the graphical glitch anymore so i think the problem is solved. Many thanks!!!

 
Met vriendelijke groeten,

 
Ricardo Woerde

Systeembeheer 
Gemeente Woerden
+31 (0)348 428655

Gemeente Woerden
Postbus 45, 3440 AA Woerden
Blekerijlaan 14, 3447 GR Woerden
Telefoonnummer 14 0348 428655
www.woerden.nl <http://www.woerden.nl/> 

 
 
Van: tho… via monorail [mailto:monorail+v2.1893718830@chromium.org] 
Verzonden: vrijdag 16 februari 2018 13:19
Aan: Woerde, Ricardo
Onderwerp:  Issue 759902  in chromium: ChromeOS issue: web RDP app artifacts on Elm/Hana

 

Comment #40 on  issue 759902  by tho...@g.company <mailto:tho...@g.company> : ChromeOS issue: web RDP app artifacts on Elm/Hana
https://bugs.chromium.org/p/chromium/issues/detail?id=759902#c40

Hi,

Could someone explain to me how to update a chromebook to R66?
We would like to test to see if the issue is fixed.

Regards,

Thomas
Labels: Merge-Request-65
Project Member

Comment 45 by sheriffbot@chromium.org, Feb 19 2018

Labels: -Merge-Request-65 Merge-Review-65 Hotlist-Merge-Review
This bug requires manual review: M65 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: cmasso@(Android), cmasso@(iOS), bhthompson@(ChromeOS), govind@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Hotlist-Merge-Review -Merge-Review-65 Merge-Approved-65
Project Member

Comment 47 by bugdroid1@chromium.org, Feb 21 2018

Labels: merge-merged-release-R65-10323.B
The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/vendor/img-ddk/+/2474ea1e0473d1456e425231858cb70d53c15cf0

commit 2474ea1e0473d1456e425231858cb70d53c15cf0
Author: Afar Lin <afar.lin@imgtec.com>
Date: Wed Feb 21 09:18:58 2018

#43: Thanks a lot for testing! Merged to M65 as well (should be in release >= 10323.40.0).
Project Member

Comment 49 by sheriffbot@chromium.org, Feb 26 2018

Cc: bhthompson@google.com
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible!

If all merges have been completed, please remove any remaining Merge-Approved labels from this issue.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Merge-Approved-65
Status: Fixed (was: Started)

Sign in to add a comment