Going to googles official webpage will tell you how to get chrome for Debian/Ubuntu/Opensuse/Fedora. This is about as good as it can be because chrome is closed source.
I just downloaded the official Chrome .deb and did a sudo dpkg -i foo.deb.
Can't understand how that would fail, really. One thing you might try is doing an apt-get install -f, since there might be implicit dependencies depending on the build, and this forces apt to figure them out.
Google's solution for Chrome on Debian and Ubuntu is to distribute a .deb package that installs not only Chrome, but also installs a reference to their own package repository. When the user updates packages on their system, it updates Chrome from Google's repository. Chrome does not update itself, nor can it, since the package installs it to /usr/bin, which would require a su/sudo prompt to get access to.
Chrome's auto-update feature on Debian-based distributions at least consists of it installing its apt repository in your sources.list. Which is fine by me.
The problem is that the Nouveau (and Ubuntu) devs have no way to overturn Googles decision in Chrome. Ubuntu can compile Chromium with a modified blacklist but Google distributes Chrome in a deb. You would need some special logic to catch the Chrome .desktop on install and add in the unblacklist flag.
I'm using Chrome on my personal laptop running Debian 9 since Firefox is still a minor pain on Debian. The "firefox-esr" package is based on version 52 and it's become usable again (IMO) since 56.0 or so - where I switched on my Windows based work laptop. The alternatives to using firefox-esr are OK but a bit fiddly - extract a tar.gz somewhere and add to PATH or muck around with symlinks, or install via apt using an unsupported third party (Ubuntu) package source.
That's my excuse, not great but switching is on my TODO :-)
Debian patched the Chromium browser to refuse to install or update add-ons from the Chrome store. At first I found this annoying, but I am coming around to their way of thinking--that ultimately I can only trust software in the Debian archive.
32 bit: http://www.google.com/chrome/intl/en/eula_dev.html?dl=unstab...
64 bit: http://www.google.com/chrome/intl/en/eula_dev.html?dl=unstab...
I've used the 32 bit package on Ubuntu (9.10 beta) and Debian testing the last weeks, no problems so far.
reply