Mageia forum

Hi,
I have a machine running Mageia 3, and the auto-updates today gave an update of Chromium v34.xxx to chromium-browser-stable-37.0.2062.120-1.mga3.
I tried loading a site that uses flash and it gave a message about needing to install flash. I have flash-plugin-11.2.202.406-release installed (the last release).

From what I read Chromium stopped supporting flashplayer at v34.x, and should now use something called pepperflash-plugin (libpepflashplayer.so), yet don't find this.
Setting the URL to chrome://plugins/ doesn't show much at all now with v37.

Any ideas where I look for this pepperflash plugin? If sending an auto-update to v37 of Chromium I'd expect there to be the ability to still use flash somehow.

Thanks in advance

The advisory for the update explains this: http://advisories.mageia.org/MGASA-2014-0413.html
See the link to the MAQeia on how to install chrome: viewtopic.php?t=2053

Pretty clever of Google. Kill a key feature of the open-source variant of the package that does not have all the call-the-google-mothership stuff in it in order to push everyone into the variant that does routinely call the mothership and give you away (even if it is claimed to be "anonymous").

Of course, Google promises us that you can disable the spyware code. And if you believe that, I would like to offer you a good price on a bridge I am selling. The best way to know the "feature" is disabled is for the feature to not be present to begin with.

Thx doktor500, much appreciated.

Back to Firefox it is.

So what is the status of pepperflash-plugin?

I just installed Chrome and then copied libpepflashplayer.so and manifest.json to the /usr/lib64/chromium-browser/ and to the /usr/lib64/chromium-browser/plugins
don't actually know which of them are wrking but there's flash in my Chromium

daniewicz wrote:So what is the status of pepperflash-plugin?

It's an alternate version of flashplayer maintained by Google, and it's shipped with chrome.

On the latest version of chromium "about:plugins" does not show any flashplayer.
It just shows this:

Code: Select all


Plug-ins (1)      
Details
Chromoting Viewer
This plugin allows you to securely access other computers that have been shared with you. To use this plugin you must first install the Chrome Remote Desktop webapp.
Name:   Chromoting Viewer
Description:   This plugin allows you to securely access other computers that have been shared with you. To use this plugin you must first install the Chrome Remote Desktop webapp.
Version:   
Location:   internal-remoting-viewer
Type:   PPAPI (out-of-process)
    Disable
MIME types:   
MIME type   Description   File extensions
application/vnd.chromium.remoting-viewer      
.
Disable   Always allowed?


chromium-browser no longer supports plugins:
http://advisories.mageia.org/MGASA-2014-0413.html

To install chrome see the MAQeia:
viewtopic.php?f=36&t=2053

Jim

Was asked recently, and I've made it a sticky thread in this subforum: viewtopic.php?f=7&t=8568
Does anybody actually use the search function or look before posting new threads about existing issues? -.-
Sometimes I really wonder why we write down these things ...

Has even been added in MAQeia linked above:

Chromium 35 and issues with plugins
Since version 35, chromium doesn't support browser plugins anymore. See http://advisories.mageia.org/MGASA-2014-0413.html
and the thread viewtopic.php?f=7&t=8568 for more information.
See http://blog.chromium.org/2013/09/saying ... npapi.html or http://blog.chromium.org/2014/05/update ... ation.html for more information on why and when the support for NPAPI browser plugins has been dropped.

It's still possible to get at least flash working, by using pepperflash plugin from chrome.
See the above linked forum post for the pepperflash plugin, and the following instructions on how to install chrome to obtain the plugin.

Thankyou Jim and Doktor5000.
I have installed the Chrome browser and it all seems to be working.

Hi,
I had an update for google chrome today and it said it had a bad key.
I did this:

Code: Select all

rpm --import https://dl-ssl.google.com/linux/linux_signing_key.pub


This part is different:

Code: Select all

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.2.2 (GNU/Linux)


On my system.

