Google Chrome 64-bit packages - [CLOSED]

[Mike Walsh]

Now you have to re-edit the thread title to get rid of the "Now running as SPOT"

Whoops..!!

Forgot that; thanks for reminding me... What am I like, eh??


Mike.

[orrin]

Chrome 56 is giving me SSL errors on some sites like
https://dnsquery.org/

The error I get is:

This site can’t provide a secure connection

dnsquery.org sent an invalid response.
ERR_SSL_PROTOCOL_ERROR

Google must have changed something in version 56!

I've gone back to version 55 which works on the above site
without errors!

[jake29]

YouTube html5 720p video playback in 56.0.2924.87 started having issues in the last 7 days or so for me. Very high CPU Usage, resulting in choppy playback. OS is FatDog64 710. Have been using Chrome for many months and not observed this issue before. Infact, being able to watch 720p60 video was the primary reason I started using Chrome.

Change to flash video playback and there are no problems.

Disabling HW Acceleration doesn't help. Perhaps it's a video driver issue on my setup - only posting to see if anyone knows more.

[Mike Walsh]

Morning, Jake.

Wouldn't like to say what's going on here, TBH. Not only Google, but YouTube, seem to have been engaged in a spell of 'chase the monkey' for the last few weeks; changing stuff virtually at random, seemingly on a whim.....and changing back as often as there are days in the week (often breaking other stuff between changes back & forth).

Of course, YouTube is under Google's jurisdiction, so you would think they'd have at least that one working correctly. Currently I'm 'beta-testing' 57.0.2987.74. As of this moment, YouTube seems to be behaving itself perfectly; mind you, I can't test 720p, since I've only got an elderly 1024 x 768 monitor.....it would be rather pointless!


Mike.

[jake29]

Just a follow-up post regarding the problem I was having with YouTube HD videos.

After doing a clean install of Fatdog64 710, the issue is pretty much gone. I still get the occasional stutter when changing from full-screen to windowed with YouTube 720p60 video - but playback is otherwise much smoother. That may have always been the case and probably the best I can expect from my core2duo.

CPU usage has gone down from consistently 95%+ to as low as 70%. I'm almost certain now the issue was due to GPU Drivers, which I have not messed with this time around.

In conclusion, Google / YouTube are not to blame; rather my own misadventures in driver compiling.

[Mike Walsh]

***NEW VERSION***

Afternoon, all.

The current version, 57.0.2987.98, released yesterday, 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/

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

This ought to run OK, without any problems.....as usual, I've been 'beta-testing' for a while. 2 or 3 major changes to report:-

1 ) The biggest is WebAssembly support, which is a new standard for 'packing' & delivering web pages.

2 ) CSS Grid Layout; this is a new feature for web developers, enabling a new method for layout of items on web pages, which doesn't require 100's of lines of CSS code for every change, and allows much smoother page resizing. And finally,

3 ) Media Session API. This is primarily for Android, and allows developers to push rich media content to notifications.

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

The major security 'fix' is related to the total deprecation of SHA-1 certificates; these are now distrusted by default.

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

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

After this, the new 'fingerprinted' PepperFlash will download automatically to ~/.config/google-chrome/PepperFlash, and will also be deployed automatically, without you needing to do anything.

Any probs, you know where I am.


Mike.

[orrin]

Version 57 seems to be working OK here. It's now my backup browser!
I like Slimjet better and use it most of the time.

Thanks for your efforts!

[Mike Walsh]

Hi, orrin.

You're very welcome, mate.....and I'm pleased to hear about 'Slimmie', by the way. I tend to use it quite a lot myself.....but I still keep up with Chrome, simply 'cos I've been using it for so long.

I'll be doing a new 64-bit release of SlimJet pretty soon. I don't do every release, 'cos FlashPeak pop out another one every few days, seemingly; I'd never be away from it if I gave in to it!


Mike.

[Mike Walsh]

***NEW VERSION***

Afternoon, all.

The current version, 57.0.2987.110, released yesterday, 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

After this, the new 'fingerprinted' PepperFlash will download automatically to ~/.config/google-chrome/PepperFlash, and will also be deployed automatically, without you needing to do anything.

You know where to find me.


Mike.

[Mike Walsh]

Afternoon, all.

Just as an aside, I can reveal that version 58, when it makes its appearance, will in all likelihood be missing highlighting in the bookmark listings. This is currently the case with the 'beta' of 58, which I'm testing ATM. It'll probably carry over to the 'stable' 58, when it's released.

This means that ya gotta make sure sure that the tip of your cursor is right on top of the bookmark you want to use.....because there's no indication now. I suspect this is line with their new 'Modern UI' as they call it (part of which was the change from the 'hamburger' Menu symbol to the the current 'three dots'.)

The other cosmetic change seems to be with the 'tooltips', which instead of black text on a white field, are now inverted; white text on a black field instead. Slightly uglier, IMHO.

It is, of course, also in line with integrating everything in with Chrome OS and Android later on this year.....something else to watch out for!

Memory usage, is improving all the time. An important plus point, considering Chrome used to be a serious RAM hog!


Mike.

[Mike Walsh]

***NEW VERSION***

Evening, all.

The current version, 58.0.3029.81, released yesterday, 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

