Google Chrome 64-bit packages - [CLOSED]

Browsers, email, chat, etc.
Message
Author
orrin
Posts: 140
Joined: Tue 06 Sep 2016, 01:09
Location: sparks, NV
Contact:

#21 Post by orrin »

Mike Walsh wrote:Hi, orrin.

Mm. Yeah; tell me about it! AFAIK, the repositories are always way behind when it comes to the 'big' browsers....Chrome and FireFox. Mostly because they release new versions so often that the repository maintainers can't keep up with them. The bit that banks and other similar institutions are interested in are the certificates being up-to-date.

This is why I do the SFS packages for the community. I, too, needed to keep things up-to-date for online banking, and I got to thinking, 'Right; I can download the .deb packages for Chrome. It's easy enough to unpack them, re-arrange things in a way that will work with Puppy, and then re-package them again.' Only takes around 10 minutes or so now, since I have my scripts all semi-automated & set-up for maximum ease of use. And if they work correctly for me, then why not publish them and let other folks share the benefits?

For the 'buntu-based Pups, invariably all dependencies are satisfied already. Foe the Slackware-based Pups, the most they need to add are libgconf, and libgnomekeyring. Bob's yr uncle...sorted.

And the beauty of SFS packages is that they're really easy to uninstall and change when you want to upgrade. Just 'unload' the old one, then 'load' the new one. Your config and settings in /root/.cache and /root/.config don't need to be touched, since they'll carry on working from version to version.
I have been running an old version of OpenSuse for a long time and got
Puppy Slacko 64-6.3.2 so that I had up to date browsers. I still use SuSe
for record keeping and as it turns out, for the Adobe Reader.

I am not familiar with .sfs files. Is there a tutorial somewhere as to how
to install them in Slacko64, and getting them to run. I read that they
are copied to the mnt/home directory, but how do you run them, and
do I have to uninstall Chrome 46 or will the two versions co-exist.

If Chrome 46 is uninstalled, what happens to the extensions and settings.
Do they somehow carry over to the new version?

