Closed Bug 356694 Opened 15 years ago Closed 14 years ago
Flash doesn't work on Intel Macs, problems with "Flash Player Enabler
.plugin" (which is Power PC)
Since updating to Firefox 2 rc2, Flash doesn't work on any sites. I've tried upgrading my flash player (currently 9.0 r19), and still no dice. Steps to reproduce: 1. load said URL 2. click on any of the video thumbnails. 3. notice the player doesn't load. 4. notice no Flash context menu appears when you ctrl-click (right click) in the expected flash area. Although I can't view the article, this macfixit title seems to imply others are having issues too. http://www.macfixit.com/article.php?story=20060905094554613
this was happening in 10.4.7 OSX also; before I upgraded to .8
Does it work in Safe mode? http://kb.mozillazine.org/Safe_mode
Component: Plugin Finder Service → General
QA Contact: plugin.finder → general
did not know about safe mode; now I do; thanks! however, safe mode did not solve the problem unfortunately.
This bug exists on my Intel based Mac (MacBook), running OSX 10.4.8, FFox2rc2, Flash 9.0 r19 (highest version). This bug DOES NOT exist on my PowerPC based Mac (iMac), running OSX 10.4.8, FFox2rc2, Flash 9.0 r16 (highest version).
Summary: Flash doesn't work. → Flash doesn't work on Intel Macs
data point: I've just upgraded to 9.0r20 on my intel mac running FF2 (version number coming next) and it works for me. Shockwave Flash File name: Flash Player.plugin Shockwave Flash 9.0 r20 MIME Type Description Suffixes Enabled application/x-shockwave-flash Shockwave Flash swf Yes application/futuresplash FutureSplash Player spl Yes jud tells me there are reports of problems on macfixit, I'll look for more details.
the version of firefox I am using is: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1) Gecko/20061003 Firefox/2.0 I got the new version of flash from http://www.adobe.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash&P2_Platform=MacOSX (I used to be running Flash 8.0 r27, which also worked for me.) jud, can you try upgrading to 9r20?
jud, is http://forums.mozillazine.org/viewtopic.php?t=472272&highlight=flash+mac similar to what you are seeing? are you seeing anything in the console if you do: 1) launch Terminal 2) from your shell, do: /Applications/Firefox.app/Contents/MacOS/firefox-bin
That mozillazine article is what I'm seeing too. I'm on flash 9r20 now, but just noticed that I appear to have two things registered for flash. Shockwave Flash File name: Flash Player Enabler.plugin Shockwave Flash 9.0 r19 MIME Type Description Suffixes Enabled application/x-shockwave-flash Shockwave Flash swf Yes application/futuresplash FutureSplash Player spl Yes Shockwave Flash File name: Flash Player.plugin Shockwave Flash 9.0 r20 MIME Type Description Suffixes Enabled application/x-shockwave-flash Shockwave Flash swf Yes application/futuresplash FutureSplash Player spl Yes
I moved the "Flash Player Enabler.plugin" out of the way, and all is well. I did not make any changes to my plugins prior to upgrading to FF2rc2, so this still feels like a bug to me.
Component: General → Plug-ins
Product: Firefox → Core
QA Contact: general → plugins
Version: 2.0 Branch → 1.8 Branch
from http://www.flip4mac.com/fusetalk/forum/messageview.aspx?catid=32&threadid=1524&enterthread=y Just noticed that by "getting info" for the Flash plug-ins, the Flash Player Enabler.plugin "Kind" is "Plug-in (PowerPC)" and the Flash Player.plugin is "Plug-in (Universal)". What is a PowerPC plug-in doing there? Can That be the problem? I followed the standard installation instructions of Adobe. Thanks for your time and patience. We may be getting to the bottom of this. jud, can you see if your "Flash Player Enabler.plugin" (Shockwave Flash 9.0 r19) is a PowerPC plugin?
mine, which I moved out the way (e.g. not using now), is indeed PowerPC.
Running Firefox 2.0 RC3 since updating to this I get the error below. Cannot recognize type of executable for CFBundle 0x18704890 </Library/Internet Plug-Ins/Flash Player Enabler.plugin> (not loaded) I have already tried reinstalling the universal binary version of flash with no success. Running OS X 10.4.8 on an Intel iMac.
jay / judson: before flash stopped working, what version of Firefox were you using? (Was it OK with FF 2.0 RC 2 or RC 1?) From the forum link cited above (http://forums.mozillazine.org/viewtopic.php?t=472272&highlight=flash+mac): "Since updating (automatically) to the new FF 2.0 RC2 this morning (07 Oct 2006 05:41 pm) flash no longer works"
Summary: Flash doesn't work on Intel Macs → Flash doesn't work on Intel Macs, problems with "Flash Player Enabler.plugin" (which is PowerPC)
broke for me when auto-update from rc1 to rc2.
thanks for the info, jud. Can you zip up your "Flash Player Enabler.plugin" and attach it here?
Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0 WFM. I updated from RC1 ->RC3. Flash worked in RC1 and still worked in RC3. However, I have Flash 9 r20 installed. Shockwave Flash File name: Flash Player.plugin Shockwave Flash 9.0 r20
> WFM. I updated from RC1 ->RC3. Flash worked in RC1 and still worked in RC3. > However, I have Flash 9 r20 installed. it WFM, too. But it's the PowerPC "Flash Player Enabler.plugin" that is tripping us up.
I upgraded from 188.8.131.52 and flash was working fine.
dan pointed me to bug #302737 and bug #354124. I'll try to see if this is the same issue or not, by reproducing the bug with jud's plugin and FF2.0RC2 and then testing with RC3.
jud, where was "Flash Player Enabler.plugin" located for you? /Library/Internet Plug-Ins/, or somewhere else?
that's where it used to be... I moved it to my Documents folder so I could get things working again.
> that's where it used to be. Thanks jud. the reason I ask is that I have the same "enabler" plugin, but it doesn't show for me in about:plugins just for extra some background info on this plugin and the files, see http://weblogs.macromedia.com/mesh/archives/2006/01/flash_player_sw.html
One thing I've noticed (and it's not clear to me from the discussion whether it's relevant here or not; sorry) is that the Flash Player installer often only updates "half" of an existing Flash Plugin install, so you end up with one file that's from 8.0 and another from 9.0, etc.--and potentially one Universal and one PPC-only. So I've taken to completely removing Flash Plugin files from /Library/Internet Plug-ins before installing a new version. I don't have an Intel Mac, so I can't tell if the Enabler.plugin is supposed to be Uni or not.
Josh - any thoughts on this?
Minusing for 1.8.1 but adding relnote comment. Nominating for 184.108.40.206. Better STR would help me with the release notes! :)
I think I found the culprit here... Both Intel machines that I've now seen this on (just experienced it on my new home iMac) were migrated to from previous PowerPC machines. I used the Apple migration assistant to migrate from PowerPC machines to Intel machines. The assistant must be carrying over the PowerPC Flash Player Enabler.plugin to the new, Intel, mac. Not sure how the migration asst works, but it shouldn't be carrying over bits that don't run on Intel.
jud, thanks for the additional info. fwiw, on my Intel Mac, I have a "/Library/Internet Plug-Ins/Flash Player Enabler.plugin", and I did not migrate from a PowerPC mac. Just having the "Flash Player Enabler.plugin" isn't enough to cause this bug. perhaps we should add code to ignore any PowerPC plugins on Mac Intel? (file for "Flash Player Enabler.plugin/Contents/MacOS/Flash Player Enabler" returns "header for PowerPC PEF executable")
What should be of interest to the Mozilla team is that Flash works fine on Safari without jumping through any of these hoops. Firefox breaks, Safari doesn't. That should be a worthwhile data point. I finally got mine working be deleting every file I could find with the word "flash" in it: 659 11:29 sudo rm -rf /Applications/SAFlashPlayer 660 11:29 sudo rm -rf /Library/Application\ Support/Macromedia/Shockwave\ 10/ 661 11:30 sudo rm -rf /Library/Internet\ Plug-Ins/Flash\ Player* 662 11:30 sudo rm -rf /Library/Internet\ Plug-Ins/flashplayer.xpt 664 11:30 sudo rm -rf /Library/Internet\ Plug-Ins/NP-PPC-Dir-Shockwave 665 11:30 rm -rf Library/Internet\ Plug-Ins/* 666 11:31 rm -rf Library/Caches/Java\ Applets/cache/javapi/v1.0/file/flashpro.class-4e8ff740-28ffe73f.* 669 11:34 rm -rf Library/Application\ Support/Firefox/pluginreg.dat
thanks for the additional info, lolife. jud, can you attach your ~/Library/Application\ Support/Firefox/pluginreg.dat or email it to me? I am wondering if your pluginreg.dat (since you used the migration assistant to go from PowerPC to Intel) contains a reference to the PowerPC based "Flash Player Enabler.plugin".
if that is it, we might be able to add some ifdef XP_MACOS_X code to nsPluginHostImpl.cpp to use nsILocalFileMac::GetFileType() to determine if the plugins are all safe for the current architecture, and if not, rebuild the pluginreg.dat file http://lxr.mozilla.org/seamonkey/source/modules/plugin/base/src/nsPluginHostImpl.cpp#234 http://lxr.mozilla.org/seamonkey/source/xpcom/io/nsLocalFileMac.cpp#3165
When pluginreg.dat is generated on a PPC machine you can't use it on an Intel machine in this case. Delete pluginreg.dat to fix the problem. We should probably run loadability checks on plugins every time instead of relying on the cache, otherwise we'll run into problem like this. Working on it...
more info from josh over AIM: I think you're onto something with pluginreg.dat. the enabler file is not just the trigger. we have code that checks the plugin arch before loading it and skips it if it can't execute. I wrote that code myself, nsPluginsDirDarwin.cpp IsLoadablePlugin() if you wipe out your profile then force FF to run as a PPC app, then use that plugin.dat, I bet you'll repro. the trick for forcing FF to run as a PPC app is to do "Get Info" on the app and check "Run in Rosetta". I can repro with those exact steps.
Assignee: nobody → joshmoz
Whiteboard: [Fx 220.127.116.11]
from https://bugzilla.mozilla.org/show_bug.cgi?id=346954#c20 "it just moves IsPluginFile() calls after the cache check). Benefits: avoid inspecting executables we already know are plugins (because they're in the cache)." this assumption may be the cause of the problem, because as josh/jud have found, the plugins in the cache may not be valid, due to migration.
Attachment #244913 - Flags: review?(sspitzer) → review?(sayrer)
if sayrer is OK with the backout, I'd recommend adding a comment about why we need to call IsPluginFile() where we call it, and refer back to this bug.
Comment on attachment 244913 [details] [diff] [review] back this out, patch -R this rots... but we should fix this ASAP. drivers: this will cause at least one safari plugin to get loaded every time a feed is visited.
Attachment #244913 - Flags: review?(sayrer) → review+
"this will cause at least one safari plugin to get loaded every time a feed is visited." That was fixed by the first patch on the other bug. we're only backing out the second patch, so that shouldn't happen.
(In reply to comment #38) > > That was fixed by the first patch on the other bug. we're only backing out the > second patch, so that shouldn't happen. Yes, you're right. It will cause some plugins to be loaded every time a feed is visited, but nothing really common AFAIK (the other patch in the old bug prevents the Safari plugin problem).
just to clarify (in case I wasn't the only one who got confused) backing out part 2 of sayrer's 2 part fix for bug #346954 will, to quote robert from irc: "will regress part of it, but not the worst part. so it's livable"
14 years ago
Comment on attachment 244913 [details] [diff] [review] back this out, patch -R sr=jst
Attachment #244913 - Flags: superreview?(jst) → superreview+
landed on trunk
Comment on attachment 244913 [details] [diff] [review] back this out, patch -R approved for 1.8 branch, a=dveditz for drivers
Attachment #244913 - Flags: approval18.104.22.168? → approval22.214.171.124+
landed on 1.8 branch
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
WFM: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:126.96.36.199pre) Gecko/20061130 BonEcho/188.8.131.52pre
You need to log in before you can comment on or make changes to this bug.