[Bug 1892340] Re: Setting Java Flight Recorder option forces English locale

This bug seems to have been fixed in newer versions; I now have: $ dpkg -S $(readlink -f $(which java)) openjdk-17-jre-headless:amd64: /usr/lib/jvm/java-17-openjdk-amd64/bin/java $ java -version openjdk version "17.0.1" 2021-10-19 OpenJDK Runtime Environment (build 17.0.1+12-Ubuntu-120.04)

[Bug 1892340] [NEW] Setting Java Flight Recorder option forces English locale

Public bug reported: (I don't have access to file bugs upstream at ) Platform information: $ uname -m x86_64 $ lsb_release -d Description:Ubuntu 20.04.1 LTS $ dpkg -S $(readlink -f $(which java)) openjdk-11-jre-headless:amd64:

[Bug 1878378] [NEW] add_mountroot_fail_hook uses wrong target name

Public bug reported: Upon boot of a system that uses LVM2 you get the message: ln: /tmp/mountroot-fail-hooks.d//scripts/init-premount/lvm2: No such file or directory This is because the script /usr/share/initramfs-tools/scripts/init- premount/lvm2 uses the add_mountroot_fail_hook function from

[Bug 1873797] Re: add_mountroot_fail_hook is either buggy or not used properly, causes boot problems

I have reported this to the initramfs-tools package: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1878378 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873797 Title:

[Bug 1873797] Re: add_mountroot_fail_hook is either buggy or not used properly, causes boot problems

I also get this problem, on a minimal Ubuntu installed on an LVM-managed disk. However, I believe that the fix should be: sudo sed -i 's,\(ln -s "\$0" /tmp/mountroot-fail- hooks\.d/\)"\$0",\1"\$1",' /usr/share/initramfs-tools/scripts/functions i.e, that the path in /tmp/mountroot-fail-hooks

[Bug 1799070] Re: Netboot initrd is not updated with signed modules

It used to be that the kernel in main/installer-amd64 was unsigned, which is why my scripts had to go look in main/signed instead. Apparently this changed at some point, which announcement I missed, and as you say the kernel that is stored together with the netboot image is now signed. I am happy,

[Bug 1799070] Re: Netboot initrd is not updated with signed modules

** Description changed: At the time of writing (21-oct-2018) the distribution directory at http://ftp.ubuntu.com/ubuntu/dists/bionic-updates/main/signed/linux- amd64/ contains kernels for versions 4.15.0-33.36, 4.15.0-34.37 and 4.15.0-36.39, whereas

[Bug 1799070] [NEW] Netboot initrd is not updated with signed modules

Public bug reported: At the time of writing (21-oct-2018) the distribution directory at http://ftp.ubuntu.com/ubuntu/dists/bionic-updates/main/signed/linux- amd64/ contains kernels for versions 4.15.0-33.36, 4.15.0-34.37 and 4.15.0-36.39, whereas