Google Chrome Installed Correctly?

darcode · March 23, 2020, 9:17am

Followed the instros from https://www.google.com/linuxrepositories/ but Dicover couldn’t install the package and failed with internal error, went the Zypper way and it seems to have worked, can anyone please explain the last part to me, the additional rpm output one, I’m trying to learn my way around openSUSE, thanks a lot.

dar@linux:/tmp/mozilla_dar0> wget https://dl.google.com/linux/linux_signing_key.pub
--2020-03-23 08:57:08--  https://dl.google.com/linux/linux_signing_key.pub
Resolving dl.google.com (dl.google.com)... 216.58.205.78, 2a00:1450:4002:807::200e
Connecting to dl.google.com (dl.google.com)|216.58.205.78|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 10218 (10.0K) [application/octet-stream]
Saving to: ‘linux_signing_key.pub’


linux_signing_key.pub                           100%======================================================================================================>]   9.98K  --.-KB/s    in 0.002s  


2020-03-23 08:57:08 (4.02 MB/s) - ‘linux_signing_key.pub’ saved [10218/10218]


dar@linux:/tmp/mozilla_dar0> sudo rpm --import linux_signing_key.pub
warning: Rebuilding outdated index databases
warning: Generating 18 missing index(es), please wait...
dar@linux:/tmp/mozilla_dar0> rpm --checksig -v google-chrome-stable_current_x86_64.rpm
google-chrome-stable_current_x86_64.rpm:
    Header V4 DSA/SHA1 Signature, key ID 7fac5991: OK
    Header SHA1 digest: OK
    V4 DSA/SHA1 Signature, key ID 7fac5991: OK
    MD5 digest: OK
dar@linux:/tmp/mozilla_dar0> sudo zypper install google-chrome-stable_current_x86_64.rpm
Loading repository data...
Reading installed packages...
Resolving package dependencies...


The following 5 NEW packages are going to be installed:
  google-chrome-stable libappindicator3-1 libdbusmenu-glib4 libdbusmenu-gtk3-4 libindicator3-7


5 new packages to install.
Overall download size: 60.4 MiB. Already cached: 203.8 KiB. After the operation, additional 213.8 MiB will be used.
Continue? [y/n/v/...? shows all options] (y): y
In cache libdbusmenu-glib4-16.04.0-6.1.x86_64.rpm                                                                                                         (1/5),  66.8 KiB (188.2 KiB unpacked)
In cache libindicator3-7-16.10.0+bzr20171205-3.1.x86_64.rpm                                                                                               (2/5),  44.5 KiB (110.8 KiB unpacked)
In cache libdbusmenu-gtk3-4-16.04.0-6.1.x86_64.rpm                                                                                                        (3/5),  54.6 KiB (156.5 KiB unpacked)
In cache libappindicator3-1-12.10.1+bzr20170215-7.1.x86_64.rpm                                                                                            (4/5),  38.0 KiB ( 88.7 KiB unpacked)
Retrieving package google-chrome-stable-80.0.3987.149-1.x86_64                                                                                            (5/5),  60.4 MiB (213.3 MiB unpacked)


Checking for file conflicts: ............................................................................................................................................................[done]
(1/5) Installing: libdbusmenu-glib4-16.04.0-6.1.x86_64 ..................................................................................................................................[done]
(2/5) Installing: libindicator3-7-16.10.0+bzr20171205-3.1.x86_64 ........................................................................................................................[done]
(3/5) Installing: libdbusmenu-gtk3-4-16.04.0-6.1.x86_64 .................................................................................................................................[done]
(4/5) Installing: libappindicator3-1-12.10.1+bzr20170215-7.1.x86_64 .....................................................................................................................[done]
(5/5) Installing: google-chrome-stable-80.0.3987.149-1.x86_64 ...........................................................................................................................[done]
Additional rpm output:
service: no such service atd
update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/google-chrome (google-chrome) in auto mode

malcolmlewis · March 23, 2020, 2:52pm

Hi
I’m guessing this bit;


Additional rpm output:
service: no such service atd
update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/google-chrome (google-chrome) in auto mode

So google in it’s wisdom IMHO is a bit sneaky (or helpful…?) in the rpm the have a post install script that sets a ‘at’ job to run (zypper if at) adding their repo, so atd command is the daemon and is by default not installed so the job fails, not to worry because they also install a cron job (going forward it should be a systemd service and timer entry). In saying that again, google being sneaky again as this now leaves a cron job to add the repo, check for updates. I always remove the cronjob and disable the repo, if I need an update can re-enable and update as the system admin and not letting a third party determine what and how will run on my system(s)

The update-alternatives is used to determine the default commands to be run, for example with multiple versions of say java or gcc, as root user your can use this command to say use gcc7 or gcc9 as the default symbolic link to gcc. If you as root user run the command update-alternative --all and just press enter you can go down through each item to determine the system defaults.

More info via update-alternatives --help or man update-alternatives.

darcode · March 24, 2020, 10:06pm

malcolmlewis:

Hi
I’m guessing this bit;
Additional rpm output:
service: no such service atd
update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/google-chrome (google-chrome) in auto mode
So google in it’s wisdom IMHO is a bit sneaky (or helpful…?) in the rpm the have a post install script that sets a ‘at’ job to run (zypper if at) adding their repo, so atd command is the daemon and is by default not installed so the job fails, not to worry because they also install a cron job (going forward it should be a systemd service and timer entry). In saying that again, google being sneaky again as this now leaves a cron job to add the repo, check for updates. I always remove the cronjob and disable the repo, if I need an update can re-enable and update as the system admin and not letting a third party determine what and how will run on my system(s)

The update-alternatives is used to determine the default commands to be run, for example with multiple versions of say java or gcc, as root user your can use this command to say use gcc7 or gcc9 as the default symbolic link to gcc. If you as root user run the command update-alternative --all and just press enter you can go down through each item to determine the system defaults.

More info via update-alternatives --help or man update-alternatives.

Thank you very much indeed for your comprehensive reply, that’s exactly what I needed, appreciated.

karlmistelberger · March 25, 2020, 8:12am

malcolmlewis:

Hi
I’m guessing this bit;
Additional rpm output:
service: no such service atd
update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/google-chrome (google-chrome) in auto mode
So google in it’s wisdom IMHO is a bit sneaky (or helpful…?) in the rpm the have a post install script that sets a ‘at’ job to run (zypper if at) adding their repo, so atd command is the daemon and is by default not installed so the job fails, not to worry because they also install a cron job (going forward it should be a systemd service and timer entry). In saying that again, google being sneaky again as this now leaves a cron job to add the repo, check for updates. I always remove the cronjob and disable the repo, if I need an update can re-enable and update as the system admin and not letting a third party determine what and how will run on my system(s)

Chrome comes with a nice post install script even suitable for openSUSE/zypper. To check the actions before installing run: rpm -qp --scripts google-chrome-stable_current_x86_64.rpm If in doubt run rpm --install --noscripts and then manually select and run the parts you actually want to have done, e.g updating application starter menu, adding the repo holding the package, configuring alternatives stable, beta, unstable and more.

malcolmlewis · March 25, 2020, 1:29pm

Hi
Yes that’s an option, but still should advise an end user to what is happening in the post install output.

karlmistelberger · March 25, 2020, 1:57pm

I agree. But it never hurts to know about things happening silently.