(old)Puppy Linux Discussion Forum

Now:
chromium_79.0.3945.117+pepper_32.0.0.303

Now:
chromium_79.0.3945.117+pepper_32.0.0.314

Now:
chromium_79.0.3945.130+pepper_32.0.0.314

Now:
chromium_80.0.3987.87+pepper_32.0.0.314

peebee wrote:07-Feb-2020


64-bit:
chromium64_80.0.3987.87+pepper_32.0.0.314

hello at all, the link for 64 bit version is broken.

https://sourceforge.net/projects/lxpup/ ... s/download

the right one is:

https://sourceforge.net/projects/lxpup/ ... 0.0.31[b]4[/b]_lx_spot.sfs/download

EgiX

Subito Piano wrote:Hmm -- having some trouble here but IDK if these are supposed to work with XenialPup (32-bit)...? Starting from terminal, i'm told i need GLIBC-2.29 (not available through PPM). At least for now, I've installed Chromium 79 from PPM and it works...but, it's BLOATED? Any advice?

Hi, i now writing from Chromium 80 on XenialPup 64 bit. see image.

how I did this:
1. download chromium SFS
2. convert_sfs option 2
3. load new chromium.sfs
4. copy /usr/lib/libgdk-3.so.0.1800.9 to /usr/lib/chromium/
5. copy /usr/lib/libgtk-3.so.0.1800.9 to /usr/lib/chromium/
6. go in /usr/lib/chromium/
7. re-link (relative) libgdk-3.so to libgdk-3.so.0.1800.9
8. re-link (relative) libgdk-3.so.0 to libgdk-3.so.0.1800.9
9. re-link (relative) libgtk-3.so to libgtk-3.so.0.1800.9
a. re-link (relative) libgtk-3.so.0 to libgtk-3.so.0.1800.9
b. run chromium-browser

Bye EgiX

17-feb-2020

Now:
chromium_80.0.3987.106+pepper_32.0.0.330

I need a bit of help. I've download the sfs version and tried using this to convert to a .PET file, but version 80 (64-bit version) still won't launch. The little "splash screen" of a yellow message about downloads will pop-up, but the actual browser itself fails!

I'm extremely new to this OS...is it possible for the OP to provide the PET version of this? I am completely unfamiliar with converting SFS to PET.

I somehow got Chromium working (version 79??) on my BionicPup32, so why won't the 64-bit version work on x64?

http://www.murga-linux.com/puppy/viewto ... 05#1045105

n.b. BionicPup64-8.0 requires the 64-bit .sfs to be converted - see: http://murga-linux.com/puppy/viewtopic. ... 205#867205 (use option 2)

If you really want a .pet (why??) then do it twice - option 2 followed by option 1

I will need baby-steps for this because I am way too used to Windows' interface.

I am in the directory and installed the sfs file. How do I get the terminal to change directory? Then I assume I just type in the final line and a prompt will come up to give me option 1 or 2?

I really don't want to be stuck on Palemoon; Chromium has been a lot faster for me on BionicPup32. Codecs for streaming sites don't even work on Palemoon either.

Hi XiaoSpence,

"I will need baby-steps for this because I am way too used to Windows' interface."

Hopefully, this post will help, http://www.murga-linux.com/puppy/viewto ... 94#1051294

peebee wrote:http://www.murga-linux.com/puppy/viewto ... 05#1045105

n.b. BionicPup64-8.0 requires the 64-bit .sfs to be converted - see: http://murga-linux.com/puppy/viewtopic. ... 205#867205 (use option 2)

If you really want a .pet (why??) then do it twice - option 2 followed by option 1

Okay. I managed to figure this out by opening the file through right-click to allow me to use the terminal option of 1 or 2. I selected option 2 and installed the new SFS, but Chromium still is not opening. Tried turning the file into a PET without success...

I really don't wanna give up on Puppy Linux! Palemoon has zero sound with videos on the internet!

XiaoSpence wrote:installed the new SFS, but Chromium still is not opening.

Please run chromium in a terminal and report the error messages. Thanks.

peebee wrote:

XiaoSpence wrote:installed the new SFS, but Chromium still is not opening.

Please run chromium in a terminal and report the error messages. Thanks.

Okay, I'll have to re-install and check. Where can I find the location of installed files? Rox file manager isn't making it easy for me.

It frustrates me that I can't just drag-and-drop icons from the task manager to the desktop for a shortcut.

Ok - I can see what is the problem.......

The conversion utility is working correctly and producing an sfs and a pet which both install correctly. (pet creation is very slow)

The problem is that the version of GTK+3 in the sfs is too new for BionicPup64.

The solution is to delete 6 files from /usr/lib/chromium:
3 called libgdk-3.so.*
3 called libgtk-3.so.*

I will amend the build to do this automatically for future builds.

@ XiaoSpence:-

XiaoSpence wrote:I really don't want to be stuck on Palemoon; Chromium has been a lot faster for me on BionicPup32. Codecs for streaming sites don't even work on Palemoon either.

Oh, that one's easily understood. The guys who build Palemoon have made it quite clear that they have no intentions of ever adding WideVine/DRM support to Palemoon, because it was never in the "vision".

(See my thread about it over on the Pale Moon forum:-

https://forum.palemoon.org/viewtopic.ph ... 43#p175043 )

You can watch stuff like the BBC's iPlayer, because it relies on Flash.....but even 'Auntie Beeb' is gonna have to re-code the site to use HTML5 instead, because Flash dies at the end of this year.....

Widevine is always supported on Chromium & derivatives (including the best-known derivative, Chrome), because it was originally Google's 'baby'.

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

What you have to understand is that the Chromium Project (sponsored by Google) always build/compiles their browser with the expectation that the user is always running the most current, up-to-date, whizz-bang mainstream distro with the very newest of everything on the system, OK?

The majority of Chromium 'clones' (including Chrome) take the source-code, but then tend to re-compile it against an older glibc & older dependencies, which makes them accessible to a far greater number of people. The whole business of Widevine/DRM not being included as standard in most clones is down to licensing restrictions; the user is free to add the necessary codecs/modules if they wish, but the developers are not legally allowed to supply them with the build.

Google, of course, being the developers of Widevine, and sponsors of many other proprietary codec packages, are a law unto themselves, and generally do what the hell they like.....


Mike.

Hi all,

i really don't know if this is the right topic to post this ?!

Have you heard about this script : https://github.com/scheib/chromium-latest-linux

jplt3 wrote:Hi all,

i really don't know if this is the right topic to post this ?!

Have you heard about this script : https://github.com/scheib/chromium-latest-linux

Given that Chromium expects up-to-date versions of everything to be in use, a script like that would be best suited to summat like Arch....a 'rolling-release' distro, where everything is updated to the newest version, as soon as it's available. And that's continuous, and on-going.

It's not peebee's fault these often don't work for us. He does a magnificent job of keeping up with the multitude of changes, but I believe even he has to dig around sometimes, to find builds that will work with Puppy.

Chromium is where Google try out all their bleeding-edge ideas; the semi-autonomous 'build-bots' at the Project are constantly churning out build after build, 24/7....many of which don't compile, and never see the light of day...


Mike.

Now:
chromium_80.0.3987.122+pepper_32.0.0.330

Now:
chromium_80.0.3987.132+pepper_32.0.0.344