Chrome: Installation aborted by user

English Applications
1

Hi,
(new user here :slight_smile: )
When I try to install Chrome after I insert pasword, it starts to download packages and then I get: Installation aborted by user.

So I try with zypper and this is it: (I did rename the chrome file so it is not so long, it was downloaded from google page)

linux-yh8p:/home/bojan # zypper install chrome.rpm
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following 9 NEW packages are going to be installed:
  glibc-i18ndata google-chrome-stable kdelibs3-default-style libjpeg62 libpng12-0 lsb m4 patch qt3 

The following recommended package was automatically selected:
  kdelibs3-default-style 

9 new packages to install.
Overall download size: 45,8 MiB. Already cached: 6,1 MiB  After the operation, additional 196,0 MiB will be 
used.
Continue? [y/n/? shows all options] (y): y
Retrieving package libpng12-0-1.2.51-3.1.2.x86_64                       (1/9),  75,4 KiB (171,0 KiB unpacked)
Retrieving: libpng12-0-1.2.51-3.1.2.x86_64.rpm ........................................................[done]
Retrieving package m4-1.4.17-2.1.2.x86_64                               (2/9), 236,9 KiB (503,7 KiB unpacked)
Retrieving: m4-1.4.17-2.1.2.x86_64.rpm ..................................................[done (831,5 KiB/s)]
In cache qt3-3.3.8c-135.1.3.x86_64.rpm                                  (3/9),   2,7 MiB (  9,6 MiB unpacked)
In cache kdelibs3-default-style-3.5.10-83.1.10.x86_64.rpm               (4/9), 124,6 KiB (355,3 KiB unpacked)
In cache glibc-i18ndata-2.19-16.15.1.noarch.rpm                         (5/9),   3,1 MiB ( 10,8 MiB unpacked)
In cache libjpeg62-62.1.0-30.5.1.x86_64.rpm                             (6/9), 102,1 KiB (270,0 KiB unpacked)
In cache patch-2.7.5-7.7.1.x86_64.rpm                                   (7/9),  94,4 KiB (181,1 KiB unpacked)
In cache lsb-4.0-26.1.2.x86_64.rpm                                      (8/9),   8,5 KiB (  110   B unpacked)
Retrieving package google-chrome-stable-45.0.2454.85-1.x86_64           (9/9),  45,5 MiB (174,1 MiB unpacked)
chrome.rpm:
    Header V4 DSA/SHA1 Signature, key ID 7fac5991: NOKEY
    V4 DSA/SHA1 Signature, key ID 7fac5991: NOKEY

google-chrome-stable-45.0.2454.85-1.x86_64(Plain RPM files cache): Signature verification failed [4-Signatures public key is not available]
Abort, retry, ignore? [a/r/i] (a):
2

Well, as the message says: the package’s signature cannot be verified because the key is not available.
Choose ‘i’ for ignore to install it anyway.

3

All done. Thank you.:slight_smile:

4

Is this a bug at Google’s or OpenSuse’s end?

5

Depends on how you look at it.

The main problem is that the package is signed with an unknown key. If you added Google’s repo and installed it from there, you should get the key, otherwise you’d have to install it manually.

openSUSE’s software stack (zypper) became more strict regarding this in the last months. This is not really a bug though, I’d say… :wink:

Unfortunately, PackageKit cannot cope with such complications (it’s not designed for openSUSE in particular, it’s intended to be a general tool for all distributions), and just aborts instead of asking the user whether he wants to continue (and ignoring a possible security problem) or abort, like zypper does.

6

You can obtain the key from Google by going to https://www.google.com/linuxrepositories/ The page has instructions for installing the key. Follow them and then try installing Chrome again. It worked for me.