Google Chrome 64-bit packages - [CLOSED]

[Mike Walsh]

NOTICE

I just thought I'd better make this a wee bit more obvious.

For anybody who's still stuck with 32-bit hardware, and absolutely must have Chrome itself (no imitations!!), the very final 32-bit Linux release before Google 'pulled the plug' was 48.0.2564.116.

I still use this regularly myself, alongside much more recent Chromium-based 'clones' (i.e., SlimJet, Iron, even Chromium itself). It's very reliable, and will often work with certain sites where the newer browsers (for reasons explained here) will turn their noses up at them.....

Pet & SFS packages for this are available here:-

https://www.mediafire.com/folder/deqayv78nd0ip/32-bit

You'll need to update PepperFlash with the newest version, from here:-

https://www.mediafire.com/folder/gq96iya8in8ix/Chrome

Stay safe online.


Mike.

[Mike Walsh]

ANNOUNCEMENT

Evening, boys & girls.

I hoped I wouldn't have to do this, but the sad fact is, my production 'run' for the 64-bit Chrome packages will now be ending.

Google, in their wisdom, have upgraded the Network Security Services requirements to the very newest version(>=3.26), and this is beyond the capabilities of Tahr64 to handle, as it also requires the use of a newer version of the glibc.

I quit using Slacko64 a while back, as it was just giving me too many problems.....and Chrome hasn't run on there for the last couple of releases.

I've tried several times to get Xenialpup64 running on here, but it just won't run properly. And unless there's any other 64-bit Pups floating around out there which aren't based on either the current 'buntu or Slacko offerings, I'm afraid this thread will now be coming to a premature end.

Sorry to have to let all you Chrome fans down. I've taken it as far as I can.....but from this point on, will be concentrating on the 64-bit SlimJet and Iron packages. (Until such time as things go 'tits-up' with those two!)

If I do manage to figure out what the hell's needed to solve this for running in Tahr (maybe a glibc 'upgrade'? Who can tell? Anything's possible with Pup, as I'm sure you're all aware...), then I shall of course resume Chrome package production.

Until such time, in the words of the immortal Bugs Bunny....."That's all, folks!"

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

EDIT:- 60.0.3112.101 will, naturally, remain available. It's the newest I can offer.

I thought it only fair to let y'all know.


Mike.

[Mike Walsh]

Good news, boys & girls. I shall be continuing with Chrome production after all.

Following a tutorial from battleshooter, I'm now beginning to understand the use of 'library paths' and 'environment variables'. Something new I've learnt today..!

It's the kind of stuff anybody who packages (or re-packages) software needs to know. Until now, I've had no need.....

Never mind. Anyway, here is Chrome 61.0.3163.79......available from the usual location. Pepper is still taken care of automatically, and 'silent-launch' is enabled in /root/Startup.

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

The very newest version of lib_nss (>= 3.26), which Chrome now insists on, lives locally within the /chrome directory, and is called by LD_PRELOAD. The main 'chrome' lib and 'chrome-sandbox' are both treated with PhilB's 'bbe' script, and iguleder's 'libpuppygc.so' is still in residence, convincing Chrome that Puppy is just a normal user!

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

Details of 'fixes' at the usual URL:-

https://chromereleases.googleblog.com/

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

Any probs, y'all know where to find me.....but do be aware, these recent releases are getting increasingly 'unstable' in Puppy, no matter what we do. Spontaneous 'shutdowns' are becoming more & more common; I make no guarantees.


Enjoy.


Mike.

[peebee]

The main 'chrome' lib and 'chrome-sandbox' are both treated with PhilB's 'bbe' script, and iguleder's 'libpuppygc.so' is still in residence, convincing Chrome that Puppy is just a normal user!

Hi Mike
Have you found a need to "bbe" chrome-sandbox?? I don't, and haven't noticed a problem....
Cheers
peebee

[Mike Walsh]

Hi, Peter.

No, not a specific need, as such.....but it does cut down on crap in the terminal, and, as Oscar found out, dbus doesn't seem to get quite so confused as to what's happening..!

