32-bit PepperFlash is BACK...
Posted: Thu 14 Jul 2016, 12:52
***32-bit Pepperflash makes a 'comeback'! ***
Morning, kiddiwinks!
I have a treat for those of you running Chrome/Chromium/SlimJet on 32-bit Pups. Whether by accident or design (not sure which yet), Adobe have apparently re-commenced development of 32-bit Linux Pepper, and are, for the first time, making it publicly available for download.
This means you have a chance to at least update this trouble-prone item in your browser. There's two ways you can do this:-
1) For the more experienced among you, download 32-bit Pepper as a tar.gz file from the Adobe 'Player Download Center'.
https://get.adobe.com/flashplayer/
If you visit the page in your Chrome/Chromium-based browser, the site will auto-detect the type of download you need, based on your browser's user-agent string. Extract the 'libpepflashplayer.so' and 'manifest.json' files from the package, and manually move them into your PepperFlash folder (or relevant location, depending on the browser), following my instructions from here:-
http://www.murga-linux.com/puppy/viewtopic.php?t=101275
2) Or, for the less technically competent among you, I've produced a new series of PepperFlash .pets, to be found at the usual location:-
http://www.murga-linux.com/puppy/viewtopic.php?t=106409
Since none of us know how long this happy state of affairs might last for, "grab 'em while you can..!"
BTW:- It's come to my notice that these .pets may not work for the final three versions of 32-bit Chrome (46, 47, and 48 ). Google had begun to introduce a semi-working updater mechanism to the Linux version of Chrome, and, rather than the browser looking in /opt/google/chrome/PepperFlash for the player module, it was now looking in /root/.config/google-chrome/PepperFlash/[Pepper-version]. It would be a bit daft to make yet another series of .pets just for 3 browsers, so the above location is where you would need to manually move the relevant files to. Even then I'm not convinced it will work, since the definition of this location appears to be hard-coded into the 'manifest.fingerprint' file found at the stated location.....and the file is not to amenable to editing, since it isn't a text file.
All you can do is try. It doesn't appear to have worked for me; although 'chrome://flags' shows the path as being correct, apparently the browser is not seeing it. 'Couldn't load plug-in'. I haven't yet figured out a solution to this one.....but I'm working on it!
For most of you, though, these pets should just 'work' as usual.
Enjoy.
Mike.
Morning, kiddiwinks!
I have a treat for those of you running Chrome/Chromium/SlimJet on 32-bit Pups. Whether by accident or design (not sure which yet), Adobe have apparently re-commenced development of 32-bit Linux Pepper, and are, for the first time, making it publicly available for download.
This means you have a chance to at least update this trouble-prone item in your browser. There's two ways you can do this:-
1) For the more experienced among you, download 32-bit Pepper as a tar.gz file from the Adobe 'Player Download Center'.
https://get.adobe.com/flashplayer/
If you visit the page in your Chrome/Chromium-based browser, the site will auto-detect the type of download you need, based on your browser's user-agent string. Extract the 'libpepflashplayer.so' and 'manifest.json' files from the package, and manually move them into your PepperFlash folder (or relevant location, depending on the browser), following my instructions from here:-
http://www.murga-linux.com/puppy/viewtopic.php?t=101275
2) Or, for the less technically competent among you, I've produced a new series of PepperFlash .pets, to be found at the usual location:-
http://www.murga-linux.com/puppy/viewtopic.php?t=106409
Since none of us know how long this happy state of affairs might last for, "grab 'em while you can..!"
BTW:- It's come to my notice that these .pets may not work for the final three versions of 32-bit Chrome (46, 47, and 48 ). Google had begun to introduce a semi-working updater mechanism to the Linux version of Chrome, and, rather than the browser looking in /opt/google/chrome/PepperFlash for the player module, it was now looking in /root/.config/google-chrome/PepperFlash/[Pepper-version]. It would be a bit daft to make yet another series of .pets just for 3 browsers, so the above location is where you would need to manually move the relevant files to. Even then I'm not convinced it will work, since the definition of this location appears to be hard-coded into the 'manifest.fingerprint' file found at the stated location.....and the file is not to amenable to editing, since it isn't a text file.
All you can do is try. It doesn't appear to have worked for me; although 'chrome://flags' shows the path as being correct, apparently the browser is not seeing it. 'Couldn't load plug-in'. I haven't yet figured out a solution to this one.....but I'm working on it!
For most of you, though, these pets should just 'work' as usual.
Enjoy.
Mike.