Hi
When i boot my computer and it finishes loading (kde) i always get this message
“A security relationship is not present. A security trust relationship could not be made with the software origin. Please check your software signatures settings.”
Could someone please help with this message?
As always, your help is appreciated.
Please be more specific.
Do you mean you get this when after boot the login screen (Display Manager) is shown or after there is a login (automatic login being enabled)?
Is it on the screen, in a pop-up window?
Google Repo?
If yes either delete repo or answer key question with “ok”.
Hi
It is a pop-up form the bottom right hand side of the screen. It happens once kde is finished loading, all the icons have been displayed . That’s right after login. I don’t have auto login enabled
I hope that is enough info, i can’t think of any think else
testi55
I don’t quiet understand you’re answer, can you be more specific
Thank you
Thus it is after login of a user, NOT at boot.
Hm, this is indeed a bit vague suggestion.
It could be that because the message mentions about software, it could be about the applet that looks after software updates. That applet (when your user uses it) start at login and tries to contact all your enabled repositories. Thus it could be that one of those repos gives a problem. I guess that @testi55 assumes that a/the Google repo could be the source of that (maybe out of his own experience).
But there are a lot of “maybe”, “assume” and “guess” in the above, Maybe @testi55 could explain his case a bit more so that others understand his strain of thoughts and thus his suggested solution.
Sigh, ok, do you have the google repo in your list of repositeries? Only you can answer that.
If so the message is caused by the opensuse updater, which can not handle the google key,
or a weired key. Read also here: https://forums.opensuse.org/showthread.php/526290-Google-Chrome-Update-Key-Validation-Error
To get rid of the message either accept the key by running yast > software installation, which is only a temp. solution and has to be
done repeatedly or delete the repo or set it inactive.