Although there are a couple of threads about widevine and opera, make sure you have installed opera-ffmpeg-codecs. It is a package from the arch repos, so it should exist in manjaro as well. Once you are done with that and have the precious h264 support, continue reading on opera's paths for widevine.
Plus, if you are on ubuntu 19.10 or newer, on which chromium and its derivative packages come only as snaps, please read this first
I was having major 'problems' getting WideVine to function at all under Opera 66 & 67; the method we'd previously used to set absolute paths for the Puppy 'portable' packages via the use of the 'tee' command was no longer working. And then it struck me.....the answer was so simple I could have kicked myself.
Bearing in mind that Puppy's 'run-as-root' model has been causing us grief for the last four years with the Chromium/'Blink'-based browsers, we run these packages as user 'spot'.....this being a restricted user with the same type of permissions as any normal user in the mainstream distros. Consequently, the whole of a Chromium-based browser's files live in the /root/spot directory.
For the 'portables', we use the 'readlink' command to set the location variable for the portable's directory, irrespective of its actual location. This allows us to create the browser's profile within that directory, and this all works very well.
However, regardless of Pup's slightly odd set-up, Opera is still looking in the locations it expects to find Widevine and libffmpeg in, as dictated by the internal coding and the .json files in /opera/resources. Bummer..!
But the answer, as I said, was very simple.
Puppy, as part of its 'frugal' install/run method, empolys what are known as SFS files (Squash File-System). These things can be loaded/unloaded 'on-the-fly' by the use of a special script which has been part of the standard Puppy build-process for well over a decade.
The simple solution was to build a wee SFS package which would 'load' libffmpeg and libwidevinecdm to the same locations as the .deb package installs them to.....and since these things CAN be 'loaded/unloaded' on-the-fly, and moved from one place to another, they are also portable.
So you put the portable-Opera in its desired location. You 'load' the Opera-extras.sfs package. You fire the browser up, go to NetFlix/Spotify/Hulu/Amazon Prime/whatever, annnd.....
.....everything just 'works'. Issue solved, and the 'portable' package remains 'portable', even if it IS now ever so slightly 'clunky' in nature.
I assume that the "software manager" is just the snap store app which mentions opera as not installed, because it was not installed as a snap but from the deb file...
So ignore it. If you want to check that opera is installed, use a proper app like synaptic or dpkg like so
$ dpkg -l | grep opera
ii opera-stable 67.0.3575.53 amd64 Fast, secure, easy-to-use web browser
Now that I have a ton of time to spare due to the virus quarantine, I made some tests to prove my point. And because I did not want to ruin my opera installation, I installed opera beta, on v68 today, and did all the testing there.
So, 10 days after my original question, here is some proof that the libffmpeg from other electron based project works too. The libffmpeg in question comes from skypeforlinux. I just downloaded the deb file, extracted libffmpeg from it and moved it to opera's folder. It's the same procedure that the thread and the "wiki" on reddit describes, but with libffmpeg coming a different source.
Without it, the usual poor, codec support, with most notable the lack of h264 decoding
And with it, that... precious h264 support is now available and all sites work as they should.
So the questoin remains. Why should someone prefer that libffmpeg from the github repo and not from some other electron app?
In my eyes, both give the user an equal amount of risk to break their system or the browser.
@idontknowaname476 I think its for security as has been said before and its probably a good idea dude - sometimes we have to sacrifice useability for those users who are not as expert in IT as we are - ie 90% of the numpty popuiation.
But look on the bright side maybe after the coronavirus takes out all the potato stupid people all the intelligent folks will be left and we can get what we need lol
@leocg Deleting my ~/.config/opera folder did not get rid of the blank Settings page. I have switched to Opera developer and got rid of Opera-stable via "apt purge --autoremove opera-stable". If I'm inclined to try Opera stable again I'll download it. Fresh start.
If it is a drm-only issue, check one of the dozens of threads about widevine. And also check the thread on my signature and this one, just in case it is also a "poor codec support" issue as well.
Use a descriptive and relevant title for new threads. Try to use at least three words in the thread title.
Be clear and concise when describing the problem. Be specific and remember to include important details, such as the exact error message or address of the site you're having trouble with.