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

Browsers, email, chat, etc.
Message
Author
User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

chromium_44.0.2403.107 with pepperflash_18.0.0.209

#166 Post by 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
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

chromium_44.0.2403.157 with pepperflash_18.0.0.233

#167 Post by 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
Last edited by peebee on Fri 04 Sep 2015, 08:21, edited 3 times in total.
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

EXPERIMENTAL - for LxPupVivid-15.05 only

#168 Post by 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
Attachments
capture26269.png
(148.78 KiB) Downloaded 4904 times
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

chromium_44.0.2403.157 + pepperflash_18.0.0.233

#169 Post by peebee »

chromium_44.0.2403.157 + pepperflash_18.0.0.233

is now available - see 2 posts up
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

chromium_45.0.2454.93 + pepperflash_19.0.0.185

#170 Post by 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
Last edited by peebee on Sat 26 Sep 2015, 17:37, edited 3 times in total.
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

starhawk
Posts: 4906
Joined: Mon 22 Nov 2010, 06:04
Location: Everybody knows this is nowhere...

#171 Post by 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
Posts: 1349
Joined: Fri 04 May 2012, 11:20

latest-pepper-flash.sh

#172 Post by 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.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]

Payoon
Posts: 32
Joined: Wed 26 May 2010, 15:40
Location: Duisburg, Germany on the banks of the Rhine

#173 Post by Payoon »

Hi peebee
Thanks for that!
Payoon :D

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

chromium_45.0.2454.93 + pepperflash_19.0.0.185

#174 Post by 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.
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
caiosama
Posts: 104
Joined: Fri 02 Jan 2015, 14:54
Location: Concepcion, Chile

#175 Post by caiosama »

Thank you Peebee!
[i]Pupjibaro 1.0.4 2015 / LxpupTahr 15.05.2 - Live USB - Dell D630
Precise 5.7.1 - Full installation - Asus EeePC 701 4G (2 GB RAM)
Carolina Vanguard Frugal /Arch Linux Antergos - Lenovo G4070[/i]

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

chromium_45.0.2454.101+pepperflash_19.0.0.185

#176 Post by 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
Last edited by peebee on Thu 15 Oct 2015, 17:14, edited 2 times in total.
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
Marv
Posts: 1264
Joined: Wed 04 May 2005, 13:47
Location: SW Wisconsin

#177 Post by 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
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.

User avatar
Marv
Posts: 1264
Joined: Wed 04 May 2005, 13:47
Location: SW Wisconsin

fonts in chromium

#178 Post by 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.
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.


User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

sfs - convert into pet and for tahrpup64

#180 Post by 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
Attachments
chromium_convert_sfs-1.pet
(1.14 KiB) Downloaded 1119 times
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

gcmartin

#181 Post by gcmartin »

This is a good provision as it can be useful with @BarryK's recent distros where they support PETs, but, not SFSs due to the distro design.

GR8!

gcmartin

Tested the SFS conversion to PET and install to TahrPUP

#182 Post by gcmartin »

Here is a record of testing of the CURRENT version of SFS conversion to an installable PET and installing that PET to TahrPUP64-6038.

I used both options and have discovered couple of not so obvious items in script use. One is already reported to @Peebee and he is aware; "multiple SFSs cannot reside in the folder with the current script's design". The other is a delay that occurs when the script is building the actual PET for use. Important to note that those are not errors; rather operational awareness required for the script's current use.
  • 1. Downloaded and installed, both, the current Chromium SFS and the "convert_SFS" script.
    2. Install the PET to create the folder contents to be used for making a PET; namely /opt/convert_sfs was created.
    3. Copyied the sfs you want to convert into the folder /opt/convert_sfs
    4. Opened a terminal in the folder /opt/convert_sfs by right-click>Windows>Terminal Here
    5. Started the convert program with: ./convert_sfs.sh

    6. Select either of the following
    • Type 1 to convert the sfs to a pet
      Type 2 to convert the sfs from using /usr/lib64 to /usr/lib
      • Typing "1", I took defaults by simply hitting "Enter". This took me to the GUI screen Package Manager entry. Not changing anything I hit the "Generate ..." button.
        Image
        Next, an editor opened to display the entry to be added to PPM's tables. I quit that screen and the convert_sfs script then proceeded to create the PET for Chromium installation.

        Beware: Excepting for the message "Creating package..." there is no other indicator of the script progressing until it completes minutes (maybe many minutes, for some) later. Be patient!!!

        All finally exited with a PET residing in the folder /opt/convert_sfs.
    7. Chromium was installed by clicking the PET file in /opt/convert_sfs.
    8. Typed chromium on the console to start the browser (Menu>Internet works as well)
