Flash plugin getting blocked by an overzealous entry in the blocklist

RESOLVED FIXED

Status

()

Firefox for Android
Plugins
RESOLVED FIXED
4 years ago
2 years ago

People

(Reporter: TeoVermesan, Assigned: jorgev)

Tracking

Trunk
ARM
Android
Points:
---
Bug Flags:
in-testsuite ?

Firefox Tracking Flags

(firefox34 affected, firefox35 affected, firefox36 affected, firefox37 affected)

Details

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Steps to reproduce:
1. Open Firefox and go to http://www.intel.com/museumofme/mobile/index.htm
2. Put Firefox in background and wait for a few minutes
3. Exit Firefox from app menu or from Task Manager
3. Reopen Firefox and go again to http://www.intel.com/museumofme/mobile/index.htm

Expected results:
- Flash content should be correctly displayed.

Actual results:
- Flash doesn't work. Grey content is displayed.
Note: 
-flash will work again only with a clean profile.
-even if you change the "dom.ipc.plugins.flash.disable-protected-mode" pref to true, flash still does not work
Can you run a debug build and attach a log-cat?
Component: General → Plugins
(Reporter)

Comment 2

4 years ago
Created attachment 8537741 [details]
logflash.txt

Here are the attached the logs.
tracking-fennec: --- → ?
Assignee: nobody → snorp
tracking-fennec: ? → +

Updated

4 years ago
Duplicate of this bug: 1110683

Updated

4 years ago
Duplicate of this bug: 1114339
From the bug above, other STR

> Steps to reproduce:
> 
> For more background look at this thread:
> https://support.mozilla.org/en-US/questions/1036546
> 
> Install firefox for android. Install flash.
> 
> Go to https://settings.adobe.com/ or any other site that uses flash. Force
> stop firefox or wait a day so that plugin block list gets updated. Then
> attempt to visit a flash page. Instead of flash content you will have a gray
> box.
> 
> 
> 
> 
> 
> Actual results:
> 
> There will be no option to enable the flash content and you will just have a
> grey box as there is no option presented to allow the plugin to be allowed. 
> 
> 
> Expected results:
> 
> An option to start content should have been presented. Otherwise there needs
> to be a way to modify blocked list since adobe no longer provides new flash
> plugins.

Comment 6

