repo signatures not stored?

English Applications
1

Hi all,

using OpenSUSE 13.2

I’m prompted like this:

http://i.imgur.com/c9uBH21.png

So, I click ‘Yes’, enter my password and all seems OK.

After a reboot, the same thing happens. It looks like my willingness to trust this (and other) repos is not being recorded.

How do I fix this?

Thank you.

2

I’ve seen that as well a few times in the recent past, and I do remember a bug report about it.

Unlikely to be fixed for 13.2 any more though (if it’s a bug in the package management), as 13.2 is nearly end-of-life.

How do I fix this?

Running “sudo zypper ref” and accepting the signature there should help.

3

Hi and thanks for your fast reply!

Which means I have a problem. I can’t get 42.1 to run, so I’ll probably have to find another distro.

I think that has fixed it. I selected ‘always’ trust for each repo, then rebooted. The autoupdate thingy ran and didn’t show the screen above.

Thank you! :slight_smile:

4

Well, Leap 42.2 has been released two months ago, maybe try that?

Strange problem you have there though.

Normally Plasma5 should work, with the proprietary driver at least (nouveau does and did have its share of problems depending on the exact graphics card, that likely are more exposed by newer software like Plasma5).
Sorry, but I missed that thread so far.

Maybe something went wrong with the nvidia installation?
Should be fixable then.

I think that has fixed it. I selected ‘always’ trust for each repo, then rebooted. The autoupdate thingy ran and didn’t show the screen above.

Thank you! :slight_smile:

Your welcome.

5

I’ll try it out this weekend. :wink:

But it seems I spoke too-soon about the repo trust issue being fixed. It’s back to prompting me as shown in the screencap.

6

It might also be a problem with that particular repo.
Maybe the repo’s signature has indeed changed again?

Personally I had that problem with some specific repos only, but since running “zypper ref” I haven’t encountered that again.
And that was two months ago or something like that.

7

With 13.2 going end of life things may be changing. Like some may be moving to som backup long term storage site thus the need to change certs