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

[peebee]

THIS VERSION WILL ONLY WORK ON "MODERN" PUPPIES - LxPup, LxTahrPup, Slacko6Beta2, TahrPup6

32bit:
chromium_41.0.2272.118+pepper_17.0.0.134_lx.sfs

64bit:
chromium64_with_pepperflash_41.0.2272.118.sfs

Caveats and constraints as detailed above

[peebee]

THIS VERSION WILL ONLY WORK ON "MODERN" PUPPIES - LxPup, LxTahrPup, Slacko6Beta2, TahrPup6

32bit:
chromium_41.0.2272.118+pepper_17.0.0.169_lx.sfs

64bit:
chromium64_with_pepperflash_41.0.2272.118.sfs

Caveats and constraints as detailed above

[peebee]

THIS VERSION WILL ONLY WORK ON "MODERN" PUPPIES - LxPup, LxTahrPup, Slacko6Beta2, TahrPup6
and then only on versions with kernels newer than 3.14

32bit:
chromium_42.0.2311.90+pepper_17.0.0.169_lx.sfs

64bit:
chromium64_with_pepperflash_42.0.2311.90.sfs

Caveats and constraints as detailed above

[starhawk]

peebee, I'm having a very odd problem with Chromium in Carolina Vanguard. See here for details --> http://murga-linux.com/puppy/viewtopic. ... 087#842087

If it's not too much trouble, could you rebuild Chromium for me, exactly the way it is in this thread EXCEPT with all the debugging stuff present? Specifically the binaries need to not be debug-stripped. My local guru guy says he can help me but not when the stack traces are all hex with no labels.

I specifically need 3 versions --

chromium_37.0.2062.120+pepper_15.0.0.152_lx.sfs
chromium_40.0.2214.111+pepper_16.0.0.305_lx.sfs
chromium_42.0.2311.90+pepper_17.0.0.169_lx.sfs

If I'm asking too much, tell me and I'll go away...

[peebee]

could you rebuild Chromium for me, exactly the way it is in this thread EXCEPT with all the debugging stuff present?

Hi starhawk

I'm afraid that I don't "build" Chromium - I just "repackage" the Slackware14.1 version produced by "alien".

I have noticed and noted above that in the move from 41 to 42 this version of Chromium will not run on "older" kernels - e.g. 3.4.94 is too old now, 3.14.20 seems OK - not sure where the exact cutoff for "old" occurs.

Sorry I can't help more.
Cheers
peebee

[starhawk]

Oh, OK, I didn't know.

Thanks for telling me, at least...

[peebee]

THIS VERSION WILL ONLY WORK ON "MODERN" PUPPIES - LxPup, LxTahrPup, Slacko6Beta2, TahrPup6
and then only on versions with kernels newer than 3.14 unless you apply the patch here which does affect sandboxing

32bit:
chromium_42.0.2311.135+pepper_17.0.0.169_lx.sfs

64bit:
chromium64_with_pepperflash_42.0.2311.135.sfs

Caveats and constraints as detailed above

[peebee]

Chromium 42 can be made to run on older kernels like the 3.4.94 kernel in Slacko6Beta (Slacko 5.9.3) by editing:

/usr/bin/chromium

to add:

Code: Select all

--disable-setuid-sandbox --disable-namespace-sandbox --disable-infobars

to the exec command so that it reads:

Code: Select all

exec /usr/lib/chromium/chromium --user-data-dir=$PWD/.config/chromium --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=17.0.0.169 --disk-cache-size=10000000 --media-cache-size=10000000 --allow-outdated-plugins --disable-setuid-sandbox --disable-namespace-sandbox --disable-infobars "$@"

Note however that in this mode sandboxing is completely switched off.

[peebee]

Download deleted 16-aug-15

[peebee]

THIS VERSION WILL ONLY WORK ON "MODERN" PUPPIES - LxPup, LxTahrPup, Slacko6Beta2, TahrPup6
and then only on versions with kernels newer than 3.14 unless you apply the patch here which does affect sandboxing

32bit:
chromium_43.0.2357.81 + pepper_17.0.0.188_lx.sfs

