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.
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 te.getLocalName : Can not obtain local name mkkdjlnlmdcmcke dlal/touch_ communication. js: 246: 35 ", source: chrome-extension: //ebongfbmlegep mkkdjlnlmdcmcke dlal/page. html (0) nniiaepcgkdilop flbb/background _worker. html (0)
[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 operaTouchPriva
at chrome-extension: //ebongfbmlegep
[18908: 18908: 18908: 0429 / 233018.577888: ERROR: CONSOLE (0)] "Uncaught (in promise) #", source: chrome-extension: //obhaigpnhcioa
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 325039. 994321: ERROR: sandbox_linux.cc (368)] InitializeSandbox () called with multiple threads in process gpu-process.
[27942: 27942: 272942/
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=6dbfc1d185e6 73ad82f2539083b 0e625c746dfa6
Thank You