My word, I hope not. You're one of the saner ones around here.

1 members found this post helpful.

Oh well, Google Chrome 49 is out, fixing around a dozen CVEs of various shapes and sizes, and not a 32bit version to be seen!

1 members found this post helpful.

I tried it and got rid of it when I could not find any features at all

I have both installed (Google-Chrome and Vivaldi) and Vivaldi is really faster to load and more customizable than Google-Chrome, it has mouse gestures that allow me open new tabs, return to previous/next opened sites, save open tabs during researches for further works, etc, but web browser is a matter of taste and practice, I used to like Google-Chrome, it was my favourite until I try Vivaldi that is based on Chromium.

1 members found this post helpful.

Vivaldi is giving its version of Blink many of the features of the "old" Opera 12.x (presto engine) and I like what I have seen. IF and when it stops calling home, I'll consider using it full time, but for now SeaMonkey has been a more than adequate replacement for the "old" Opera.

Just a word of warning and advice, especially for users of Slackware. It really is safest to never trust auto-updaters and just spend the extra few minutes to do it yourself. For me the best feature of Slackware is that nothing happens that I don't do or allow so I always know where to look if any difficulties present themselves. I find this pays me back for those few minutes many times over. It amazes me how many people try to make Slackware "more convenient" missing the losses they can incur by breaking with the basic philosophy of Slack. Nobody, let alone someone's software, knows your system like you do.

3 members found this post helpful.

Thanks, mate. Updated my boxen to 49.0.

What is the problem for you again? I recall your concerns when I was at Opera but I think we have all this covered at Vivaldi. Open vivaldi://settings/privacy and uncheck whatever you don't like.

I'm not sure you looked very hard.

Here this might help http://vivalditips.com It does not include all of our features but it has most of them and is a good starting point.

Yes, the "new" opera does that and Vivalida, still, also calls home or somewhere, but it is calling out.
I wrote down the URLs.... let me see if I can find my notes....
The first one was 104.20.64.251, and you get a page with a message from some outfit called Cloud Flare saying, "direct access is not allowed." The second was 173.194.79.105, which, IIRC, was something to do with google.

In the meantime, I've switched from SeaMonkey-2.39, which hasn't been updated in 4 months, to Firefox-45. It is a nice improvement over previous versions of Firefox.

You can just download the 64bit deb version of chrome; extract it and as root, move
the contents of ~/Downloads/opt/google/chrome directory to /opt/google/chrome

Make a ~/Downloads/chrome directory.

Go to: https://www.google.com/chrome/browser/desktop/

Download the 64 bit Debian version to your ~/Downloads/chrome directory.

Open a terminal and $ cd ~/Downloads/chrome

$ ar -x google-chrome-stable_current_amd64.deb

$ tar -xvJf data.tar.xz

Only care about the /opt directory that is created. Nothing else.

Check if you've already got a /opt/google/chrome directory. If so rename it chrome.old or something.

$ sudo cp -r /home/YourUsername/Downloads/chrome/opt/google/chrome /opt/google

$ sudo chown -R root:root /opt/google/chrome/*

$ sudo chmod 4755 /opt/google/chrome/chrome-sandbox

Make a link, icon, whatever to /opt/google/chrome/google-chrome

2 members found this post helpful.

Way too many steps coldbeer! You can knock it back to just two, if you want a basic install.

As root issue:

P.S. Why do people always fetch a .deb to use as a basic install or repack, when it is a two step process to unpack, while a .rpm is just one?

P.P.S. You do not need "J" on a tar decompress (leave it off and you will see it works just fine).

@cwizardone this is after disabling the various things listed in vivaldi://settings/privacy (e.g. unchecking "Report Diagnostics", "Enable Google Phishing and Malware protection")??

Also which Vivaldi version did you last check with?

In the case of google-chrome.SlackBuild, I used the .deb for Ubuntu because the shared libraries they had linked against seemed to be a closer match to our own set. Whether this is still true, I don't know. But the point remains that the binaries in a .deb may be different than the ones in an .rpm, which might be a more important issue than which package format can be unpacked in the least number of steps.

2 members found this post helpful.

Nothing new , google team say some months a go , removing 32bit !BINARY ,packages support.

Then , no more VERSION-i386.deb or rpm , but , google team say NO REMOVE 32 BITS from sources.

At this point can build 32 bits packages from sources...later need to build separately the pepper flash.

Of course , pretty nice when *.deb or *.rpm packages because are "all in one" packages last chrome + latest pepper flash.

The ruario script , drop the 32bit support.


if some one want 32 bit support , need to build from sources...or go with Alien chromium binary packages.