Bug 696277

Summary: Flash picture is damaged
Product: [Fedora] Fedora Reporter: Zdenek Kabelac <zkabelac>
Component: firefoxAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: gecko-bugs-nobody, mcepl
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-18 23:22:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Example of damaged picture none

Description Zdenek Kabelac 2011-04-13 18:25:04 UTC
Description of problem:

I'm not quite sure why it happens - but recent rawhide Fedoras' mozilla builds used together with Adobe Flash plugin are producing images which are often obscured by various flashing rectangles at various locations.

Whenever I use 'raw' Mozilla build I'm not seeing such picture damages.
Is there anything 'special' about Fedora compilation ?
firefox-4.0.1pre.cs.linux-x86_64.tar.bz2
firefox-4.2a1pre.en-US.linux-x86_64.tar.bz2

I'm using T61 with Intel graphics driver. I've originally suspect driver - but as with Mozillas' build I do not see it - it must be something with Fedora building options. 

Version-Release number of selected component (if applicable):
firefox-4.0-3.fc16.x86_64
xulrunner-2.0-3.fc16.x86_64
xorg-x11-drv-intel-2.14.0-5.fc15.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Zdenek Kabelac 2011-04-13 18:27:23 UTC
Created attachment 491846 [details]
Example of damaged picture

I've picked i.e. http://www.opel.cz  where the welcome page has the Flash  graphics. As one can see - white boxes should not be there.

Comment 2 Zdenek Kabelac 2011-04-13 18:28:56 UTC
I should note - as a flash plugin I'm using 64bit plugin - for this case - 10.0 r45

Comment 3 Zdenek Kabelac 2011-04-16 18:59:52 UTC
Ok - I've looked more on this issue - and when 2 things looks the same - it's not really the same.

For a long time I've had 64bit plugin  nspluginwrapped - because when flash crashed - ff survived. However it now makes the problem.

Before a long time I've placed libflash plugin into my home dir:
 ~/.mozilla/plugin - and I've believed it's the one used by both firefox as ff added plugin container wrapping by default.

But this is only the case of Mozilla builds -  Fedora builds prioritize nsplugin version (or possibly Mozilla builds do not know about /usr/lib64/mozilla dir). So even though simple check of installed plugins shows the version 10.0.45 - in the Fedora case it's 'nswrapped' version - and that's the reason for difference (also in runtime - once there is once npviewer.bin task or in the other case there is plugin-container).

When I remove nswrapped version - both version will use the same plugin from my home dir - and there is no problem with picture quality.

So it seems to show few related problems:

nswrapped version shows broken picture - but it's now bug of nspluginwrapper.

Plugins from the user's home directory do not have priority over system version - which is imho bad idea.

Comment 4 Matěj Cepl 2011-04-18 23:22:56 UTC
For this issue there is already a bug in the upstream database (https://bugzilla.mozilla.org/show_bug.cgi?id=629472 and related bugs) and we believe that it is more appropriate to let it be resolved upstream.

We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates.

However, I believe that the proper solution for this bug and whole nspluginwrapper problems is fixing of https://bugzilla.mozilla.org/show_bug.cgi?id=559142 or Adobe providing properly supported x86_64 version of their Flash player.

We would strongly encourage you to subscribe to the upstream bug as well (by logging in and adding yourself to the Cc list), so that you can provide whatever information required for the successful resolving of this issue.

Thank you for helping to make free software better.