Code: Select all

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: rpm-4.11.1 (NSS-3)


Does this make any difference?
Is there any way I can test it out?

I think I may have fixed it.

Code: Select all

rpm --checksig -v google-chrome-stable_current_x86_64.rpm
google-chrome-stable_current_x86_64.rpm:
    Header V4 DSA/SHA1 Signature, key ID 7fac5991: OK
    Header SHA1 digest: OK (87056256c26ea10f380665de6323388567ed89cd)
    MD5 digest: OK (e99f652e6d9978bc30e167fdae69366c)
    V4 DSA/SHA1 Signature, key ID 7fac5991: OK


nigelc wrote:Does this make any difference?
Is there any way I can test it out?

I think I may have fixed it.

What now? Do you ask how to test it, or did you change your mind in the middle of the post and it's already fixed?

I should have made 2 separate posts as this was some time later.

So do you still have an issue or is it fixed now?

I think it's fixed.

You can use this script if you want the latest pepper-flash plugin but would prefer not install Chrome.

Thanks for the script ruario
I'm not certain if this is required, but I made these changes on line 102 to adapt it for Mageia, as explained below

Code: Select all

# adapt for Mageia
#elif [ -r /etc/os-release ] && grep -qx 'ID=\(ubuntu\|linuxmint\)' /etc/os-release; then
elif [ -r /etc/release ] && grep -qx 'ID=\(Mageia\)' /etc/release; then

1. Mageia has a 'release' file in /etc, not 'os-release'
2. Obviously, the name in the file is 'Mageia', not 'ubuntu', or 'linuxmint' as in your original

The script can be run as an ordinary user, and it will prompt you for the root password when copying files into directories where root permissions are required

At the time of writing, the version of Google Chrome downloaded was at 39.0.2171.95, whereas Chromium in Mageia 4 is at 39.0.2171.65, so I also renamed /opt/google/chrome/PepperFlash/chrome-version-39.0.2171.95 as root. I'm not certain this is required, but its an empty file, and it seems logical to synchronise version numbers.

Code: Select all

mv chrome-version-39.0.2171.95 chrome-version-39.0.2171.65

Restart Chromium, type

Code: Select all

chrome://plugins

in the location bar to check the plugin is registered OK (the Mageia chromium-wrapper script neatly points chromium at the folder that the script installs the pepperflash plugin into ). Checking at https://www.adobe.com/software/flash/about/, it all worked , it said I had the latest version and other flash-based websites ( ) like http://www.eilidhbarbour.com/ (personal website for independent TV Sports presenter) also work now.

The script worked for me without modifications.

I also used it with OpenSUSE 13.1. In OpenSUSE 13.1, after running the script, go to the directory /usr/lib64/chromium and enter the command:

Code: Select all

ln -s /opt/google/chrome/PepperFlash PepperFlash


and it will work.

FWIW, the script worked fine without modifications. Together with freshplayerplugin package this allows firefox to use current pepperflash plugin

As I look at the apps for M5RC I notice that there is no Shockwave/Flash Plug-in for the provided Chromium Browser. Am I missing something here or has it always been that way? Is there a way to install it? Thanks

That feature has been removed more then 6 months ago. Check viewtopic.php?f=41&t=8568 for details and workaround (use chrome).

doktor5000 wrote:That feature has been removed more then 6 months ago. Check viewtopic.php?f=41&t=8568 for details and workaround (use chrome).

Thanks dok.

If you wilcal install chrome from google chromium will auto pick pepper flash and use it.

ruario

Thank you! I have been beating my head against this issue all afternoon. I have uninstalled and reinstalled flash players to no end. Your script downloaded and installed the pepperflash plugin in with no modification. I really wish Mageia could get on top of this and "userfy" it. I understand there is a popular movement to kill flash for something (anything) better, but just getting flash to play in a web browser shouldn't take six hours and a friend in a forum.

But that's what it was and I'm grateful that it works.

I salute you sir.


Mark