Issue metadata
Sign in to add a comment
|
Flash is broken if user-data-dir is on a network drive
Reported by
easya...@gmail.com,
Sep 29 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 Example URL: https://www.schoolseatingplanner.com/staffConsole.html Steps to reproduce the problem: 1. Fresh install of Chrome and you can visit the site OK 2. As soon as the pepperflash update occurs you cannot load the website, Get Adobe Flash Player shown instead of the website 3. What is the expected behavior? the website should load What went wrong? chrome://plugins is indicating that the pepflashplayer.dll should be version 23.0.0.166, but the version in the folder is actually 23.0.0.162 Did this work before? N/A Is it a problem with Flash or HTML5? Flash Does this work in other browsers? Yes Chrome version: 53.0.2785.116 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 23.0 r0
,
Sep 30 2016
You do not have that option (only the normal web browser right-click options) if you hover over the Get adobe Flash Player, see attached file. If you left click on the Get adobe Flash Player Icon you are directed to the Adobe Flash Player site where it tells you Your Google Chrome browser already includes Flash Player (See attachment).
,
Oct 7 2016
Thank you for providing more feedback. Adding requester "ajha@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 7 2016
Hi, thanks for reporting. Having trouble reproducing this; Could you send a screenshot of chrome://plugins? It's worth noting that it's expected behavior that .166 contains .162 binaries; .166 is a rename of .162 for [various reasons].
,
Oct 10 2016
Unable to reproduce the issue on Win7/64 bit - Version 53.0.2785.143 m (64-bit)
,
Oct 13 2016
,
Oct 13 2016
Screen shot of the about plugins attached. It's still an issue.
,
Oct 13 2016
Re #7: Is "U:" a network drive?
,
Oct 13 2016
U is where we redirect ours users folders to on The network. We did this via group policy so users chrome settings etc follow them around on the network. This is the way we have always used chrome. Worked before the update.
,
Oct 13 2016
I see. Thanks for the quick reply. We cannot load Flash from a network drive, which is why it is not working for you. Prior to the update, Flash worked because there was a version of Flash also bundled with Chrome that lived alongside the Chrome installation (probably in C:), and this would be loaded instead. After the update, that file no longer exists and we can only load Flash from the user-data-dir or from a system-wide installation of Flash. In the short term, the only advice I can give is to install system Flash on your machines from https://get.adobe.com/flashplayer/ or https://get.adobe.com/flashplayer/otherversions/ . :( In the long term, we want to improve the component update of Flash to avoid this problem, but there are many security issues to sort out before those changes can be made. I will also talk with the team and try to figure out if we can code up some other workaround.
,
Oct 13 2016
,
Oct 13 2016
,
Oct 13 2016
issue 572131 is probably the best to dup this into as it has all the history and background on this.
,
Oct 13 2016
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ajha@chromium.org
, Sep 30 2016Components: -Internals>Media Internals>Plugins>Flash
Labels: Needs-Feedback