Chromium v83 with pepper-flash **RUNS-AS-SPOT**

[edoc]

64-bit "OpenMandriva" build:

chromium64_53.0.2785.116+pepper_23.0.0.162.sfs

Tested on slacko64_6.9.6.1

and after being converted on xenialpup64-7.0.7

Cool!

I wonder when Kernel 4.8rc will be used as it opens up the possibility of use on tablets such as the Chuwi Hi12.

Thanks!

[peebee]

UPDATED 09-nov-2016

***Please delete file /usr/lib/chromium-browser-stable/chromium-run1 before running this new version***

chromium_54.0.2840.59+pepper_23.0.0.207.sfs

chromium64_54.0.2840.59+pepper_23.0.0.207.sfs

This version of chromium comes from the OpenMandriva project

Works on "2016" era pups such as:
xenialpup-7.0.4 and derivatives (LxPupXenial-16.08.2)
slacko-6.9.6.4
LxPupSc-16.10.1

slacko64-6.9.6.4
LxPup64-16.10.1

It sadly doesn't work on:
slacko-6.3.2 and derivatives (LxPup-s-16.07.1 and X-Slacko-4.2)

[peebee]

Updated to pepperflash 23.0.0.207 - Adobe Security Bulletin

[Illutorium]

UPDATED 11-oct-16

chromium_53.0.2785.116+pepper_23.0.0.185.sfs

This version of chromium comes from the OpenMandriva project

It appears to work on:
tahrpup-6.0.5 and derivatives (LxPupTahr-15.12.1 and X-Tahr-2.0)

It also works on "2016" era pups such as:
xenialpup-7.0.4 and derivatives (LxPupXenial-16.08.2)
slacko-6.9.6.1
LxPupSc-16.09.3

It sadly doesn't work on:
slacko-6.3.2 and derivatives (LxPup-s-16.07.1 and X-Slacko-4.2)
LxPupPrecise-15.09.1

It's also a bit smaller (10MB) than the AlienBob Slackware builds.

Please test and report any issues.

64-bit version in later post

So yet that's are be worked on My Tahr build (Tahr Lite 6.1 with Willy X.org Port),But if be will more modulated that's will be pack at .SFS with:

1. libnspr4 [/usr/lib]
2. libnss3 [/usr/lib]
3. libnss3-nssdb [/etc and /var]

but Chromium 54 doesn't be works on Tahr because that's depends at Xenial libraries as libpng16 anyway'

[peebee]

UPDATED 19-nov-16

Based on AlienBob builds:

For 32 bit slackware-14.2 and xenial pups only:
chromium_54.0.2840.100+pepper_23.0.0.207_lx.sfs

For 64 bit slackware-14.2 pups only:
chromium64_54.0.2840.100+pepper_23.0.0.207_lx.sfs

Widevine plugin for 64-bits

[peebee]

Updated 10-jan-2017

***Please delete file /usr/lib/chromium-browser-stable/chromium-run1 before running this new version***

chromium_55.0.2883.75+pepper_24.0.0.194.sfs

chromium64_55.0.2883.75+pepper_24.0.0.194.sfs

This version of chromium comes from the OpenMandriva project

Works on "2016" era pups such as:
xenialpup-7.0.4 and derivatives (LxPupXenial-16.08.2)
slacko-6.9.6.4
LxPupSc-16.12.2

slacko64-6.9.6.4
LxPup64-16.10.1

It sadly doesn't work on:
slacko-6.3.2 and derivatives (LxPup-s-16.07.1 and X-Slacko-4.2)

[Mike Walsh]

Glad to see you finally got the bugs ironed out, mate!

Think I'll stick with Chrome, though. That older glibc requirement is a definite bonus, at the moment...

No doubt I'll find this same problem cropping up at some point in the not too distant future. (*groan*)

But we're not there.....yet. If we do, I'll just revert back to Chrome 53.....the last one that had the path coded for the separate PepperFlash folder. We shall see...after all, I'm running Chrome 26 in Lucid..!

An out-of-date browser in an out of date OS!


Mike.

[peebee]

Now PepperFlash-24.0.0.186

[peebee]

AlienBob builds....bigger but no GTK3.....

chromium_55.0.2883.75+pepper_24.0.0.186_lx

chromium64_55.0.2883.75+pepper_24.0.0.186_lx

[peebee]

Updated to pepperflash-24.0.0.194

[peebee]

chromium_56.0.2924.76+pepper_24.0.0.194_lx.sfs

32-bit only so far....based on AlienBob's slackware build

IMPORTANT CHANGE - with version 56 chromium will only run as a "normal" user (i.e. not as root) - therefore this version is "run-as-spot"

