Signature verification for Repository NVIDIA failed

Getting this error in Tumbleweed the last week or so. I did a search and had a hit from 2011 in zypper. I’m not having the problem there. Back then…10 years ago many adviced to wait for it to be fixed.

As a matter of fact. The manual “zypper refresh” reports “Repository ‘NVIDIA’ is up to date.”

bill@bill-MS-7B79:~> sudo zypper refresh
[sudo] password for root:  
Repository 'Atom Editor' is up to date. 
Repository 'Google-Chrome' is up to date. 
Repository 'NVIDIA' is up to date. 
Retrieving repository 'Node.js (openSUSE_Tumbleweed)' metadata ...............................................................................................................[done]
Building repository 'Node.js (openSUSE_Tumbleweed)' cache ....................................................................................................................[done]
Repository 'Main Repository (NON-OSS)' is up to date. 
Repository 'Main Repository (OSS)' is up to date. 
Repository 'Main Update Repository' is up to date. 
Retrieving repository 'google-chrome' metadata ...............................................................................................................................[done]
Building repository 'google-chrome' cache ....................................................................................................................................[done]
Repository 'packman-essentials' is up to date. 
Retrieving repository 'vscode' metadata ......................................................................................................................................[done]
Building repository 'vscode' cache ...........................................................................................................................................[done]
All repositories have been refreshed.
bill@bill-MS-7B79:~>

At first I thought…could it be possibly related to the “failed to update” error I get when 1st signing on? It’s Almost as if it needs a few more seconds (a short pause if you will) to establish connection before attempting to update. Answer…NO. I clicked the “Check for Updates” button in the Software Updates GUI panel and got the same thing!