** Changed in: evdi (Ubuntu Hirsute)
Status: Confirmed => In Progress
** Changed in: evdi (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux-hwe-5.11 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ub
** Description changed:
[Impact]
focal users running latest hwe kernel, version 5.11, won't be able to use
evdi-dkms.
[Test case]
Built evdi dkms and loaded the evdi module on 5.4, 5.8 and 5.11 kernels.
[Potential regression]
DisplayLink devices will stop working.
-
--
** Description changed:
[SRU Justification]
[Impact]
backport-iwlwifi-dkms/8324-0ubuntu3~20.04.3 ADT test failure with linux-
hwe-5.11/5.11.0-20.21~20.04.1.
[Fix]
In Focal, we have been disabling installing of built DKMS binary modules
since bug 1863583. While it's unlike
** Description changed:
[Impact]
Openafs 1.8.4~pre1-1ubuntu2.1 FTBFS when built against Linux 5.11
-
[Fix]
Apply the attached debdiff (that is, in turn, a backport of upstream
Linux build fixes), build the debs, install the dkms deb and build it
against an installed 5.11 ker
** Description changed:
[Impact]
This is a scripted bug report about ADT failures while running xtables-
addons tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether
this is caused by the dep8 tests of the tested source or the kernel has
yet to be determined.
Testing fa
ubuntu@gen2:~$ dpkg-query -W linux-cloud-tools-common
linux-cloud-tools-common5.4.0-79.88
ubuntu@gen2:~$ systemctl status hv-kvp-daemon.service
● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon
Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor
preset: ena
python3.5 has stopped passing its testsuite due to expried test certs.
Thus upload of openssl has triggered regression in python3.5
I've cherrypicked updated test certs and keys, but to cherry-pick those
cleanly, I also had to cherrypick an earlier bug fix. All of these are
unmodified from 3.5.10
PPA with these changes available from https://launchpad.net/~ci-train-
ppa-service/+archive/ubuntu/4594
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928989
Title:
expiring trust anchor compatibili
ADT results at https://bileto.ubuntu.com/excuses/4594/xenial.html
** Description changed:
[Impact]
* openssl fails to talk to letsencrypt website past September 2021,
despite trusting the letsencrypt root certificate.
[Test Plan]
* Import staging cert equivalent to ISRG Root
I am glad that this worked out fine now.
I am not sure there is time to fix this in 20.10, as it has only a few
months of support left. I hope that having libffi7 in 21.04 is enough.
** Changed in: pyopenssl (Ubuntu Groovy)
Status: Incomplete => Invalid
** Changed in: pyopenssl (Ubuntu)
My understanding of resilient boot is that there are multiple ESPs
trying to boot the same raid device.
If there is only one rootfs filesystem, boot that one. Which in case of
raid, there will be only one.
I'm more concerned about the case of two ubuntu-server preinstalled
images on two usb stick
Public bug reported:
[Impact]
* regression in xenial updates - grub2 cannot handle new relocations
* grub-efi-arm64-bin gained new recommends on -signed package which is
attempted to be installed
* it pulls in one grub which was built with a newer toolchain and has
more relocations
* non-s
** Patch added: "grub2_2.02_beta2-36ubuntu3.31_2.02_beta2-36ubuntu3.32.diff"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1926748/+attachment/5493871/+files/grub2_2.02_beta2-36ubuntu3.31_2.02_beta2-36ubuntu3.32.diff
--
You received this bug notification because you are a member of Ubu
** Also affects: openafs (Ubuntu Focal)
Importance: Undecided
Status: New
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915854
Title:
openafs-modules-dkms:
I've rebuilt all the packages mentioned above in bileto ppa against
security pocket and pushed them to focal-proposed queue, ready for sru
review and accept.
All, but openafs which ftbfs now, and will need to be fixed up for v5.11
anyway. So it will be rebuild in security pocket with v5.11 fixes l
debdiffs are on https://bileto.ubuntu.com/#/ticket/4543
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914279
Title:
linux from security may force reboots without complete dkms modules
To manage no
dbxupdate got published on uefi.org website. I would be happy to sponsor
the fwupd debdiff for groovy now. To unblock roll-outs of the new shim.
The split to have standalone fwupd-efi should happen as it is a good
idea - it will enable shipping newer fwupd user-space tooling in the
snap / OEM arch
This is because one-grub update was published in xenial, but not in
bionic.
Thus upgrading from xenial-proposed to bionic-updates introduces
regression.
To mitigate this issue you can temporarily eanble bionic-proposed and
install all packages from there.
This is due to breakage introduced in xe
@vorlon please do not publish packages in earlier series before later
ones, as otherwise, as shown above, upgrade from xenial to bionic
introduces regressions.
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Steve Langasek (vorlon)
--
You received this bug notification because you a
This bug was fixed in the package lttng-modules - 2.12.5-1
Sponsored for Paolo Pisati (p-pisati)
---
lttng-modules (2.12.5-1) unstable; urgency=medium
* [8e0b514] New upstream version 2.12.5
* [9feae13] Refreshed patches
* Add support for kernel v5.11
* Add support for stable
virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (s390x, ppc64el, armhf,
arm64) -> is a false negative. virtualbox-hwe is only supported on amd64
i thought.
https://autopkgtest.ubuntu.com/packages/v/virtualbox
https://autopkgtest.ubuntu.com/packages/v/virtualbox-hwe
Suggests that to be the case.
--
** Description changed:
shim supports disabling validation using shim specific variable, whilst
keeping the firmware secureboot on.
The state for it, is currently incorrectly parsed on Ubuntu, and thus
error message is not printed that machine is booting without signature
verification
Could you please boot daily impish image, and let us know if you still
observe the messages in question?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
Title:
Failed to set MokListRT: Invalid
$ dput ubuntu dwarves-dfsg_1.20-1ubuntu1_source.changes
Checking signature on .changes
gpg: /tmp/dwarves-dfsg_1.20-1ubuntu1_source.changes: Valid signature from
9B8EC849D5EF70ED
Checking signature on .dsc
gpg: /tmp/dwarves-dfsg_1.20-1ubuntu1.dsc: Valid signature from 9B8EC849D5EF70ED
Uploading to
sru-release comments:
virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (s390x, ppc64el, armhf,
arm64) -> autopkgtest failures are a false negative. It only is built
and supported on amd64
sysdig/riscv64 - ftbfs is not a regression, never built on riscv64 in
focal
zfs-linux/riscv64 - ftbfs is not a re
** Changed in: u-boot (Ubuntu)
Status: Fix Released => New
** Changed in: u-boot (Ubuntu Hirsute)
Status: Fix Released => Triaged
** Changed in: u-boot (Ubuntu Hirsute)
Status: Triaged => New
** Changed in: u-boot (Ubuntu)
Importance: Critical => Undecided
** Also affect
** Changed in: shim-signed (Ubuntu)
Status: New => Triaged
** Changed in: shim-signed (Ubuntu)
Importance: Undecided => Critical
** Changed in: shim (Ubuntu)
Importance: Undecided => Critical
** Changed in: shim (Ubuntu)
Status: New => Triaged
--
You received this bug notif
** Description changed:
- When booting v5.11 based riscv unmatched image in qemu with uboot, it
- fails to boot.
+ [Impact]
- When booting v5.11 based riscv unmatched kernel+initrd directly, it
- boots fine.
+ * u-boot may crash when attempting to boot extlinux.conf which
+ specifies fdtdir; t
For your current work around to persist, you should also do:
$ sudo dpkg-divert /usr/lib/shim/shimx64.efi.signed
$ sudo cp /usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed
/usr/lib/shim/shimx64.efi.signed
This way whenever grub-install is called, _grub_ is used instead of
shim.
Unfortunately
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
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
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
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
** 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
** 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
** 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
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
** 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/
** 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/
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
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
*** 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
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
@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
@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
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
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
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
** 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
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:
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
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
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
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
** 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 '
** 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
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
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
@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
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
** 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
@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
# file perl-base_5.32.1-3ubuntu2_amd64.deb
perl-base_5.32.1-3ubuntu2_amd64.deb: Debian binary package (format 2.0), with
control.tar.zs, data compression zst
Looks odd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
# display 3rd character of file name extension like 2 of bz2 or m of lzma
>&-1ubyte x \b%c
>>&0ubyte !0x20
>>>&-1 ubyte !0x2f
is odd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The concern is that uefi amd64 image format is widely used as the basis
for other image formats.
And that it must not have baked in datasource when creating new formats.
It should be harder to missbuild images.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
MBA 5,2 is https://support.apple.com/kb/SP670?locale=en_GB aka MacBook
Air (13-inch, Mid 2012)
** Also affects: shim-signed (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Can you please check that the machine boots with just grub without shim.
Aka, replace /EFI/Boot/BOOTX64.efi & /ef/ubuntu/shimx64.efi files wtih
/efi/ubuntu/grubx64.efi => this could possibly be a workaround, given
that secureboot is not possible on Mac platforms.
--
You received this bug notific
Upstream recommends to try https://github.com/rhboot/shim/pull/364/files
patch. I'll prepare an upload of that into a PPA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925010
Title:
shim-signed do
Public bug reported:
efi: Failed to lookup EFI memory descriptor
is an error message generated by the kernel.
Please pull in https://github.com/rhboot/shim/pull/361/files to fix it.
** Affects: shim (Ubuntu)
Importance: Undecided
Status: New
** Affects: shim-signed (Ubuntu)
Public bug reported:
shim supports disabling validation using shim specific variable, whilst
keeping the firmware secureboot on.
The state for it, is currently incorrectly parsed on Ubuntu, and thus
error message is not printed that machine is booting without signature
verification by shim.
plea
ltrager - the secure-boot.log ends with
"EFI stub: UEFI Secure Boot is enabled."
Which is the first message from the loaded linux kernel. At this point
grub & shim have all succeeded, no?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Can you please try to have the installed machine booting without 'quiet'
and with 'earlyprintk=efi' ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865515
Title:
Chainbooting from grub over the net
I am concerned about the -no-reboot option, and what constitutes a
"reboot".
Because chainloader; exit 1; boot linux => all can look like reboots
depending what qemu is monitoring/trapping. As all of those things start
brand new EFI application via LoadImage2 call.
--
You received this bug notif
Public bug reported:
u-boot unmatched dtb does not match kernel dtb
We have reverted u-boot-menu upload and stopped using kernel provided
dtbs, because that was preventing booting hirsute images under qemu. As
dtb generated by qemu should be used, and there is no kernel provided
dtb for qemu plat
** Changed in: u-boot (Ubuntu Hirsute)
Status: Fix Released => 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 notifications ab
** Tags added: block-proposed-hirsute
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925267
Title:
u-boot unmatched dtb does not match kernel dtb
To manage notificati
** Tags added: block-proposed 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/1923162
Title:
riscv64 images fail to boot in qemu
To manage notifications about this bug go to:
h
$ wget http://archive.ubuntu.com/ubuntu/dists/groovy-proposed/main/uefi
/fwupd-amd64/1.4.7-0~20.10.1/fwupdx64.efi.signed
$ md5sum fwupdx64.efi.signed
e3a387f8f87852e670d105145cb96168 fwupdx64.efi.signed
$ objdump -h ./fwupdx64.efi.signed
./fwupdx64.efi.signed: file format pei-x86-64
Sectio
Also i am kind of confused why there are different per-arch grub.cfg for
enlistment.
there is no reason to have different grub.cfg per arch, as inside the
grub.cfg that is served everything can be provided for all arches.
--
You received this bug notification because you are a member of Ubuntu
B
I am slightly confused what is being asked here.
The default grub.cfg that is built into grubnet comes from here:
https://git.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/tree/debian
/build-efi-images?h=ubuntu#n71
Can you please make a merge proposal with exactly what you are asking
for?
Cau
Can you please paste the contents of MAAS generated:
grub.cfg-default-amd64
grub.cfg-default-arm64
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923268
Title:
grubnet default grub.cfg should tr
Note that upstream and all distro grubs have moved on to query for:
"""
This patch implements a search for a specific configuration when the config
file is on a remoteserver. It uses the following order:
1) DHCP client UUID option.
2) MAC address (in lower case hexadecimal with dash separato
Public bug reported:
[Impact]
* armhf & arm64 images do not contain cpc image customizations for
grub.
Specifically they do not have
/etc/default/grub.d/50-cloudimg-settings.cfg
Which disables "quiet splash", removes timeouts, enables serial
consoles.
[Test Plan]
* Boot arm64 clo
Public bug reported:
ARM images should support ttyAMA0 too
It is more common for i.e. arm virtual machines to have tty on ttyAMA0
rather than on ttyS0 or hvc0, thus we should support ttyAMA0 by default
in cloud images for ARM.
** Affects: cloud-images
Importance: Undecided
Status:
Public bug reported:
something something precise (test bug)
** Affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux-gcp (Ubuntu Precise)
Importance: Undecided
Status: Won't Fix
** Affects: linux-gcp (Ubuntu Trusty)
Importance:
** Description changed:
[Impact]
* openssl fails to talk to letsencrypt website past September 2021,
despite trusting the letsencrypt root certificate.
[Test Plan]
* Import staging cert equivalent to ISRG Root X1
https://letsencrypt.org/certs/staging/letsencrypt-stg-root-x1.
I would have thought that this patch upstream would have been suitable
for stable series.
It seems like the bug that the patch fixes is not annotated correctly,
hence it was not picked for stable updates yet.
I wonder if we should try to submit to linux-stable for v5.4 v5.8
series.
--
You recei
Re: u-boot-menu backport, imho debian/changelog should have documented
that debhelper-compat version is lowered from 13 to 12, to make it build
on focal. But also it is self-explanatory (i did try to get debhelper 13
into focal before it released, but that upload got rejected).
Otherwise no change
@jawn-smith https://paste.ubuntu.com/p/hjqFz46frm/ is what i'm
sponsoring, after fix ups.
--
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
re: u-boot-menu backport, imho the debian/changelog should be merged and
focal entries should not be lost.
--
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
** Summary changed:
- Update dwarves-dfsg in focal to version 1.17 from groovy
+ Update dwarves-dfsg in focal to version 1.21 from hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912811
Title:
** Description changed:
[Impact]
BTF is an extremely useful tool for BPF developers. Enabling BTF support
- in the kernel requires pahole 1.16 or later, but in focal we have only
- 1.15. The simplest path for us to get a sufficiently updated version of
- pahole is to backport dwarves-dfsg f
Preparing packages in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4619/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912811
Title:
Update dwarves-dfsg in focal to version
For SRU see https://bugs.launchpad.net/ubuntu/+source/dwarves-
dfsg/+bug/1912811
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928244
Title:
pahole: FAILED unresolved symbol cubictcp_state with lin
** Description changed:
[Impact]
BTF is an extremely useful tool for BPF developers. Enabling BTF support
in the HWE kernel requires pahole from dwarves-dfsg 1.21 or later, but
in focal we have only 1.15. The simplest path for us to get a
sufficiently updated version of pahole is to b
(bionic-amd64)root@ottawa:/tmp# dpkg-query -W initramfs-tools liblz4-tool zstd
initramfs-tools 0.130ubuntu3.13
liblz4-tool 0.0~r131-2ubuntu3.1
zstd1.3.3+dfsg-2ubuntu1.2
(bionic-amd64)root@ottawa:/tmp# mkinitramfs -c zstd -o zstd-initrd.img
4.15.0-150-generic
(bionic-amd64)root@ottawa:/tmp
Public bug reported:
Over at https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-
dkms/+bug/1932158
you can observe that it was chosen to skip the dkms module for a given
kernel, and dkms-autopkgtest did not manage to handle it well.
** Affects: dkms (Ubuntu)
Importance: Undecided
Opened https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1936344 to
make dkms autopkgtest smarter.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932158
Title:
backport-iwlwifi-dkms/8324-0ubuntu3~
Building initial module for 5.4.0-77-generic
Error! The
/var/lib/dkms/backport-iwlwifi/8324/5.4.0-77-generic/aarch64/dkms.conf for
module backport-iwlwifi includes a BUILD_EXCLUSIVE directive which
does not match this kernel/arch. This indicates that it should not be built.
Skipped.
Processing
Public bug reported:
[Impact]
* u-boot-sifive package currently does not upgrade bootloader on
loader1/loader2 partitions.
* there have now been bugs identified, meaning that upgrading u-boot is
required to upgrade from v5.8 kernel to v5.11 (i.e. either in-focal, or from
focal to hirsute).
201 - 300 of 9094 matches
Mail list logo
