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

[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]

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.
      
      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!

[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.

[Mike Walsh]

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...!


Mike.

[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,

[gcmartin]

Converter tested and PETs made for 45 and 46. Tested on April72s

[Skydog007]

is there any way to limit the cahce size?

[peebee]

is there any way to limit the cahce size?

Yes - edit /usr/bin/chromium - the switches on the exec line

[peebee]

Update to pepperflash-19.0.0.245 - see above

Security fix

[Marv]

Update to pepperflash-19.0.0.245 - see above

Security fix

Another extremely easy update (5 computers running X-Slacko 3.1n). Unload the previous SFS, load this one. Period! All profile information kept in symlinked external location on an EXT2 partition so it is unaffected. Could it be easier

Thanks

[peebee]

could it be easier
Thanks

Maybe......

Here's what I do:

2 folders at base of partition - 1 for the frugal install - 1 for chromium

In the chromium folder I symlink the sfs to a generic chromium.sfs

In the frugal folder I symlink another generic chromium.sfs to the generic link in the chromium folder.

Then sfs-load the generic chromium.sfs link in the frugal install folder.

i.e. a double symlink to the actual sfs

then when a new version appears just delete and recreate the symlink in the chromium folder to the new version and reboot - no need to do any sfs unloading or loading....

Have I described this adequately? A diagram might help....

Thanks for the feeback

Cheers
peebee

[Marv]

could it be easier
Thanks

Maybe......
snip
Have I described this adequately? A diagram might help....

No, I get it. Clever. If I did it oftener and on only my own computer, as you probably do, I guess I'd try that. I'll bark twice for just swapping the SFS -and no reboot- for now.

[peebee]

THIS VERSION WILL ONLY WORK ON "MODERN" PUPPIES - e.g. LxPup, LxPupTahr, Slacko6, 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_47.0.2526.73+pepper_20.0.0.267_lx.sfs

64bit sfs:
chromium64_47.0.2526.73+pepper_20.0.0.267_lx.sfs

.pet versions are not yet available.

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.

[unicorn316386]

@peebee: 32-bit version sfs is working for me in Slacko 6 / kernel 3.14.55 after adding the /usr/bin patch in your link. Chromium 47 is somewhat laggy loading and playing music in Pepper Flash on my single core CPU so I'm going back to Firefox now, just reporting back that it works

[Marv]

Updated 32 bit SFS to chromium_47.0.2526.73+pepper_19.0.0.245 on X-Slacko 3.1n, X-tahr 1b3, LxPupSc. Unloaded previous SFS, loaded this one. Working well. External profile from previous version recognized and used.

[peebee]

Security update to pepperflash-20.0.0.228 - see above for updated download links

[HumanTeeth]

Thanks peebee for your work.

Following instructions in this thread 64bit version works with tahrpup64 6.0.3.9 when started from command line.
Youtube OK.


Unfortunately my motive was a simple Netflix solution. So it's back to the search function of this forum for me.

[peebee]

Security update to pepperflash-20.0.0.267 - see above for updated download links

Security fix

[davids45]

G'day peebee,

Thanks for the converter of sfs files to alter the location of the /usr/lib files so a "normal" 64-bit sfs can be run in tahrpup64.

I had just about given up trying to get my libreoffice64 sfs to run in tahrpup64 and was getting psyched up to manually alter the lib location when I noticed your comment about the updated chromium-pepper sfs and the tahrpup64 issue, and the converter you'd posted .

So I've done both sfs files (office & chromium) for tahrpup64 compatability.

(I'm trusting they'll work when next I open tahrpup64 )

David S.

Follow-up:
Used the sfs converter and I now have tahpup64-working sfs of chromium and libreoffice.
This chromium version (like other recent chromiums) seems unstable when I'm running Geoguessr - drops out often but mostly recovers to keep game going. Geoguessr is using a lot of the two CPUs and some of the 2GB RAM on this old desktop.

[PetRose]

peebee, shouldn't this be linked to from this wiki below, which are one of the first one encounters when searching top down ?
http://puppylinux.org/wikka/chromium
It runs, albeit not quick, on my NetBook LG X110 with a 1 core, 2 processor Atom N270 CPU and 1GB RAM.
Thanks for this final piece of SW I needed for the minimalistic netbook of mine.