5.1.5 is a bug-fix release. A database stored on a filesystem that does not implement POSIX file locks, most notably the Flatpak XDG document-portal path (/run/user/<uid>/doc/) that the file chooser hands back, could not be opened or created and failed with Failed to acquire database lock: Function not implemented (#466). This was a regression from the lock file added in 5.1.4, which is now treated as best-effort. This release also fixes the secure-memory pool consuming the entire locked-memory budget, which left the password entry unable to lock its own buffer on every unlock (Debian #1141809).
Fixes
- FIX: a database stored on a filesystem without lock support (the Flatpak document portal, and some NFS/SMB mounts) could not be opened or created, failing with
Failed to acquire database lock: Function not implemented. Locking is now best-effort, so the database opens normally on those filesystems, while real locking is unchanged everywhere else (#466) - FIX: the secure-memory pool reserved the whole
RLIMIT_MEMLOCKbudget, so the GTK password entry could not lock its own buffer and warnedcouldn't lock 16384 bytes of memory (gtk): Cannot allocate memory, falling back to unlocked memory for the typed password on every unlock. The pool now leaves headroom for it (Debian #1141809)
sha256: 2e15b6106d9170373d2e44d78d3ff839c294363857883d9e72c997e14be1b12e