The log path below,using only the script Option 1, was taken, as, there is no need to "fix" the lib64 in TahrPUP64.

Code: Select all

Welcome to the 'dir2pet' script.
This will convert a directory into a PET package. Example, you have a 
directory named 'abiword-0.5.6' and inside that you place whatever is
needed for the package, for example usr/local/bin/abiword (the executable)
and usr/share/applications/abiword.desktop (the XDG menu file).
Whatever the packages needs, though don't worry if there is no .desktop
file as this script will ask some simple questions and optionally create
one. The package only needs a .desktop file if a menu entry is to be
created, and also an icon is required for the menu.

The directory chromium64_45.0.2454.101+pepper_19.0.0.185_lx must separate name of the package and
version number with a dash. Ex: abiword-0.5.6

The package may optionally have post-install and post-remove scripts,
named 'pinstall.sh' and 'puninstall.sh' placed at the top directory.
(to create official PETs for the Unleashed suite, see its README file
 for more information how to create these scripts properly)

If any of the above needs to be further sorted out, you can quit this
script right now by pressing CTRL-C, otherwise just press ENTER
to use the default "xz" compression or "g" then ENTER for 
"gzip" compression.
Press ENTER key or "g" and ENTER to continue: 

Step 1
A .desktop file was found here:
chromium64_45.0.2454.101+pepper_19.0.0.185_lx/usr/share/applications/chromium.desktop
So this application will have a menu entry.
If you want to change the .desktop file in any way, open it in a text editor
right now, before proceeding and make any changes you want.
In particular, check that the icon exists, and that 'Category' entry fits
into Puppy's menu hierarchy (see file /etc/xdg/menus/hierarchy).
After satisfying yourself that the .desktop file is ok, press the ENTER key
to continue this script.
Or, type 'ignore' to build pet pkg as if there is no .desktop file.
Or, type 'new' if you would like this script to ask a series of
questions and rebuild the .desktop file from scratch: 

Dependencies
Please enter a dependency-list for the PET package that is now being
created. Packages already built-in to Puppy do not need to be
explicitly named as dependencies (except a cut-down barebones version
of Puppy may not have all of these built in, so you may have to
think of the worst-case situation).
How to enter this dependency-list is shown by an example: the package
'pupdvdtool-0.5b' has the following dependency list:
+vamps,+vobcopy,+ffmpeg,+dvdauthor,+gtkdialog3
Each package name is preceded by a '+' and delimited by a ','.
NOTE1: that 'gtkdialog3' requires the GTK libraries, but it is not
       necessary to specify sub-dependencies, as if 'gtkdialog3'
       needs to be installed it has its own dependency list.
NOTE2: You can lookup the dependency-list of each package in the
       /root/.packages/Packages-* database files
NOTE3: it is not required to specify package version numbers,
       VERSION NUMBERS NOT YET SUPPORTED BY PACKAGE MANAGER
NOTE4: If you don't know what to specify, just press ENTER key
       (the package manager will still do some basic dependency checking)

Type dependency-list: 