4 years ago
(In reply to Aaron Train [:aaronmt] from comment #5)
> From the bug above, other STR
> 
> > Steps to reproduce:
> > 
> > For more background look at this thread:
> > https://support.mozilla.org/en-US/questions/1036546
> > 
> > Install firefox for android. Install flash.
> > 
> > Go to https://settings.adobe.com/ or any other site that uses flash. Force
> > stop firefox or wait a day so that plugin block list gets updated. Then
> > attempt to visit a flash page. Instead of flash content you will have a gray
> > box.
> > 
> > 
> > 
> > 
> > 
> > Actual results:
> > 
> > There will be no option to enable the flash content and you will just have a
> > grey box as there is no option presented to allow the plugin to be allowed. 
> > 
> > 
> > Expected results:
> > 
> > An option to start content should have been presented. Otherwise there needs
> > to be a way to modify blocked list since adobe no longer provides new flash
> > plugins.

I believe this bug is due to plugin blocking. Because if you set extensions.blocklist.enable=false, then firefox works as expected. If there was a way to allow for blocked content I believe it would work.
Which version of Android Flash is installed on the device? The last available version on the Adobe Archives? (http://helpx.adobe.com/flash-player/kb/archived-flash-player-versions.html, version: 11.1.115.81)?

Comment 8

4 years ago
Yes, I am using version: 11.1.115.81. However I believe this version is on blocked plugin list.
The plugin cannot be blocked because of the version, because we don't report that version (11.1.115.81) to gecko anywhere. See bug 1112143. The fact that it worked when the pref was toggled is probably just a coincident.

Comment 10

4 years ago
It might be coincidence, but when extensions.blocklist.enable=true you get a grey box, but if you set extensions.blocklist.enable=false you get the tap to enable flash which allows flash to work. If you go to about:plugins when

extensions.blocklist.enable=false

You get the following:

State: Enabled (STATE_VULNERABLE_UPDATE_AVAILABLE)

When

extensions.blocklist.enable=true

You get the following:

State: Enabled
We should indeed re-evaluate this if this is what is happening on release right now
tracking-fennec: + → ?
Summary: Flash doesn't work after putting Firefox in background for a few minutes and then restart → Flash plugin getting blocked by the non-existent block list
a regression window would be useful here
Keywords: regressionwindow-wanted
(In reply to ram_80 from comment #10)
I stand corrected! It does look like blocking is at work here. Weirdness. I'll look into it more today.
It looks like click-to-play is busted on the second attempt a page is loaded (and only after restart?). We get a null eventType here[0] in the broken state.

[0] http://mxr.mozilla.org/mozilla-central/source/mobile/android/chrome/content/PluginHelper.js#157
Found a regression range: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=e90536aa55dd&tochange=df3fc7cb7e80

The change that causes the breakage is here: https://hg.mozilla.org/mozilla-central/rev/54b831a0ce00

Specifically, the first hunk of that patch. Building locally without that change (and fresh profile) makes things work again.
Sorry, it's the second hunk. The one that adds this:

    1.24 +      <emItem  blockID="i792" id="{8f894ed3-0bf2-498e-a103-27ef6e88899f}">
    1.25 +                        <versionRange  minVersion="0" maxVersion="*" severity="3">
    1.26 +                    </versionRange>
    1.27 +                    <prefs>
    1.28 +              </prefs>
    1.29 +    </emItem>
(In reply to Kevin Brosnan [:kbrosnan] from comment #17)
> That seems unlikely https://bugzilla.mozilla.org/show_bug.cgi?id=1109795 and
> https://addons.mozilla.org/en-US/firefox/blocked/p796 updated the Linux
> block recently.

Flash plugin on Android reports its version as "11.1 r115" so that's certainly within the blockrange added by bug 1109795:

<pluginItem  blockID="p796">
  <match name="filename" exp="libflashplayer\.so" />
  <versionRange  minVersion="0" maxVersion="11.2.202.424" severity="0" vulnerabilitystatus="1"
  </versionRange>
  <infoURL>https://get.adobe.com/flashplayer/</infoURL>
</pluginItem>

The problem is that the block added by bug blocks the plugin by filename only. It should probably be updated to only block with os="Linux"
Blocks: 1109795
(In reply to James Willcox (:snorp) (jwillcox@mozilla.com) from comment #15)
> Found a regression range:
> https://hg.mozilla.org/mozilla-central/
> pushloghtml?fromchange=e90536aa55dd&tochange=df3fc7cb7e80
> 
> The change that causes the breakage is here:
> https://hg.mozilla.org/mozilla-central/rev/54b831a0ce00
> 
> Specifically, the first hunk of that patch. Building locally without that
> change (and fresh profile) makes things work again.

Were you completely deleting your profile folder between each test? That's pretty much the only sure way to make only a change to the application blocklist have an actual effect on the plugins.
(In reply to Dave Townsend [:mossop] from comment #19)
> (In reply to James Willcox (:snorp) (jwillcox@mozilla.com) from comment #15)
> > Found a regression range:
> > https://hg.mozilla.org/mozilla-central/
> > pushloghtml?fromchange=e90536aa55dd&tochange=df3fc7cb7e80
> > 
> > The change that causes the breakage is here:
> > https://hg.mozilla.org/mozilla-central/rev/54b831a0ce00
> > 
> > Specifically, the first hunk of that patch. Building locally without that
> > change (and fresh profile) makes things work again.
> 
> Were you completely deleting your profile folder between each test? That's
> pretty much the only sure way to make only a change to the application
> blocklist have an actual effect on the plugins.

mozregression does start with a fresh profile each time, yeah.
Assignee: snorp → dtownsend
Sorry, I don't have any ability to fix the blocklist. Jorge maybe
Assignee: dtownsend → jorge
[Tracking Requested - why for this release]:
tracking-firefox35: --- → ?
Flags: in-testsuite?
(Assignee)

Comment 23

4 years ago
I added OS=Linux to the block in dev and prod. We'll need someone to make sure that the block still works on Linux and it's no longer blocking on Android. Juan, can you help with this?
Flags: needinfo?(jbecerra)
Keywords: regressionwindow-wanted → qawanted
Android seems to be working again

Comment 25

4 years ago
Checked on Nexus 5 ( Android 5.0.1) and Galaxy Nexus ( Android 4.3) - Works fine again on Android.

Updated

4 years ago
Keywords: qawanted

Updated

4 years ago
tracking-fennec: ? → ---
tracking-firefox35: ? → ---
Summary: Flash plugin getting blocked by the non-existent block list → Flash plugin getting blocked by an overzealous entry in the blocklist
(Assignee)

Comment 26

4 years ago
Aaron, did you verify that the block still works correctly on Linux?
Flags: needinfo?(aaron.train)
(In reply to Jorge Villalobos [:jorgev] from comment #26)
> Aaron, did you verify that the block still works correctly on Linux?

There's a NI on Juan for that.
Flags: needinfo?(aaron.train)
I tested on Linux Mint using Firefox 34.0.5 and the Flash versions below. The older version was blocklisted (click-to-pay) whereas the latest one, ...425, wasn't. 

    File: libflashplayer.so
    Path: /usr/lib/adobe-flashplugin/libflashplayer.so
    Version: 11.2.202.411
    State: Enabled (STATE_VULNERABLE_UPDATE_AVAILABLE)
    Shockwave Flash 11.2 r202

    File: libflashplayer.so
    Path: /usr/lib/adobe-flashplugin/libflashplayer.so
    Version: 11.2.202.425
    State: Enabled
    Shockwave Flash 11.2 r202
Flags: needinfo?(jbecerra)
(Assignee)

Comment 29

4 years ago
Thank you, Juan. Looks like we're good then.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.