I tell you this, though; these recent releases are getting more and more temperamental. This current Chrome, and as I said to you a little while ago, Chromium 60, every time I try to upload anything with either of 'em, instant 'crash'. I have never come across as many problems as I have this last few releases. Unless it's just my system. (*shrug*)

SlimJet and Iron.....smooth sailing. Nary a problem.....yet!

Give it time.....


Mike.

[orrin]

Hi Mike,

Just like version 60, 61 will not start in Slacko 64-6.3.2
I reloaded 59 which works OK!

Thanks anyway!

[Mike Walsh]

@orrin:-

See my reply to your post in the Iron thread. Did you ever install that GTK3/GDK3 stuff, BTW?


Mike.

[Pelo]

Chromium Versión 60.0.3112.78 (Build para desarrolladores) (64 bits)
on test with shiba inu 64 (included in the Puppy by Josejp2424)
Chromium has never been my cup of tea. So i am not used to it.
However i never had real problems with older versions

..desarrolladores : developers

Well i translate the topic, to share your ideas if any.

[jake29]

Thanks Mike, glad to see development continue. I appreciate the effort you are making here.

Regarding, GTK3 - it became a requirement with v59. Perhaps orrin intended to say v58 is the last working version for him?

[orrin]

Thanks Mike, glad to see development continue. I appreciate the effort you are making here.

Regarding, GTK3 - it became a requirement with v59. Perhaps orrin intended to say v58 is the last working version for him?

I have GTK3 installed and Chrome 59 works OK, but it is only a backup
browser. My primary is Slimjet!

[jake29]

Latest build - v61.0.3163.79 - is not working with FatDog64 710.

Code: Select all

# google-chrome
/usr/bin/google-chrome: error while loading shared libraries: libpcre.so.3: cannot open shared object file: No such file or directory

This distro only has libnss v3.21 available, and I am unable to compile v3.26 or newer.

[Mike Walsh]

Hi, Jake.

You shouldn't actually need to. This is what battleshooter was helping me out with. What he eventually figured out was needed was to install all the required versions of libnss, gtk3, and their dependencies in a separate 'lib' folder inside the Chrome directory. These are then called by LD_PRELOAD, before the exec-line is run.

The 'libpcre' requirement...hmmm. I know I had this one with one of peebee's recent Chromium builds in Xenialpup, but I think that was a 32-bit version..... Leave it with me; let me do some tracking down. Chrome draws its code from Chromium anyway, so, we'll see what's what. I believe we can sort that one.

I know FatDog uses a weird mixture of Slackware and something else.....and Slackware are notorious for being sparing with deps, etc, as supplied. It's not a distro for beginners, I know that much.

Bear with me...


Mike.

[Mike Walsh]

Try these, Jake:-

http://www.mediafire.com/file/kov2igqwe ... ibs.tar.gz

I'm not making any guarantees, but these are the 64-bit versions of what I needed for Chromium in Xenial. You've got libpcre.so.3, and libpng16.so.16 (which was also needed).

Give 'em a try; that's all you can do. Extract them, then place them in the /usr/lib64 directory. Let me know what happens, please.


Mike.

[jake29]

Try these, Jake:-

http://www.mediafire.com/file/kov2igqwe ... ibs.tar.gz

I'm not making any guarantees, but these are the 64-bit versions of what I needed for Chromium in Xenial. You've got libpcre.so.3, and libpng16.so.16 (which was also needed).

Give 'em a try; that's all you can do. Extract them, then place them in the /usr/lib64 directory. Let me know what happens, please.

Thanks Mike, adding those libs as instructed got this version working for me in FatDog64.

[Mike Walsh]

Ah, good. I'm glad that's worked. Onwards and upwards..!

Just out of curiosity, are you having any problems with it if you try to upload/download anything? Are you getting any crashes?


Mike.

[jake29]

Ah, good. I'm glad that's worked. Onwards and upwards..!

Just out of curiosity, are you having any problems with it if you try to upload/download anything? Are you getting any crashes?


Mike.

No issues or crashes so far in my testing.

[plrsmith]

Hi Mike

I am a newbie at using a live usb persistent version of Puppy Linux (tahr64-6.0.5) with an encrypted save file. I have installed your latest Chrome sfs which generally works well. Thank you. However, whenever I try a right click and save action (e.g. right click "save image as") Chrome crashes to a black screen and I have to reboot.

