New issue
Advanced search Search tips

Issue 813254 link

Starred by 1 user

Issue metadata

Status: Unconfirmed
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Native Client Pepper Websocket APIs and Pepper APIs both won't auto-update and open automatically.

Reported by pa_strat...@students.fmcsd.org, Feb 17 2018

Issue description

Chrome Version: <From chrome://version: Google Chrome 64.0.3282.144>
Chrome OS Version: <From chrome://version: Platform 10176.68.0 (Official Build) stable-channel daisy>
Chrome OS Platform: <Samsung Chromebook/XE303C12-A01US>
Network info: <IP/IPv4, AES/WPA-PSK Encryption, Windstream 2-channel DSL>

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).
Cr-* Pepper APIs, Cr-* Websocket APIs, Cr-* Native Client
Steps To Reproduce:
(1) I went to this Chrome OS URL: chrome://flags.
(2) I clicked on enable Nacl and Nacl APIs.
(3) I then, updated my Components, Chrome OS Version, and all other Flags.

Expected Result: I expected Chrome OS to update and open Native Client and Pepper Websocket APIs and also Pepper APIs for Nacl to where I can open them now on.

Actual Result: It instead, did nothing and responded back with a Google Search every time and also did not enable and update them.

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?) Always.
What is the impact to the user, and is there a workaround? If so, what is
it? The impact was that I couldn't do anything, there were no workarounds at all.
Please provide any additional information below. Attach a screen shot or
log if possible.
Google Chrome	64.0.3282.144 (Official Build) (32-bit)
Revision	0
Platform	10176.68.0 (Official Build) stable-channel daisy
Firmware Version	Google_Snow.2695.132.0
JavaScript	V8 6.4.388.41
Flash	28.0.0.161 /opt/google/chrome/pepper/libpepflashplayer.so
User Agent	Mozilla/5.0 (X11; CrOS armv7l 10176.68.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.144 Safari/537.36
For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.
Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
Disabled Features: native_gpu_memory_buffers
Disabled Extensions	GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent
Data exported	2/16/2018, 6:22:58 PM
Chrome version	Chrome/64.0.3282.144
Operating system	Linux 3.8.11
Software rendering list URL	https://chromium.googlesource.com/chromium/src/+/0/gpu/config/software_rendering_list.json
Driver bug list URL	https://chromium.googlesource.com/chromium/src/+/0/gpu/config/gpu_driver_bug_list.json
ANGLE commit id	2987f0fde973
2D graphics backend	Skia/64 0
Initialization time	53
In-process GPU	false
Passthrough Command Decoder	false
Supports overlays	false
Sandboxed	true
GPU0	VENDOR = 0x0000, DEVICE= 0x0000
Optimus	false
Optimus	false
AMD switchable	false
Driver vendor	ES
Driver version	3.1
Driver date	
Pixel shader version	3.10
Vertex shader version	3.10
Max. MSAA samples	4
Machine model name	
Machine model version	
GL_VENDOR	ARM
GL_RENDERER	Mali-T604
GL_VERSION	OpenGL ES 3.1 v1.r12p0-04rel0.f59038529369929fa5eb884aed147486
 

Comment 1 by ricea@chromium.org, Feb 20 2018

Components: Platform>NaCl

Sign in to add a comment