Closed Bug 433101 Opened 16 years ago Closed 16 years ago

Flash plugin isn't installed

Categories

(Toolkit Graveyard :: Plugin Finder Service, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 416396

People

(Reporter: ptomes, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008050906 Minefield/3.0pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008050906 Minefield/3.0pre

See the screencast:
http://www.phil.muni.cz/~ptomes/flash.swf

Reproducible: Always

Steps to Reproduce:
1. open http://www.youtube.com
2. let Firefox install the Flash plugin
Actual Results:  
Flash plugin is not installed

Expected Results:  
Flash plugin is installed
Flags: blocking-firefox3?
I try it immediately after a fresh install of Windows XP SP 2 and an upgrade to SP 3.
Tony, can you get QA to check into this (I'm not sure if this is covered by the FFTs, but if not, it should be) and if you can confirm it, please renominate as blocking?
Flags: blocking-firefox3?
Keywords: qawanted
I am unable to reproduce this.  Reporter, what version of Flash do you have installed?  You said you could repro this on both xp2 and xp3?   Can you also check if there are errors thrown?

i followed steps on comment #0 using manual Install on PFS, and flash works immediately on youtube after restarting.  

My settings:
- Windows XP sp2
- Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008032805 Minefield/3.0pre
- Shockwave Flash
File name: NPSWF32.dll
Shockwave Flash 9.0 r124

For litmus tests, there are a few existing ones tracking this:
- https://litmus.mozilla.org/show_test.cgi?id=4383
- https://litmus.mozilla.org/show_test.cgi?id=4355
Flags: in-litmus+
looks like a dupe of bug 416396.  lets track it over there.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Keywords: qawanted
Resolution: --- → DUPLICATE
Product: Firefox → Toolkit
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.