Thanks for the quick response.
I did see that bug, but I'm not convinced it's a duplicate, as the
machine is not loaded and
> systemctl start locate.service
reproducibly generates
pam_wtmpdb ... SQLITE_DONE: 8 pam_lastlog2 ... SQLITE_DONE: 8
Running /etc/cron.daily/locate directly doesn't create the errors so
it's something to do with the sandbox that systemd is setting up.
But I'm no expert and obviously bow to superior knowledge.
Derek
On 28/07/2026 17:41, Andreas Metzler wrote:
Control: reassign 1142935 libpam-wtmpdb
On 2026-07-28 Derek Roberts<[email protected]> wrote:
Package: findutils
Version: 4.10.0-3
Severity: normal
Running locate.service on Debian 13 causes every internal su
invocation in updatedb.findutils (including the two select_shell()
probes) to produce:
pam_wtmpdb(su:session): add_entry: Adding an entry did not return SQLITE_DONE: 8
pam_lastlog2(su:session): Delete statement did not return SQLITE_DONE: 8
Running the same script manually does not reproduce the issue.
[...]
Hello Derek,
this does not look like a locate issue. The pam_lastlog2 thing seems to
be a duplicate ofhttps://bugs.debian.org/1138529 (fixed in upstream
git). I am reassigning to libpam-wtmpdb, since there is no bug tracking
this there.
cu Andreas