Google Chrome 64-bit packages - [CLOSED]

Message

Mike Walsh · #151 Post by **Mike Walsh** » Tue 13 Jun 2017, 23:00

Evening, all.

Currently 'beta-testing' Chrome 60.0.3112.24. Everything, so far, is dead-centre 'on the green'.

29/06/17:- Now on 60.0.3112.50; still trouble-free.

Looking good.

Mike.

Mike Walsh · #152 Post by **Mike Walsh** » Tue 04 Jul 2017, 11:50

I think I spoke too soon.

I produce, as you know, Chrome packages for both Tahr64 and Slacko64.....although I'm running the original Slacko64, 6.3.0.

I've been spending a lot of time in Tahr64 lately, and the upgrade from the earlier 60 'Beta' to this current version was hassle-free. I've booted into Slacko64 for the first time in over a week.....and now Chrome won't start. It has an

Code: Select all

undefined_symbol_lookup_error

Seems to be something to do with the

Code: Select all

gdk_screen_authentication_factor

????

Seems it's possible that I won't be able to produce the Slacko package any more.....unless I get to the bottom of this fairly pronto. Chrome 60 'stable' will be out in a couple more weeks, so.....

Any ideas, anyone?

Mike.

snayak · #153 Post by **snayak** » Fri 21 Jul 2017, 11:44

Hi,

I am running on little older Fatdog 611.
Tried google-chrome-09042016-x86_64-official.sfs from
http://www.murga-linux.com/puppy/viewto ... 966#921966.
It didn't work. Shows error.
Chrome available from Fatdog 611's repository is bit old one too. Version 29.0.
Is there anywhere a newer Chrome available that runs on Fatdog 611?

Kindly help.

Sincerely,
Srinivas Nayak

Mike Walsh · #154 Post by **Mike Walsh** » Fri 21 Jul 2017, 14:45

Hallo, snayak.

My guess is that you need the GTK 3.0 stuff installed into FatDog. Chrome introduced the requirement for this a couple of releases ago. Further back in this thread, there is a link to a how-to.

I don't normally keep older stuff; only the current version, and the one immediately before it. But because I'm in a good mood today, and these don't take long, I've put this together specially for you. Please understand; I don't make a habit of doing this!! Give this a try, and see if it works for you. It's the 64-bit version of Chrome 48. I still use the 32-bit version of this, and it functions fine.

http://www.datafilehost.com/d/224d86a1

Let me know how it goes, please.

Mike.

snayak · #155 Post by **snayak** » Fri 21 Jul 2017, 16:48

Dear Mike,

I am very much thankful for your help. It is my greatest pleasure that I received your kind favor. Being in open source world for more than fifteen years, I very much understand and respect all our friend's good wishes, help and support. Such generous help must never be taken for granted and should never be demanded just for building special packages.

Glad to download the sfs. Tried on my puppy. It gives me the same error which google-chrome-09042016-x86_64-official.sfs gave me.

Code: Select all

~# google-chrome 
/usr/bin/google-chrome: symbol lookup error: /usr/bin/google-chrome: undefined symbol: gconf_client_get_default
~#

It seems I am missing some library.
Can you guess anything from this error message?
Looks like libgconf issue. But didn't get any such package in Fatdog repo. Guess of any solution?

By the way, from your post from https://www.bleepingcomputer.com/forums ... -of-puppy/ I got link for Chrome 48 for 32bit OS. Downloading it to try. Will let you know if it works.

Sincerely,
Srinivas Nayak

Mike Walsh · #156 Post by **Mike Walsh** » Fri 21 Jul 2017, 20:36

@snayak:-

Try the attached .pet. If that doesn't help, we'll approach it from a different angle.....

Mike.

snayak · #157 Post by **snayak** » Sat 22 Jul 2017, 07:37

Dear Mike,

My sincere thanks.

I installed the libgconf pet. It gets installed in /usr. Added /usr to /etc/ld.so.conf and ran #ldconfig. Now running #ldconfig -v | grep gconf shows me installed libgconf.

This means your pet was perfectly installed and system finds it nicely. While I ran #google-chrome after loading Google_Chrome-48.0.2564.109-amd64.sfs, the same error came.

I remember, while I had loaded google-chrome-09042016-x86_64-official.sfs, I had seen presence of libgconf-2.so.4.1.5, but the same error coming.

So this means, some other problem which this innocent error message not able to convey us.

Now, about 32 bit Chrome that I downloaded from another thread of yours... google-Chrome-48.0.2564.97-i386.sfs. This gives new error:

Code: Select all

~# google-chrome 
/usr/bin/google-chrome: error while loading shared libraries: libnss3.so: wrong ELF class: ELFCLASS64
~#

This means I have 64bit libnss3.so but no 32bit libnss3.so.
So here I am now.

Like you said, we should try from all angle possible. Another way could be to upgrade my OS to latest fatdog. But Fatdog 611 is so professional that I have almost drowned in love of it. Found it nicer than newer version 710 even. So have got attached to it for last 5 years. And it is my only OS I work with.

I will be very very happy to get your suggestion on another approach which you are thinking about.

Sincerely,
Srinivas Nayak

Mike Walsh · #158 Post by **Mike Walsh** » Wed 26 Jul 2017, 00:57

***NEW VERSION***

Evening, all.

The current stable version, 60.0.3112.78, released this afternoon, is now available for download from the usual location.

