Hello Christopher,
Le 2023-09-04 à 04 h 09, Christopher Voglstätter a écrit :
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.
It's a good and a bad news at the same time. A good news because you
found a working workaround, and a bad news because since a database
reset works, it should mean a problem in gdbm itself during some kind of
upgrades.
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?
I don't know if we can go further with this, but did you keep the old
database file? So one could try to reproduce the problem, and if so,
forward it upstream.
/Nicolas
