We're running 10.6.8 and a lot of machines display a plug-in failure no matter what troubleshooting steps are taken with Flash Player 13. Updating from 12, installing/re-installing through a JSS policy, uninstalling and clean installing manually all do not work as a resolution on machines with the plug-in failure.
It's the strangest thing - some computers have no issue, others just will not cooperate.
I Googled flash player 13 10.6.8 and others have posted about this, but of course the Adobe forums are down right now. Is anybody else with OS X 10.6.8 experiencing issues with Flash Player 13?
For the time being I've rolled back to version 12 and everything's working fine, until Apple disables that out-of-date plug-in.
10.6.8 machines went plug in failure after taking the update. Adobe forums are "down for maintenance" but I did see the topic on Apple support forums to confirm it wasn't just me and mine. Hopefully Adobe releases another version sooner rather than later.
Yea, we are seeing a big issue here in a limited test group, too. 10.6-10.7 are failing with all browsers. Stick with Flash 12.0.0.77 for now….looks like the minimums are higher than announced.
What browser(s) are you having issues with Flash Player 13.0.0.182? Is it a specific website that isn't working or is it failing on http://helpx.adobe.com/flash-player.html
here, here, rtrouton, script is working great. I have it as a Self Service and as a policy with a manual trigger, if one ever wanted to do it in terminal.
One thing I have noticed, the script does not seem to create a "tmp" folder, So the DMG file gets installed on the users desktop, or at Casper Imaging time, the DMG gets copied to "/". I inserted a rm -rf to delete the file, but the file could be in the admin users desktop or any AD user's desktop, etc.
I had problems with this too, on 10.7.5. In Firefox & Safari, the plugin crashed as soon as they tried to load any Flash content. I advised our dept. not to roll it out until Adobe fixes whatever is broken - we have a mix of OS versions, and I can't afford to deal with a file that won't work across the board.
This is a perfect example of why I don't rely on automatic updates, either.
We have determined that this problem is due to a compiler update in our build infrastructure that exposed a long-standing bug in a Mac system library. Flash Player now attempts to use CPU instructions that are not available on a subset of supported Mac hardware from 2006 to 2007. None of the machines in our compatibility labs are affected, so the issue didn't show up in our testing, but we were able to track down a machine that reproduces the issue yesterday. We're actively working on a fix and I'll update this post again once we have more information.
Then says
Update 4/16 I'm pleased to announce that Flash Player 13.0.0.201 for Mac is now available from http://get.adobe.com/flashplayer. This release resolves the crash described in this thread. As noted below, you can either download this immediately from adobe.com or wait for the update to be applied automatically, within 24 hours, via our recommended auto update mechanism. If you encounter any problems updating, please visit http://helpx.adobe.com/flash-player.html for basic troubleshooting steps.