*** This bug is a duplicate of bug 1953610 ***
https://bugs.launchpad.net/bugs/1953610
I can confirm that the fix for bug 1953610 fixes this for me.
My umask is set to 027 (per hardening guidelines), and I previously ran
into this issue, but it works as expected now (following the
verification process in bug 1953610).
** This bug has been marked a duplicate of bug 1953610
cnf-update-db creates unreadable database if wrong umask
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824000
Title:
command-not-found crashes: unable to open database file (stack trace)
To manage notifications about this bug go to:
https://bugs.launchpad.net/command-not-found/+bug/1824000/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
