You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
openSuse Leap 15.1
kde environment (sddm)
Skype app uses gnome keyring also in kde environment.
If you install skype package then this installs all about gnome keyring technology.
Login password is the same as gnome keyring password.
During kde session login skype is launched automatically then gnome keyring asks for user the password to open gnome keyring according to get id and pwd for skype connecting.
We can conclude that login process does not unlock gnome keyring (kwallet unlocking succeeds). This is the problem. i want to unlock the 2 storages during logging process.
I check that statements about gnome keyring are well added to
For "login" we can check that "default" is in grey
For "Connexion" we can check that "default" is not in grey
If I use lightdm to open a kde session then unlocking gnome keyring succeeds.
In /var/log/messages i get this error message:
2019-08-27T20:04:08.866459+02:00 grognon su: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control
2019-08-27T20:04:08.866678+02:00 grognon su: gkr-pam: couldn't unlock the login keyring.
The text was updated successfully, but these errors were encountered:
promeneur
changed the title
kde environment
kde environment, unlocking gnome keyring fails
Aug 28, 2019
openSuse Leap 15.1
kde environment (sddm)
Skype app uses gnome keyring also in kde environment.
If you install skype package then this installs all about gnome keyring technology.
Login password is the same as gnome keyring password.
During kde session login skype is launched automatically then gnome keyring asks for user the password to open gnome keyring according to get id and pwd for skype connecting.
We can conclude that login process does not unlock gnome keyring (kwallet unlocking succeeds). This is the problem. i want to unlock the 2 storages during logging process.
I check that statements about gnome keyring are well added to
common-auth-pc
auth required pam_env.so
auth optional pam_gnome_keyring.so
auth optional pam_kwallet5.so
auth required pam_unix.so try_first_pass
common-passsword-pc
password requisite pam_cracklib.so
password optional pam_gnome_keyring.so use_authtok
password optional pam_kwallet5.so
password required pam_unix.so use_authtok nullok shadow try_first_pass
common-session-pc
session optional pam_systemd.so
session required pam_limits.so
session required pam_unix.so try_first_pass
session optional pam_umask.so
session optional pam_gnome_keyring.so auto_start only_if=gdm,gdm-password,lxdm,lightdm
session optional pam_kwallet5.so
session optional pam_env.so
With seahorse we can check there are 2 keyrings:
For "login" we can check that "default" is in grey
For "Connexion" we can check that "default" is not in grey
If I use lightdm to open a kde session then unlocking gnome keyring succeeds.
In /var/log/messages i get this error message:
2019-08-27T20:04:08.866459+02:00 grognon su: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control
2019-08-27T20:04:08.866678+02:00 grognon su: gkr-pam: couldn't unlock the login keyring.
The text was updated successfully, but these errors were encountered: