Gnome Keyring Issue

long story short. 13.1 accidentally moved a bunch of the system folders to a sub folder. Finally got them moved back using live 13.1 usb stick

I copied them twice. The first time i didn’t preserve the permissions and date time stamps. The second time i did.

Had an authentication manager issue on startup. Found that i need to change a folder permission so it could run properly.

Then I found i couldn’t use any of the yast2 applications. Yast2 would open but that was it. I found had these errors in messages log.


gnomesu-pam-backend: The gnome keyring socket is not owned with the same  credentials as the user login: /run/user/1000/keyring/control
gnomesu-pam-backend: gkr-pam: couldn't unlock the login keyring
gnomesu-pam-backend: pam_unix(gnomesu-pam:session): session opened for user root by (uid=1000)

then there’s this…


 gnomesu-pam-backend: pam_unix(gnomesu-pam:session): session closed for user root
 org.gnome.evolution.dataserver.Sources4[3327]: ** (evolution-source-registry:3492): WARNING **: secret_service_search_sync: must specify at least one attribute to match
 gnomesu-pam-backend: pam_unix(gnomesu-pam:session): session opened for user root by (uid=0)
 YaST.desktop[6313]: terminate called after throwing an instance of 'YUIPluginException'
 YaST.desktop[6313]: what():  Couldn't load plug-in qt
 YaST.desktop[6313]: YaST got signal 6 at file /usr/share/YaST2/modules/Wizard.rb:782
 YaST.desktop[6313]: sender PID: 6567
 YaST.desktop[6313]: /sbin/yast2: line 440:  6567 Aborted                 $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS
 gnomesu-pam-backend: pam_unix(gnomesu-pam:session): session closed for user root

So somehow when i restored the folders it messed up the gnome key ring?

So i changed the repo’s over to 13.2, dup, then to leap repo’s and dup.

It didnt fix the issue. So where do i start? Reading blogs and forums, there isn’t much on this. What I can find doesn’t seem applicable to the error i’m seeing.

I also see this when opening yast itself.

What seems to have fixed my issue was running the the usb installation, but choosing upgrade. The unixmen approach of just replacing repo’s missed a step somewhere. It also left me with many broken dependencies.

if you’re upgrading from 13.2, I would use the upgrade option from the install dvd OR just install fresh.