Issue metadata
Sign in to add a comment
|
[Samus] Digital FCC E-Label is missing. |
||||||||||||||||||||||
Issue descriptionChrome os version: 9460.24.0/59.0.3071.36 Please specify Cr-* of the system to which this bug/feature applies (add the label below). Steps To Reproduce: 1:Go into Settings. 2:Click "About Chrome OS". 3:At the bottom E label is available. Verify: with device specification. (In Samus) Expected Result: Digital FCC E-Label should be available in Samus device. Actual Result: Digital FCC E-Label is missing. How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) What is the impact to the user, and is there a workaround? If so, what is it? Please provide any additional information below. Attach a screen shot or log if possible. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
May 3 2017
Hmm, I see it in 59.0.3071.25. It only shows up in official builds though, can you confirm this was an official build and provide a screenshot? Thanks!
,
May 3 2017
abodeti: Does the e-label appear in the old Options Help overlay? chrome://settings-frame/help If it doesn't appear there either, could you check if the following URL loads the image on your device? file:///usr/share/chromeos-assets/regulatory_labels/us/label.png
,
May 4 2017
No e-label with the old Options Help overlay, Please see the attached screenshots. and image also failed to load with given url.
,
May 4 2017
If you can bisect between 59.0.3071.25 and 59.0.3071.36 that would be very helpful. Otherwise I will try creating an official build and bisecting tomorrow or Friday.
,
May 4 2017
If it's not at the given URL, that means either Chrome is blocking that URL (a regression) for some reason, or the file doesn't exist on your device (how was it imaged?). Can you access file:///usr/share/chromeos-assets? If so, does the regulatory_labels folder exist, and what's in it?
,
May 4 2017
Can you access file:///usr/share/chromeos-assets? Yes. but regulatory_labels folder is missing.
,
May 4 2017
The logo is still present in 59.0.3071.35 (my dev channel device just updated). I'll try a 59.0.3071.36 version soon.
,
May 4 2017
How was this device acquired and imaged? If the folder is missing on the device, this isn't a Chrome issue (unless Chrome is suddenly blocking that directory??). IIRC the image should be installed during factory setup. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by abodenha@chromium.org
, May 3 2017Labels: -Pri-2 ReleaseBlock-Stable Pri-1
Owner: steve...@chromium.org
Status: Assigned (was: Untriaged)