tom@, by chance do you have any inputs here?

Thank you!

+mmoss.  The same subkey issue?

I don't think this is directly related to the subkey issue, although maybe there were other errors introduced as part of those packaging changes.

Does the /etc/cron.daily/google-chrome* cron job get installed? If it does, it should should periodically try to setup the repo config if for some reason it didn't get setup during the initial install.

Was this an upgrade or a fresh install? It looks like you're installing a newly downloaded RPM, but the log says "going to be upgraded", so it's a little unclear. If it is an upgrade, was the Chrome repo configured and working before? Is it possible it was previously disabled/deleted (in which case, reinstalling/upgrading won't enable it)?

> Does the /etc/cron.daily/google-chrome* cron job get installed? If it does, it should should periodically try to setup the repo config if for some reason it didn't get setup during the initial install.

Yes, the cron job is there:

suse-laptop:~ # ls -l /etc/cron.daily/google-chrome
-rwxr-xr-x 1 root root 15142 Aug  2 04:20 /etc/cron.daily/google-chrome
suse-laptop:~ #

> Was this an upgrade or a fresh install?

Upgrade.

> It looks like you're installing a newly downloaded RPM, but the log says "going to be upgraded", so it's a little unclear.

I downloaded the package to update my existing Google Chrome installation because I noticed the Google Chrome repository was not previously added and activated and Chrome consequently not updated.

> If it is an upgrade, was the Chrome repo configured and working before?

No.

> Is it possible it was previously disabled/deleted (in which case, reinstalling/upgrading won't enable it)?

No.

@mmoss-- Could you please look into the comment #4 and respond to it.

Thanks!

@mmoss -- Friendly ping to look into this issue as per the comment #4.

Thanks.

@mmoss/@thomasanderson,
Friendly ping!!

Could you please look into this issue & update the thread accordingly.
Thank you..!

As a heads-up, the issue still persists with the current version of Google Chrome downloaded from google.com/chrome. There is no repository set up and I have to download new versions manually.

Thank you for providing more feedback. Adding requester "jmukthavaram@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Assigning to mmoss@ for more inputs based on C#4. 

Hello, any news about this issue? Not fixed yet.

Chrome 64 is still affected:

glaubitz@suse-laptop:~> zypper info google-chrome-stable
Loading repository data...
Reading installed packages...


Information for package google-chrome-stable:
---------------------------------------------
Repository     : @System                                 
Name           : google-chrome-stable                    
Version        : 64.0.3282.119-1                         
Arch           : x86_64                                  
Vendor         : Google Inc.                             
Installed Size : 177.6 MiB                               
Installed      : Yes                                     
Status         : up-to-date                              
Source package : google-chrome-stable-64.0.3282.119-1.src
Summary        : Google Chrome                           
Description    :                                         
    The web browser from Google

    Google Chrome is a browser that combines a minimal design with sophisticated technology to make the web faster, safer, and easier.

glaubitz@suse-laptop:~> zypper lr
Repository priorities in effect:                                                                                                            (See 'zypper lr -P' for details)
      50 (raised priority)  :  1 repository  
      99 (default priority) : 14 repositories

#  | Alias                                         | Name                                                                | Enabled | GPG Check | Refresh
---+-----------------------------------------------+---------------------------------------------------------------------+---------+-----------+--------
 1 | Cloud_Tools                                   | Cloud:Tools (openSUSE_Tumbleweed)                                   | Yes     | (r ) Yes  | Yes    
 2 | Cloud_Tools_azuresdkbreak                     | Break up Azure SDK (openSUSE_Tumbleweed)                            | No      | ----      | ----   
 3 | SUSE_CA                                       | SUSE Internal CA Certificate (openSUSE_Tumbleweed)                  | Yes     | (r ) Yes  | Yes    
 4 | devel_languages_python                        | Python Modules (openSUSE_Tumbleweed)                                | Yes     | (r ) Yes  | No     
 5 | devel_languages_python3                       | Python-3 modules (openSUSE_Tumbleweed)                              | No      | ----      | ----   
 6 | devel_tools_compiler                          | Various compilers (openSUSE_Factory)                                | Yes     | (r ) Yes  | No     
 7 | home_FrodeSolheim_devel                       | home:FrodeSolheim:devel (openSUSE_Tumbleweed)                       | No      | ----      | ----   
 8 | home_FrodeSolheim_stable                      | home:FrodeSolheim:stable (openSUSE_Tumbleweed)                      | No      | ----      | ----   
 9 | home_glaubitz_branches_devel_languages_python | Branch project for package python-azure-batch (openSUSE_Tumbleweed) | Yes     | (r ) Yes  | No     
10 | http-download.opensuse.org-1032d401           | devel:languages:python                                              | Yes     | (r ) Yes  | Yes    
11 | http-download.opensuse.org-cd492a31           | X11:RemoteDesktop:x2go                                              | Yes     | (r ) Yes  | Yes    
12 | http-download.opensuse.org-f81d5448           | openSUSE:Tumbleweed                                                 | Yes     | (r ) Yes  | Yes    
13 | packman                                       | Packman repository (openSUSE_Tumbleweed)                            | Yes     | (r ) Yes  | No     
14 | repo-debug                                    | repo-debug                                                          | No      | ----      | ----   
15 | repo-non-oss                                  | repo-non-oss                                                        | Yes     | (r ) Yes  | Yes    
16 | repo-oss                                      | repo-oss                                                            | Yes     | (r ) Yes  | Yes    
17 | repo-src-non-oss                              | repo-src-non-oss                                                    | Yes     | (r ) Yes  | Yes    
18 | repo-src-oss                                  | repo-src-oss                                                        | Yes     | (r ) Yes  | Yes    
19 | repo-update                                   | repo-update                                                         | Yes     | (r ) Yes  | Yes    
20 | skype-stable                                  | skype (stable)                                                      | Yes     | (r ) Yes  | Yes    
glaubitz@suse-laptop:~>

@adrian - FYI, I think this issue was fixed in Chrome 67.0.3396.79.

Odd, I just installed google-chrome-stable-67.0.3396.79-1.x86_64, but I don't see any Chrome repository added. Do I need to purge the old package first?

@adrian - Please check if you have the fix by doing:

grep 'SUSE LINUX' /etc/cron.daily/google-chrome

If you have the fix, you should see:
    "SUSE LINUX"|"openSUSE")

If you have the fix, then do:

cat /etc/default/google-chrome

If you see "false", edit that file (as the root user) and replace "false" with "true". The repo should be added the next time the daily cron runs. If you don't want to wait a day, you could delete the /var/spool/cron/lastrun/cron.daily file (as the root user) and then the repo should get added after the next 00, 15, 30, or 45 minutes past the hour.

If you don't have the fix, you could try removing the google-chrome-stable package. Then remove /etc/default/google-chrome and /etc/cron.daily/google-chrome if they still exist. Finally, reinstall the google-chrome-stable package.