Pepper Flash not working with Google Roaming Profiles
Reported by
macneils...@hotmail.com,
Jan 17 2018
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Edge/16.16299 Example URL: N/A - probably any URL Steps to reproduce the problem: 1. Delete 28.0.0.137 from Google roaming profile on network drive. 2. Launch chrome, access training videos, it works. (because it default to local server version of pepper flash). 3. Once you log out or close chrome, pepper flash folder get copied back up to roaming profile. 4. launch chrome again and it tries to use pepper flash in network roaming profile, and training videos don't work. The should be a GPO option to set the pepper flash launch location to use local server version, or an option to exclude copying the pepper flash directory to the roaming profile so that it uses local server pepper flash. What is the expected behavior? That it would launch the videos properly using the network location plugin...I know the sandbox discussions and that using network location may not be preferred....but then, why have google roaming profiles as an option in the first place? What went wrong? Training videos don't play because I believe chrome does not like using the pepperflash plugin from the network location. Did this work before? N/A Is it a problem with Flash or HTML5? Flash Does this work in other browsers? Yes Chrome version: 63.0.32.39.132 Channel: n/a OS Version: 2008 R2 Flash Version: 28.0.0.137 Contents of chrome://gpu: ote: To properly save this page, select the "Webpage, Complete" option in the Save File dialog. Graphics Feature Status Canvas: Software only, hardware acceleration unavailable CheckerImaging: Disabled Flash: Software only, hardware acceleration unavailable Flash Stage3D: Software only, hardware acceleration unavailable Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable Compositing: Software only, hardware acceleration unavailable Multiple Raster Threads: Enabled Native GpuMemoryBuffers: Software only. Hardware acceleration disabled Rasterization: Software only, hardware acceleration unavailable Video Decode: Software only, hardware acceleration unavailable Video Encode: Software only, hardware acceleration unavailable WebGL: Hardware accelerated but at reduced performance WebGL2: Software only, hardware acceleration unavailable Problems Detected Drivers older than 2009-01 on Windows are possibly unreliable: 72979, 89802, 315205 Disabled Features: flash_stage3d, gpu_compositing, panel_fitting, flash3d, gpu_rasterization, accelerated_2d_canvas, accelerated_video_decode, accelerated_webgl2, accelerated_webgl, flash_stage3d_baseline, accelerated_video_encode GPU rasterization should only be enabled on NVIDIA and Intel DX11+, and AMD RX-R2 GPUs for now.: 643850 Disabled Features: gpu_rasterization Native GpuMemoryBuffers have been disabled, either via about:flags or command line. Disabled Features: native_gpu_memory_buffers Checker-imaging has been disabled via finch trial or the command line. Disabled Features: checker_imaging Version Information Data exported 1/17/2018, 11:38:23 AM Chrome version Chrome/63.0.3239.132 Operating system Windows NT 6.1.7601 SP1 Software rendering list version 13.13 Driver bug list version 10.34 ANGLE commit id 2ff870db3a3b 2D graphics backend Skia/63 dbae7001c9805fb0a4b18fd0cbc889941cb39db4- Command Line "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --flag-switches-begin --flag-switches-end Driver Information Initialization time 0 In-process GPU true Passthrough Command Decoder false Supports overlays false Sandboxed false GPU0 VENDOR = 0x0000, DEVICE= 0x0000 Optimus false Optimus false AMD switchable false Desktop compositing none Driver vendor Google Inc. Driver version 3.3.0.2 Driver date 2017/04/07 Pixel shader version 3.0 Vertex shader version 3.0 Max. MSAA samples 4 Machine model name Machine model version GL_VENDOR Google Inc. GL_RENDERER Google SwiftShader GL_VERSION OpenGL ES 2.0 SwiftShader GL_EXTENSIONS Disabled Extensions Window system binding vendor Window system binding version Window system binding extensions Direct rendering Yes Reset notification strategy 0x0000 GPU process crash count 0 Compositor Information Tile Update Mode One-copy Partial Raster Enabled GpuMemoryBuffers Status ATC Software only ATCIA Software only DXT1 Software only DXT5 Software only ETC1 Software only R_8 Software only R_16 Software only RG_88 Software only BGR_565 Software only RGBA_4444 Software only RGBX_8888 Software only RGBA_8888 Software only BGRX_8888 Software only BGRA_8888 Software only RGBA_F16 Software only YVU_420 Software only YUV_420_BIPLANAR Software only UYVY_422 Software only Display(s) Information Info Display[2528732444] bounds=0,0 1364x631, workarea=0,0 1364x591, scale=1, external Color space information {primaries:BT709, transfer:IEC61966_2_1, matrix:RGB, range:FULL, icc_profile_id:0} Bits per color component 8 Bits per pixel 24 Diagnostics ... loading ... This is a citrix environment, so to keep profile bloat to a minimum, we've used Google Roaming profiles setting the user data dir and the roaming profile location using GPO and pointing to the roaming profile location. There should be a way to force local server use of pepperflash in C:\program files or exclude copying the pepperflash folder to the roaming profile so that it defaults to the server local version. Is there any way around this or command line to use to force this?
,
Jan 18 2018
,
Jan 19 2018
The only way round this for us was to drop hosting our Chrome User Data on a live network drive - it's now either stored in AppData\Roaming for our staff (not redirected - this does get pretty bloated due to extensions though) or AppData\Local for students (we've got the newish 'Enable the creation of roaming copies for Google Chrome profile data' policy item enabled). There's definitely a gap that needs filling for environments such as ours though.
,
Jan 19 2018
CC'ing dev for further triage
,
Jan 19 2018
You can try to disable component updates through policy for Chrome and install Flash from the MSI provided by Adobe itself. This should make Chrome use the installed version and will not try to download one itself in the USer Data directory.
,
Jan 19 2018
Thanks all. I will try disabling the component updates feature. I thought this feature just installed security fixes and updates to Chrome locally. If I have chrome roaming profiles and the user-data-dir set to the roaming profile...will disabling component updates stop it from copying the pepper flash folder back up to the roaming profile? Seems like that would be a function of the google roaming profile and not component updates.
,
Jan 19 2018
I think there is some misunderstadning what the chrome roaming profile feature is doing. It won't move your regular Chrome profile to the roaming directory. Instead it will still use a local profile directory on each machine in AppData\Local\Google\Chrome unless changed by the UserDataDir policy or cmd line flag and also a streamlined copy of the profile data (like bookmarks, history, password etc) and then synchronize it to the local profile on each machine that logs into the same profile. If you have this feature enabled and also use the UserDataDir policy to keep the regular profile on the roaming location you are not winning anything. Therefore this feature does not change how the Flash plugin is handled in the User Data dir. The component update policy will prevent binary components like flash to update but will not stop chrome from pulling critical security updates like Certificate Revocation Lists etc.
,
Jan 19 2018
So what would happen if I leave the enable chrome roaming profiles set to the network location, and remove the user-data-dir setting? Wouldn't I then lose my users bookmarks and settings then? or would that pull down to the local server as a copy ? and if I did that, would I still be able to create new bookmarks and have that sync up to the roaming profile location so that if I log into a different server, I'd see that bookmark. I thought I tested this and it didn't work that way until I set the user-data-dir.
,
Jan 22 2018
,
Jan 30 2018
,
Jan 31 2018
any update on this, if we'll have the ability to set these features in the future ?
,
Jan 31 2018
I can confirm that disabling component updates & installing the PPAPI Adobe Flash MSI (you'll need a free distribution license) will bypass Pepper Flash for a fresh profile. Not sure if this is the case for existing profiles with Pepper Flash installed though. Just to clarify the point made by pastarmovj - the terminology 'Roaming Profile' in relation to Chrome pertains to the single 'profile.pb' file generated by the 'RoamingProfileSupportEnabled' policy. Moving the 'User Data' folder to the Windows roaming profile is not the same as this: Chrome Roaming Profile - stripped down user data stored in profile.pb file. User Data stored in Windows roaming profile - full user data stored in 'User Data' folder. There's more work to be done in separating the disposable & non-disposable parts of the 'User Data' folder (pepperflash, Browser Metrics & Extensions spring to mind) but it's always improving.
,
Jan 31 2018
Re #12: This is correct. RoamingProfileSupportEnabled will start maintaining the profile.pb file in the Roaming location but the User Data will stay on the local profile (unless moved by the UserDataDir policy). Re #8: Please read the https://support.google.com/chrome/a/answer/7349337?hl=en for more information how the Chrome roaming profile is support is supposed to help you roam Chrome between machines while keeping the User Data dir local to each machine.
,
Oct 29
No recent activity, so archiving |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by krajshree@chromium.org
, Jan 18 2018