Help please.

Thank you

Peter

[Mike Walsh]

Hallo, plrsmith. And 'Welcome' to the kennels. Nice to have you on board...

Y'know, I suspect your problem stems from that encrypted save-file. I don't know of anybody who actually uses one of those things. With Puppy, it's just unnecessary, extra 'complication'.....and it makes Puppy work twice as hard.

However.....

Can you give us some idea of your hardware; make & model, CPU, RAM, HDD, graphics, etc?

How did you install Puppy? Full or 'frugal'? HDD.....or flash drive? Where did you get the download from.....and did you check the md5 hash, just to be on the safe side? You might have a corrupted download; I've not heard of Tahr misbehaving quite like that before.

Mind you, Google are steadily making it harder & harder to produce the Chrome packages for Puppy. Many of us are turning to FlashPeak's SlimJet browser, and SRWare's Iron browser; both based on Chromium (which is where Chrome draws its source code anyway), and both allow you to use a normal Google a/c, along with all your bookmarks and extensions. And the Puppy packages are both 'NetFlix-ready', with the WideVine DRM modules already installed.

You can find them both at the MediaFire a/c in my sig; 'My Puppy Packages'. Just navigate through and help yourself.

It's also possible your Tahr64 needs the GTK-3.0 stuff installed; Chrome has required this since 56 or 57.....but I don't think it'll even fire up without it. You would need to manually install that from the PPM (Puppy Package Manager); you may have realised by now that Pup doesn't 'do' automatic updates.....it's all very 'hands-on', I'm afraid!

Out of curiosity, are you a Linux beginner.....or just new to Puppy?


Mike.

[plrsmith]

Dear Mike

Thank you for your response. In answer to your questions. I have been using Linux for about 15 years now but am by no means an expert, although I know my way around more than some. However, I am new to USB live installations though and very new to Puppy Linux.

I am trying to revive an old (10+ years) Panasonic Letsnote CF-Y7 Laptop which is a Centrino Duo L7300 1.4GHz with built in 965GM graphics and 2Gb RAM. It is currently running Fedora 20 (which is no longer supported) and I have been experimenting with using a live persistent version of PuppyLinux on a 64GB USB stick to make certain aspects of my PC usage completely and very easily portable. It is because I intend to carry this USB stick around that I have encrypted the save file. The PuppyLinux even though it is on a USB stick is much faster than the installed Fedora OS.

I installed the official distribution of puppy tahr64 from one of the official mirrors and checked the MD5 hash. I have libgtk-3-bin_3.10.8 installed and cannot see any further gtk3 packages in PPM. Chrome loads and starts without hitch.

I also thought my problems may be due to the encryption but I could not see how to remove the encryption from the save file. Can I do this? Or do I have to start from scratch again?

Since my original post, I have discovered an additional problem. Viewing YouTube videos crashes the x server. That is the video keeps playing ( I can hear the sound) but the display goes black.

I am happy with everything else with this installation (although I had to change the permissions on the my-documents folder) and can connect to my wifi, print to my wireless printer, use Libreoffice, mount all the drives/partitions on the laptop etc.

The built in Palemoon browser seems to work without any problems but I would like to use Chrome if possible.

Any help/suggestions would be greatly appreciated.

Thanks in advance

Peter

[Mike Walsh]

Hi, Peter.

Hm. Well, I'm pretty certain this isn't what you want to hear....but the easiest way to get rid of the encryption is to create a new save-file (without encryption.)

What I would do is to make a back-up of the existing save-file. In Puppy, this is literally a simple copy/paste operation; just copy the save-file to somewhere safe. Then, delete the one on the USB stick's /mnt/home. Reboot, shut-down straight away, and create a normal save-folder. The save-folder has the advantage of being able to expand/contract (like a normal folder/directory) up to the available space on the partition.....unlike the save-file, which periodically needs enlarging if you add a lot of stuff to Pup.

If everything else is working fine, great; that's good to hear. Try it with recreating a new save-folder (you'll have to re-load the Chrome SFS, of course), and let us know what transpires, please. If you've still got problems after that, we'll have a think about the next step. Hopefully, there won't be one!


Mike.