Please allways tell which version of openSUSE you use. Saying things like “the last” does not convince others that you realy know what you use and it will make the thread unusable when newer versions are released. Remember that many people will find your thread in maybe two or three years when they search for a solution of the same problem.
Then something that is not obvious for a new user here. Please copy/paste your computer output (like your zypper one) complete (that is prompt, command, output, next prompt) between CODE tags in the post. You get the CODE tags by clickingn the # button in the tool bar of the post editor.
Then the key acceptance. The confusing thing is that the repos use keys, but you can nowhere check if they are the correct ones. Once you have accepted the key, it will be used for any new installs fromn that repo, so then ui offers some security. But for the moment, the only thing you can do is accept it.
Hi hcvv, I appreciate your patience. I’m currently using OpenSUSE 13.1 and next time I open a thread, I’ll try to pay attention to the details you pointed out, thanks again! I couldn’t find an “edit” button to edit my post.
I think I was able to solve this problem. Here is what I did. I found this site:
I tryed to follow the instructions for RPM, but it didn’t work. What worked was downloading “linux_signing_key.pub” from that link, then I opened my YaST >> Software repositories >> GPG Keys >> Add. I specified the file I’ve just downloaded the error was gone. I installed google-chrome-stable from YaST >> Software Management.
> I think I was able to solve this problem. Here is what I did. I found
> this site:
> I tryed to follow the instructions for RPM, but it didn’t work. What
> worked was downloading “linux_signing_key.pub” from that link, then I
> opened my YaST >> Software repositories >> GPG Keys >> Add. I specified
> the file I’ve just downloaded the error was gone. I installed
> google-chrome-stable from YaST >> Software Management.
Well, but what you did turns out to be the same as if you do what Henk
told you, to simply accept the key when asked.
When you use a repository the first time in YaST, it tells you about the
new GPG key, and whether you want to accept it or not. Simple.
Whether this is a secure procedure, that’s another matter. There is no
secure key verification method implemented.
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
> Hi, I’m using the last version of OpenSUSE, I’m a complete newbie in
> this distro. I would like to install Google Chrome, I followed this
> But it’s not working. I receive this error when I try to install Google
> Chrome via zypper:
> # zypper in google-chrome-stable
> File ‘repomd.xml’ from repository ‘Google-Chrome’ is signed with an
> unknown key ‘A040830F7FAC5991’. Continue? [yes/no] (no):
> How do I validade this GPG key so I can install Google Chrome?
Welcome to the forums. openSUSE supplies chromium(free alternative to
chrome) and packman repo provides chromium’s codecs.