Help will be greatly appreciated!
[color=#FF0000]Engineer/Photographer/Webmaster[/color]
[img]https://i.postimg.cc/fL9MypfV/sig-image.png[/img]

dancytron
Posts: 1519
Joined: Wed 18 Jul 2012, 19:20

#22 Post by dancytron »

orrin wrote:
Mike Walsh wrote:Hi, orrin.

Mm. Yeah; tell me about it! AFAIK, the repositories are always way behind when it comes to the 'big' browsers....Chrome and FireFox. Mostly because they release new versions so often that the repository maintainers can't keep up with them. The bit that banks and other similar institutions are interested in are the certificates being up-to-date.

This is why I do the SFS packages for the community. I, too, needed to keep things up-to-date for online banking, and I got to thinking, 'Right; I can download the .deb packages for Chrome. It's easy enough to unpack them, re-arrange things in a way that will work with Puppy, and then re-package them again.' Only takes around 10 minutes or so now, since I have my scripts all semi-automated & set-up for maximum ease of use. And if they work correctly for me, then why not publish them and let other folks share the benefits?

For the 'buntu-based Pups, invariably all dependencies are satisfied already. Foe the Slackware-based Pups, the most they need to add are libgconf, and libgnomekeyring. Bob's yr uncle...sorted.

And the beauty of SFS packages is that they're really easy to uninstall and change when you want to upgrade. Just 'unload' the old one, then 'load' the new one. Your config and settings in /root/.cache and /root/.config don't need to be touched, since they'll carry on working from version to version.
I have been running an old version of OpenSuse for a long time and got
Puppy Slacko 64-6.3.2 so that I had up to date browsers. I still use SuSe
for record keeping and as it turns out, for the Adobe Reader.

I am not familiar with .sfs files. Is there a tutorial somewhere as to how
to install them in Slacko64, and getting them to run. I read that they
are copied to the mnt/home directory, but how do you run them, and
do I have to uninstall Chrome 46 or will the two versions co-exist.

If Chrome 46 is uninstalled, what happens to the extensions and settings.
Do they somehow carry over to the new version?

Help will be greatly appreciated!
sfs files a squash file system files like the main Puppy Linux sfs file. Puppy loads them underneath the main sfs file.

So, all you need to do is copy them to the same subdirectory as your main Puppy files, then find the "Load SFS on the fly" program and select and load them. You can also set them up to load automatically on boot in the Boot Manager program (I think, I'm not in Puppy right now to check).

I think you are going to have to uninstall your prior Chrome. That's because sfs files load underneath your save file/folder. However, if you are logged on to Google with it, when you relog in to Google, it should remember all your settings and reload your bookmarks and addons. It might be worth backing up your user profile (probably in /root/.config just in case that doesn't work.

see: http://puppylinux.org/wikka/sfsload


http://puppylinux.org/wikka/SquashFS

http://puppylinux.org/wikka/BootManager

User avatar
Mike Walsh
Posts: 6351
Joined: Sat 28 Jun 2014, 12:42
Location: King's Lynn, UK.

#23 Post by Mike Walsh »

Morning, orrin.

dancytron has the right of it. With SFS packages, it's all self-contained (and with mine, I always make sure that PepperFlash is up-to-date as well).

The actual package gets 'unloaded', then the new package gets 'loaded'. The configuration and settings at /root/.config & /root/.cache aren't touched, so these are straightaway read by the new version.

Yes, you do need to 'unload' the old package first. Either of two ways (both covered on the Wikka in dancytron's links):-

1) Right-click on the package and select 'sfs_load', or
2) Left-click on the package, and select 'Install'. If unloaded, it will ask if you wish to load, and if already loaded, if you wish to unload. It's pretty foolproof.

Then, just start your Chrome from the Menu entry.....or go into /usr/share/applcations, and 'drag' the .desktop entry onto the ROX pinboard (desktop, if you like.) This will then act as your desktop 'launcher'.

Anything else, just ask.

BTW:- If PepperFlash gets updated before the next version of Chrome comes out, you can update it with my PepperFlash .pets, from here:-

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

(To check the version of PepperFlash, and whether you're up-to-date, go here. Or, if you're in the US, here.)


Mike. :wink:

orrin
Posts: 140
Joined: Tue 06 Sep 2016, 01:09
Location: sparks, NV
Contact:

#24 Post by orrin »

Mike Walsh wrote:Morning, orrin.


Yes, you do need to 'unload' the old package first. Either of two ways (both covered on the Wikka in dancytron's links):-

Anything else, just ask.

BTW:- If PepperFlash gets updated before the next version of Chrome comes out, you can update it with my PepperFlash .pets, from here:-
I cannot find a way to unload Chome 46! It does not show-up when the uninstall button is pressed in the Package manager, and does not show
in the list under remove builtin packages.
Instuctions in the Wikka link is for earlier versions of Slacko. I have
Slacko 64-6.3.2.

My pepperflash is up to date!
[color=#FF0000]Engineer/Photographer/Webmaster[/color]
[img]https://i.postimg.cc/fL9MypfV/sig-image.png[/img]

User avatar
Semme
Posts: 8399
Joined: Sun 07 Aug 2011, 20:07
Location: World_Hub

#25 Post by Semme »

Terminal >> "sfs_load" should bring it up..

I avoid menus because excessive mouse pointing, and, or, typing, impede progress. :D
>>> Living with the immediacy of death helps you sort out your priorities. It helps you live a life less trivial <<<

orrin
Posts: 140
Joined: Tue 06 Sep 2016, 01:09
Location: sparks, NV
Contact:

#26 Post by orrin »

Semme wrote:Terminal >> "sfs_load" should bring it up..

I avoid menus because excessive mouse pointing, and, or, typing, impede progress. :D
That only brings up "libreOffice", no listing of Chrome.

Apparently the version in the repository that I loaded was not a .pet file! I notice that there is google-chrome-46.0.2490.86-1-x86_64.tar.xz in my root directory. That may be why the normal tools don't work!
[color=#FF0000]Engineer/Photographer/Webmaster[/color]
[img]https://i.postimg.cc/fL9MypfV/sig-image.png[/img]

orrin
Posts: 140
Joined: Tue 06 Sep 2016, 01:09
Location: sparks, NV
Contact:

#27 Post by orrin »

Thank you all for the help. I solved the problem by starting over with the CD and a different USB and reconfigured Poppy!

I used the sfs file for Chrome and it works fine
[color=#FF0000]Engineer/Photographer/Webmaster[/color]
[img]https://i.postimg.cc/fL9MypfV/sig-image.png[/img]

User avatar
Mike Walsh
Posts: 6351
Joined: Sat 28 Jun 2014, 12:42
Location: King's Lynn, UK.

#28 Post by Mike Walsh »

***NEW VERSION***

The current version, 53.0.2785.101 (with Pepper 22.0.0.209), released in the last 36 hours or so, is now available for download from the usual location..

Link as above in post #1.

Enjoy, as always. Any probs, you know where to find me.


Mike. :wink:

orrin
Posts: 140
Joined: Tue 06 Sep 2016, 01:09
Location: sparks, NV
Contact:

Chrome 64 sfs breakes CUPS

#29 Post by orrin »

Hello,

I discovered that when the Chrome sfs is loaded, Cups will not work.
When I unload the sfs, CUPS works fine.

Is there a way to make them co-exist so that I can print from a web page in Slacko 64-6.3.2?
[color=#FF0000]Engineer/Photographer/Webmaster[/color]
[img]https://i.postimg.cc/fL9MypfV/sig-image.png[/img]

gcmartin

#30 Post by gcmartin »

Seems, as I remember, Chrome can directly print to your LAN printer without going thru your PC. This doesn't fix anything, but, for some users, this solution is a blessing as it reduces the hardship on your PC for that print task. Again, this is NOT a suggestion to replace/fix anything locally, its just a print option that some may not be aware of in using the Chrome browser, IIRC.

Just an idea.

gcmartin

#31 Post by gcmartin »

@Mike. I used the Chrome for Slacko64 SFS. And have hit a problem. The "material design" component is missing on the browser. Was this feature deleted in the implementation?

Just a note: On @PeeBee's version it remains. So there must be something done different.

That component is general seen as the "pancake stack" or "hamburger" or "3 vertical dots" which resides in the upper right side of the browser screen.

I am running the latest Slacko64-V7a3. Is the component present on your browser in your distro?

User avatar
Mike Walsh
Posts: 6351
Joined: Sat 28 Jun 2014, 12:42
Location: King's Lynn, UK.

#32 Post by Mike Walsh »

Hi, gc.

You've lost me, mate. I haven't a clue what you mean by the 'material design'.

If you're talking about the three dots that have replaced the 'hamburger', yes they are indeed present. I'm posting from the new, current Chrome right now. But I'm using Slacko64 6.3.0, based on Slackware 14.1.....not 14.2. Not yet. I don't tend to jump into alpha & beta releases feet-first!

I much prefer to wait until they're at 'release candidate' stage, at the very least... I don't think the new Slacko64 will be there for a while yet. :)

The current Chrome SFS packages were built in Tahr64, and Slacko64-s14.1. So it's quite possible there will be 'hiccups', as Slackware transitions to the new variant. I'm running 14 Pups as it is. I don't intend adding any more for some time to come, I'm afraid.....and I never like building packages for any of my Pups until I'm absolutely happy with them.


Mike. :wink:

User avatar
Mike Walsh
Posts: 6351
Joined: Sat 28 Jun 2014, 12:42
Location: King's Lynn, UK.

#33 Post by Mike Walsh »

Evening, all.

Following orrin's discovery that loading the SFS breaks CUPS (which it does!), I've re-worked the packages (putting the permissions right). 'Twas my fault, I'm afraid; quite simply, I forgot to correct them this time around.

It's a well-known problem when converting .deb components into Puppy packages..!


Mike. :wink:

User avatar
Mike Walsh
Posts: 6351
Joined: Sat 28 Jun 2014, 12:42
Location: King's Lynn, UK.

Re: Chrome 64 sfs breakes CUPS

#34 Post by Mike Walsh »

orrin wrote:Hello,

I discovered that when the Chrome sfs is loaded, Cups will not work.
When I unload the sfs, CUPS works fine.

Is there a way to make them co-exist so that I can print from a web page in Slacko 64-6.3.2?
Hi again, orrin.

A-hem. (*Cough, cough...*) :oops: That shouldn't have happened. It was my fault.

I create the SFS packages using components from the .deb download from the Chrome website. The snag is (and it's a well-known one in 'Puppy-land') that .deb packages are set-up for Debian and Ubuntu (in fact, any Debian-based distro, as well). They're primarily multi-user systems.....unlike Puppy, which is essentially single-user, and that's why it runs as root.

Accordingly, the permissions are totally different to what Puppy runs with.....and when you forget to change them, invariably CUPS throws a wobbly. It's one of the first things affected by incorrectly-set Chrome packages, I'm afraid.

One of the folder entries in Chrome is the /etc directory. When it installs /etc/cron/google-chrome (the Chrome updater, which doesn't work under Linux in any case), it changes permissions on /etc. So /etc/CUPS isn't seeing what it expects to.....and misbehaves. Strangely, CUPS is the only thing that really seems to be affected by it..!

I tried it out myself, in Tahr64. I don't print often, so had no reason to check it. I, too, got the 'Internal Server Error' stuff you get when CUPS goes on the fritz.....so I knew straightaway what I'd forgotten to do..! Thanks for bringing it to my attention.

If you download the new package I've just uploaded (with permissions fixed, now), you'll find everything's working as it should.


Mike. :wink:

orrin
Posts: 140
Joined: Tue 06 Sep 2016, 01:09
Location: sparks, NV
Contact:

#35 Post by orrin »

Thanks Mike,

CUPS in the new version is no longer broken!

It works a bit strange though with my Canon MP990, when I try to print from
the Chrome print dialog, the printer comes on and does nothing! When I
check the job in CUPS, it is listed as failed. But if I click on reprint from Cups,
it prints OK. Strange..!! ... but that's off-topic for this thread!
[color=#FF0000]Engineer/Photographer/Webmaster[/color]
[img]https://i.postimg.cc/fL9MypfV/sig-image.png[/img]

User avatar
Mike Walsh
Posts: 6351
Joined: Sat 28 Jun 2014, 12:42
Location: King's Lynn, UK.

#36 Post by Mike Walsh »

Hi again, orrin.
orrin wrote:Thanks Mike,

CUPS in the new version is no longer broken!
Good, good; glad to hear it. I made sure it was all working in both my 64-bit Pups, so I knew it should have been OK for upload.

Re: CUPS in Slacko64. At least yours sounds as though it does work! I haven't, as yet, been able to get my Epson working at all in Slacko64.....yet it works beautifully in every other Pup I run.

How's that for inexplicable?

(*shakes head in exasperation*)


Mike. :wink:

orrin
Posts: 140
Joined: Tue 06 Sep 2016, 01:09
Location: sparks, NV
Contact:

#37 Post by orrin »

Mike Walsh wrote:
Re: CUPS in Slacko64. At least yours sounds as though it does work! I haven't, as yet, been able to get my Epson working at all in Slacko64.....yet it works beautifully in every other Pup I run.
I have very old Epson dot matrix that I finally got working in Slacko64...
First I had to add some code to /etc/rc.d/rc.local to get the parallel port
turned on. Then I found a ppd file for the LQ570 series on the net and
now it works just fine!
[color=#FF0000]Engineer/Photographer/Webmaster[/color]
[img]https://i.postimg.cc/fL9MypfV/sig-image.png[/img]

User avatar
Mike Walsh
Posts: 6351
Joined: Sat 28 Jun 2014, 12:42
Location: King's Lynn, UK.

#38 Post by Mike Walsh »

***NEW VERSION***

The current version, 53.0.2785.116 (with Pepper 23.0.0.162), released during the last 24 hours, is now available for download from the usual location.

Link as above in post #1.

Enjoy, as usual. Any probs, you know where to find me.


Mike. :wink:

orrin
Posts: 140
Joined: Tue 06 Sep 2016, 01:09
Location: sparks, NV
Contact:

#39 Post by orrin »

Mike Walsh wrote:***NEW VERSION***
The current version, 53.0.2785.116 (with Pepper 23.0.0.162), released during the last 24 hours, is now available for download from the usual location.
Link as above in post #1.
Enjoy, as usual. Any probs, you know where to find me.
Mike.
How is this diffferent from the previous version, and do I really need to
update since the one I have works just fine!
Both are Chrome 53.
[color=#FF0000]Engineer/Photographer/Webmaster[/color]
[img]https://i.postimg.cc/fL9MypfV/sig-image.png[/img]

User avatar
Mike Walsh
Posts: 6351
Joined: Sat 28 Jun 2014, 12:42
Location: King's Lynn, UK.

#40 Post by Mike Walsh »

Hi, Orrin.

Nah, there's very little change, TBH. One or two bits of sandbox code have been modified, and that's about it, really. I'm just trying to keep up with each release for anybody who may want them.....some folks are obsessive about always having the newest, most up-to-date version. 54 is out on the Beta channel, the Dev Channel is currently hosting 55, and I believe 56 is already being 'sketched-out' in the wings..!

'xx.-.----.---' is the major version, '--.-.xxxx.---' is the point release, and '--.-.----.xxx' is usually minor revisions to the point release.

'Newest ain't always the best.....'

Yours'll be fine for a while yet; just keep Pepper up to date, and you'll be laughing. The last version but one was out for around 6 weeks. This last couple, Google have released two updates in a matter of days; that's just how it goes, sometimes. Probably summat to do wi' the 'bug bounty' programme they constantly have running, which encourages users to email in with problems, in exchange for a reward.....

Go figure..! :roll:

My 32-bitters are quite happy with the final release Google did before dropping 32-bit support; 48.0.2564.116. Still plays NetFlix, so I'm happy, too!


Mike. :wink:

Post Reply