Closed Bug 123522 Opened 23 years ago Closed 23 years ago

Shockwave plugin does not start

Categories

(Core Graveyard :: Plug-ins, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 116562

People

(Reporter: jomo, Assigned: serhunt)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:0.9.8+) Gecko/20020204
BuildID:    20020204

After installing the latest Linux shockwave plugin (ShockwaveFlash.class and
libflashplayer.so) the browser shows the plugin in the list of plugins, but when
visiting www.shockwave.com the message "Starting Plugin for type
application/x-shockwave-flash" appears in the status line and nothing happens.
This does happen on Debian/Woody (latest dist-upgrade). On Slackware 8.0
installations the plugin does work without a problem. I tested this with Mozilla
Build-ID 2002020421.


Reproducible: Always
Steps to Reproduce:
1. Visit http://www.shockwave.com
2.
3.
(third flash bug today) again, I am using 020412 trunk on linux, things are 
fine. Gotta check this with today's trunk respin...to see if something really 
broke after last night's checkin..hmm.
pls turn ON your disk cache if it is OFF. I see the problem when I changed disk 
cache to '0' from 50k and selected the 'never' radio button. Turning it ON 
..brings things back to normal. A bug is already filed for that.(disk cache 
issue)
*** Bug 123526 has been marked as a duplicate of this bug. ***
*** Bug 123536 has been marked as a duplicate of this bug. ***
It is the disk cache, I just tried it out: changing the disk cache to <> 0 and
restarting the the browser helped. After hanging the disk cache to 0 and
restarting the browser brings up the problem again. This happens obviously on
both Debian/Woody and Slackware.

Kind reagrds, Joerg.

*** This bug has been marked as a duplicate of 116562 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
v
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.