** Changed in: systemd (Ubuntu)
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/1957086
Title:
Autopkgtest systemd fail against dnsmasq 2.86 (22.04)
To ma
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
This issue was fixed in the openstack/ovsdbapp 1.6.1 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895727
Title:
OpenSSL.SSL.SysCallError: (111, 'ECONNREFUSED') and Connection thread
st
Debian released a new upstream version this week-end and applied the
same fix.
freezegun (1.1.0-1) unstable; urgency=medium
* New upstream release
-- Federico Ceratto Sat, 29 Jan 2022 13:07:17
+
$ head -n 15 patches/001-fix-staticmethod.patch
Author: Karthikeyan Singaravelan
Descripti
Thanks Dan
I've rolled back to kernal 5.11.0-46-generic and shut-down/restart is
re-established normally.
I've updated the grub to save this as default for the time being.
I'm new to the way Linux distros release their updates/bug fixes. My
system is fixed (stable) for now, but how will I know i
dnsmasq | 2.86-1.1 | jammy| source
dnsmasq | 2.86-1.1 | jammy/universe | all
** Changed in: dnsmasq (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
New merge is available. I tend to use the same bug to keep a track for
simplicity. I'll take care of this.
** Changed in: exim4 (Ubuntu)
Assignee: Lena Voytek (lvoytek) => Utkarsh Gupta (utkarsh)
** Changed in: exim4 (Ubuntu)
Milestone: ubuntu-22.01 => ubuntu-22.02
** Changed in: exim4
This bug was fixed in the package at - 3.2.4-1
Sponsored for Utkarsh Gupta (utkarsh)
---
at (3.2.4-1) experimental; urgency=medium
* New release 3.2.3
* Jose M Calhariz
- Fix two typos on documentation
* Giulio Benetti
MR14 - Makefile: fix parallel build failure
** Changed in: breeze (Ubuntu)
Status: New => Fix Committed
** Changed in: drkonqi (Ubuntu)
Status: New => Fix Committed
** Changed in: kactivitymanagerd (Ubuntu)
Status: New => Fix Committed
** Changed in: kde-gtk-config (Ubuntu)
Status: New => Fix Committed
** Chan
This has been fixed via 3.1.2-2 upload and the package has migrated
already. Closing now. \o/
** Changed in: node-pbkdf2 (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.launchpa
This bug was fixed in the package binutils - 2.37.90.20220130-0ubuntu2
---
binutils (2.37.90.20220130-0ubuntu2) jammy; urgency=medium
* Also ignore regressions for the cross packages.
-- Matthias Klose Sun, 30 Jan 2022 16:59:06 +0100
** Changed in: binutils (Ubuntu Jammy)
KDE (and other) things now seem to be building ok with the latest
2.37.90.20220130-0ubuntu2
Thank you doko (Matthias)
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1959325
Title:
New binut
Hi Przemysław Lal,
What you mean by "affected" network? Do you mean there are multiple
networks in your setup, and out of those only one such network is
misbehaving in terms of routes?
If above is true, is the "affected" network misbehaving since when it's
created, or it used to work earlier and
This bug was fixed in the package binutils - 2.37.90.20220130-0ubuntu2
---
binutils (2.37.90.20220130-0ubuntu2) jammy; urgency=medium
* Also ignore regressions for the cross packages.
-- Matthias Klose Sun, 30 Jan 2022 16:59:06 +0100
** Changed in: binutils (Ubuntu Jammy)
** Package changed: ubuntu => focal (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959550
Title:
If ubuntu returned from screen offed to on, ubuntu cannot show desktop
screen
To manage n
Hello Thomas,
here`s how I did it, step by step.
1) install acpica-tools
apt-get install acpica-tools
2) Grab the DSDT of your device
cat /sys/firmware/acpi/tables/DSDT > dsdt.dat
3) Decompile the dsdt.dat
iasl -d dsdt.dsl
4) Open the dsdt.dsl with whatever editor tickles your fancy
e.g. xed d
Just spun-up a couple of Gnome Boxes to test this. 21.10 fails as per my
description whereas 20.04.03 LTS works fine. Just to be clear I am
selecting to revert the snapshot at the top of the list each time (this
is the snapshot taken just before neofetch is installed).
Meanwhile my main laptop whe
** Changed in: breeze (Ubuntu)
Status: Fix Committed => In Progress
** Changed in: drkonqi (Ubuntu)
Status: Fix Committed => In Progress
** Changed in: kactivitymanagerd (Ubuntu)
Status: Fix Committed => In Progress
** Changed in: kde-gtk-config (Ubuntu)
Status: Fix C
Quick edit for a typo:
in number 8) it should of course be :
OperationRegion and not perationRegion ...
And the recompile will throw warnings not errors ...
Sorry about that I am in a bit of a hurry ^^*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Possible duplicate on Impish:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1959522
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
To
multipath-tools | 0.8.5-2ubuntu3 | jammy | source,
amd64, arm64, armhf, ppc64el, riscv64, s390x
multipath-tools | 0.8.8-1 | testing| source, amd64, arm64,
armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
We should try to get these upstream minor v
** Description changed:
This is ubuntu bug.
If ubuntu returned from screen offed to on, ubuntu cannot show desktop screen.
OS : Ubuntu 20.04.3
CPU : AMD Ryzen 7 4800H with Radeon Graphics
VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir (rev
c6)
+
+ SYSTEM LO
Hello Thomas and thanks for your bug report. I have no problems adding
ed25519 keys to ssh-agent on a Jammy system. Could you please try the
following steps, which may help identifying where the problem is?
Thanks!
$ mkdir /tmp/ed25519test
$ cd /tmp/ed25519test
$ echo $SSH_AUTH_SOCK
/run/user/100
I can reproduce this:
$ shopt -s failglob
$ ssh bash: no match: /etc/ssh/ssh_config.d/*.conf
but I believe the bugs belongs to the bash-completion package.
** Changed in: openssh (Ubuntu)
Importance: Undecided => Low
** Changed in: openssh (Ubuntu)
Status: New => Confirmed
** Package
*** This bug is a duplicate of bug 1948685 ***
https://bugs.launchpad.net/bugs/1948685
** This bug has been marked a duplicate of bug 1948685
AX210 iwlwifi doesn't work on 5.13 kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954854
Title:
bind 9.16.1-ubuntu on ubuntu 20.04 randomly exits with segfault signal
To manage notifications abou
** Tags added: fr-2005
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959397
Title:
Autopkgtest failure with Python 3.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu
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
Public bug reported:
When using the netplan-dbus API on Ubuntu Core and the network-manager
renderer the "netplan-dbus" appication will crash. To reproduce take a
UC20 or UC22 system and run:
```
$ sudo snap set system system.network.netplan.network.bridges.br54.dhcp4=true
```
(which in effect ju
Hello Timo!
I have just enabled the focal-proposed repo (which required me to also
update libc and other libraries despite the guide saying that no other
packages should be shown as updatable after the preferences.d entry is
added) and updated to 1.187.26.
The issue seems to be fixed for me.
--
Many thanks to sil2100 -- the rename has been uploaded to jammy-
proposed.
** Also affects: linux-firmware-raspi (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-firmware-raspi2 (Ubuntu)
Status: New => Fix Committed
** Changed in: linux-firmware-raspi (Ubuntu)
The updated firmware is now in jammy-proposed under the renamed linux-
firmware-raspi package. SRUs will for impish and focal will be under the
original linux-firmware-raspi2 name.
** Also affects: linux-firmware-raspi (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: lin
** Changed in: libphonenumber (Debian)
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/1958308
Title:
New upstream release - please update
To manage notifications a
After a discussion with a member of the Debian Haskell team, the
simplest solution is to backport the OpenSSL 3.0 patch from upstream.
** Changed in: haskell-hsopenssl (Ubuntu)
Status: New => Fix Committed
** Changed in: glirc (Ubuntu)
Status: New => Invalid
--
You received this b
Public bug reported:
The package fails to build against OpenSSL 3.0, due to lack of support
in the Haskell package haskell-hlopenssl.
** Affects: glirc (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: haskell-hsopenssl (Ubuntu)
Importance: Undecided
Status:
Public bug reported:
My script /usr/share/libpam-script/pam_script_ses_open has no access to
any of the PAM_* variables. The man page still states that it should
have.
/usr/share/libpam-script/pam_script_ses_close has access to all PAM_*
variables.
** Affects: libpam-script (Ubuntu)
Importa
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xl2tpd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951832
Title:
xl2
It feels like we should just copy libgcc_s.so.1 and libpthread always.
It is tiny in size and something is bound to use them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958594
Title:
Boot error:
I can also confirm that it is good not for libvirt again - Thanks for
the quick fix!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959325
Title:
New binutils causes build failures for many RISC-V p
FYI: Keeping things up is even harder, while restarting sockets in the past
complained about services already being up they now restart the service.
So if anyone is looking at this for some package, be careful that you'd also
need to handle .socket files special now as they are affected by this i
Same "Cannot find tunnel" in syslog.
Had a working VPN connection in 21.10 with IPSEC/L2TP (PSK + username password)
setup from Settings using GUI.
Did an upgrade to 22.04 and it stopped working.
Will attach an extract from my syslog.
--
You received this bug notification because you are a membe
** Attachment added: "syslog-vpn-l2tp-fails.txt"
https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+attachment/5558409/+files/syslog-vpn-l2tp-fails.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
I'd like to know if there already is an Ubuntu position on this, will we revert
[1] to avoid a yet unknown amount of breakage in Jammy?
I'd like to know to adapt my packages accordingly ...
[1]: https://salsa.debian.org/debian/debhelper/-/commit/6067bc2
--
You received this bug notification bec
Hi!
> When connecting to MUME with Force CHARSET negotiation enabled (box
NOT checked under Special settings)
There is no 'force charset negotiation on' option, just an option to
turn it off which is why I think you're confused.
The way it works is: you can either allow the server to set the
enc
Public bug reported:
A new version in Debian is available and rebasing the delta onto that
should be super easy.
** Affects: pandoc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
so, this was not verified in time, and we're missing the regression fix
as well.. I'm thinking of dropping this
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955790
Title:
Got black screen when res
it's just a device id, marking verified
** 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/1956407
Title:
Add missing B
This bug was fixed in the package linux - 4.15.0-167.175
---
linux (4.15.0-167.175) bionic; urgency=medium
* bionic/linux: 4.15.0-167.175 -proposed tracker (LP: #1955276)
* hisi_sas driver may oops in prep_ssp_v3_hw() (LP: #1953386)
- scsi: hisi_sas: Fix to only call scsi_get
This bug was fixed in the package linux - 4.15.0-167.175
---
linux (4.15.0-167.175) bionic; urgency=medium
* bionic/linux: 4.15.0-167.175 -proposed tracker (LP: #1955276)
* hisi_sas driver may oops in prep_ssp_v3_hw() (LP: #1953386)
- scsi: hisi_sas: Fix to only call scsi_get
This bug was fixed in the package linux - 4.15.0-167.175
---
linux (4.15.0-167.175) bionic; urgency=medium
* bionic/linux: 4.15.0-167.175 -proposed tracker (LP: #1955276)
* hisi_sas driver may oops in prep_ssp_v3_hw() (LP: #1953386)
- scsi: hisi_sas: Fix to only call scsi_get
This bug was fixed in the package linux-azure-4.15 - 4.15.0-1130.143
---
linux-azure-4.15 (4.15.0-1130.143) bionic; urgency=medium
* bionic/linux-azure-4.15: 4.15.0-1130.143 -proposed tracker (LP:
#1955257)
* linux-azure 4.15 fails to boot on Standard_M416s_v2 in Azure (LP: #1951
This bug was fixed in the package linux-aws - 4.15.0-1119.127
---
linux-aws (4.15.0-1119.127) bionic; urgency=medium
* bionic/linux-aws: 4.15.0-1119.127 -proposed tracker (LP: #1955252)
* linux-aws: Make a signed kernel (LP: #1951011)
- [Packaging] aws: Enable signed kernel
This bug was fixed in the package linux - 5.4.0-97.110
---
linux (5.4.0-97.110) focal; urgency=medium
* icmp_redirect from selftests fails on F/kvm (unary operator expected)
(LP: #1938964)
- selftests: icmp_redirect: pass xfail=0 to log_test()
* Focal: CIFS stable updates
This bug was fixed in the package linux-azure - 5.4.0-1068.71
---
linux-azure (5.4.0-1068.71) focal; urgency=medium
* focal/linux-azure: 5.4.0-1068.71 -proposed tracker (LP: #1955219)
[ Ubuntu: 5.4.0-97.110 ]
* icmp_redirect from selftests fails on F/kvm (unary operator expect
This bug was fixed in the package linux - 5.4.0-97.110
---
linux (5.4.0-97.110) focal; urgency=medium
* icmp_redirect from selftests fails on F/kvm (unary operator expected)
(LP: #1938964)
- selftests: icmp_redirect: pass xfail=0 to log_test()
* Focal: CIFS stable updates
This bug was fixed in the package linux - 5.4.0-97.110
---
linux (5.4.0-97.110) focal; urgency=medium
* icmp_redirect from selftests fails on F/kvm (unary operator expected)
(LP: #1938964)
- selftests: icmp_redirect: pass xfail=0 to log_test()
* Focal: CIFS stable updates
This bug was fixed in the package linux - 5.4.0-97.110
---
linux (5.4.0-97.110) focal; urgency=medium
* icmp_redirect from selftests fails on F/kvm (unary operator expected)
(LP: #1938964)
- selftests: icmp_redirect: pass xfail=0 to log_test()
* Focal: CIFS stable updates
This bug was fixed in the package linux - 5.4.0-97.110
---
linux (5.4.0-97.110) focal; urgency=medium
* icmp_redirect from selftests fails on F/kvm (unary operator expected)
(LP: #1938964)
- selftests: icmp_redirect: pass xfail=0 to log_test()
* Focal: CIFS stable updates
This bug was fixed in the package linux - 5.4.0-97.110
---
linux (5.4.0-97.110) focal; urgency=medium
* icmp_redirect from selftests fails on F/kvm (unary operator expected)
(LP: #1938964)
- selftests: icmp_redirect: pass xfail=0 to log_test()
* Focal: CIFS stable updates
This bug was fixed in the package linux - 5.4.0-97.110
---
linux (5.4.0-97.110) focal; urgency=medium
* icmp_redirect from selftests fails on F/kvm (unary operator expected)
(LP: #1938964)
- selftests: icmp_redirect: pass xfail=0 to log_test()
* Focal: CIFS stable updates
This bug was fixed in the package linux-aws-5.13 -
5.13.0-1012.13~20.04.1
---
linux-aws-5.13 (5.13.0-1012.13~20.04.1) focal; urgency=medium
* focal/linux-aws-5.13: 5.13.0-1012.13~20.04.1 -proposed tracker
(LP: #1955186)
* linux-aws: Make a signed kernel (LP: #1951011)
- [
This bug was fixed in the package linux-raspi2 - 4.15.0-1102.109
---
linux-raspi2 (4.15.0-1102.109) bionic; urgency=medium
* bionic/linux-raspi2: 4.15.0-1102.109 -proposed tracker (LP:
#1955272)
* Boot time from snap in 20/stable increases boot time on 3.5 seconds
(LP: #19488
This bug was fixed in the package linux-azure-5.11 -
5.11.0-1028.31~20.04.2
---
linux-azure-5.11 (5.11.0-1028.31~20.04.2) focal; urgency=medium
* focal/linux-azure-5.11: 5.11.0-1028.31~20.04.2 -proposed tracker (LP:
#1955200)
* Re-enable DEBUG_INFO_BTF where it was disabled (
This bug was fixed in the package linux - 5.4.0-97.110
---
linux (5.4.0-97.110) focal; urgency=medium
* icmp_redirect from selftests fails on F/kvm (unary operator expected)
(LP: #1938964)
- selftests: icmp_redirect: pass xfail=0 to log_test()
* Focal: CIFS stable updates
This bug was fixed in the package linux-gcp-5.11 -
5.11.0-1029.33~20.04.3
---
linux-gcp-5.11 (5.11.0-1029.33~20.04.3) focal; urgency=medium
* focal/linux-gcp-5.11: 5.11.0-1029.33~20.04.3 -proposed tracker (LP:
#1955202)
* Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1
This bug was fixed in the package linux - 5.4.0-97.110
---
linux (5.4.0-97.110) focal; urgency=medium
* icmp_redirect from selftests fails on F/kvm (unary operator expected)
(LP: #1938964)
- selftests: icmp_redirect: pass xfail=0 to log_test()
* Focal: CIFS stable updates
This bug was fixed in the package linux - 5.4.0-97.110
---
linux (5.4.0-97.110) focal; urgency=medium
* icmp_redirect from selftests fails on F/kvm (unary operator expected)
(LP: #1938964)
- selftests: icmp_redirect: pass xfail=0 to log_test()
* Focal: CIFS stable updates
This bug was fixed in the package linux - 5.4.0-97.110
---
linux (5.4.0-97.110) focal; urgency=medium
* icmp_redirect from selftests fails on F/kvm (unary operator expected)
(LP: #1938964)
- selftests: icmp_redirect: pass xfail=0 to log_test()
* Focal: CIFS stable updates
This bug was fixed in the package linux-gke - 5.4.0-1061.64
---
linux-gke (5.4.0-1061.64) focal; urgency=medium
* focal/linux-gke: 5.4.0-1061.64 -proposed tracker (LP: #1959355)
* Vulnerability in af_packet handling (LP: #1959173)
- net/packet: rx_owner_map depends on pg_vec
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
* imp
This bug was fixed in the package linux-oracle - 5.13.0-1016.20
---
linux-oracle (5.13.0-1016.20) impish; urgency=medium
* impish/linux-oracle: 5.13.0-1016.20 -proposed tracker (LP: #1955193)
* Impish update: upstream stable patchset 2021-12-09 (LP: #1954337)
- [Config] oracl
This bug was fixed in the package linux-raspi - 5.13.0-1016.18
---
linux-raspi (5.13.0-1016.18) impish; urgency=medium
* impish/linux-raspi: 5.13.0-1016.18 -proposed tracker (LP: #1955194)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
* imp
This bug was fixed in the package linux-intel-5.13 - 5.13.0-1009.9
---
linux-intel-5.13 (5.13.0-1009.9) focal; urgency=medium
* focal/linux-intel-5.13: 5.13.0-1009.9 -proposed tracker (LP:
#1956411)
* rtw89 kernel module for Realtek 8852 wifi is missing (LP: #1945967)
- [Conf
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
* imp
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
* imp
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
* imp
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
* imp
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
* imp
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
* imp
This bug was fixed in the package linux-raspi - 5.13.0-1016.18
---
linux-raspi (5.13.0-1016.18) impish; urgency=medium
* impish/linux-raspi: 5.13.0-1016.18 -proposed tracker (LP: #1955194)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
* imp
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
* imp
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
* imp
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
* imp
This bug was fixed in the package linux - 5.4.0-97.110
---
linux (5.4.0-97.110) focal; urgency=medium
* icmp_redirect from selftests fails on F/kvm (unary operator expected)
(LP: #1938964)
- selftests: icmp_redirect: pass xfail=0 to log_test()
* Focal: CIFS stable updates
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
* imp
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
* imp
This bug was fixed in the package linux-aws - 5.4.0-1064.67
---
linux-aws (5.4.0-1064.67) focal; urgency=medium
* focal/linux-aws: 5.4.0-1064.67 -proposed tracker (LP: #1955214)
* Enable arm64 nitro enclaves (LP: #1951873)
- nitro_enclaves: Fixup type and simplify logic of th
This bug was fixed in the package linux-aws - 5.13.0-1012.13
---
linux-aws (5.13.0-1012.13) impish; urgency=medium
* impish/linux-aws: 5.13.0-1012.13 -proposed tracker (LP: #1955187)
* [SRU][Ubuntu 21.10][Broadcom] mpi3mr driver submission request
(LP: #1933359)
- [Config
This bug was fixed in the package linux - 5.4.0-97.110
---
linux (5.4.0-97.110) focal; urgency=medium
* icmp_redirect from selftests fails on F/kvm (unary operator expected)
(LP: #1938964)
- selftests: icmp_redirect: pass xfail=0 to log_test()
* Focal: CIFS stable updates
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
* imp
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
* imp
This bug was fixed in the package linux-raspi - 5.13.0-1016.18
---
linux-raspi (5.13.0-1016.18) impish; urgency=medium
* impish/linux-raspi: 5.13.0-1016.18 -proposed tracker (LP: #1955194)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
* imp
This bug was fixed in the package linux - 5.4.0-97.110
---
linux (5.4.0-97.110) focal; urgency=medium
* icmp_redirect from selftests fails on F/kvm (unary operator expected)
(LP: #1938964)
- selftests: icmp_redirect: pass xfail=0 to log_test()
* Focal: CIFS stable updates
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
* imp
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
* imp
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
* imp
This bug was fixed in the package linux - 5.13.0-28.31
---
linux (5.13.0-28.31) impish; urgency=medium
* amd_sfh: Null pointer dereference on early device init causes early panic
and fails to boot (LP: #1956519)
- HID: amd_sfh: Fix potential NULL pointer dereference
* imp
1 - 100 of 343 matches
Mail list logo
