@rcj
these are ubuntu-server daily-prinstalled images. See
http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/pending/
currently it's arm64+pi armhf+pi riscv64+unleashed riscv64+unmatched,
and this wants to add arm64+generic and amd64+generic variants.
--
You received this bug notificat
** Changed in: systemd (Ubuntu)
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779721
Title:
systemd-networkd does not configure DHCPv4
Public bug reported:
unleashed fails to boot of sd-card with u-boot-sifive from hirsute
1) focal's u-boot-sifive on loader1/loader2 boots hirsute's 5.11 kernel
fine.
2) upgrading loader1/loader2 to u-boot-sifive from hirsute makes the sd-
card boot of sifive fail with
This is a banner for port
@ycheng-twn securution/foundations would like to recheck fwupd.efi
binaries.
we will not release new shim to groovy, until we know that fwupd.efi is
compatible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
The way uc20 is booted, and how bind mounts are setup means that we do
force unmount eventually.
It matters which snaps are installed, and which processes have memory
mapped which files.
Many things should probably be marked for lazyunmount.
Please provide details why is held up /oldroot/run/mnt
20.04.1 is obsolete point release. Can you please try with 20.04.2?
** Changed in: nvidia-graphics-drivers-455 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Changed in: livecd-rootfs (Ubuntu)
Importance: Undecided => Critical
** Changed in: livecd-rootfs (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923832
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Tags added: rls-hh-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923150
Title:
unexpected error pop-up after '
dropping armhf from scope of this bug for now, until grub is SRUed with
working armhf support.
** Summary changed:
- Provide generic preinstalled images for armhf, arm64, amd64
+ Provide generic preinstalled images for arm64, amd64
** Description changed:
- Provide generic preinstalled images f
I did not ask for this to be removed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923833
Title:
removal of more udeb packages
To manage notifications about this bug go to:
https://bugs.launchpad
or do you not need localechooser-data at all for calamares?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923881
Title:
Lubuntu and Ubuntu Studio Hirsute incorrectly launch Ubiquity
installer
To
leh sigh.
I think the right way forward is for ubiquity to publish _standalone_
ubiquity-localechooser-data like package, which otherwise has no other
ubiquity dependencies.
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu)
Sta
21.04 still ships i386 as a partial architecture. Hence it has not been
removed.
** Changed in: ubuntu
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918137
Title:
** Changed in: gnutls28 (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851427
Title:
Consider updating GNUTLS for TLSv1.3 and unified config w/Focal
To
I would not want to fix this.
CA that use SHA1 are insecure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875920
Title:
New default %PROFILE_MEDIUM breaks root ceritificates which use SHA1
To m
Public bug reported:
Provide generic preinstalled images for armhf, arm64, amd64
They should broadly look like ubuntu-cpc cloud image, however they
should be
1) RAW .xz compressed disk images
2) use linux-generic, instead of linux-virtual
3) have CIDATA partition with sample datasource files tha
Public bug reported:
It seems that ESP sizes differ between
* desktop
* server subiquity
* server maas
* server preinstalled
* cloud-images
I see numbers like 512MiB, 538 (?!), 204 (?), 106MiB.
I guess all of them should be 512MiB. But I guess increasing ESP size
can be seen as a regression by c
@callegar
It would be nice to see the full resolvectl status.
Because depending on which things you have configured it might be
expected to have DNSSEC validation working, and the request is routed to
multiple interfaces, and none of them return results or the results fail
to validate.
Also note
@vorlon this is the same user that already is in `sudo` & `lxd` groups,
thus they can do that anyway.
To use the real UART rx/tx pins one has to disable bluetooth and use
/dev/ttyAMA0
For gpio pins, I see that some use group `gpio` and then mark
/dev/gpiomem to be owned by gpio group.
We should
When upgrading shim-signed, it will install new shim in
/boot/bootx64.efi and in /ubuntu/shimx64.efi, it will also install grub
with sbat section to /ubuntu/grubx64.efi.
If the machine was booting /boot/grubx64.efi before, it will fail, as
/boot/grubx64.efi will remain an old one without sbat sect
*** This bug is a security vulnerability ***
Public security bug reported:
ubuntu must support upgrading images with grub in removable path
Currently whilst we install shim into removable path, we never upgrade
grubx64.efi in the removable path.
This leads to inconsistent behavior, where upgrad
New shim is available in hirsute-proposed now, and I guess since this is
now available in groovy-proposed, we can copy shim into groovy-proposed
to complete end to end testing with the new shim.
** Changed in: fwupd-signed (Ubuntu Hirsute)
Status: In Progress => Fix Released
--
You receiv
Ideally I would want us to split fwupd into fwupd-unsigned & fwupd-
unsigned, like we did with grub.
That way
* fwupd will drop shipping .efi binaries
* fwupd-unsigned will only build and submit .efi binary for signing
* fwupd-signed will ship signed .efi binary
with fwupd-unsigned & fwupd-signed
** Tags removed: block-proposed-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921134
Title:
SBAT shim 15.4 release
To manage notifications about this bug go to:
https://bugs.launchpad.net/
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu)
Milestone: None => ubuntu-21.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
So the issue around providing fdtdir was that qemu did not know what fdt
file to attempt loading, and hence was failing to boot.
Now that we dropped fdtdir in extlinux.conf, all riscv64 boards need to
use preboot to pick up fdt from the .itb. This was already the case on
unleashed and smode, but n
** Changed in: grub2-unsigned (Ubuntu Groovy)
Status: Fix Committed => 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/1915536
Title:
one grub
To manage notifications about this b
** Tags added: block-proposed-hirsute
** Tags added: block-proposed-bionic block-proposed-focal block-
proposed-groovy block-proposed-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921134
Titl
** Tags added: fr-1282
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
confirmed with cpc team, it's good now.
** Changed in: debootstrap (Ubuntu Hirsute)
Status: Triaged => 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/1920055
Title:
debootstrap
Public bug reported:
Ideally we should strive to boot rootfs from a matching hard drive.
I.e. if we are booting rootfs by UUID, we should try to find the one
that came from the same drive as where ESP (UEFI) came from, or u-boot
spl / u-boot got loaded from (loader1/loader2).
Such that for examp
BTW. is https://patchwork.kernel.org/project/linux-
integrity/patch/20210330131636.21711-4-na...@linux.ibm.com/ of any help
to us?
Ideally we'd want to do that, but load the 2017 & 2019 keys there into
the .ima keyring instead of the kernel module signing ones.
--
You received this bug notifica
It appears that although fdtdir option from u-boot-menu works on bare
metal, it breaks qemu booting.
Thus revert it from now, seeking more details from u-boot upstream.
** Also affects: u-boot-menu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: u-boot-menu (Ubuntu)
St
** Also affects: linux-riscv (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
To manage notifica
** Description changed:
When booting on SiFive boards, there are two gettys launched on the same
console.
There is sifive serial console which is the active/only physical
console.
But also, there is serial console exposed over legacy opensbi extension;
which in linux kernel is im
** Attachment added: "direct-qemu-riscv.txt"
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1923162/+attachment/5485930/+files/direct-qemu-riscv.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
This is reproducible with any uboot from focal/groovy/hirsute.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
To manage notifications about this bu
Public bug reported:
When booting v5.11 based riscv unmatched image in qemu with uboot, it
fails to boot.
When booting v5.11 based riscv unmatched kernel+initrd directly, it
boots fine.
Somehow, it seems that u-boot fails to correctly load & start v5.11
kernel.
** Affects: u-boot (Ubuntu)
** Attachment added: "uboot-qemu-riscv.txt"
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1923162/+attachment/5485929/+files/uboot-qemu-riscv.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
When booting on SiFive boards, there are two gettys launched on the same
console.
There is sifive serial console which is the active/only physical
console.
But also, there is serial console exposed over legacy opensbi extension;
which in linux kernel is implemented as hvc0 c
New York I think is a default fallback when there is no internet
connectivity.
Is internet connected properly?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903312
Title:
Ubiquity not selecting co
somehow i was expecting the snap mount units to start after local-
fs.target, and for zfs.target to complete by then. But it looks like
that's not how things are ordered unfortunately.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
It is possible that you have the key in _two_ keyrings in trusted.gpg.d/
& in trusted.gpg itself.
It would be best for you to do the following:
1) sudo apt remove --purge ubuntu-dbgsym-keyring
2) sudo apt-key del 0xC8CAB6595FDFF622
3) sudo apt-key list | grep C8CAB6595FDFF622 => it should be em
Accessibility icon & language selection from preboot environment was
only ever possible on x86, when booting in bios mode, when booting with
isolinux.
focal was the last release to use isolinux.
All releases since focal use unified grub2 bootloader on x64 for both
bios & efi boot, thus the experi
** Changed in: shim (Ubuntu)
Status: New => Confirmed
** Changed in: shim (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922581
Title:
5s boot delay
Note that vTPM presence is at stake here too.
Without vTPM there are no delays.
** Description changed:
# Overview
- Recent changes in boot logic moved grub from "removable disk" path to
"/efi/ubuntu" in order to fix grub package updates. This had the side-effect of
adding a 5-second boot de
1.50.0+dfsg1+llvm-0ubuntu5 is allowed to migrate.
** Changed in: rustc (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/1921445
Title:
bootstrapping 1.50
T
** Changed in: linux-riscv (Ubuntu)
Milestone: None => ubuntu-21.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920916
Title:
cold boot panics on unmatched board, soft reboot is fine
To mana
Alternative to all of the above, you could choose to "enable all the
devices" hack on 18.04.
Aka if the MAAS initrd includes a script to do `chzdev -e --all` by
default on 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
In https://launchpad.net/ubuntu/+source/initramfs-tools/0.133ubuntu3 in
eoan+ manual chzdev -e got added to activate qeth devices, if they have
been specified in the ip= command, i.e. if enc300 is the device in the
ip= command.
This has not been backported to bionic.
To boot without specifying th
** Summary changed:
- SBAT shim 15.3 release
+ SBAT shim 15.4 release
** Description changed:
[Impact]
- * New upstream shim release 15.3
+ * New upstream shim release 15.4
* It includes and enforces SBAT validation
[Test Plan]
* https://wiki.ubuntu.com/UEFI/SecureBoot/ShimU
So shim upstream has changed how sections are ordered now, such that in
shim 15.4 can now be signed by either old or new sbsigntool, and it
verifies correctly in either case.
However, I still think it is a good idea to upgrade to the better
sbsigntool to correctly sign even the odd looking binarie
patch #7 looks good to me!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920825
Title:
FTBFS and autopkgtest failure in Hirsute (badly generated symbols
files)
To manage notifications about this
somehow settings --with / --without did not help, to exclude the filter
commands.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920825
Title:
FTBFS and autopkgtest failure in Hirsute (badly generat
If we only want to replace environment variables and nothing else, we
can use
#!/usr/share/dh-exec/dh-exec-subst-env
then even with DEB_BUILD_PROFILES set, the lines preserve the leading
whitespace.
It would be nice for DEB_BUILD_PROFILES to preserve leading whitespace
and/or only strip it for f
** Description changed:
[Impact]
- * Cannot update apt metadata from ddebs.ubuntu.com whilst using ubuntu-
+ * Cannot update apt metadata from ddebs.ubuntu.com whilst using ubuntu-
dbgsym-keyring package
[Test Plan]
+ * Install ubuntu-dbgsym-keyring package
+ * Add ddebs.ubuntu.
For SRU release - all three source packages must be released / copied
together. It is best to monitor that copies are successful, as
previously src:grub2-unsigned failed to copy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Changed in: grub2-unsigned (Ubuntu Groovy)
Status: New => Fix Committed
** Changed in: grub2-unsigned (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: grub2-unsigned (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: grub2-unsigned (Ubuntu Xenial)
I've marked the SRU bug reports as verification-done, there was positive
test feedback from Certification too. We are in a position to start
release the one-grub updates to at least some series in stages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
@kleber this has been fixed in xenial & bionic now. Retriggering tests
against grub2-signed alone, should all work now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917509
Title:
Call for testing:
Similar on groovy
# dpkg-query -W | grep grub
grub-common 2.04-1ubuntu35.4
grub-efi-amd64 2.04-1ubuntu35.4
grub-efi-amd64-bin 2.04-1ubuntu35.4
grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4
grub2-common2.04-1ubuntu35.4
# apt install grub-efi-amd64-signed
Reading package lists... D
On focal:
# dpkg-query -W | grep grub
grub-common 2.04-1ubuntu26.9
grub-efi-amd64 2.04-1ubuntu26.9
grub-efi-amd64-bin 2.04-1ubuntu26.9
grub-efi-amd64-signed 1.142.11+2.04-1ubuntu26.9
grub2-common2.04-1ubuntu26.9
grub2-common from release is good enough for one grub (it is same maj
In bionic chroot, without proposed, installed grub-efi-amd64-signed
# dpkg-query -W | grep grub
grub-common 2.02-2ubuntu8.21
grub-efi-amd64 2.02-2ubuntu8.21
grub-efi-amd64-bin 2.02-2ubuntu8.21
grub-efi-amd64-signed 1.93.24+2.02-2ubuntu8.21
grub2-common2.02-2ubuntu8.21
Enable -prop
In xenial chroot, without proposed, installed grub-efi-amd64-signed
# dpkg-query -W | grep grub
grub-common 2.02~beta2-36ubuntu3.29
grub-efi-amd64 2.02~beta2-36ubuntu3.29
grub-efi-amd64-bin 2.02~beta2-36ubuntu3.29
grub-efi-amd64-signed 1.66.29+2.02~beta2-36ubuntu3.29
grub2-common2.
** Changed in: ubuntu-keyring (Ubuntu Hirsute)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920640
Title:
EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbo
** Description changed:
needrestart MIR has been completed.
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/1907422
We are post FF, thus I am asking FFe to include needrestart as
recommends in the ubuntu-server package.
This change will results in needrestart being insta
Public bug reported:
needrestart MIR has been completed.
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/1907422
We are post FF, thus I am asking FFe to include needrestart as
recommends in the ubuntu-server package.
This change will results in needrestart being installed by default i
situation in hirsute is not sorted yet.
we had to revert & remove 1.50 from hirsute, and currently 1.49 is published
there once again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915722
Title:
r
Public bug reported:
bootstrapping 1.50
** Affects: rustc (Ubuntu)
Importance: Undecided
Status: New
** Tags: block-proposed update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
"America" does not maintain neither tzdata nor ISO 3166-2 database, both
of which are delegated to international community of Internet Standards
via RFC & to a committee headquartered in Genera with delegates from all
around the world. All of which has lots of experience with classifying
and updati
** Changed in: ubuntu-keyring (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: ubuntu-keyring (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** Changed in: ubuntu-keyring (Ubuntu Groovy)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920640
Title:
EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Arch
** Description changed:
+ [Impact]
+
+ * Cannot update apt metadata from ddebs.ubuntu.com whilst using ubuntu-
+ dbgsym-keyring package
+
+ [Test Plan]
+
+ * Install ubuntu-dbgsym-keyring package
+ * Add ddebs.ubuntu.com repository for your release
+ * sudo apt update must be successful
+
Verifying existing binaries with new sbsigntool:
# wget
http://archive.ubuntu.com/ubuntu/dists/bionic/main/uefi/fwupdate-amd64/current/fwupx64.efi.signed
# wget
http://archive.ubuntu.com/ubuntu/dists/bionic/main/uefi/fwupdate-amd64/current/control/uefi.crt
# sbverify --cert ./uefi.crt ./fwupx64.
# wget
https://launchpad.net/ubuntu/+source/sbsigntool/0.9.2-2ubuntu1~18.04.1/+build/21207939/+files/sbsigntool_0.9.2-2ubuntu1~18.04.1_amd64.deb
# apt install ./sbsigntool_0.9.2-2ubuntu1~18.04.1_amd64.deb
# dpkg-query -W sbsigntool
sbsigntool 0.9.2-2ubuntu1~18.04.1
# sbverify --cert 15.3-0u
# dpkg-query -W sbsigntool
sbsigntool 0.6-3.2ubuntu2
# sbverify --cert 15.3-0ubuntu1~ppa1/control/uefi.crt
15.3-0ubuntu1~ppa1/shimaa64.efi.signed
warning: gap in section table:
.data : 0x0007f000 - 0x000b3800,
.sbat : 0x000b4000 - 0x000b5000,
gaps in the section table may result
TASK [apps/app_web : install browsers] *
fatal: [focal-uefi]: FAILED! => changed=false
cache_update_time: 1616679270
cache_updated: false
msg: |-
'/usr/bin/apt-get -y -o "Dpkg::Options::=--force-confdef" -o
"Dpkg::Options::=--force-confold" i
Public bug reported:
preseeded snaps prevent installing chromium-browser deb2snap in chroot,
again
potentially https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1882232 regressed since preseeded snaps landed in focal
desktop.
** Affects: chromium-browser (Ubuntu)
Importance:
Also good to check that existing bionic x64 binaries still verify
correctly. I.e. grub / kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921387
Title:
launchpad signing shimaa64.efi fails to
** Description changed:
[Impact]
* Calculating the hash of the binary is ill defined if there are gaps
in sections, or sections are not aligned to ensure that signature table
is aligned.
* This results in sbsign/sbverify to calculate incorrect hash when
there are gaps, such as
** Description changed:
[Impact]
* Calculating the hash of the binary is ill defined if there are gaps
in sections, or sections are not aligned to ensure that signature table
is aligned.
* This results in sbsign/sbverify to calculate incorrect hash when
there are gaps, such as
** Description changed:
- launchpad signing shimaa64.efi fails to validate
+ [Impact]
+
+ * Calculating the hash of the binary is ill defined if there are gaps
+ in sections, or sections are not aligned to ensure that signature table
+ is aligned.
+
+ * This results in sbsign/sbverify to calcu
Public bug reported:
launchpad signing shimaa64.efi fails to validate
cd $(mktemp -d)
wget
http://ppa.launchpad.net/xnox/nonvirt/ubuntu/dists/hirsute/main/signed
/shim-arm64/15.3-0ubuntu1~ppa1/signed.tar.gz
tar xvf ./signed.tar.gz
sbverify --cert 15.3-0ubuntu1~ppa1/control/uefi.crt
15.3-0ubunt
That was old keyring location.
They should now be in the platform keyring
Can you check that the certs you expect are in:
$ sudo keyctl list %:.platform
?
** Changed in: efitools (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of
To be fair, Sevastopol has always had a special status of a federal city
- across all times. Closes analogy being Vatican City. It was federal
city separate from Crimea during whichever government defacto government
ruling be it USSR, Ukranian SSR, Ukrain or Russian Federation.
--
You received th
In the iso-codes package there is a related issue, ISO 3166-2:RU
contains no codes for the Russian-administered Republic of Crimea and
Federal City of Sevastopol. Instead the UA codes are still specified,
i.e. UA-43 for Crimea.
** Also affects: iso-codes (Ubuntu)
Importance: Undecided
St
** Description changed:
- initramfs-tools does not include fsck in initrd if MNT_PASS equals zero
- in the fstab entries.
+ [Impact]
+
+ * initramfs-tools does not include fsck in initrd if MNT_PASS equals
+ zero in the fstab entries.
This has lead to the following situation :
when droppi
*** This bug is a security vulnerability ***
Public security bug reported:
[Impact]
* New upstream shim release 15.3
* It includes and enforces SBAT validation
[Test Plan]
* https://wiki.ubuntu.com/UEFI/SecureBoot/ShimUpdateProcess/TestPlan
[Where problems could occur]
* Upgrading to new
** Changed in: shim (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838712
Title:
TPM event log does not contain kernel validation key
To manage notificatio
Setting the status of the bug report to Opinion, as it doesn't fit the
scope of Ubuntu project. It has to be fixed by IANA in upstream releases
of tzdata. Once they come up with a better solution in the file format,
the bug can change to confirmed to be integrated in Ubuntu.
--
You received this
Is there anything in particular about all the other packages that you
marked them as affected? I suspect that they all use Ubuntu's provided
tzdata as the source of information, and hence they will all be
reflecting simply whatever tzdata tells them. Hence any changes will be
automatically reflecte
The upstream IANA tzdata file format is very restrictive and cannot
change and reflect country codes correctly, across correct historical
dates.
>From "europe" file:
Zone Europe/Simferopol 2:16:24 - LMT 1880
2:16 - SMT 1924 May 2 # Simferopol Mean T
Also note https://bugs.launchpad.net/subiquity/+bug/1905932
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920933
Title:
live desktop system booted with ip=dhcp has the right lease, hostname
not s
Looks like we carry out of date l2_cache patch
https://paste.ubuntu.com/p/y6hWvqYhdF/
** Changed in: linux-riscv (Ubuntu)
Status: New => In Progress
** Changed in: linux-riscv (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notifi
** Summary changed:
- sometimes cold boot hangs on unmatched board
+ cold boot panics on unmatched board, soft reboot is fine
** Attachment added: "screenlog.0"
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1920916/+attachment/5480079/+files/screenlog.0
** Description changed:
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Public bug reported:
[ 16.319808] pci :04:00.0: enabling device ( -> 0002)
[ 16.325596] Kernel panic - not syncing: L2CACHE: DirFail @
0x.0001CB00
[ 16.325665] L2CACHE: No. of Banks in the cache: 4
[ 16.332152] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.11.0-1002-generic
As per private conversation, it's not a bug but a feature to only
consider candidates by default.
** Changed in: apt (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/b
never mind `apt build-dep` also fails.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920804
Title:
Apt does not seem to automatically consider non-candidates when
resolving deps
To manage notifi
Public bug reported:
# apt show sbuild-build-depends-main-dummy
Package: sbuild-build-depends-main-dummy
Version: 0.invalid.0
Maintainer: Debian buildd-tools Developers
Installed-Size: unknown
Depends: debhelper (>= 9), debhelper-compat (= 12), dpkg-dev (>= 1.17.14),
python3, cargo (>= 0.40.0),
801 - 900 of 9087 matches
Mail list logo
