Comment # 3 on bug 1150356 from Marco Calistri

I suppose you should investigate around gkr-pam module as I get isolated by
journalctl:

sudo journalctl -x -p err

ott 09 17:37:58 linux-turion64.ddns.net lightdm[2108]: gkr-pam: unable to
locate daemon control file

ott 10 10:07:30 linux-turion64.ddns.net cinnamon-screensaver-pam-helper[9812]:
gkr-pam: the password for the login keyring was invali>
ott 10 10:07:30 linux-turion64.ddns.net cinnamon-screensaver-pam-helper[9812]:
gkr-pam: the password for the login keyring was invali>
ott 10 10:08:11 linux-turion64.ddns.net cinnamon-screensaver-pam-helper[9812]:
gkr-pam: the password for the login keyring was invali>
ott 10 10:08:11 linux-turion64.ddns.net cinnamon-screensaver-pam-helper[9812]:
gkr-pam: the password for the login keyring was invali>
ott 10 10:08:25 linux-turion64.ddns.net lightdm[10220]: gkr-pam: unable to
locate daemon control file
ott 10 10:08:48 linux-turion64.ddns.net cinnamon-screensaver-pam-helper[9812]:
gkr-pam: couldn't get the password from user: Errore d>
ott 10 10:09:04 linux-turion64.ddns.net lightdm[10237]: gkr-pam: unable to
locate daemon control file
ott 10 10:27:27 linux-turion64.ddns.net sudo[12487]: gkr-pam: unable to locate
daemon control file