Issue metadata
Sign in to add a comment
|
Chrome 56 always re-activates disabled flash plugin after restart
Reported by
m.k...@irregular.at,
Jan 26 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76 Safari/537.36 Steps to reproduce the problem: 1. Goto chrome://plugins/ 2. Disable Adobe Flash Player 3. Restart Browser 4. Again check chrome://plugins/ What is the expected behavior? Flash should stay disabled. What went wrong? Flash was enabled again (without user interaction) after the restart. Did this work before? N/A Chrome version: 56.0.2924.76 Channel: stable OS Version: Ubuntu 16.10 Flash Version: Shockwave Flash 24.0 r0 Worked before, behaviour started with Chrome 56.
,
Jan 26 2017
It seems that this also applies to other plugins than Flash. My Flash, Widevine and Native Client all get re-enabled after a restart.
,
Jan 26 2017
@xhwang, is this a duplicate of Issue 683379 ?
,
Jan 26 2017
I think this is related to issue 615738 . But this seems to be different from what's described at https://bugs.chromium.org/p/chromium/issues/detail?id=615738#c34 tommycli / ericde: Thoughts?
,
Jan 26 2017
Adding Julian.
,
Jan 26 2017
no repro for me on Windows 56.0.2924.67 (non-policy).
,
Jan 26 2017
I am using 56.0.2924.76 (64-bit) on Ubuntu 16.10: Linux 4.8.0-34-generic #36-Ubuntu SMP Wed Dec 21 17:24:18 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux and can reproduce
,
Jan 26 2017
There is someone who can repro on Win 7: https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html?showComment=1485386690233#c3154367030131754547 > Just updated to Chrome 56.0.2924.76 (64-bit/Win7) > It automatically re-activates your flash plugin. ON EVERY RESTART.
,
Jan 26 2017
Jep, that was me. Flash was disabled on my machine (Win7Pro 64bit) for a couple of years now. Since Chrome 56 update it gets re-enabled on every Chrome restart.
,
Jan 26 2017
Can anyone that can repro show a screenshot of about://plugins? Thanks!
,
Jan 26 2017
Screenshot attached
,
Jan 26 2017
This is how it looks after a Chrome restart:
,
Jan 26 2017
Thank you both! Do you mind to click the "Details" link and share the screenshot again?
,
Jan 26 2017
See attachment ;)
,
Jan 26 2017
Details extended:
,
Jan 26 2017
Thanks again! So this has nothing to do with issue 683379 . Other owners might have better idea why this is happening.
,
Jan 26 2017
,
Jan 26 2017
I can't view 673199 "You do not have permission to view the requested page. Reason: User is not allowed to view this issue" Why?
,
Jan 26 2017
Sorry the bug was mislabeled and made non-public. I fixed it. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by m.k...@irregular.at
, Jan 26 2017