Failed howdy authentication causes core dump

[mlbullett]

I'm currently trying to get howdy and gtklock to play nicely together but have noticed that a failed auth attempt with howdy (so letting it timeout) causes gtklock to seg fault. Successful authentication with howdy works fine. Not sure if this is better posted upstream but figured I'd start here.

Some useful info:
I'm running sway on Linux 5.19.11-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 24 Sep 2022 18:24:15 +0000

Have howdy plugged into pam and gtklock as follows:
/etc/pam.d/login

#%PAM-1.0

auth       sufficient   pam_unix.so try_first_pass likeauth nullok
auth       sufficient   pam_python.so /lib/security/howdy/pam.py
auth       required     pam_securetty.so
auth       requisite    pam_nologin.so
auth       include      system-local-login
auth       optional     pam_gnome_keyring.so
account    include      system-local-login
session    include      system-local-login
session    optional     pam_gnome_keyring.so auto_start
password   include      system-local-login

Steps to reproduce:

• Add howdy to pam.d/login
• Run gtklock
• Trigger auth attempt by leaving password empty
• Let attempt timeout

[Jackaed]

I'm also experiencing this issue.