Puppy Linux Discussion Forum

peebee · Posted: Tue 12 Sep 2017, 11:18 Post subject:

Pepperflash updated to 27.0.0.130 - see above

peebee · Last edited by peebee on Mon 16 Oct 2017, 04:37; edited 3 times in total

UPDATED 16-oct-2017

32-bit chromium_61.0.3163.100+pepper_27.0.0.170_lx.sfs

64-bit chromium64_61.0.3163.100+pepper_27.0.0.170_lx.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 et al already has this update).

For xenialpup-7.0.8.1 the following links need to be made:

peebee · Posted: Fri 15 Sep 2017, 02:45 Post subject:

For LxPupSc only (32-bit) .....

chromium_61.0.3163.91+pepper_27.0.0.130_lxsc.sfs

peebee · Posted: Fri 22 Sep 2017, 11:37 Post subject:

For LxPupSc only (32-bit) .....

chromium_61.0.3163.100+pepper_27.0.0.159_lxsc.sfs

jss83 · Joined: 06 Jan 2015 Posts: 267

How to make it work on Tahrpup 6.0.5 ?

peebee · Posted: Sat 07 Oct 2017, 10:18 Post subject:

jss83 · Joined: 06 Jan 2015 Posts: 267

To tell the truth sir, I can't seem to find the one as good as tahrpup Smile

I tried a lot of derivatives but none of them work as sweet as tahrpup 6.0.5 does(for me ie), not even 6.0.6 or xenial (something works something doesn't) and since 666philib seems to have gone MIA for indefinite duration, I don't think it is going to be updated at all, which is going to be a problem for me because I am used to it too much. Confused

I installed slimjet and its gonna work for now Very Happy

Thanks..

peebee · Posted: Tue 10 Oct 2017, 07:11 Post subject:

PepperFlash updated to 27.0.0.159

peebee · Posted: Mon 16 Oct 2017, 04:38 Post subject:

PepperFlash updated to 27.0.0.170 - links above

VanZan · Joined: 15 Oct 2012 Posts: 6

I just need a Puppy and the Chromium browser (or anything that would let me use my Google account, passwords, extensions etc). Could someone recommend the best solution? As I said my only requirements are the browser!

I tried Tahrpup64 6.0.6 and it asked to be default browser but then never started. I'm guessing I need a newer Puppy.

Mike Walsh · Joined: 28 Jun 2014 Posts: 5672 Location: King's Lynn, UK.

Hi, VanZan.

Well, poor old peebee's got his hands tied with the most releases of Chromium. Google (via the Chromium Project) are insisting on bang-up-to-date everything now.....even XenialPup is having problems with it these days, unless you install a shed-load of extra stuff.

If all you want is a browser that'll allow you use of your Google a/c, I produce a couple of Chromium 'clones' that still run OK in Tahr64. Flashpeak's 'Slimjet' browser, and SRWare's 'Iron' browser. You can find the Slimjet64 thread here:-

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

.....and the Iron64 thread here:-

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

Both allow full use of any Google a/c. I especially recommend SlimJet; it's developed quite a following here in Puppy-land!

Hope that helps.

Mike. Wink

peebee · Posted: Wed 18 Oct 2017, 12:18 Post subject:

See below....

belham2 · Joined: 15 Aug 2016 Posts: 1707

Hi Peebee,

I was wondering: will these chromium32.sfs builds run in micko's slacko32-6.9.9.9?

From the LxPupSc32 'frugal' folder, I copied over the latest chromium.sfs into the 'frugal' folder I have for Micko's Slacko32-6.9.9.9. SFS-Load-On-The-Fly seemed to load it ok, but it would not start (tried the desktop shortcut, then actually its executable in /usr/lib/ and /usr/bin/---no response). Next I opened a terminal and tried to run it, and below pic is what I got (never seen one of these before--what is "undefined symbol: hb_font_set_variations symbol lookup error"??):

peebee

peebee · Posted: Fri 20 Oct 2017, 05:42 Post subject:

RUN-AS-SPOT

For LxPupSc only (32-bit) .....

chromium_62.0.3202.62+pepper_27.0.0.183_lxsc_spot.sfs

RUN-AS-SPOT

All downloads will have user:group = spot:spot
HOWEVER
All items in /root/spot/Downloads will be changed to user:group = root:root ON EXIT

If you want to use existing configs with this Run-As-Spot version then you will need to change the ownership to spot:spot - strongly suggest a copy is made before doing this!!