Now this is interesting, if I click on "Block" in the Incognito window, it displays the Flash content! That makes no sense at all. 

Hi,

Have you tried it on another machine? It works fine for me and after I click 'Allow' in Incognito, it shows flash version.

Yes, I filed the report from a different computer than where it was first reported. I'll test again on a third to confirm. I'm assuming you're using the same version? 

Yes, I tried it on 3 Windows 10 (64 bit) machines with Chrome 57.0.2987.133 and all 3 were OK.

As per your comment #3, could you please update the thread with the latest behavior.

Thanks!

I have the same issue with Chrome 61.0.3163.100 (Official Build) (64-bit) on Linux (Debian 9.1 x64).
I have explicitly allowed flash and it still doesn't load (only happens in incognito windows).

Deleted: Screenshot from 2017-10-06 10-03-46.png 153 KB

	Screenshot from 2017-10-06 10-03-46.png 153 KB View Download

Hi,

I've tried it on two machines, both Windows 10 x64.
On one, it didn't happen. On the other one flash does not get enabled. I've enabled flash in the settings and set it to 'allow site to run flash', but it still shows the flash plugin blocked both in normal and incognito mode.

tkent@, can you help on this?

andrewimutch@,

Can you still reproduce the error. It seems to be fixed.

Still seeing it with the latest release:

Version 66.0.3359.117 (Official Build) (64-bit)

1. Open an Incognito window
2. Browse to http://get.adobe.com/flashplayer/about/
3. Right-click on puzzle piece icon and select "Enable Flash"
4. Click "Allow" for "Run Flash" dialog
5. Reload page - Flash does not run

Alternatively, browse here in Incognito mode:

https://www.whatismybrowser.com/detect/is-flash-installed

It reports "Flash is disabled or not installed in this browser"

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tested the issue on chrome version 67.0.3359.117 using Windows-10 with steps mentioned below:
1) Launched chrome version and navigated to URL: http://get.adobe.com/flashplayer/about/
2) Clicked on puzzle like image and clicked on enable flash and clicked on "Allow"
3) Now opened Incognito mode and entered URL: http://get.adobe.com/flashplayer/about/, licked on puzzle like image and clicked on enable flash and clicked on "Allow"
4) Clicked on secure chip, able to see Flash as "Allow" in combo box, reloaded the page and again checked the secure chip, able to flash in "Allow" 

@Reporter: Please find the attached screencast for your reference and let us know if we missed anything in verifying the issue, provide your feedback on it which help in further triaging it in better way.

Thanks!

Deleted: 709228.mp4 4.1 MB

	709228.mp4 4.1 MB View Download

I also couldn't reproduce it on two computers.

I'm able to reproduce this issue *with my usual profile* (and have been able to for a while), but I'm unable to reproduce it if I generate a fresh profile by running chrome with the flag `--user-data-dir=/tmp/blankslate` (where `/tmp/blankslate/` doesn't exist beforehand).

Here's my version info from `chrome://version`:
Google Chrome	68.0.3440.84 (Official Build) (64-bit)
Revision	520a5c14b858e4b1441dd2d3bab9bc745911a23b-refs/branch-heads/3440@{#774}
OS	Linux
JavaScript	V8 6.8.275.24
Flash	30.0.0.154 /home/na/.config/google-chrome/PepperFlash/30.0.0.154/libpepflashplayer.so

rhalavati: Can you think of anything that changed between October 8th when you were able to reproduce the issue, and April 17th when you weren't?

While I'm not about to upload my profile for folks to poke at, if anyone has any hypotheses, or good ways to debug what's going on, I'm happy to poke around to see if I can help narrow it down.

I've got a solid reproduction now. For me, it looks like the issue was that I had an entry in `profile.content_settings.exceptions.plugins` that looked like:
```
"*,*":{
  "per_resource": {
    "adobe-flash-player": 1
  }
}
```

I can consistently reproduce the reported issue by pre-setting that value in the Preferences file (e.g. by running `mkdir -p blankslate/Default && echo '{"profile":{"content_settings":{"exceptions":{"plugins":{"*,*":{"per_resource":{"adobe-flash-player":1}}}}}}}' > blankslate/Default/Preferences` before `google-chrome-stable --user-data-dir=/tmp/chromescience/blankslate/`). Unfortunately, I've got no idea how I managed to add a content exception for "*,*"

I can't think of any change between Oct 8 and Apr 17, and I cannot reproduce it again!
I am not familiar with the content settings file, and I think manually modifying it may result in unexpected errors, is it possible to do it through settings page? (Also note that Flash permissions are more ephemeral from 69).

Adding bbudge@ and raymes@ as they may know more about the issue.

Given that flash settings are now ephemeral this is probably a non-issue. But assigning to dullweber to confirm.

The bug states that Flash cannot be enabled at all. The ephemeral storage just effects keeping the permission after it is enabled.

The setting looks like a default content setting but default content settings are stored in "default_content_setting_values" and not the "exceptions" preference. I'm not sure how you could have gotten that entry but there might be a conflict between the default setting and your *,* entry.

"default_content_setting_values": {
      "automatic_downloads": 3,
      "images": 1,
      "javascript": 1,
      "media_stream_camera": 1,
      "notifications": 2,
      "plugins": 5,
      "popups": 2
    },


As of Chrome 69 this probably doesn't matter anymore because flash settings are not persisted. Could you check if the bug still reproduces on 69?

I'm no longer able to reproduce the bug with Chrome 69; flash works fine in incognito even with the strange *,* entry added to Preferences. If andrewimutch@'s broken flash was caused by the same thing, then it looks like this isn't a problem any more.

I've still got no idea how I managed to create that entry. I couldn't find any sign of it in the regular preferences UI, and I don't remember making a change like that manually (which I suspect I *would* remember, given the fight I had with sync trying to remove it manually). According to profile.created_by_version, this profile has been around since Chrome 30 (late 2013, according to wikipedia), so the problematic entry probably worked its way in sometime in the past, and just got carried forward until it ran into this bug.

Great, thanks for verifying. I guess we can mark this as fixed.

I also suspect that this is caused by old data that wasn't migrated at some point or an old bug that allowed the creation of this setting.