Since versoin 34 included, chromium doesn't support anymore the netscape plugin API used by www-plugins/adobe-flash. As such, flash doesn't work anymore This can be checked with chrome://flash I confirm it used to work on my computer and it does not anymore. I'm on ~amd64. According to my google search, chrome/chromium >=32 now use the "pepper" api for plugin, and adobe does release a flash plugin with this API. It's probably bundled already in the binary "chrome". To fix this bug, i think the flash-provided plugin should be either automatically installed with www-client/chromium (probably not a good idea), or shipped in another ebuild/package.
just emerge chrome-binary-plugins and you will get pepper.
The real problem is java which you would think someone would at least mod icedtea for ppapi. Stuck running java apps in firefox.
gee, indeed, it was already there. I did search quite a lot though, it should probably be documented somewhere. thanks a lot harris ! Though it doesn't work here :-( But it's probably worth another ticket. >>> Failed to emerge www-plugins/chrome-binary-plugins-35.0.1916.99_beta1, Log file: >>> '/var/tmp/portage/www-plugins/chrome-binary-plugins-35.0.1916.99_beta1/temp/build.log' >>> Jobs: 0 of 1 complete, 1 failed Load avg: 1.24, 0.73, 0.91 --2014-05-16 00:13:01-- http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-beta/google-chrome-beta_35.0.1916.99-1_amd64.deb Resolving dl.google.com... 173.194.34.166, 173.194.34.160, 173.194.34.165, ... Connecting to dl.google.com|173.194.34.166|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2014-05-16 00:13:01 ERROR 404: Not Found. !!! Couldn't download 'google-chrome-beta_35.0.1916.99-1_amd64.deb'. Aborting.
*** Bug 516896 has been marked as a duplicate of this bug. ***
Wouldn't it be correct to utilize adobe-flash flag in Chromium ebuild pulling new plugins in this situation? The flag would at least imply that the new flash plugin is required.
(In reply to Igor Franchuk from comment #5) We are not doing that. Optional plugins do not go in RDEPEND.
(In reply to Igor Franchuk from comment #5) > Wouldn't it be correct to utilize adobe-flash flag in Chromium ebuild > pulling new plugins in this situation? The flag would at least imply that > the new flash plugin is required. It isn't distributed freely unless you count the Google Chrome browser as being distributedly freely, which it isn't.
