261663 - Flash/Shockwave plugin only installed in main firefox folder and not in profile

Status: RESOLVED WORKSFORME

(Firefox :: Installer, defect)

Description

[Charley]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040925 Firefox/0.10 (MOOX M1)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040925 Firefox/0.10 (MOOX M1)

Everytime the autoinstaller for flash appears, and installs flash on the system,
it puts flash into firefox/plugins and if the folder was ever deleted, the user
has to reinstall flash/shockwave. 

Reproducible: Always
Steps to Reproduce:
1.have a fresh firefox that doesn't have flash.
2.go to a flash site and autoinstall flash
3.delete the firefox folder and reinstall
4.open a flash site and you'll have to redownload flash.

Actual Results:  
reinstall flash/shockwave plugin. 

Expected Results:  
install into the profile Mozilla/Plugins, so that deleting the firefox folder
won't delete the plugin.

Comment 1

[Peter van der Woude [:Peter6]]

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040926
Firefox/0.10

confirming

->NEW
->?1.0

Comment 2

[chris hofmann]

rafael, can you check with the macromedia folks on this?

Comment 3

[Peter Helcmanovsky]

This is reason of crash after ("correct") update of firefox + "flashblock"
extension.
(possible cause of bug #301276 ?)

If you just uninstall 1.0.4 and reinstall 1.0.5 into same directory (without
deleting content of firefox directory), flash plugin remains and it works all ok.

I followed instructions from mozilla.org when I was updating to 1.0.6:
uninstall 1.0.5
delete firefox folder completely
install 1.0.6

-> crash on page with flash objects caused by flashblock extension.
(works ok without flashblock extension)

Once you install flash plugin again, flashblock extension stops to crash and
everything works fine.

So there are actually 2 problems...
a) why extension *can* crash firefox? (sloppy extension programming for sure,
but maybe firefox can be more robust too)

b) to change Macromedia's flash plugin itself to install for user(s).

Comment 4

[timeless]

[e-mail]: an extension is basically just another *trusted* part of
gecko, by installing it, you indicate that you trust it not to reformat your
hard drive, just like you trust gecko not to do so. extensions are *not* java
applets, but if you want to think about them that way, pretend they're signed
with full privledges, they can load random libraries and execute arbitrary bad
code. many of the extensions written for gecko do so.

Comment 5

[Rafael Ebron (:rebron)]

Is this still a problem?

Comment 6

[Robert Strong (they/them - no direct email)]

Flash at least is using the windows registry for us to find where it is installed now so we don't copy it anymore. If the problem still exists for other plugins - quicktime is one example - it should be fixed by evangelizing the vendor to use the registry. resolving -> wfm