Some folk like to Install Chrome instead of Chromium (I don't know why).
If you must, it's easy. Simply search Google for: install google chrome. When you get there, locate "download" near the top of page and select the big button to DOWNLOAD and select the RPM option.
Suppose the download lands in the Download directory. The path to the file should look like this:
Code:
/home/YourName/Downloads/google-chrome-stable_current_x86_64.rpm
All you have to do now (that you know where it is) is open a console and switch to root, then enter this command:
Code:
zypper in /home/john/Downloads/google-chrome-stable_current_x86_64.rpm
A full dialogue will ensue, like this (copied from my console):
Code:
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following 16 NEW packages are going to be installed:
glibc-i18ndata google-chrome-stable libcairo-script-interpreter2 libjpeg62 libpng12-0 libpng15-15 lsb5 lsb5-core lsb5-desktop
lsb5-imaging lsb5-languages m4 ncurses-devel patch perl-Class-ISA tack
The following recommended package was automatically selected:
perl-Class-ISA
16 new packages to install.
Overall download size: 51.4 MiB. Already cached: 0 B. After the operation, additional 208.9 MiB will be used.
Continue? [y/n/? shows all options] (y): y
Retrieving package glibc-i18ndata-2.22-3.7.noarch (1/16), 3.2 MiB ( 10.9 MiB unpacked)
Retrieving: glibc-i18ndata-2.22-3.7.noarch.rpm ..........................................................................[done (1.7 MiB/s)]
.......A whole bunch of files are prepared
Retrieving package lsb5-5.0-2.1.x86_64 (15/16), 3.4 KiB ( 0 B unpacked)
Retrieving: lsb5-5.0-2.1.x86_64.rpm .................................................................................................[done]
Retrieving package google-chrome-stable-55.0.2883.87-1.x86_64 (16/16), 43.9 MiB (171.3 MiB unpacked)
google-chrome-stable_current_x86_64.rpm:
Header V4 DSA/SHA1 Signature, key ID 7fac5991: NOKEY
V4 DSA/SHA1 Signature, key ID 7fac5991: NOKEY
google-chrome-stable-55.0.2883.87-1.x86_64 (Plain RPM files cache): Signature verification failed [4-Signatures public key is not available]
Abort, retry, ignore? [a/r/i] (a): i
[my note: choose "i" for "ignore", press enter and everything will be good]
Checking for file conflicts: ........................................................................................................[done]
( 1/16) Installing: glibc-i18ndata-2.22-3.7.noarch ..................................................................................[done]
.......A whole bunch of files are installed
(16/16) Installing: google-chrome-stable-55.0.2883.87-1.x86_64 ......................................................................[done]
Additional rpm output:
warning: /var/cache/zypp/packages/_tmpRPMcache_/google-chrome-stable_current_x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 7fac5991: NOKEY
update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/google-chrome (google-chrome) in auto mode
Have a look at the blue lines. I coloured them in so you can see them. This is where the installation stops to say that the RPM didn't come with a signature key and what do you want to do about it. If you are sure you downloaded from Google, select to "ignore" by typing in a simple i and pressing enter. The installation should then proceed.
An aside: The process should install a Google Chrome repository during the installation so that you will have auto-access to all future updates.
That's all folks., be well.
Footnote 170214: Silverclipper has kindly added two interesting comments about installing the chrome repository and about dodging the public key issue if you are a stickler for security.
