What is the correct repository for chrome?

[https://en.opensuse.org/Additional_package_repositories Additional package repositories] lists [https://www.google.com/linuxrepositories/], but Yast gives an error message trying to add it. I saw a reference to [http://dl.google.com/linux/chrome/rpm/stable/x86_64] at a third party web site, but don’t know whether it is the correct one for LEAP 15.1. Which, if either, is the correct one and should I submit a ticket on the error message to get Additional package repositories updated?

Also, is this the correct forum for web browsers?

Please never only say "I got an error message, but always copy/paste (or copy in any other way) error messages you get in a post. Our crystal globes are far awya because of a lockdown.

Asking a bbout a web-browsers behaviour is IMHO asking about an application. Asking about instllation of anythinf=g (application or not) belongs IMHO in Install/…

But I guess, now it is here and people will try to help you, if you help them by showing your error message


erlangen:~ # zypper lr -uEP chrome
Alias          : chrome                                             
Name           : chrome                                             
URI            : http://dl.google.com/linux/chrome/rpm/stable/x86_64
Enabled        : Yes                                                
GPG Check      : ( p) Yes                                           
Priority       : 100 (lowered priority)                             
Autorefresh    : On                                                 
Keep Packages  : Off                                                
Type           : rpm-md                                             
GPG Key URI    :                                                    
Path Prefix    :                                                    
Parent Service :                                                    
Keywords       : ---                                                
Repo Info Path : /etc/zypp/repos.d/chrome.repo                      
MD Cache Path  : /var/cache/zypp/raw/chrome                         
erlangen:~ #

I’m not asking about the error message; I’m asking for the correct repository URL. I mentioned the error message from Yast only to provide context and to avoid being pointed at the web page that I had already seen. If the URL at the openSUSE web site is supposed to be current then I will, of course, quote the error text in any ticket that I create.

Does that include asking what repository to use?

Assuming what @karlmistelberger posted is accurate,
You should be able to add that repository to your openSUSE with the following command

zypper ar -f http://dl.google.com/linux/chrome/rpm/stable/x86_64 Google_Chrome_repository

Refresh your repostitories and accept the GPG key when prompted, then search for and install Chrome using either zypper or YaST.

Note that when you install Chrome, you will probably be prompted again that a signing key is missing because Chrome builds require another package to be installed from Google. You can safely instruct the install to ignore the error and continue. The alternative is to find the instructions from elsewhere how to obtain and install that signing key which IMO is more trouble than it’s worth for the one-time initial installation (All further updates shouldn’t prompt you for that key).

BTW - I don’t see it mentioned anywhere in this Thread that the open source Chromium is available for you in the default openSUSE repositories. Chromium is the open source build that provides the basis for Google to build their proprietary Chrome on top of. With Chromium, you should be able to do at least 90% of everything that can be done in Chrome, the main difference is support for certain types of Extensions.


Download the openSUSE Chrome .rpm from google.
Right click it and choose to install using “open with Yast software”
During installation it will also automatically add the correct repository to Yast for future updates.

Google provides concise and accurate information about how to install their software: Linux Software Repositories – Google

Note: Google’s Linux software packages will automatically configure the repository settings necessary to keep your Google Linux applications up-to-date. Please download and install packages from the appropriate product pages.

As an alternative users may add the following to their list of repos:

erlangen:~ # cat /etc/zypp/repos.d/chrome.repo 
erlangen:~ # 

Install using zypper:

erlangen:~ # zypper in google-chrome-stable
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.6 MiB. Already cached: 0 B. After the operation, additional 213.8 MiB will be used.
Continue? [y/n/v/...? shows all options] (y): 
Retrieving package libdbusmenu-glib4-16.04.0-7.1.x86_64                                  (1/5),  67.1 KiB (188.2 KiB unpacked)

Checking for file conflicts: ....................................................

Additional rpm output:
warning: /var/cache/zypp/packages/chrome/google-chrome-stable-80.0.3987.162-1.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 7fac5991: NOKEY
service: no such service atd
update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/google-chrome (google-chrome) in auto mode

erlangen:~ # 

Unless one is masochistic,
I wouldn’t follow generic steps to add a repository which not only requires multiple steps but would be much more susceptible to error.

Adding a repository as I described is not only simple (a command to add, then to refresh and accept the key if you didn’t include an option to automatically accept the GPG repository key) which can usually be accomplished in a few seconds, not minutes.


Straight users use copy and paste, which is done in seconds. But not all users use straight thinking. Note the difference:

erlangen:~ # diff -y /etc/zypp/repos.d/Google_Chrome_repository.repo /etc/zypp/repos.d/chrome.repo 
[Google_Chrome_repository]                                    | [chrome]
enabled=1                                                       enabled=1
autorefresh=1                                                   autorefresh=1
baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64     baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64
type=rpm-md                                                     type=rpm-md
                                                              > priority=100
                                                              > gpgcheck=1
                                                              > gpgkey=https://dl.google.com/linux/linux_signing_key.pub
erlangen:~ # 

Contrary to the claim made I did not get prompted for gpgkey when installing a new package from Google_Chrome_repository:

erlangen:~ # zypper lr -uEP Google_Chrome_repository
Alias          : Google_Chrome_repository                           
Name           : Google_Chrome_repository                           
URI            : http://dl.google.com/linux/chrome/rpm/stable/x86_64
Enabled        : Yes                                                
GPG Check      : (r ) Yes                                           
Priority       : 99 (default priority)                              
Autorefresh    : On                                                 
Keep Packages  : Off                                                
Type           : rpm-md                                             
GPG Key URI    :                                                    
Path Prefix    :                                                    
Parent Service :                                                    
Keywords       : ---                                                
Repo Info Path : /etc/zypp/repos.d/Google_Chrome_repository.repo    
MD Cache Path  : /var/cache/zypp/raw/Google_Chrome_repository       
erlangen:~ #

Users should be aware that installing a Google package tinkers with the list of their repos and watch /etc/zypp/repos.d for new entries they never added manually by running “zypper ar”.