GUI window
Press ENTER key to bring up a GUI window that will help you to create
a database entry for the package. This will be shown in a text editor
for saving somewhere, also written to file 'pet.specs' inside the pkg.
Press ENTER: 
achromium64_45.0.2454.101+pepper_19.0.0.185_lx bInternet cEMPTY dAccess the Internet echromium64_45.0.2454.101+pepper_19.0.0.185_lx f283852 gEMPTY hyes iEMPTY

chromium64_45.0.2454.101+pepper_19.0.0.185_lx|chromium64_45.0.2454.101+pepper_19.0.0.185_lx|||Internet|283852K||chromium64_45.0.2454.101+pepper_19.0.0.185_lx.pet||Access the Internet|ubuntu|trusty||

Creating package...

File ./chromium64_45.0.2454.101+pepper_19.0.0.185_lx.tar.xz created. Now converting to .pet...

chromium64_45.0.2454.101+pepper_19.0.0.185_lx.pet has been created. Finished.

If you look in chromium64_45.0.2454.101+pepper_19.0.0.185_lx you will see the new '.specs' file.
Directory chromium64_45.0.2454.101+pepper_19.0.0.185_lx is now configured correctly as a PET package
and in future you do not need to go through this script again.
You could manually edit the files if required, and create another
.pet package just by doing this:
# tar -c -f chromium64_45.0.2454.101+pepper_19.0.0.185_lx.tar chromium64_45.0.2454.101+pepper_19.0.0.185_lx/
# xz -z -9 -e chromium64_45.0.2454.101+pepper_19.0.0.185_lx.tar
# tgz2pet chromium64_45.0.2454.101+pepper_19.0.0.185_lx.tar.xz

dir2pet exited.
sfs has been converted to pet
root# 
root# chrom
chromedriver  chromium      
root# chromium 
libva info: VA-API version 0.35.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: va_openDriver() returns -1
[29609:29609:1011/151335:FATAL:sandbox_seccomp_bpf_linux.cc(203)] Check failed: policy->PreSandboxHook(). 
[29579:29603:1011/151342:ERROR:socket_libevent.cc(79)] CreatePlatformSocket() returned an error, errno=97: Address family not supported by protocol
root#
root# echo "Chromium browser starts on the desktop and allow navigation on the web"
root# Chromium browser starts on the desktop and allow navigation on the web
Browser Works!

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

chromium_46.0.2490.71+pepper_19.0.0.226

#183 Post by 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 sfs:
chromium_46.0.2490.71+pepper_19.0.0.245_lx.sfs

64bit sfs:
chromium64_46.0.2490.71+pepper_19.0.0.226_lx.sfs

.pet versions with pepperflash-19.0.0.207 are available here

Caveats and constraints as detailed above

If you need a .pet instead of a .sfs or you want the 64-bit .sfs to run on tahrpup64 then use this converter.
Last edited by peebee on Sat 05 Dec 2015, 07:27, edited 4 times in total.
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
Mike Walsh
Posts: 6351
Joined: Sat 28 Jun 2014, 12:42
Location: King's Lynn, UK.

Re: latest-pepper-flash.sh

#184 Post by Mike Walsh »

step wrote: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.
Looks very like the Ubuntu technique for providing PepperFlash for Chromium. You've done it by the 'coding' method; I've done it manually:-

http://www.murga-linux.com/puppy/viewtopic.php?t=101275

The end result is essentially the same. However, if you look at peebee's reply, you'll see that neither of our 'methods' are strictly necessary.

I'm quite happy to let alienbob use his bandwidth, bless his little cotton socks...! :lol:


Mike. :)

User avatar
Marv
Posts: 1264
Joined: Wed 04 May 2005, 13:47
Location: SW Wisconsin

Re: chromium_46.0.2490.71+pepper_19.0.0.207

#185 Post by Marv »

Quicktest of the 32 bit SFS,

Your 45.xx 32 bit SFS unloaded, this SFS loaded in X-slacko 3.1n, X-tahr 1b3, and LxpupTahr 15.05. All running just fine using my common chromium profile located on an EXT2 partition and symlinked in /root/.config in each pup.

Thanks,
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.

Post Reply