Noob here. See here —> https://paste.opensuse.org/pastes/55a51b26348f
Chrome repo signing key errors. I got this error today and yesterday. What should I do? Anyone else getting these errors?
Anyone know why these errors are happening?
1 Like
I first got the error yesterday. Today, I posted a thread out at the Google Chrome forum. The link is in the thread that @nrickert posted above. I’ll put it here too …
So far, Google hasn’t been able to fix it, or determine the issue.
I installed Chrome on two other openSUSE machines today, that have never had Chrome installed … they now get the error too. And I installed it two different methods.
I suggest creating a new thread at Google Chrome so they see this isn’t just one or two people getting the error.
And maybe add a comment to my thread, “I see the same issue”
Link to my thread
https://support.google.com/chrome/thread/453694878/chrome-on-linux-os-will-not-update?hl=en
1 Like
Ok, so it’s not just me, good to know. I’ll follow the link soon to learn more. Hopefully Google fixes it soon. This morning I disabled the Chrome repo and was able to successfully run sudo zypper dup.
1 Like
Sort of sad really. Google which touts have the “smartest people on the planet” and obviously has more money than money, can’t figure this out??
1 Like
I have the same here for the last couple of days too. I have added that to your thread over at Google.
2 Likes
What’s even worse, is that Chrome forum software. It’s highly restrictive in what you can post. So, the Admin responding to my thread, has asked for the output of commands xx, yy, zz, etc. So I did then composed the reply text and clicked “Reply” and it was rejected.
The response from the Admin is:
“Capture screenshots of your terminal output to bypass the forum’s Community Policy text filter. The filter frequently blocks text containing file paths, repository URLs, and code blocks”.
So what if the output is 300 lines long? Output is beyond screen size … but I did a screenshot reply - crazy.
1 Like
Sorry, but this guy is no forum admin nor a developer. He has no connections to the developer team or something. It is a normal forum user. Chromium devlopers have different badges in the forum. He even lacks basic understanding of the issue. Better follow the Chromium ticket which is processed by real Chromium/Chrome developers with actual knowledge.
The Chromium issue tracker doesn’t have the content restriction of the forum. The forum is only for user-helps-user. The Chromium issue tracker is there to get professional help from the devs and to report bugs.
1 Like
The Chromium ticket made progress. A developer replicated the issue and it is assigned and investigated.
2 Likes
You can update now. The issue is fixed.
The issue was (quote from issue tracker):
It appears that the signing script is reusing the aarch64 repository signature for the x86_64 repository.
3 Likes
I’ll cross my fingers the update goes okay … considering some of the commands I was asked to execute in the past 
I noticed they locked the thread out in Chrome forum
2 Likes
Too late to track it down. I already packed my bags and boarded on Firefox.
One less repository on the list, one less concern to encounter.
2 Likes
I re-enabled the Chrome repo, ran zypper dup and it’s working. Google’s fix is working.
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.