If /usr/sbin/run-as-spot is not available then it will run with all sandboxing disabled.

Config files and downloads are stored in /root/spot - therefore it will not use previous configs - it might be possible to copy them over but this has not been tested.

So - use with caution!!!

[peebee]

Slightly changed version re-uploaded - now changes the ownership to root:root of anything in /root/spot/Downloads on closure of chromium

[Mike Walsh]

Hi, peebee.

Check your 'Inbox'.....and let me know what you think. Perhaps we can work out a common refined 'fix' between us?


Mike.

[peebee]

Re-uploaded 14-feb-2017

***Please delete file /usr/lib/chromium-browser-stable/chromium-run1 before running this new version***

chromium_56.0.2924.87+pepper_24.0.0.221.sfs

chromium64_56.0.2924.87+pepper_24.0.0.221.sfs

This version of chromium comes from the OpenMandriva project

Should work on "2016/17" era pups such as:
slacko-6.9.6.4
LxPupSc-17.02.1 (tested)

LxPupXenial-16.08.2 needs libharfbuzz update pet - attached

slacko64-6.9.6.4
LxPup64-16.10.1 (tested)

It sadly won't work on:
slacko-6.3.2 and derivatives (LxPup-s-16.07.1 and X-Slacko-4.2)

[01micko]

@Mike and peebee.

If running as root is necessary then Iguleder's trick still works. See http://murga-linux.com/puppy/viewtopic.php?t=72667.

I also tried this on the CLI

Code: Select all

# LD_PRELOAD="/usr/lib64/libpuppygc.so" /usr/bin/google-chrome-stable
[22132:22156:0205/213818.957618:ERROR:bus.cc(427)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken

I'm not fussed by the error.. chrome/chromium is noisy.. I'm posting from it now (google-chrome 56.0.2924.87 (64-bit)) downloaded with Ruari's gist.

The LD_PRELOAD routine *should* be able to be sed'd into the Exec= line of the desktop entry thus most menu systems can then pick it up. I didn't test that but did briefly hack my ~/.jwmrc with that line.

Cheers!

[Mike Walsh]

Hi, Micko.

Thanks for the heads-up. I like the look of iguleder's script, I must say. Very neat.....and simple. As all the best ideas usually are.

peebee will probably be able to incorporate some of that into the Chromium launcher script. Chrome, being a wee bit more proprietary, employs a very different 'wrapper-script' to start things.....but anything's possible.

I'm not fussed by the error.. chrome/chromium is noisy.. I'm posting from it now (google-chrome 56.0.2924.87 (64-bit)) downloaded with Ruari's gist.

Tell me about it. I've never seen owt quite like the Chromium-based browsers for generating crap in the terminal. For all that, they still run...

-----------------------------------------------------------------------------------------

I'll have a look at iguleder's script when I get in later on. It might be just as easy to incorporate that into my Chrome builds, and let it run through before it actually starts; d'you suppose he would mind my 'borrowing' it?

Perhaps start the exec-line with that, stick a 'sleep 3 (or 5)' statement in, then let the normal google-chrome exec statement run.

Something like:-

Code: Select all

/usr/bin/puppy-chrome
sleep 5
exec -a "$0" /opt/google/chrome/chrome --user-data-dir=/root/.config/google-chrome --disable-infobars "$@"

What d'you think? Sound feasible? Or am I approaching this from the wrong angle? (Remember, I'm still feeling my way with all this scripting stuff...)

I'll have a look at that download script, too, when I get the time.

Cheers.


Mike.

[peebee]

18-feb-2017 - changed

With thanks to @666philb - run as root fix changed to bbe binary edit

previously - With many thanks to @Micko and @Iguleder for ld_preload fix.....

56.0.2924.87 sfs's - both 32 and 64 bit - are reuploaded and now are happy to run as root due to binary edit above

[peebee]

PepperFlash has been updated to 24.0.0.221

[DAC324]

Re-uploaded 14-feb-2017

***Please delete file /usr/lib/chromium-browser-stable/chromium-run1 before running this new version***

chromium_56.0.2924.87+pepper_24.0.0.221.sfs

Does not work on TahrPup, either:

/usr/lib/chromium-browser-stable/chrome: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory

[simes]

Hello peebee,
Sorry to report, I've installed the linked Chromium 56 on lxpup xenial 16.08 and I'm getting the 'Aw, snap!' message on every page in Chromium, even the Chromium settings page. I've used Puppy for years but even so, I wonder whether I've missed something basic... All suggestions welcome.

Thanks,
Simon.