Hi Mike,
Backporting and SRU-ing GRUB 2.12 to Jammy is part of the roadmap for
the Ubuntu 24.10 cycle. I would like to not make a more specific public
commitment right now, but it's inside the realm of possibility that it
will happen a lot sooner than October 2024.
Mate
On Sat, May 18, 2024 at
Also C programming wall of shame, aka the best way to obtain a zero
value for time_t:
> (time_t) NULL
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059131
Title:
slurmdbd segfaults on armhf
To
There are 100s of printf invocations to fix, it would take hours by
hand. Unless someone really needs this package, I don't necessarily
believe doing this is a good idea.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is there any point in fixing this package? Maybe removal from the
archive is a good option?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059139
Title:
Please remove pngphoon on Noble/armhf
To
Setting all to 'Fix Released', none of these packages are in -proposed
anymore.
** Changed in: cloudkitty (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: python-oslo.db (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: flask-restful (Ubuntu)
It seems to be passing currently
** Changed in: fonttools (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059188
Title:
fonttools autopkgtest failure
It's 1.4.2-1build2, but it seems to be passing.
** Changed in: flatpak-builder (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059189
Title:
please
It looks like this is passing now.
** Changed in: ubiquity (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059257
Title:
autopkgtest failure on
@wxl
There are two solutions:
- Always remove the existing GRUB configuration before installing GRUB
- If you know that os-prober entries are required in the new install, use,
GRUB_DISABLE_OS_PROBER=false grub-install ...
--
You received this bug notification because you are a member of Ubuntu
Tagging calameres fix.
Desktop/server installer also potentially will need a fix for this if no
reformat installs will be re-eanbled.
** Also affects: calamares-settings-ubuntu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu)
Status: New => Invalid
--
I finally found the cause, the two big hints were:
- 2 fresh installs were in this order sda1, sda2
- only happens with install *without a reformat to sda1*
After the first install to sda1:
- MBR (and MBR gap) contains GRUB core pointing to sda1, sda1 contains modules
and config, this config on
This is not the same issue unfortunately, and will be investigated
further.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060624
Title:
lubuntu/xubuntu reinstall (& install) on dual boot system,
ive said this on IRC, but putting it here for the record: UEFI still
installs via the /boot/efi mountpoint as a fallback, so don't be
concerned about secure boot.
of course it should still be fixed due to user annoyance and outdated
BIOS bootloader
--
You received this bug notification because
Public bug reported:
This debconf is required to be set for grub package reinstallations
(especially grub-pc) to work correctly.
This was masked in the 23.10 cycle due to
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889556.
That workaround was removed in the 24.04 cycle in
Yes, I agree there might be other ways to trigger it, I'm just leaving a
reproducible one I found above.
And not being a release blocker doesn't mean it won't be fixed btw, just
that I am not going to rush this.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Reproduced again. I think the steps are, and they have to be repeated
from step 1 each time:
Start with clean disk:
1. Partition disk as MBR with two partitions, install lubuntu on sda1 _with_
format
2. Install lubuntu on sda2 _with_ format
3. Install lubuntu on sda1 _without_ format
I'll
Hmm it seemingly reproduced once, but then i fixed it with dpkg-
reconfigure grub-pc, did another install to overwrite it, and it was
working there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@guiverc, it seemingly reproduced with an install to sda1, but only
_without_ the format
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060624
Title:
lubuntu/xubuntu reinstall (& install) on dual
Hi Chris, i'll try the same thing:
- two preinstalled noble system on MBR, with sda1 and sda2
- install lubuntu without reformat on sda1 first
- install lubuntu without reformat on sda2 second
If none of that reproduces, i'll mark it incomplete.
--
You received this bug notification because you
I haven't managed to reproduce this issue yet, I've installing various
dual boot combinations of Xubuntu/Lubuntu into a BIOS qemu VM.
@guiverc If you could provide exact steps to reproduce this starting
from an empty virtual machine, that would be extremely helpful.
--
You received this bug
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Mate Kukri (mkukri)
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060624
Title:
lubuntu/xubu
This is just a matter of updating encrypt-cloud-image with the new
secboot, please see: https://github.com/canonical/encrypt-cloud-
image/pull/22
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062373
Daily ISO also works fine. Noble seems to use the old pc-kernel snap and
snapd in the archive wasnt updated for this either, so removing that.
** No longer affects: snapd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've installed desktop FDE from the 24.04 beta ISO. It installed and
booted just fine. It also results in an installation with pc-kernel
23.10/stable which contains a shim 15.7-0ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have proposed a patch for this now:
https://github.com/rhboot/shim/pull/657
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061551
Title:
Merely booting Ubuntu 24.04 beta live CD breaks BitLocker
Do you get any error messages with the boot failure?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062179
Title:
ugrading grub breaks ubuntu system boot (UEFI, BIOS), if root on zfs
To manage
@peat-new
After some discussion about the upstream bug, I'm re-opening this as
'New'.
It seems that 'Volume Full' here indeed only refers to the event log
filling up and not the entire variable store.
The shim debug log was confusing me into thinking it was the full
variable store.
This could
I am still pretty sure it is the variable storage failure mode we are
seeing in this firmware. I also personally own an ASUS device with
firmware from 2019 and I managed to reach the same failure mode on it
even when using Mantic.
Also let me try to explain why errors crop up in other places too:
Perhaps we could remove secureboot-db from the ISO, so that only
installing Ubuntu causes the varstore filling up on such systems, but
Secure Boot isn't easily supportable on buggy firmware unfortunately.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The only workaround for a system with such broken firmware (in absence
of a firmware update that resolves the issue) is to disable UEFI Secure
Boot entirely.
** Changed in: shim-signed (Ubuntu)
Status: New => Invalid
** Changed in: secureboot-db (Ubuntu)
Status: New => Invalid
--
> 1. The dbx update causes breakage to TPM measured boot on this
particular firmware.
The dbx update causes the measurements in PCR 7 to change yes. This is not
breakage and is required and expected.
BitLocker asking for a recovery key in this scenario is normal behavior.
Entering the recovery
Verification OK, mantic remains bootable after upgrading to proposed
package.
** Tags removed: verification-needed verification-needed-mantic
** Tags added: verification-done verification-done-mantic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: cloud-init (Ubuntu)
Assignee: Mate Kukri (mkukri) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060695
Title:
24.04 grub-pc cannot upgrade on mirrored softw
@sylon This is just waiting for archive admin approval, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060766
Title:
Can't run bpftrace , ERROR: too many arguments
To manage notifications
Reported upstream at https://github.com/cython/cython/issues/6142
** Bug watch added: github.com/cython/cython/issues #6142
https://github.com/cython/cython/issues/6142
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looks like the time_t type and struct stat structure known to cython is wrong
and that is resulting in bad values:
https://github.com/cython/cython/blob/master/Cython/Includes/posix/types.pxd
** Also affects: cython (Ubuntu)
Importance: Undecided
Status: New
** Tags added:
Actually it might a time_t abi problem.
the sqlite3 integers are 64-bit, and in the file creation function it produces
a value such as
1712840079336130048 with length 61 bits which fits.
however the mtime attribute update in the same tmpfs example produces a 91 bit
timestamp such as
Upon further digging it seems one of the tests try to put the newly
64-bit timestamps into a sqlite3 database's INT type:
root@autopkgtest-lxd-dmjxfz:/tmp/autopkgtest.c6ltL9/build.h9M/src# Traceback
(most recent call last):
File "/tmp/autopkgtest.c6ltL9/build.h9M/src/examples/tmpfs.py", line
Public bug reported:
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
noble/noble/armhf/p/pyfuse3/20240410_221201_3ced2@/log.gz
** Affects: pyfuse3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Patch to remove the cloud init grub_dpkg module. This is no longer necessary:
- Curtin sets the debconf value itself
- cloud images now use the 'grub-{efi,pc}/cloud_style_installation' option
which ignores `install_devices`
** Patch added: "cloud-init-1-24.1.3-0ubuntu4.diff"
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Mate Kukri (mkukri)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060695
Title:
24.04 grub-pc cannot upgrade on mirrored softw
It looks like the installer is actually doing the correct thing, but
then upon first boot the debconf magically contains a different value.
Currently suspecting cloud-init
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: subiquity
Status:
Confirmed that this issue is definitely caused by cloud-init replacing
grub debconf with an incorrect value upon first boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060695
Title:
24.04
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060695
Title:
24.04 grub-pc cannot upgrade on mirrored software RAID root disk
To manage notifications about this bug
@cks I think I have it down to the installer configuring wrong values
for grub debconf install_devices.
** Changed in: subiquity
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: bpftrace (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060766
Title:
Can't run bpftrace , ERROR: too many arguments
To manage
Yeah you are right, this seems to be uncovered by the removal of that
workaround (the issue it solved wasn't related to this, and was solved
better in the meantime).
That seems to indicate that this was a different bug for a long time
that was hidden by that workaround.
I'll take another look at
** Patch added: "bpftrace-1-0.20.2-1ubuntu4.diff"
https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/2060766/+attachment/5763328/+files/bpftrace-1-0.20.2-1ubuntu4.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 2060766 ***
https://bugs.launchpad.net/bugs/2060766
** Patch removed: "bpftrace-1-0.20.2-1ubuntu4.diff"
https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/2060682/+attachment/5762746/+files/bpftrace-1-0.20.2-1ubuntu4.diff
--
You received this bug
*** This bug is a duplicate of bug 2060766 ***
https://bugs.launchpad.net/bugs/2060766
** This bug has been marked a duplicate of bug 2060766
Can't run bpftrace , ERROR: too many arguments
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This seems to be the same error as test failures in
https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/2060682
My guess is it being LLVM-18
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060766
This was fixed independently by vorlon in dcraw 9.28-5ubuntu1
** Changed in: dcraw (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060672
Title:
dcraw ftbfs
Could you try dpkg-reconfigure grub-pc and selecting the disks
themselves?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060695
Title:
24.04 grub-pc cannot upgrade on mirrored software RAID root
Did you set grub-pc/install-devices (e.g. through package configuration)
yourself, or is it from the installer?
> * grub-pc/install_devices: /dev/disk/by-id/md-name-ubuntu-server:0
I'd expect grub-pc/install_devices to contain the raw disks themselves
e.g. to be /dev/vda /dev/vdb and not the
Can you provide a bit more detail about the exact disk layout being used
here?
Is the RAID on the bare disks, or are there partition tables containing
the RAID?
Also is there a partition table inside the raid, or is it directly
formatted as ext4?
Is LVM used anywhere?
--
You received this bug
Public bug reported:
Fails to build on multiple architectures
https://launchpad.net/ubuntu/+source/magics++/4.15.3-1build1
** Affects: magics++ (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "LastTest.log"
https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/2060682/+attachment/5762771/+files/LastTest.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060682
** Patch added: "bpftrace-1-0.20.2-1ubuntu4.diff"
https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/2060682/+attachment/5762746/+files/bpftrace-1-0.20.2-1ubuntu4.diff
** Tags added: rls-nn-incoming update-excuse
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
LP: #2052809 [MIR] bpftrace should have provided autopkgtests for
bpftrace.
However upstream has disabled building the tests, and a rebase of the
previous patch pulled that in resulting in the current failure mode:
https://autopkgtest.ubuntu.com/packages/bpftrace
** Patch added: "dcraw-1-9.28-5ubuntu1.diff"
https://bugs.launchpad.net/ubuntu/+source/dcraw/+bug/2060672/+attachment/5762727/+files/dcraw-1-9.28-5ubuntu1.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Current package versions fails to build due to a `memmem` prototype
mismatch: https://launchpad.net/ubuntu/+source/dcraw/9.28-5build1
** Affects: dcraw (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
Someone please sponsor, this fixes a clitest autopkgtest regression
caused by the introduction of the test framework patch.
** Patch added: "tree-1-2.1.1-2ubuntu3.diff"
https://bugs.launchpad.net/ubuntu/+source/tree/+bug/2056099/+attachment/5762166/+files/tree-1-2.1.1-2ubuntu3.diff
--
You
This is now in proposed, setting to 'Fix committed'
** Changed in: grub2 (Ubuntu Noble)
Status: Triaged => Fix Committed
** Changed in: grub2 (Ubuntu Mantic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: grub2-unsigned (Ubuntu Mantic)
Status: New => Invalid
** Changed in: grub2-unsigned (Ubuntu Mantic)
Status: Invalid => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- We should update shim and shim-signed to 15.8, this version addresses
- multiple security issues.
+ [Impact]
+
+ shim 15.7 is affected by multiple CVEs, including a critical severity
+ one allowing Secure Boot bypass when netbooting.
+
+ [Test Plan]
+
+ Make sure the
Loopback booting from an ISO image isn't really an intended use-case.
The hybrid ISOs can be directly written to raw a USB block device and
booted that way.
We are aware of Debian support for f2fs and intentionally decided to
remove it in Ubuntu.
--
You received this bug notification because
*** This bug is a duplicate of bug 1940723 ***
https://bugs.launchpad.net/bugs/1940723
** This bug has been marked a duplicate of bug 1940723
GRUB (re)installation failing due to stale grub-{pc,efi}/install_devices
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 2056562 ***
https://bugs.launchpad.net/bugs/2056562
** This bug has been marked a duplicate of bug 2056562
shim-signed 1.57+15.8-0ubuntu1 upgrade failing due to
grub-common/2.12-1ubuntu3 still being present during installation
--
You received this bug
Status: New
** Changed in: shim (Ubuntu Focal)
Assignee: (unassigned) => Mate Kukri (mkukri)
** Changed in: shim (Ubuntu Jammy)
Assignee: (unassigned) => Mate Kukri (mkukri)
** Changed in: shim (Ubuntu Mantic)
Assignee: (unassigned) => Mate Kukri (mkukri)
** Changed
Is there any practical utility for this? I don't think that is a
supported use case, and *someone might use this* isn't a justifiable
reason to significantly increase our Secure Boot attack surface.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: time-t
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058958
Title:
armhf autopkgtest failure (due to time_t format args)
To manage notifications about this bug go to:
** Patch added: "1-23.1.0-1ubuntu2.diff"
https://bugs.launchpad.net/ubuntu/+source/gvmd/+bug/2058958/+attachment/5759338/+files/1-23.1.0-1ubuntu2.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Various places in the code use `%ld` as a format arg for time_t, this is
incorrect when using 64-bit time_t on 32-bit arches.
** Affects: gvmd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
** Also affects: ubuntu-boot-test (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-boot-test (Ubuntu)
Status: New => Fix Released
** Changed in: ubuntu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member
Added DEP3 header
** Patch added: "2-0.20.1-1ubuntu1.diff"
https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/2052809/+attachment/5756244/+files/2-0.20.1-1ubuntu1.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Added DEP3 header
** Patch added: "2-0.29.1+ds-1ubuntu4.diff"
https://bugs.launchpad.net/ubuntu/+source/bpfcc/+bug/2052813/+attachment/5756245/+files/2-0.29.1+ds-1ubuntu4.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This diff enables the bpftrace test suite as autopkgtests.
I was unable to get some sub-tests working, so some sub-tests are
disables. Over 80% of the original test suite is executed, so it should
still provide some useful coverage.
** Patch added: "1-0.20.1-1ubuntu1.diff"
** Description changed:
systemd-stub fails to boot when loaded via peimage.
This is because peimage internally allocates an ImageHandle for images
it starts and loads. systemd-stub will then pass its own ImageHandle as
ParentImageHandle to the firmware's LoadImage() function to load
Public bug reported:
systemd-stub fails to boot when loaded via peimage.
This is because peimage internally allocates an ImageHandle for images
it starts and loads. systemd-stub will then pass its own ImageHandle as
ParentImageHandle to the firmware's LoadImage() function to load and
start the
** Summary changed:
- package shim-signed 1.57+15.8-0ubuntu1 failed to install/upgrade: subproces
van pakket shim-signed werd script post-installation geïnstalleerd gaf de
foutwaarde 10 terug
+ shim-signed upgrade failing due to grub-common/2.12-1ubuntu3 still being
present during installation
*** This bug is a duplicate of bug 2056562 ***
https://bugs.launchpad.net/bugs/2056562
@vorlon this is the case of shim-signed triggering grub-multi-install
from the previous broken grub-common, because shim is being upgraded
first.
@mariano-cabrera A solution to upgrade the system
*** This bug is a duplicate of bug 2056562 ***
https://bugs.launchpad.net/bugs/2056562
** This bug has been marked a duplicate of bug 2056562
shim-signed upgrade failing due to grub-common/2.12-1ubuntu3 still being
present during installation
--
You received this bug notification
Can you try just upgrading grub-common and grub2-common first and then
upgrading shim-signed?
E.g. by:
apt update
apt install --only-upgrade grub-common grub2-common
apt install --only-upgrade shim-signed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Can you try just upgrading grub-common and grub2-common first and then
upgrading shim-signed?
E.g. by:
apt update
apt install --only-upgrade grub-common grub2-common
apt install --only-upgrade shim-signed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi,
Can you check what version of the grub-common and grub2-common packages
does your system have installed? (dpkg -l)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056562
Title:
package
*** This bug is a duplicate of bug 1940723 ***
https://bugs.launchpad.net/bugs/1940723
Hello,
It seems your hard disk configuration has changed, and the previously
selected grub installation device is no longer valid.
Please run `dpkg-reconfigure grub-efi-amd64-signed`, and select the disk
This should bring some working autopkgtests to this package by disabling
a set of failing tests.
** Patch added: "1-0.29.1+ds-1ubuntu4.diff"
https://bugs.launchpad.net/ubuntu/+source/bpfcc/+bug/2052813/+attachment/5753840/+files/1-0.29.1+ds-1ubuntu4.diff
--
You received this bug
Public bug reported:
I can't seem to build bpfcc against llvm-18. Please see buildlog
** Affects: llvm-toolchain-18 (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "bpfcc_0.29.1+ds-1ubuntu4_amd64-2024-03-07T16:46:48Z.build"
The fix for this has migrated to release now and newly built ISOs should
not need any workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055294
Title:
/usr/lib/grub/grub-multi-install fails
Tagging foundations-todo for the u-r-u change
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054103
Title:
grub-pc reinstallation throws a prompt asking the device
>The following packages will be REMOVED:
> grub-common grub2-common grub2-themes-ubuntustudio libefiboot1t64
> libefivar1t64 memtest86+ os-prober plymouth-theme-ubuntustudio
> ubuntustudio-lowlatency-settings
As vorlon pointed out to me, these removals a looks like *a problem* here, and
I
@martinx, apologies the fix is committed and is currently waiting on
archive work to migrate to release.
In the meantime you can run:
```
echo grub-pc grub-efi/cloud_style_installation boolean false | sudo
debconf-set-selections
```
before the upgrade as a workaround and it should succeed.
--
Hi,
Is there a particular reason why this bug is Private?
This unfortunately seems like a firmware issue to me.
> grub-install: warning: Cannot set EFI variable Boot0003.
> grub-install: warning: efivarfs_set_variable: writing to fd 7 failed: Invalid
> argument.
> grub-install: warning:
*** This bug is a duplicate of bug 2055294 ***
https://bugs.launchpad.net/bugs/2055294
** This bug has been marked a duplicate of bug 2055294
/usr/lib/grub/grub-multi-install fails on noble-daily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 2055294 ***
https://bugs.launchpad.net/bugs/2055294
Hi I believe this is caused by the same issue as LP: #2055294, the fix
is committed, and is currently being held up by archive transitions.
I'll mark this as a duplicate of LP: #2055294 for now, and we can
*** This bug is a duplicate of bug 2055294 ***
https://bugs.launchpad.net/bugs/2055294
** This bug is no longer a duplicate of bug 2055235
package grub-efi-amd64-signed 1.201+2.12-1ubuntu1 failed to install/upgrade:
installed grub-efi-amd64-signed package post-installation script
*** This bug is a duplicate of bug 2055294 ***
https://bugs.launchpad.net/bugs/2055294
This is most likely a duplicate of the grub-multi-install issue which
unfortunately slipped by. The fix is committed, and currently being held
up by archive transition things
** This bug has been marked a
** Description changed:
- We should update shim, and shim-signed to 15.8, this version addresses
+ We should update shim and shim-signed to 15.8, this version addresses
multiple security issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This is possibly caused by the new ubuntu3 `grub2` package. We are on
releasing an `ubuntu4` which resolves a known issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055235
Title:
package
** This bug is no longer a duplicate of bug 1940723
GRUB (re)installation failing due to stale grub-{pc,efi}/install_devices
** This bug has been marked a duplicate of bug 2055294
/usr/lib/grub/grub-multi-install fails on noble-daily
** This bug is no longer a duplicate of bug 2055294
1 - 100 of 124 matches
Mail list logo
