Chromium v83 with pepper-flash **RUNS-AS-SPOT**
UPDATE 10-dec-2017
For LxPupSc only (32-bit) .....
chromium_63.0.3239.84+pepper_27.0.0.187_lxsc_spot.sfs
RUN-AS-SPOT
New build....
Arch Linux have ceased all support for 32-bit systems and have completely deleted their 32-bit repositories
This build is therefore constructed from Debian 32-bit binaries....
For LxPupSc only (32-bit) .....
chromium_63.0.3239.84+pepper_27.0.0.187_lxsc_spot.sfs
RUN-AS-SPOT
New build....
Arch Linux have ceased all support for 32-bit systems and have completely deleted their 32-bit repositories
This build is therefore constructed from Debian 32-bit binaries....
- Attachments
-
- Screenshot.png
- (112.06 KiB) Downloaded 3626 times
Last edited by peebee on Sun 10 Dec 2017, 10:35, edited 1 time in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
chromium_63.0.3239.40+pepper_27.0.0.187_lxsc_spot.sfs
see above
see above
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
chromium_63.0.3239.84+pepper_27.0.0.187_lxsc_spot.sfs
see above
see above
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
chromium_63.0.3239.84+pepper_28.0.0.126_lxsc_spot
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Re: chromium_62.0.3202.75+pepper_27.0.0.183 **RUN-AS-SPOT**
where would I get the source code for libnss. I want to try compiling it for super lupupeebee wrote:RUN-AS-SPOT
32-bit chromium_62.0.3202.75+pepper_27.0.0.183_lx_spot.sfs
64-bit chromium64_62.0.3202.75+pepper_27.0.0.183_lx_spot.sfs
For the 32-bit version some tweaks are needed....
For slacko-6.9.9.9 (and LxPupSc-17.09.1) the mozilla-nss-3.31.1-i586-1_slack14.2.txz update is required.
(LxPupSc-17.09.22 and later already has this update).
For xenialpup-7.0.8.1 the following links need to be made:For LxXenial-17.06 only the libpcre link is needed:Code: Select all
cd /usr/lib && ln -s libpng14.so.14 libpng16.so.16 && cd /lib && ln -s libpcre.so.3 libpcre.so.1
Runs in ArtfulPup with NO tweaks.Code: Select all
cd /lib && ln -s libpcre.so.3 libpcre.so.1
For the 64-bit version.....
slacko64-6.9.9.9 and LxPup64-17.06b require the update: mozilla-nss-3.31.1-x86_64-1_slack14.2.txz
xenialpup64-7.0.8.5 requires the 64-bit .sfs to be converted - see: http://murga-linux.com/puppy/viewtopic. ... 205#867205 (use option 2)
RUN-AS-SPOT
means that the location and permissions on the config and cache have changed and downloads have different behaviour
RUN-AS-SPOT
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
chromium+pepper **RUNS-AS-SPOT**
RUNS-AS-SPOT
For the 32-bit version some tweaks are needed....
For slacko-6.9.9.9 (and LxPupSc-17.09.1) the mozilla-nss-3.31.1-i586-1_slack14.2.txz update is required.
(LxPupSc-17.09.22 and later already has this update).
For xenialpup-7.5 the following links need to be made:For LxXenial-17.11 and Dpup Stretch CE by Radky only the libpcre link is needed:
Runs in ArtfulPup and Upup-Bionic-Beaver with NO tweaks.
For the 64-bit version.....
slacko64-6.9.9.9 and LxPup64-17.06b require the update: mozilla-nss-3.31.1-x86_64-1_slack14.2.txz
xenialpup64-7.5 requires the 64-bit .sfs to be converted - see: http://murga-linux.com/puppy/viewtopic. ... 205#867205 (use option 2)
RUNS-AS-SPOT
For the 32-bit version some tweaks are needed....
For slacko-6.9.9.9 (and LxPupSc-17.09.1) the mozilla-nss-3.31.1-i586-1_slack14.2.txz update is required.
(LxPupSc-17.09.22 and later already has this update).
For xenialpup-7.5 the following links need to be made:
Code: Select all
cd /usr/lib && ln -s libpng14.so.14 libpng16.so.16 && cd /lib && ln -s libpcre.so.3 libpcre.so.1
Code: Select all
cd /lib && ln -s libpcre.so.3 libpcre.so.1
For the 64-bit version.....
slacko64-6.9.9.9 and LxPup64-17.06b require the update: mozilla-nss-3.31.1-x86_64-1_slack14.2.txz
xenialpup64-7.5 requires the 64-bit .sfs to be converted - see: http://murga-linux.com/puppy/viewtopic. ... 205#867205 (use option 2)
RUNS-AS-SPOT
Last edited by peebee on Sat 02 Jun 2018, 15:42, edited 3 times in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
chromium_63.0.3239.132+pepper_28.0.0.137 **RUN-AS-SPOT**
RUN-AS-SPOT
32-bit chromium_63.0.3239.132+pepper_28.0.0.137_lx_spot.sfs
64-bit chromium64_63.0.3239.132+pepper_28.0.0.137_lx_spot.sfs
as above....
32-bit chromium_63.0.3239.132+pepper_28.0.0.137_lx_spot.sfs
64-bit chromium64_63.0.3239.132+pepper_28.0.0.137_lx_spot.sfs
as above....
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
RUN-AS-SPOT
13-mar-2018 - Chromium-64.0.3282.186 & PepperFlash-29.0.0.113
32-bit chromium_64.0.3282.186+pepper_29.0.0.113_lx_spot.sfs
64-bit chromium64_64.0.3282.186+pepper_29.0.0.113_lx_spot.sfs
as above....
13-mar-2018 - Chromium-64.0.3282.186 & PepperFlash-29.0.0.113
32-bit chromium_64.0.3282.186+pepper_29.0.0.113_lx_spot.sfs
64-bit chromium64_64.0.3282.186+pepper_29.0.0.113_lx_spot.sfs
as above....
Last edited by peebee on Tue 13 Mar 2018, 07:36, edited 5 times in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
- Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Now PepperFlash-28.0.0.161 see above
7-feb-2018 - Chromium-64.0.3282.140
7-feb-2018 - Chromium-64.0.3282.140
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
-
- Posts: 168
- Joined: Fri 26 Jan 2018, 20:54
Old 32 bit Chromium version links
Has anyone reported that the links for 32bit Chromium older than 52 are not working? Could not find them on SourceForge.
Re: Old 32 bit Chromium version links
37 is still there.....WiZard wrote:Has anyone reported that the links for 32bit Chromium older than 52 are not working? Could not find them on SourceForge.
https://sourceforge.net/projects/lxpup/ ... /chromium/
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
- Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
@ WIZard:-
I don't know how far back you want to go, but I've got a whole bunch of Peebee's older 32-bit Chromium SFSs. I've got
36
37
38
39
41
42
43
45, and
48.
I always hang on to stuff like browsers, 'cos sometimes older stuff works better for older hardware/Puppies.
Let me know what you want, and I'll upload it to my MediaFire a/c for ya. I use 36.0.1985.143 as my 'go-to' backup browser; if and when all else fails, it always works for me.....despite being quite old now. And peebee's builds are dead stable.
If anybody else needs an older copy, again, let me know; the offer stands.
Mike.
I don't know how far back you want to go, but I've got a whole bunch of Peebee's older 32-bit Chromium SFSs. I've got
36
37
38
39
41
42
43
45, and
48.
I always hang on to stuff like browsers, 'cos sometimes older stuff works better for older hardware/Puppies.
Let me know what you want, and I'll upload it to my MediaFire a/c for ya. I use 36.0.1985.143 as my 'go-to' backup browser; if and when all else fails, it always works for me.....despite being quite old now. And peebee's builds are dead stable.
If anybody else needs an older copy, again, let me know; the offer stands.
Mike.
Old 32 bit Chromium versions
@ally
@peebee
@mikewalsh
Thanks guys. I'm using a Slacko 6.3.0 32bit image to update some computers with a
more secure browser hardened against the meltdown/spectre cpu flaws. Firefox
starting at 57 & 52.6.0esr and Chrome starting at 64 are supposed to mitigate
the threats. Slacko 6.3.0 will run FF 52.6.0 (needs GTK+3 installed) but won't
run Chrome 64. My image has FF 52.6.0 and chromium_52.0.2743.116+pepper_22.0.0.209_lx.sfs
Chromium is included since I have found some sites don't run correctly with FF.
Both browsers have been hardened by making recommended settings and adding ublock origin,
flash block & noscript extensions
My Chromium problem was I had one laptop, a HP 6910p, that chromium 52 just caused it
to black screen crash when you tried to open settings. I wanted to back up one
version to Chromium 51 to test it.
@ally
I found chromium_51.0.2704.84pepper_21.0.0.213_lx.sfs in your archives and it
works, thanks
@peebee
I did find chromium_37.0.2062.120+pepper_15.0.0.152_lx.sfs on Sourceforge and it
also works
@mikewalsh
Thanks for weighing in on this, I don't know how much difference there is in the
versions from say 36 to 52. I did find when making settings on Chromium 52 that
one of the recommended site isolation changes can't be implemented because that
feature did not exist in 52. +1 for old versions. Like you, I tend not to fix
things that aren't broken and hate abandoning a well tested Puppy version just to
get a workable browser.
@peebee
@mikewalsh
Thanks guys. I'm using a Slacko 6.3.0 32bit image to update some computers with a
more secure browser hardened against the meltdown/spectre cpu flaws. Firefox
starting at 57 & 52.6.0esr and Chrome starting at 64 are supposed to mitigate
the threats. Slacko 6.3.0 will run FF 52.6.0 (needs GTK+3 installed) but won't
run Chrome 64. My image has FF 52.6.0 and chromium_52.0.2743.116+pepper_22.0.0.209_lx.sfs
Chromium is included since I have found some sites don't run correctly with FF.
Both browsers have been hardened by making recommended settings and adding ublock origin,
flash block & noscript extensions
My Chromium problem was I had one laptop, a HP 6910p, that chromium 52 just caused it
to black screen crash when you tried to open settings. I wanted to back up one
version to Chromium 51 to test it.
@ally
I found chromium_51.0.2704.84pepper_21.0.0.213_lx.sfs in your archives and it
works, thanks
@peebee
I did find chromium_37.0.2062.120+pepper_15.0.0.152_lx.sfs on Sourceforge and it
also works
@mikewalsh
Thanks for weighing in on this, I don't know how much difference there is in the
versions from say 36 to 52. I did find when making settings on Chromium 52 that
one of the recommended site isolation changes can't be implemented because that
feature did not exist in 52. +1 for old versions. Like you, I tend not to fix
things that aren't broken and hate abandoning a well tested Puppy version just to
get a workable browser.
- Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
@WIZard:-
Logically, I'm not surprised you can't run Chrome 64. Chrome went 64-bit only starting from version 49, around 2 years ago.
I've no idea whether your actual machine is 64 or 32-bit. You can only run a 64-bit browser within a 64-bit OS. Even if you run a 32-bit OS on a 64-bit machine (it'll work this way round, but not the other), you're still limited to 32-bit browsers.....
peebee has made 32-bit builds available for Chromium because the Linux source code is there for it. Although Google still make 32-bit builds for Windows, it was Linux that got shafted 2 years ago.....under the guise of 'enhanced security'. I can't produce 32-bit builds for Chrome for the simple reason that there IS no source for it.
Google, in-house, use a highly-modded variant of Gentoo Linux.....which is virtually build it yourself, do-what-you-want-to-with-it. They make use of it.....but to many folks, it seems as though they're damned if they're going to accommodate the community that spawned it.
And then there's the progressive dropping of 32-bit by one major company after another, which started a year or two ago, and is slowly but surely gathering steam. 32-bit is eventually going to go the way of the dodo.....and 16-bit. And 8-bit before that. And as for 4-bit.....
Yet there's plenty of still perfectly functional 32-bit equipment about.....especially from around 10 years ago, or older. Because it was built to last.....before this obsession with 'built-in obsolescence' took over from common sense, and blinded the business community with dollar signs in their eyes. My 16-yr old Dell Inspiron lappie being a case in point; built like a brick outhouse.....and still working 100%. Apart from the keyboard's dodgy keys down the right-hand side.....but what d'you expect when you spill coffee all over it..?!
Mike.
Logically, I'm not surprised you can't run Chrome 64. Chrome went 64-bit only starting from version 49, around 2 years ago.
I've no idea whether your actual machine is 64 or 32-bit. You can only run a 64-bit browser within a 64-bit OS. Even if you run a 32-bit OS on a 64-bit machine (it'll work this way round, but not the other), you're still limited to 32-bit browsers.....
peebee has made 32-bit builds available for Chromium because the Linux source code is there for it. Although Google still make 32-bit builds for Windows, it was Linux that got shafted 2 years ago.....under the guise of 'enhanced security'. I can't produce 32-bit builds for Chrome for the simple reason that there IS no source for it.
Google, in-house, use a highly-modded variant of Gentoo Linux.....which is virtually build it yourself, do-what-you-want-to-with-it. They make use of it.....but to many folks, it seems as though they're damned if they're going to accommodate the community that spawned it.
And then there's the progressive dropping of 32-bit by one major company after another, which started a year or two ago, and is slowly but surely gathering steam. 32-bit is eventually going to go the way of the dodo.....and 16-bit. And 8-bit before that. And as for 4-bit.....
Yet there's plenty of still perfectly functional 32-bit equipment about.....especially from around 10 years ago, or older. Because it was built to last.....before this obsession with 'built-in obsolescence' took over from common sense, and blinded the business community with dollar signs in their eyes. My 16-yr old Dell Inspiron lappie being a case in point; built like a brick outhouse.....and still working 100%. Apart from the keyboard's dodgy keys down the right-hand side.....but what d'you expect when you spill coffee all over it..?!
Mike.
Browsers 32 & 64bit
@mikewalsh
Computers everywhere in my office, most of them 64bit capable but I run 32bit OS's on most. There are only a few programs that I use that require a 64it OS (Adobe) and I don't run more than 4gb of ram so there's no compelling reason to run 64bit. The 32 bit images I build will work on anything. I have 6-7 old laptops with P3 (tualitins), P4 and Pentium M cpus that are 32bit only. My old Compaq n610c P4's will run 70C-80C under load for extended periods, they make great leg warmers. You're right you allmost can't kill them. The Pentium M's are pretty snappy with Puppy Slacko 6.3.0 and even OK with Windows 7.
Thanks for the additional feedback.
Computers everywhere in my office, most of them 64bit capable but I run 32bit OS's on most. There are only a few programs that I use that require a 64it OS (Adobe) and I don't run more than 4gb of ram so there's no compelling reason to run 64bit. The 32 bit images I build will work on anything. I have 6-7 old laptops with P3 (tualitins), P4 and Pentium M cpus that are 32bit only. My old Compaq n610c P4's will run 70C-80C under load for extended periods, they make great leg warmers. You're right you allmost can't kill them. The Pentium M's are pretty snappy with Puppy Slacko 6.3.0 and even OK with Windows 7.
Thanks for the additional feedback.