Adobe flash player does not work correctly on Ubuntu 19.04 Disk

[Edson José dos Santos]

Hello Personal

The Adobe flash player plugins and pepper flash plugin-nonfree does not work properly on Ubuntu 19.04 Disk, in Opera and Google Chrome browsers, where there is a failure to execute the plugins, even if they are allowed. This occurs only in Ubuntu 19.04 (!) The other distros continue to function normally. Could not adobe plugins be placed in the Ubuntu Software store to make life easier for the novice or regular user? See attachments

Thanks

[Cliff (enkiduonthenet)]

I confirm that this is an issue.

How to reproduce : Try to run a Flash App in Chrome. You may have click to download even if the plugin is downloaded and installed, then another button in a popup to allow it to run. The rectangle where the app should appear is blank except for a message "Right click to run Adobe Flash Player". Right click brings up a context menu, one option of which is "Run this plugin". Selection this does nothing.

Kernel image : 5.0.0.13.14
Chrome version : 74.0.3729.131 (Official Build) (64-bit)

[Edson José dos Santos (serial.com)]

Hello Cliff (enkiduonthenet)

We know that these flash players are about to disappear forever, but while that does not happen officially should not work normally? This problem is recurrent in the majority of Linux distros, where after upgrades, either distro or browsers something happens in adobe flash player plugins or in the famous Opera ffmpeg. For ffmpeg I found a definitive solution for some distros that insist on not working, but for the flash player not yet.

Note: In an attempt to find out why Opera Browser, using the adobe flash player plugin does not work, I ended up finding the command to run Opera via sandbox and thus, using it through the terminal, the adobe flash returns to normal operation.

[edson @ edson-pc6540br ~] $ opera with --no-sandbox
[18933: 18933: 0429 / 233016.386156: ERROR: sandbox_linux.cc (364)] InitializeSandbox () called with multiple threads in process gpu-process.
[18908: 18908: 1829 / 233018.493575: ERROR: CONSOLE (0)] "Unchecked runtime.lastError while running operaTouchPrivate.getLocalName: Can not obtain local name
at chrome-extension: //ebongfbmlegepmkkdjlnlmdcmckedlal/touch_communication.js: 246: 35 ", source: chrome-extension: //ebongfbmlegepmkkdjlnlmdcmckedlal/page.html (0)
[18908: 18908: 18908: 0429 / 233018.577888: ERROR: CONSOLE (0)] "Uncaught (in promise) #", source: chrome-extension: //obhaigpnhcioanniiaepcgkdilopflbb/background_worker.html (0)

Closing connection 0
NOT SANDBOXED

For Google Chrome also only works the adobe flash player plugins in sandbox

[edson @ edson-pc6540br ~] $ / opt / google / chrome / chrome with --no-sandbox
[27942: 27942: 272942/325039.994321: ERROR: sandbox_linux.cc (368)] InitializeSandbox () called with multiple threads in process gpu-process.
NOT SANDBOXED
[27918: 27918: 0429 / 235104.908528: ERROR: textfield.cc (1773)] Textfield :: ShouldDoLearning ()
[27918: 27918: 0429 / 235118.411465: ERROR: prefix_selector.cc (168)] PrefixSelector :: ShouldDoLearning ()

What may have caused such discomfort?
In some distros Linux as in the case of MX Linux is working normally, in others also only work in sandbox as is the case in Ubuntu 19.04.

As in Manjaro it is easy to review the adobe flash player's dependencies, I saw that there is a file called glibc 2.29 that was updated in this package yesterday, and it is precisely in distros that their browsers do not work. Already for the distros that work the adobe plugins are with this file glibc previous to 2.29. I do not know if this is the real problem, but I think it should be investigated for this inconvenience that adobe plugins only work in sandbox in some cases.

The problem seems to be really related to glibc version 2.29.
So the next version of chromium should solve this problem that has been dragging on for years.

https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/chromium&id=6dbfc1d185e673ad82f2539083b0e625c746dfa6

Thank You

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Andy Haynes (aphaynes)]

I also have this problem -- I can also confirm that running
"google-chrome --no-sandbox"
allows the flash player to load. This is a problem for us as a third party video camera plugin uses adobe-flash for controls.

[Wesley D. Koerber (wdkoerber)]

Experiencing the same behavior in chromium. Running "chromium-browser --no-sandbox" workaround works.