Bug 703262 – >gnome-base/gnome-keyring-3.28.2 extremelly slow when unlocking on xdm

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description David Carlos Manuelda 2019-12-18 06:18:22 UTC]

When testing gnome-keyring (3.31.91-r1) with my MATE Desktop, once adding the relevant lines to lightdm (tested also sddm which already contains the lines to autounlock it on login) I found that login to my DE takes about 20 seconds.

Downgrading it to 3.28.2 solved the issue of the long waits, but the issue is that I don't know why is this happenning.

I see no relevant info under /var/log/lightdm/* logs neither in dmesg, if needed please ask me a log file and I'll attach it.

/etc/pam.d/lightdm looks like:

auth		include		system-local-login
auth		optional	pam_gnome_keyring.so
account		include		system-local-login
password	include		system-local-login
session		include		system-local-login
session		optional	pam_gnome_keyring.so auto_start

Reproducible: Always

[Comment 1 David Carlos Manuelda 2019-12-18 06:19:39 UTC]

/etc/pam.d/system-local-login 
auth		include		system-login
account		include		system-login
password	include		system-login
session		include		system-login

/etc/pam.d/system-login 
auth		required	pam_tally2.so onerr=succeed
auth		required	pam_shells.so 
auth		required	pam_nologin.so 
auth		include		system-auth
account		required	pam_access.so 
account		required	pam_nologin.so 
account		include		system-auth
account		required	pam_tally2.so onerr=succeed 
password	include		system-auth
session         optional        pam_loginuid.so
session		required	pam_env.so envfile=/etc/profile.env 
session		optional	pam_lastlog.so silent 
session		include		system-auth
session		optional	pam_ck_connector.so nox11
session		optional	pam_motd.so motd=/etc/motd
session		optional	pam_mail.so

[Comment 2 Jonas Stein 2019-12-18 20:40:58 UTC]

It is sad to read that you have problems with the software. The situation seems to be a bit more complicate and requires some analysis.
We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. 

I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3].
I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels [4].
Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product.

[1] https://www.gentoo.org/get-involved/irc-channels/
[2] https://forums.gentoo.org/
[3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html
[4] https://www.gentoo.org/support/