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

[gcmartin]

@Peebee and other users may already know about this PET for upgrade. Might it also be applicable to this Chromium PET offering for system's upgrade? Should upgraders be packaged with the browsers?

Hope this is helpful info.

[starhawk]

Please don't. I've always had problems with auto-updates... Firefox is an example... I always turn off the auto update as the first thing I do, because if it updates, it often breaks and won't run anymore. That's very user-unfriendly

[gcmartin]

There are differing types of updaters used by browsers like Palemoon, FF, SM, Opera, IE, etc. There is no "standard" method.

[starhawk]

gc, I hate to point it out, but your apparent reply to my post... doesn't actually address anything I said!

[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.134 + pepper_18.0.0.209_lx.sfs (temporary url - sourceforge is down for uploading)

64bit:
chromium64_with_pepperflash_43.0.2357.134-18.0.0.209.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_44.0.2403.107+pepper_18.0.0.209_lx.sfs

64bit:
chromium64_with_pepperflash_44.0.2403.107-18.0.0.209.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_44.0.2403.157+pepper_18.0.0.233_lx.sfs

64bit:
chromium64_with_pepperflash_44.0.2403.157-18.0.0.233.sfs

Caveats and constraints as detailed above

[peebee]

EXPERIMENTAL - TAKE CARE WHEN RUNNING!!

Here is a Development version of 32-bit Chromium-46.0.2478.0 with PepperFlash-19.0.0.128 to test...... chromium32dev_with_pepperflash_46.0.2478.0-19.0.0.128.sfs

My tests show that both LxPup-15.06 and LxPupTahr-15.05 are not "modern" enough to run this version.....(even with the update pets suggested by kost@s)

It does however run OK OOTB on LxPupVivid-15.05 - both BBC-iPlayer and YouTube checked.

Cheers
peebee

[peebee]

chromium_44.0.2403.157 + pepperflash_18.0.0.233

is now available - see 2 posts up

[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_45.0.2454.93+pepper_19.0.0.185_lx.sfs

64bit:
chromium64_with_pepperflash_45.0.2454.93-18.0.0.233.sfs

Caveats and constraints as detailed above

[starhawk]

Running 32b ver in X-Tahr 1b2 on my Dell E4310. Runs like a charm...

...for the record I'd not have upgraded except I did something very stupid last night because I was half asleep, and my desktop is presently being operated on as a result...

[step]

This isn't about Chromium but just about updating pepperflash. I found this method to work for Fatdog64 - I see no reason it shouldn't work for all Puppies:

Code: Select all

mkdir -p /usr/lib64/chromium-browser/PepperFlash &&
env PPAPI_FLASH_INSTALL_DIR=/usr/lib64/chromium-browser/PepperFlash /usr/bin/latest-pepper-flash.sh

Link to /usr/lib/latest-pepper-flash.sh

I chose the path of $PPAPI_FLASH_INSTALL_DIR from a list taken in this Opera browser-specific post.

You need to adapt the path for what your browser expects.

[Payoon]

Hi peebee
Thanks for that!
Payoon

[peebee]

32 bit chromium_45.0.2454.93 + pepperflash_19.0.0.185 is available

64 bit chromium_45.0.2454.93 + pepperflash_18.0.0.233 is available

- see post above.

[caiosama]

Thank you Peebee!

[peebee]

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

32bit:
chromium_45.0.2454.101+pepper_19.0.0.185_lx.sfs

64bit:
chromium64_45.0.2454.101+pepper_19.0.0.185_lx.sfs

Caveats and constraints as detailed above

[Marv]

Running chromium_45.0.2454.101+pepperflash_19.0.0.185 sucessfully in both X-tahr 1b3 non-PAE and X-slacko 3.1n on 2.4GHz core 2 duo laptops and on 1.2GHz Pentium M laptops. It is acceptably quick even on the Pentium Ms. The only change I made was to move the chromium (profile) folder from /root/.config to an EXT2 partition and symlink it. Do that partly to get it out of pupsave and also to share bookmarks and setup across pups.

Thanks

[Marv]

One of my beefs with chromium (and the chrome derivs slimjet and opera32) has been the VERY thin font rendering using the standard DejaVu fonts. I downloaded and installed opensans from fontsquirrel: http://www.fontsquirrel.com/fonts/open-sans and set chromium to use opensans for both sans and serif (monospace left unchanged) and IMO the font rendering is much improved. Just to see, I'm also using opensans regular as the system font in X-slacko 31n and so far like it there too. I also like that it has a semibold available.

Yes fonts are subjective but a lot of people have complained about the skinnies in chrome/chromium. Give it a try if you are one.

[gcmartin]

Moved to this forum thread.

[peebee]

It is my intention to continue to only produce sfs of chromium.

However I recognize that some people may want pet versions.

It is easy to convert an sfs to a pet - and if somebody wants to do so and upload it to a repository then send me a pm with the link then I'll be happy to publish the link here.

There is also a need for some 64bit pups (e.g. tahrpup64) to convert the sfs to use /usr/lib instead of /usr/lib64

The attached pet provides both the above conversions.

The README says:

Copy the sfs you want to convert into the folder /opt/convert_sfs

Open a terminal in the folder /opt/convert_sfs

Run the convert program with: ./convert_sfs.sh

Type 1 to convert the sfs to a pet
Type 2 to convert the sfs from using /usr/lib64 to /usr/lib

The convert program should only be run in a Linux filesystem