After this, the new 'fingerprinted' PepperFlash will download automatically to ~/.config/google-chrome/PepperFlash, and will also be deployed automatically, without you needing to do anything. If you're upgrading from the previous version, and haven't touched /root/.cache and/or /root/.config, then Pepper will continue to upgrade without you needing to touch anything at all.

As fully expected, the new design 'cues' have, indeed, carried over to the new stable release.....

Enjoy, as always.


Mike.

[orrin]

Hello Mike,

Got version 58 and so far no problems. It seems a bit more
sluggish with video as compared to Slimjet on my slow DSL connection.

[ethplorer]

anyone also can tell me where to find an sfs or pet of chrome for slacko? got some pet_packages from ibiblio.org but seem not working.

found it on https://www.mediafire.com/folder/l8lkuo ... ayv78nd0ip

thanks mike. does it work on slacko?

[orrin]

anyone also can tell me where to find an sfs or pet of chrome for slacko? got some pet_packages from ibiblio.org but seem not working.

found it on https://www.mediafire.com/folder/l8lkuo ... ayv78nd0ip

thanks mike. does it work on slacko?

I'm running Slacko 64-6.3.2 and Mikes sfs works just fine!

[Mike Walsh]

Hi, ethplorer.

What on earth possessed you to consider those old versions? Some of them are 5 years old or more.....

The only reason they were in 'My Packages' at all was because I was experimenting with old versions in a couple of truly ancient lappies, and it was easier to transfer using the cloud, since they were several miles apart at the time!

(The 'sneakernet' has it's limitations, y'know.....? )

When you say you're using Slacko, which version? There's plenty of 'em to choose from. 32-bit or 64? 6-series, or one of the older 5-series?

Personally, I run Slackos 5.6 & 5.7, X-Slacko 2.3.2, and Slacko64 6.3.0 (the version prior to orrin's.)

Need to know which one, please. Then I can make my advice a wee bit more 'informed...'


Mike.

[Mike Walsh]

***NEW VERSION***

Evening, all.

The current stable version, 59.0.3071.86, released yesterday, 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

There's a shed-load of 'fixes' in this new release; more so than usual. One interesting feature is that Chrome can now run in what's called 'headless' mode, for devs who want to test out code without running the UI.

Have fun.


Mike.

[orrin]

Evening, all.

The current stable version, 59.0.3071.86, released yesterday, is now available for download from the usual location.

For some reason, version 59 will not start in my Slacko 64-6.3.2!

I went back to version 58!

[jake29]

Cannot start 59.0.3071.86 (Slacko64 build) in Fatdog64. No issues with previous versions.

Code: Select all

# google-chrome
/usr/bin/google-chrome: error while loading shared libraries: libgtk-3.so.0: wrong ELF class: ELFCLASS32

[Mike Walsh]

@ orrin, jake29:-

Hm. Odd. I've been 'beta' testing Chrome 59 till very recently, and it's been running perfectly in Slacko64 (though my version is the original 6.3.0). There could be a different layout for some things in 6.3.2; that's the UEFI version, isn't it?

@Jake:-

Libgtk-3.so.0... You're running FatDog, yes? My guess is you've got the same problem that exists in Slacko64. In Tahr, /usr/lib64 is symlinked into /usr/lib.....so any 64-bit ELF will show up in both directories. Slacko, on the other hand, doesn't have this sym-link.....so libs must go into the correct directory to start with. I always have this problem when I'm constructing .pets or SFS packages for both of these 64-bit Pups; if there's any scripts involved that call for libs in one location or the other, I always have to write the Slacko version differently to the Tahr version, to take account of this.

Have a look in /usr/lib, and in /usr/lib64. Check 'Properties for libgtk-3.so.0, when you find it.....and let me know what ELF class each one gives, please? You may need to add a sym-link in for libgtk-3.so.0, though I'm surprised that it's suddenly giving problems with this release, especially given that the beta of 59 has worked flawlessly.

The problem being, of course, that there's no way to open up the Chrome binary in opt/google/chrome, to see what paths they've coded into it..... If there is, I don't know how you do this, I'm afraid.


Mike.

[jake29]

@Jake:-

Libgtk-3.so.0... You're running FatDog, yes? My guess is you've got the same problem that exists in Slacko64. In Tahr, /usr/lib64 is symlinked into /usr/lib.....so any 64-bit ELF will show up in both directories. Slacko, on the other hand, doesn't have this sym-link.....so libs must go into the correct directory to start with. I always have this problem when I'm constructing .pets or SFS packages for both of these 64-bit Pups; if there's any scripts involved that call for libs in one location or the other, I always have to write the Slacko version differently to the Tahr version, to take account of this.

Have a look in /usr/lib, and in /usr/lib64. Check 'Properties for libgtk-3.so.0, when you find it.....and let me know what ELF class each one gives, please? You may need to add a sym-link in for libgtk-3.so.0, though I'm surprised that it's suddenly giving problems with this release, especially given that the beta of 59 has worked flawlessly.

Yes, I'm running the latest Fatdog64 (v710).

Code: Select all

# file libgdk-3.so.0
libgdk-3.so.0: symbolic link to libgdk-3.so.0.1800.7
# file libgdk-3.so.0.1800.7
libgdk-3.so.0.1800.7: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, stripped

libgtk-3.so.0 exists in /usr/lib, but not /usr/lib64. Adding it to the latter returns the same error.