[Bug 2101893] Re: [FFe] Update zfs-linux to upstream 2.3.0

OpenZFS 2.3.1 https://github.com/openzfs/zfs/releases/tag/zfs-2.3.1 already has the 6.14 compatibility patches included (https://github.com/openzfs/zfs/pull/17114). The META file doesn't show 6.14 since 6.14 had not been released before OpenZFS 2.3.1 was released. If at all Ubuntu decides to upgra

[Bug 1964827] Re: zfs-linux upstream at 2.1.4, jammy has 2.1.2

** Summary changed: - zfs-linux upstream at 2.1.3, jammy has 2.1.2 + zfs-linux upstream at 2.1.4, jammy has 2.1.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964827 Title: zfs-linux upstream at

[Bug 1958594] Re: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

Accidentally changed the status... sorry about that. Can anyone please remove the "Fix Released" status? Not sure how to do that... ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, whic

[Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed

To check if any of the files in a given directory were corrupted due to this bug, would it be sufficient to run "sudo find ." and check if the command returns without any error or without getting stuck at a file? -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1922940] Re: plugininstall.py: lsblk -lp -oNAME, FSTYPE returned non-zero exit status 32

** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922940 Title: plugininstall.py: lsblk -lp -oNAME,FSTYPE returned non-zero exit status 32

[Bug 1922940] Re: plugininstall.py: lsblk -lp -oNAME, FSTYPE returned non-zero exit status 32

** Tags added: hirsute ** Tags added: ubiquity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922940 Title: plugininstall.py: lsblk -lp -oNAME,FSTYPE returned non-zero exit status 32 To manage n

[Bug 1924822] Re: installer crashes when using manually created EFI partition, /boot partition and choosing lvm encryption for root parition

*** This bug is a duplicate of bug 1923379 *** https://bugs.launchpad.net/bugs/1923379 ** This bug has been marked a duplicate of bug 1923379 installer crashes when using manually created EFI partition, /boot partition and choosing lvm encryption for root parition -- You received this bu

[Bug 1924822] Re: installer crashes when using manually created EFI partition, /boot partition and choosing lvm encryption for root parition

same as bug #1922940 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924822 Title: installer crashes when using manually created EFI partition, /boot partition and choosing lvm encryption for root

[Bug 1923379] Re: installer crashes when using manually created EFI partition, /boot partition and choosing lvm encryption for root parition

Same as bug #1922940 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923379 Title: installer crashes when using manually created EFI partition, /boot partition and choosing lvm encryption for root

[Bug 1924822] [NEW] installer crashes when using manually created EFI partition, /boot partition and choosing lvm encryption for root parition

Public bug reported: The installer crashes when using manually created EFI partition (512 MiB), /boot partition (ext4, 732 MiB) and rest of the disk used for root partition using 'physical volume for encryption' (lvm). This happens both for xubuntu and ubuntu installers (21.04 daily build April 16

[Bug 1923379] Re: installer crashes when using manually created EFI partition, /boot partition and choosing lvm encryption for root parition

** Summary changed: - installer crashes when using manually created EFI partition, /boot partition and choosing lvm encryption for root + installer crashes when using manually created EFI partition, /boot partition and choosing lvm encryption for root parition ** Description changed: The ins

[Bug 1923379] [NEW] installer crashes when using manually created EFI partition, /boot partition and choosing lvm encryption for root

Public bug reported: The installer crashes when using manually created EFI partition (512 MiB), /boot partition (ext4, 732 MiB) and rest of the disk used for 'physical volume for encryption' (lvm). This happens both for xubuntu and ubuntu installers (21.04 daily build April 11th 2021) ProblemType