[Bug 1824000] Re: command-not-found crashes: unable to open database file (stack trace)
We noticed this error happening after running CIS Hardening, where the umask is changed from 022 to 027 (rule 5.5.4), as stated in #24. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906266] Re: After upgrade: "libvirt.libvirtError: Requested operation is not valid: format of backing image %s of image %s was not specified"
I can confirm that installing a newer version of libvirt fixes the issue. We just did this for an nova-libvirt container in the Openstack Victoria release, wich we had upgraded from Rocky. We used the latest available libvirt version for Ubuntu 20.04: 6.0.0-0ubuntu8.12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906266 Title: After upgrade: "libvirt.libvirtError: Requested operation is not valid: format of backing image %s of image %s was not specified" To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1906266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
