Hi,
PAM-shield uses a database file that I migrated from debian 10 to debian
12 in one big double upgrade.
For testing purposes I deleted that database file, created an empty file
instead and the trap divide error disappeared. PAM-shield works fine
again as well and has been for three days now.
So... problem solved for my case.
Is this problem still relevant for libgdbm as we have a trap divide
error that should not happen no matter what? Or should I open a ticket
at libpam-shield so the problem (and the solution) is documented - even
if the package is orphaned?
Thanks for your support!
Schnitzi
