This bug was fixed in the package linux - 5.8.0-63.71
---
linux (5.8.0-63.71) groovy; urgency=medium
* Possible io_uring regression with QEMU on Ubuntu's kernel (LP: #1935017)
- SAUCE: Revert "block: don't ignore REQ_NOWAIT for direct IO"
linux (5.8.0-62.70) groovy; urgency=med
This bug was fixed in the package linux - 5.11.0-25.27
---
linux (5.11.0-25.27) hirsute; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (5.11.0-24.25) hirsute; urgency=medium
* test_pmtu_vti4_link_add_mtu() test from
This bug was fixed in the package linux - 5.8.0-63.71
---
linux (5.8.0-63.71) groovy; urgency=medium
* Possible io_uring regression with QEMU on Ubuntu's kernel (LP: #1935017)
- SAUCE: Revert "block: don't ignore REQ_NOWAIT for direct IO"
linux (5.8.0-62.70) groovy; urgency=med
This bug was fixed in the package linux - 5.4.0-80.90
---
linux (5.4.0-80.90) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (5.4.0-79.88) focal; urgency=medium
* focal/linux: 5.4.0-79.88 -proposed tracker (LP:
This bug was fixed in the package linux - 5.4.0-80.90
---
linux (5.4.0-80.90) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (5.4.0-79.88) focal; urgency=medium
* focal/linux: 5.4.0-79.88 -proposed tracker (LP:
Public bug reported:
since upgrading to firefox 90, all newly opened firefox windows are very
small and need to be manually resized to a usable size.
prior to firefox 90, new windows would be the same size as the last
opened window.
running on gnome on wayland with fractional scaling enabled, if
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1009.10
---
linux-oem-5.13 (5.13.0-1009.10) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.13 (5.13.0-1007.7) focal; urgency=medium
* focal/linux-
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1009.10
---
linux-oem-5.13 (5.13.0-1009.10) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.13 (5.13.0-1007.7) focal; urgency=medium
* focal/linux-
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux - 4.15.0-151.157
---
linux (4.15.0-151.157) bionic; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (4.15.0-150.155) bionic; urgency=medium
* bionic/linux: 4.15.0-150.155 -propos
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux - 4.15.0-151.157
---
linux (4.15.0-151.157) bionic; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (4.15.0-150.155) bionic; urgency=medium
* bionic/linux: 4.15.0-150.155 -propos
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux - 4.15.0-151.157
---
linux (4.15.0-151.157) bionic; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (4.15.0-150.155) bionic; urgency=medium
* bionic/linux: 4.15.0-150.155 -propos
This bug was fixed in the package linux - 4.15.0-151.157
---
linux (4.15.0-151.157) bionic; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (4.15.0-150.155) bionic; urgency=medium
* bionic/linux: 4.15.0-150.155 -propos
This bug was fixed in the package linux - 4.15.0-151.157
---
linux (4.15.0-151.157) bionic; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (4.15.0-150.155) bionic; urgency=medium
* bionic/linux: 4.15.0-150.155 -propos
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1009.10
---
linux-oem-5.13 (5.13.0-1009.10) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.13 (5.13.0-1007.7) focal; urgency=medium
* focal/linux-
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1009.10
---
linux-oem-5.13 (5.13.0-1009.10) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.13 (5.13.0-1007.7) focal; urgency=medium
* focal/linux-
This bug was fixed in the package linux - 4.15.0-151.157
---
linux (4.15.0-151.157) bionic; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (4.15.0-150.155) bionic; urgency=medium
* bionic/linux: 4.15.0-150.155 -propos
Public bug reported:
Newer HP laptops use Intel HID driver to send rfkill hotkey event, so we'll
need to unmask Intel HID in hwdb to make airplane mode hotkey work:
https://github.com/systemd/systemd/pull/20219
However, this will make both Intel HID driver and HP Wireless driver send
rfkill eve
This bug was fixed in the package grub2-unsigned - 2.04-1ubuntu46
---
grub2-unsigned (2.04-1ubuntu46) impish; urgency=medium
* debian/grub-common.service: change type to oneshot, add wantedby
sleep.target, after sleep.target. The service will now start after
resume from hybe
Public bug reported:
Jul 20 14:40:23 anonster kernel: [ 1716.692818] mlx5_core :03:00.0:
assert_var[0] 0x
Jul 20 14:40:23 anonster kernel: [ 1716.698541] mlx5_core :03:00.0:
assert_var[1] 0x
Jul 20 14:40:23 anonster kernel: [ 1716.704240] mlx5_core :03:00.0:
assert_v
FYI, that patch is intended specifically for s2idle, which will not work
on those older kernels without significant other backports. Are you
sure that this patch alone really helps the issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
This bug was fixed in the package systemd - 245.4-4ubuntu3.10
---
systemd (245.4-4ubuntu3.10) focal-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd
This bug was fixed in the package systemd - 245.4-4ubuntu3.10
---
systemd (245.4-4ubuntu3.10) focal-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd
This bug was fixed in the package systemd - 247.3-3ubuntu3.4
---
systemd (247.3-3ubuntu3.4) hirsute-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd
This bug was fixed in the package systemd - 245.4-4ubuntu3.10
---
systemd (245.4-4ubuntu3.10) focal-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd
This bug was fixed in the package systemd - 247.3-3ubuntu3.4
---
systemd (247.3-3ubuntu3.4) hirsute-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd
This bug was fixed in the package systemd - 245.4-4ubuntu3.10
---
systemd (245.4-4ubuntu3.10) focal-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd
This bug was fixed in the package systemd - 247.3-3ubuntu3.4
---
systemd (247.3-3ubuntu3.4) hirsute-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd
This bug was fixed in the package systemd - 245.4-4ubuntu3.10
---
systemd (245.4-4ubuntu3.10) focal-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd
This bug was fixed in the package systemd - 247.3-3ubuntu3.4
---
systemd (247.3-3ubuntu3.4) hirsute-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd
This bug was fixed in the package systemd - 245.4-4ubuntu3.10
---
systemd (245.4-4ubuntu3.10) focal-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd
This bug was fixed in the package systemd - 247.3-3ubuntu3.4
---
systemd (247.3-3ubuntu3.4) hirsute-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd
This bug was fixed in the package systemd - 245.4-4ubuntu3.10
---
systemd (245.4-4ubuntu3.10) focal-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd
This bug was fixed in the package systemd - 247.3-3ubuntu3.4
---
systemd (247.3-3ubuntu3.4) hirsute-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd
This bug was fixed in the package systemd - 245.4-4ubuntu3.10
---
systemd (245.4-4ubuntu3.10) focal-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd
This bug was fixed in the package systemd - 247.3-3ubuntu3.4
---
systemd (247.3-3ubuntu3.4) hirsute-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd
This bug was fixed in the package systemd - 245.4-4ubuntu3.10
---
systemd (245.4-4ubuntu3.10) focal-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd
Public bug reported:
package shim-signed 1.48+15.4-0ubuntu5 failed to install/upgrade: installed
shim-signed package post-installation script subprocess returned error exit
status 1
ProblemType: Package
DistroRelease: Ubuntu 21.04
Package: shim-signed 1.48+15.4-0ubuntu5
ProcVersionSignature: U
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
Public bug reported:
Hi,
on Ubuntu focal 20.04, "conntrack -L" fails to restrict output to
a specific layer three protocol family (-f).
Output of
- conntrack -L
- conntrack -L -f ipv4
- conntrack -L -f ipv6
is always the same, containing output of both ipv4 and ipv6 families.
Using th
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936961
Title:
package shim-signed 1.48+15.4-0ubuntu5 failed to install/upgrade:
installed shim-signed package p
** Changed in: kunpeng920/ubuntu-20.04-hwe
Status: Fix Committed => Fix Released
** Changed in: kunpeng920
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/
I'm also getting the same problem. Across 3x Windows 2016 machines
running Hyper-V. Had this issue with Ubuntu 18.04 and now 20.04 but only
when they are connected to a VLAN. My vlan assignments are
10,40,100,110,120,200 - I'm going to test next with an odd numbered vlan
as that seems to be a patte
Public bug reported:
libsass FTBFS on amd64, arm64, ppc64el and s390x with LTO enabled due to
1000+ of the 5600+ symbols being dropped.
Excerpt from the build log:
dh_makeshlibs -a
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see
diff output below
dpkg-gensymbols:
= bionic verification =
I verified that shim*-signed* version 1.37~18.04.10+15.4-0ubuntu7 reboots fine.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubun
Public bug reported:
Steps to reproduce:
1. Have Ubuntu 18.04 LTS installed with Unity of MATE desktops
2. Add LO PPA, install full LO by
sudo add-apt-repository ppa:libreoffice/ppa
sudo apt-get update
sudo apt-get install libreoffice
3a. Launch Libreoffice Impress, wait the Select a Te
My update in the bug description was somehow rolled back (by me in the
record), trying again.
** Description changed:
[Impact]
- [Test Case]
- I have a test Ceph cluster as an object storage with both Swift and S3
protocols enabled for Glance (Ussuri). When I use Swift backend with Glance, an
Still same problem
corrado@corrado-n4-ii-0718:~$ inxi -Fx
System:Host: corrado-n4-ii-0718 Kernel: 5.11.0-20-generic x86_64 bits: 64
compiler: gcc v: 10.2.1 Desktop: GNOME 40.2
Distro: Ubuntu 21.10 (Impish Indri)
Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A se
> 1) Can you please briefly explain what the problem was?
Patch with explanation:
https://lore.kernel.org/lkml/20210720172216.59613-1-kai.heng.f...@canonical.com/
> 2) Will your patch be backported to the 5.4 and 5.8 lines?
It should be automatically picked to any stable kernel.
5.8 is EOL soon BT
Public bug reported:
I did a fresh Ubuntu 21.04 installation from a USB drive on a machine
which already had Windows 10. I selected default settings for dual-boot,
did not connect to Wifi since I didn't have time to wait for downloads,
and checked 3rd party software. Everything went fine until it
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934783
Title:
Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 56
The verification passed for focal. The daily images are building with
u-boot-menu-4.0.2ubuntu5~20.04.1. I have successfully booted these daily
images in qemu and Unmatched hardware.
Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-29-generic riscv64)
* Documentation: https://help.ubuntu.com
* Ma
** Attachment added: "Wrong icons on WIndow List for LibreOffice Templates
windows - Unity"
https://bugs.launchpad.net/df-libreoffice/+bug/1936966/+attachment/5512269/+files/lo71-icons-unity.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
The same happens for Recover documents window. So, please make all these
secondary icons consistent or please give a recommendation which package
should be additionally installed to get all icons in place.
First seen on https://askubuntu.com/q/1352937/66509 .
** Description changed:
Steps to r
Public bug reported:
I can't seem to login to share my gists as Github now requires gist-
paste v6.0
➜ ~ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename: focal
➜ ~ gist-paste -v
gist v5.0.0
➜ ~ gist-p
The verification passed for focal. The daily images are building with
u-boot-menu-4.0.2ubuntu5~20.04.1 and u-boot-
sifive-2021.01+dfsg-3ubuntu0~20.04.1. I have successfully booted these
daily images in qemu and on Unmatched hardware.
Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-29-generic riscv6
Having re-tested this with one particular VM that was failing, it
appears to be happy on any VLAN but 10 (which has most of my clients on
at the moment, including the Hyper-V server itself).
To add some more detail in case it's relevant, each server I have 2x LAN
Teams, one for the Windows 2016 us
This bug was fixed in the package heimdal - 7.7.0+dfsg-2ubuntu1
---
heimdal (7.7.0+dfsg-2ubuntu1) impish; urgency=medium
* Disable lto, to regain dep on roken, otherwise dependencies on amd64
are different to i386 resulting in different files on amd64 and
i386. LP: #1934936
This bug was fixed in the package grub2 - 2.04-1ubuntu46
---
grub2 (2.04-1ubuntu46) impish; urgency=medium
* debian/grub-common.service: change type to oneshot, add wantedby
sleep.target, after sleep.target. The service will now start after
resume from hybernation. LP: #1929
This bug was fixed in the package grub2 - 2.04-1ubuntu46
---
grub2 (2.04-1ubuntu46) impish; urgency=medium
* debian/grub-common.service: change type to oneshot, add wantedby
sleep.target, after sleep.target. The service will now start after
resume from hybernation. LP: #1929
This bug was fixed in the package grub2 - 2.04-1ubuntu46
---
grub2 (2.04-1ubuntu46) impish; urgency=medium
* debian/grub-common.service: change type to oneshot, add wantedby
sleep.target, after sleep.target. The service will now start after
resume from hybernation. LP: #1929
This bug was fixed in the package grub2 - 2.04-1ubuntu46
---
grub2 (2.04-1ubuntu46) impish; urgency=medium
* debian/grub-common.service: change type to oneshot, add wantedby
sleep.target, after sleep.target. The service will now start after
resume from hybernation. LP: #1929
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
Ah, thanks for the clarification.
** Changed in: libguestfs (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935815
Title:
virt-sysprep: /var/lib/libvirt/images
Public bug reported:
[Summary]
Please promote bin:libnet-snmp-perl to main. It's the only binary
package built by src:libnet-snmp-perl. The package is a "new" dependency
of bin:amavisd-new which is in main. I say "new" in quotes because is
was already a dependency, but d/control missed it up to v
** Tags added: focal snap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935775
Title:
URL links functional about 5% of the time
To manage notifications about this bug go to:
https://bugs.launchpad
Reference to commit where this was fixed:
https://opendev.org/openstack/python-
magnumclient/commit/5deb538930d98bf83e11bfb1dacb509982226540
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814890
Title
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.144-0ubuntu0.21.04.1
---
nvidia-graphics-drivers-390 (390.144-0ubuntu0.21.04.1) hirsute; urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_5.1
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.144-0ubuntu0.20.10.1
---
nvidia-graphics-drivers-390 (390.144-0ubuntu0.20.10.1) groovy; urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_5.13
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.144-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-390 (390.144-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_5.13.
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.144-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-390 (390.144-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_5.13
This bug was fixed in the package nvidia-graphics-drivers-418-server -
418.211.00-0ubuntu0.20.10.1
---
nvidia-graphics-drivers-418-server (418.211.00-0ubuntu0.20.10.1) groovy;
urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop
This bug was fixed in the package nvidia-graphics-drivers-418-server -
418.211.00-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-418-server (418.211.00-0ubuntu0.20.04.1) focal;
urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop
This bug was fixed in the package nvidia-graphics-drivers-418-server -
418.211.00-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-418-server (418.211.00-0ubuntu0.18.04.1) bionic;
urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop
This bug was fixed in the package nvidia-graphics-drivers-418-server -
418.211.00-0ubunt0.21.04.1
---
nvidia-graphics-drivers-418-server (418.211.00-0ubunt0.21.04.1) hirsute;
urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.142.00-0ubuntu0.21.04.1
---
nvidia-graphics-drivers-450-server (450.142.00-0ubuntu0.21.04.1) hirsute;
urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Dro
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.142.00-0ubuntu0.20.10.1
---
nvidia-graphics-drivers-450-server (450.142.00-0ubuntu0.20.10.1) groovy;
urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.142.00-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-450-server (450.142.00-0ubuntu0.20.04.1) focal;
urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.142.00-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-450-server (450.142.00-0ubuntu0.18.04.1) bionic;
urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop
This bug was fixed in the package nvidia-graphics-drivers-460 -
460.91.03-0ubuntu0.21.04.1
---
nvidia-graphics-drivers-460 (460.91.03-0ubuntu0.21.04.1) hirsute; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
12:46:59 +0200
** Changed in
This bug was fixed in the package nvidia-graphics-drivers-460 -
460.91.03-0ubuntu0.20.10.1
---
nvidia-graphics-drivers-460 (460.91.03-0ubuntu0.20.10.1) groovy; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
12:48:27 +0200
** Changed in:
This bug was fixed in the package nvidia-graphics-drivers-460 -
460.91.03-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-460 (460.91.03-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
12:53:30 +0200
** Changed in:
This bug was fixed in the package nvidia-graphics-drivers-460 -
460.91.03-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-460 (460.91.03-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
13:00:00 +0200
** Changed in:
This bug was fixed in the package nvidia-graphics-drivers-460-server -
460.91.03-0ubuntu0.20.10.1
---
nvidia-graphics-drivers-460-server (460.91.03-0ubuntu0.20.10.1) groovy;
urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop b
This bug was fixed in the package nvidia-graphics-drivers-460-server -
460.91.03-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-460-server (460.91.03-0ubuntu0.18.04.1) bionic;
urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop b
I can confirm that this bug is fixed in the proposed 27.2.1 package on
Xenial, Bionic, Focal and Hirsute by using the following script:
--
#!/bin/sh
set -x
series=xenial
name=$series-check
lxc delete --force $name
lxc launch ubuntu-daily:$series $name
lxc exec $name -- sudo
This is still impacting corosync version 2.4.3-0ubuntu1.2 present in
Bionic. As described by Rafael this is affecting only non-systemd users
which seem to be the minority of our users, so I am setting the
importance to Low in Bionic.
** Changed in: corosync (Ubuntu Bionic)
Importance: Undecided
201 - 300 of 604 matches
Mail list logo