https://www.mediafire.com/folder/l8lkuo ... S_packages

Details of 'fixes' available here, for those interested in such things:-

https://chromereleases.googleblog.com/

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

Details for the first-time enabling of the new PepperFlash update system can be found here:-

http://www.murga-linux.com/puppy/viewto ... 393#928393

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

I thought there were a lot of 'fixes' in the previous release; there's even more in this one. Over 40 of them! At least the devs are 'on the ball' with all this. Good to know.

I'm sorry to have to say that these Chrome releases, although more efficient with memory usage nowadays, are steadily getting larger and larger. 'Tis the way of the world, I'm afraid; it's the big 'G' trying to be 'all things to all men'. Go figure.

Enjoy, mesdames et messieurs. You know where to find me if any problems crop up; I'm no longer running Slacko64, so this has only been tested in Tahr64. Those of you with Slacko-related problems, please form an orderly queue.....

Mike.

Mike Walsh · #159 Post by **Mike Walsh** » Sat 19 Aug 2017, 20:33

***NEW VERSION***

Evening, everyone.

The current stable version, 60.0.3112.101, released 3 days ago, is now available for download from the usual location.

https://www.mediafire.com/folder/l8lkuo ... S_packages

Details of 'fixes' available here, for those interested in such things:-

https://chromereleases.googleblog.com/

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

Details for the first-time enabling of the new PepperFlash update system can be found here:-

http://www.murga-linux.com/puppy/viewto ... 393#928393

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

Tested only in Tahr64. This is the most recent 'point upgrade' for version 60. Seems to be working quite nicely, boys'n'girls. I've added a little 'something extra' in /root/Startup; the Chrome version of the 'silent_launch' feature which I've been supplying with 64-bit SlimJet for the last few releases.

Essentially, it launches Chrome at boot-time, without actually opening it. This means Chrome's running in the background; when you go to launch it, all you're really doing is 'maximizing' it.....so it starts in the blink of an eye.

Enjoy.

Mike.

orrin · #160 Post by **orrin** » Sun 20 Aug 2017, 02:19

Mike Walsh wrote:***NEW VERSION***

Evening, everyone.

The current stable version, 60.0.3112.101, released 3 days ago, is now available for download from the usual location.

Hi mike,

This new version of Chrome loads, but does not run in Slacko 64-6.3.2!
Gone back to version 59.

jake29 · #161 Post by **jake29** » Sat 26 Aug 2017, 06:04

Thanks Mike, latest Slacko64 build is working well with FatDog64.

Mike Walsh · #162 Post by **Mike Walsh** » Sat 26 Aug 2017, 15:05

Glad to hear it, Jake.

It seems these builds are fine with the various FatDogs.....but Slacko64 seems to be the sticking pint. There's too much stuff 'missing'.

It's part of the reason why I gave up on Slacko64. Don't get me wrong; I love Micko's older Slacko builds.....they're some of the sweetest and most stable Pups in my kennels, but these 64-bit builds; I don't know. I doubt Micko's to blame; it's more to do with Slackware's policy of including as little as possible with the build itself, and leaving it up to the user to add everything required.....

Horses for courses. The 'buntu-based 64-bit builds just have so much 'extra' stuff included by default; it's why I prefer them these days, I guess.

I'm showing me age..!!

Mike,

belham2 · #163 Post by **belham2** » Sat 26 Aug 2017, 18:23

Hi ya, Mike!

Got around to finally getting rid of Opera in my frugal XenialPup64-7.0.8, and thought: I'll just install Mike's Slimjet. Then I saw this thread, and re-thought: ok, Google Chromey it is then

Downloaded Chromey, SFS-on-the-fly loaded it, and all is working good so far....especially the "silent-launch", tested after a reboot.

So, thank you very much!

Have a question though, best presented with a pic: "Uploaded from Belgium"? BELGIUM?? (hmmm, I always suspected you're an author-journalist-front M5-designated super Euro-spy, haha)

Mike Walsh · #164 Post by **Mike Walsh** » Sat 26 Aug 2017, 21:27

'Uploaded from Belgium...???'

No idea, mate. Don't have a clue what happened there, I'm a true-blue Brit, residing in the outer wilds of the Norfolk countryside...

I don't know where the f**k Belgium comes into it..!!

Methinks a wee bit of misdirectional re-routing is going on there.....especially considering MediaFire are based in Texas.

Mike.

orrin · #165 Post by **orrin** » Sun 27 Aug 2017, 21:32

Mike Walsh wrote:
Methinks a wee bit of misdirectional re-routing is going on there.....especially considering MediaFire are based in Texas.

OrgName: MediaFire, LLC
OrgId: ML-4
Address: PO BOX 9745
City: Spring
StateProv: TX
PostalCode: 77387-9745

It looks like a northern suburb of Houston.. I hope they are on high ground!

Mike Walsh · #166 Post by **Mike Walsh** » Sun 10 Sep 2017, 10:26

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 · #167 Post by **Mike Walsh** » Sun 10 Sep 2017, 19:40

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 · #168 Post by **Mike Walsh** » Tue 12 Sep 2017, 21:25

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 · #169 Post by **peebee** » Wed 13 Sep 2017, 12:35

Mike Walsh wrote: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 · #170 Post by **Mike Walsh** » Wed 13 Sep 2017, 14:26

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.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Google Chrome 64-bit packages - [CLOSED]