Best posts made by miqwalsh

@zekemx said in Widevine and Opera:

In conclusion.. Opera doesn't work with widevine anymore (As of today), I hope the Opera Developers would explain why, but probably they don't care about linux users anymore.

@ zekemx:- That's it in a nutshell. I read somewhere, not many days ago, that Opera has been bought out by one of the 'big boys'. Expect many more annoying changes like this over the next few releases; these people have made it crystal-clear that they are only going to support Windows exclusively.....because that's where the money is.

Everybody else can go whistle. So; it looks like I, too, will be returning to Chrome again.

Bloody annoying.....but at least Big Brother doesn't give you quite this many hoops to jump through for an overall 'experience'. And everything does work, with relatively little 'pain'.

Mike.

Hi, all.

I daresay this has probably been asked before, but what would be the likelihood of getting Opera GX ported across to Linux? Valve are working wonders with Steam for Linux these days (amongst other things), and increasing numbers of AAA titles are running better than ever under WINE, so it's not like Linux is the poor relation that it used to be anymore.

Opera has been my favourite amongst the Chromium-based browsers for a while now. It would be great to not see GX restricted only to MyCrudSoft & Crapple.....

I think a Lot of Linux users would like to see this happen.

Mike.

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.

Sorted!

Mike.