Delay during login due to PAM kwallet module

Bug #1632317 reported by Vishal Rao on 2016-10-11
This bug affects 4 people
Affects Status Importance Assigned to Milestone

Bug Description

Recently (in the last week or so, can't really remember) I noticed that after entering the correct password to login in Greeter it would take a while (about 15-20 seconds) before the desktop appeared.

Looked in /var/log/lightdm/lightdm.log and noticed an authentication related gap in the log timestamps (sorry I don't have the snippet now because I worked around the issue).

Looked at /var/log/auth.log and saw some PAM related errors for loading the kwallet module.

So I commented out the occurrences of kwallet in /etc/pam.d/ files that I could find and that seems to have resolved this issue for me:

vishal@skybird:/etc/pam.d$ grep kwall *
lightdm:#auth optional
lightdm:#auth optional
lightdm:#session optional auto_start
lightdm:#session optional auto_start
lightdm-greeter:#auth optional
lightdm-greeter:#auth optional
lightdm-greeter:#session optional auto_start
lightdm-greeter:#session optional auto_start

Not sure why this issue started for me, whether it's something I installed or this is from upstream Ubuntu or an update from elementary OS or what. Let me know if more info/logs needed from my machine.

Vishal Rao (vishalrao) wrote :

Well, turns out the issue still occurs, not related to kwallet module.

Anything I can do to troubleshoot, help resolve the issue?

Vishal Rao (vishalrao) wrote :

Happened to notice the following in my dmesg just now:

[ 101.343635] show_signal_msg: 27 callbacks suppressed
[ 101.343638] loader[1699]: segfault at 88 ip 00007f7d7cca9633 sp 00007f7d361d1008 error 4 in[7f7d7cb32000+71a000]

haofei (haofei) wrote :

 I randomly get that too

Evgenii Frolov (frol-onn) wrote :

Yes, that affects me too!
Nothing interesting in dmesg though:

[ 98.926095] Bluetooth: BNEP socket layer initialized
[ 103.721868] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
[ 103.737027] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
[ 103.740614] IPv6: ADDRCONF(NETDEV_UP): enp37s0: link is not ready
[ 104.110229] r8169 0000:25:00.0 enp37s0: link down
[ 104.110295] IPv6: ADDRCONF(NETDEV_UP): enp37s0: link is not ready
[ 105.925258] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
[ 107.795972] wlo1: authenticate with 10:fe:ed:80:df:de
[ 107.815164] wlo1: send auth to 10:fe:ed:80:df:de (try 1/3)
[ 107.818403] wlo1: authenticated
[ 107.822100] wlo1: associate with 10:fe:ed:80:df:de (try 1/3)
[ 107.827017] wlo1: RX AssocResp from 10:fe:ed:80:df:de (capab=0x431 status=0 aid=3)
[ 107.827123] wlo1: associated
[ 107.827133] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready
[ 113.340916] vboxdrv: Found 4 processor cores
[ 113.358285] vboxdrv: TSC mode is Invariant, tentative frequency 2294771026 Hz
[ 113.358288] vboxdrv: Successfully loaded version 5.0.32_Ubuntu (interface 0x00240000)
[ 113.396343] VBoxNetFlt: Successfully started.
[ 113.440206] VBoxNetAdp: Successfully started.
[ 113.505181] VBoxPciLinuxInit
[ 113.569007] vboxpci: IOMMU not found (not registered)
[ 163.273450] Bluetooth: RFCOMM TTY layer initialized
[ 163.273457] Bluetooth: RFCOMM socket layer initialized
[ 163.273464] Bluetooth: RFCOMM ver 1.11

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers