This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1029.33 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp'
to 'verification-done-jammy-li
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-j
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
nvidia-tegra-5.15' to 'verificat
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-6.5' to
'verification-done-jammy-linux-nvi
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
'verification-done-jammy-linux-
This bug is awaiting verification that the linux-oracle/5.15.0-1053.59
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-oracle' to 'verification-done-
jammy-linux-oracle'. I
This bug is awaiting verification that the linux-raspi/5.15.0-1048.51
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If t
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1050.56 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-in
This bug is awaiting verification that the linux-kvm/5.15.0-1052.57
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-kvm' to 'verification-done-jammy-
linux-kvm'. If the pro
This bug is awaiting verification that the linux-
hwe-6.5/6.5.0-25.25~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
hwe-6.5' to 'verification-done-jammy-linux-hw
This bug is awaiting verification that the linux-azure/6.5.0-1016.16
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
This bug is awaiting verification that the linux-aws/6.5.0-1015.15
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-aws' to 'verification-done-mantic-
linux-aws'. If the pr
Thank you Stefan!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049689
Title:
partprobe is broken on empty loopback device
To manage notifications about this bug go to:
https://bugs.launchpad.net/
Ok, so I created bug #2056143 for the fresh issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049689
Title:
partprobe is broken on empty loopback device
To manage notifications about this bug g
It would be good to have a second bug report about the new finding. In some way
this is now working as designed but not as expected. Basically loop block
devices set a generic flag to disable partition support
(/sys/block/loop?/capabilities -> 0x200 GENHD_FL_NO_PART). There is a change in
5.19
Sorry, I verified my original test case when 5.15.0-97.107 was made
available in jammy-updates a few days ago, but this new failure was only
caught by a CI job recently after new Ubuntu images became available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
On Monday we're supposed to release this. This feedback would have been crucial
1-2 weeks before.
Plus, we already started the next releases..
I'll try to prioritize this, but it's very late to be included in the
next releases (I'll probably respin)
--
You received this bug notification because
Kernel 5.15.0-97.107 resolves the issue for the test case documented in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052842
However, I still see a regression with the following test case:
$ fallocate -l 1G /tmp/blob
$ sudo losetup $LOOPDEV /tmp/blob
$ sudo /usr/sbin/parted -s -m -a optim
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the pro
** Summary changed:
- partproke is broken on empty loopback device
+ partprobe is broken on empty loopback device
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049689
Title:
partprobe is broken on
20 matches
Mail list logo