64bit:
chromium64_with_pepperflash_43.0.2357.65.sfs

Caveats and constraints as detailed above

Tested on LxPup-15.03 and LxPup64-15.03 to work with BBC iPlayer and YouTube.

The location of the PepperFlash plugin has changed slightly in this version.

[kost@s]

My tests show that both LxPup-15.05 and LxPupTahr-15.03 are not "modern" enough to run this version.....
Quote:
/usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.20' not found

hello my friend, try the
lib6+libstdc6-4.9.2.pet

[peebee]

Now version:

32bit: chromium_43.0.2357.81 + pepperflash_17.0.0.188

see above.

[kost@s]

yes, i mean for this http://murga-linux.com/puppy/viewtopic. ... 686#846686

My tests show that both LxPup-15.05 and LxPupTahr-15.03 are not "modern" enough to run this version.....
Quote:
/usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.20' not found

So we may be reaching the end of the Chromium versions that will run on LxPup and LxPupTahr

download lib6+libstdc6-4.9.2

[peebee]

THIS VERSION WILL ONLY WORK ON "MODERN" PUPPIES - LxPup, LxTahrPup, Slacko6Beta2, TahrPup6
and then only on versions with kernels newer than 3.14 unless you apply the patch here which does affect sandboxing

32bit:
chromium_43.0.2357.125 + pepper_18.0.0.160_lx.sfs

64bit:
chromium64_with_pepperflash_43.0.2357.125-18.0.0.160.sfs

Caveats and constraints as detailed above

[666philb]

My tests show that both LxPup-15.05 and LxPupTahr-15.03 are not "modern" enough to run this version.....
Quote:
/usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.20' not found

hello my friend, try the
lib6+libstdc6-4.9.2.pet

hi kost@s

can we have the .dev as well

cheers

[peebee]

THIS VERSION WILL ONLY WORK ON "MODERN" PUPPIES - LxPup, LxTahrPup, Slacko6Beta2, TahrPup6
and then only on versions with kernels newer than 3.14 unless you apply the patch here which does affect sandboxing

32bit:
chromium_43.0.2357.130 + pepper_18.0.0.194_lx.sfs

64bit:
chromium64_with_pepperflash_43.0.2357.130-18.0.0.194.sfs

Caveats and constraints as detailed above

[peebee]

THIS VERSION WILL ONLY WORK ON "MODERN" PUPPIES - LxPup, LxTahrPup, Slacko6Beta2, TahrPup6
and then only on versions with kernels newer than 3.14 unless you apply the patch here which does affect sandboxing

32bit:
chromium_43.0.2357.132 + pepper_18.0.0.204_lx.sfs

64bit:
chromium64_with_pepperflash_43.0.2357.132-18.0.0.204.sfs

Caveats and constraints as detailed above

[gcmartin]

Is there a utility which will keep Chromium current in PUPs?

[peebee]

Is there a utility which will keep Chromium current in PUPs?

Here's what I do....

I have a folder (chromium) in which I place the current .sfs and then I make a relative link #1 to the current version called chromium.sfs

Then in my frugal install folder I make another relative link #2 to the above link #1 - again called chromium.sfs

sfs-load-on-the-fly loads and installs the 2nd link with no problems and the load survives reboots.

So when a new version is available, just remake link #1 and reboot......easy peasy

The double link mechanism ensures that the personal save folder record always points to the current version and no unloading or reloading of sfs's is needed other than the reboot.

I suppose I could produce a small utility to automate the above scheme but that would mean standardising or locating the folder names (I think). Does a frugal install "know" the name of the folder it has been booted from??

[gcmartin]

Is there a utility which will keep Chromium current in PUPs?

... I suppose I could produce a small utility to automate the above scheme but that would mean standardising or locating the folder names (I think). Does a frugal install "know" the name of the folder it has been booted from??

Should you or anyone do so, bear in mind that the result is a pathway for making and keeping Chromium current. And, the resulting utility should reside in the Menu system somewhere. Just an idea.

This is the pathway currently used by Palemoon. Just for sake of some idea as a beginning.