Public bug reported:
Three external monitors connected via DisplayPort MST through a USB-C
docking station (Anker, ID 291a:8392) fail to work correctly on kernel
6.17.0-14-generic. Only the internal display and one external monitor
are usable. The other two displays repeatedly turn off and on in a loop,
as if the system is continuously attempting and failing to negotiate the
DP MST link.
The same hardware configuration works correctly on kernel
6.14.0-37-generic with no issues.
Symptoms on 6.17.0-14:
Of three external DP MST outputs (DP-1-1-1, DP-1-1-2, DP-1-1-3), only
one or two activate; the third is connected but has no active mode
Connected monitors show severely degraded EDID — e.g. a 3440x1440
display only reports 640x480, 800x600, and 1024x768 as standard modes
All displays (including working ones) cycle off and on repeatedly
NVIDIA log shows all DFP ports cycling between connected and
disconnected
Two USB Billboard devices appear (VIA Labs, ID 2109:8817), suggesting
USB-C DisplayPort Alt Mode is not fully negotiating
Hardware:
Laptop: Lenovo Legion Pro 7 16IAX10H
GPU: NVIDIA GeForce RTX 5070 Ti Laptop GPU
NVIDIA driver: 580.126.09 (open kernel modules)
Dock: Anker USB-C Docking Device (USB ID 291a:8392) with VIA Labs USB3.1
hub (ID 2109:0822)
Monitors: 3 external displays connected via DP MST through the dock
(3440x1440, 1920x1080, 1600x1200)
Versions:
Ubuntu 24.04.3 LTS (HWE kernel)
Working: 6.14.0-37-generic
Broken: 6.17.0-14-generic
Steps to reproduce:
Connect three external monitors to an Anker USB-C dock via DP MST
Boot with kernel 6.17.0-14-generic
Observe that only one or two external displays activate, and all
displays cycle on/off repeatedly
Reboot into 6.14.0-37-generic — all three displays work immediately
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142146
Title:
DisplayPort MST over USB-C regression in 6.17.0-14 — external monitors
cycle on/off (works on 6.14.0-37)
Status in linux package in Ubuntu:
New
Bug description:
Three external monitors connected via DisplayPort MST through a USB-C
docking station (Anker, ID 291a:8392) fail to work correctly on kernel
6.17.0-14-generic. Only the internal display and one external monitor
are usable. The other two displays repeatedly turn off and on in a
loop, as if the system is continuously attempting and failing to
negotiate the DP MST link.
The same hardware configuration works correctly on kernel
6.14.0-37-generic with no issues.
Symptoms on 6.17.0-14:
Of three external DP MST outputs (DP-1-1-1, DP-1-1-2, DP-1-1-3), only
one or two activate; the third is connected but has no active mode
Connected monitors show severely degraded EDID — e.g. a 3440x1440
display only reports 640x480, 800x600, and 1024x768 as standard modes
All displays (including working ones) cycle off and on repeatedly
NVIDIA log shows all DFP ports cycling between connected and
disconnected
Two USB Billboard devices appear (VIA Labs, ID 2109:8817), suggesting
USB-C DisplayPort Alt Mode is not fully negotiating
Hardware:
Laptop: Lenovo Legion Pro 7 16IAX10H
GPU: NVIDIA GeForce RTX 5070 Ti Laptop GPU
NVIDIA driver: 580.126.09 (open kernel modules)
Dock: Anker USB-C Docking Device (USB ID 291a:8392) with VIA Labs
USB3.1 hub (ID 2109:0822)
Monitors: 3 external displays connected via DP MST through the dock
(3440x1440, 1920x1080, 1600x1200)
Versions:
Ubuntu 24.04.3 LTS (HWE kernel)
Working: 6.14.0-37-generic
Broken: 6.17.0-14-generic
Steps to reproduce:
Connect three external monitors to an Anker USB-C dock via DP MST
Boot with kernel 6.17.0-14-generic
Observe that only one or two external displays activate, and all
displays cycle on/off repeatedly
Reboot into 6.14.0-37-generic — all three displays work immediately
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142146/+subscriptions
среда
[Bug 2141216] Re: Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT (andgpu SMU resume failure)
As a retired research chemist and not a computer person I may be in over
my head here so need more guidance. I followed your link, but at sudo
apt update ended up with...
Err:7 https://ppa.launchpadcontent.net/alessiofaina/launchpad-bug-2141216/ubuntu questing Release
404 Not Found [IP: 185.125.190.80 443]
Error: The repository 'https://ppa.launchpadcontent.net/alessiofaina/launchpad-bug-2141216/ubuntu questing Release' does not have a Release file.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
I'm on Ubuntu questing (25.04). The PPA appears to publish nobel (LTS)
packages. Can you provide me a questing build? If not, point me toward
the correct package for my series? Or perhaps how to test a LTS/nobel
package on questing? I really appreciate all the support I'm getting
from you guys
Mike
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141216
Title:
Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT
(andgpu SMU resume failure)
Status in linux package in Ubuntu:
New
Status in linux source package in Questing:
Triaged
Bug description:
Summary: Suspend/resume broken after latest Ubuntu update on AMD RX
What Happens: After suspend, system wakes but display remains black. VT switching (Ctrl–Alt–F3) does not work. Only hard reboot recovers.
Regression: This started immediately after a recent Ubuntu update
Hardware: AMD RX 960 XT (Nav 44) + AMD Raphael iGPU
Relevant logs: SMU resume failure. GPU ring timeouts, GPU ring timeouts, devcoredump created (already captured by ubuntu-bug tool)
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-12-generic 6.17.0-12.12
ProcVersionSignature: Ubuntu 6.17.0-12.12-generic 6.17.2
Uname: Linux 6.17.0-12-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 7 17:54:17 2026
InstallationDate: Installed on 2025-10-20 (110 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: ASUS System Product Name
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-12-generic root=UUID=3412c7b3-e116-4927-b603-3da7641a647b ro quiet splash mem_sleep_default=s2idle crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2025
dmi.bios.release: 32.65
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3265
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B650E-E WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3265:bd06/11/2025:br32.65:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650E-EWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141216/+subscriptions
my head here so need more guidance. I followed your link, but at sudo
apt update ended up with...
Err:7 https://ppa.launchpadcontent.net/alessiofaina/launchpad-bug-2141216/ubuntu questing Release
404 Not Found [IP: 185.125.190.80 443]
Error: The repository 'https://ppa.launchpadcontent.net/alessiofaina/launchpad-bug-2141216/ubuntu questing Release' does not have a Release file.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
I'm on Ubuntu questing (25.04). The PPA appears to publish nobel (LTS)
packages. Can you provide me a questing build? If not, point me toward
the correct package for my series? Or perhaps how to test a LTS/nobel
package on questing? I really appreciate all the support I'm getting
from you guys
Mike
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141216
Title:
Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT
(andgpu SMU resume failure)
Status in linux package in Ubuntu:
New
Status in linux source package in Questing:
Triaged
Bug description:
Summary: Suspend/resume broken after latest Ubuntu update on AMD RX
What Happens: After suspend, system wakes but display remains black. VT switching (Ctrl–Alt–F3) does not work. Only hard reboot recovers.
Regression: This started immediately after a recent Ubuntu update
Hardware: AMD RX 960 XT (Nav 44) + AMD Raphael iGPU
Relevant logs: SMU resume failure. GPU ring timeouts, GPU ring timeouts, devcoredump created (already captured by ubuntu-bug tool)
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-12-generic 6.17.0-12.12
ProcVersionSignature: Ubuntu 6.17.0-12.12-generic 6.17.2
Uname: Linux 6.17.0-12-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 7 17:54:17 2026
InstallationDate: Installed on 2025-10-20 (110 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: ASUS System Product Name
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-12-generic root=UUID=3412c7b3-e116-4927-b603-3da7641a647b ro quiet splash mem_sleep_default=s2idle crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2025
dmi.bios.release: 32.65
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3265
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B650E-E WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3265:bd06/11/2025:br32.65:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650E-EWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141216/+subscriptions
[Bug 2142112] Re: Resolute update: v6.19.2 upstream stable release
** Changed in: linux (Ubuntu Resolute)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142112
Title:
Resolute update: v6.19.2 upstream stable release
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Resolute:
Fix Committed
Bug description:
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 a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v6.19.2 upstream stable release
from git://git.kernel.org/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142112/+subscriptions
Status: Confirmed => Fix Committed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142112
Title:
Resolute update: v6.19.2 upstream stable release
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Resolute:
Fix Committed
Bug description:
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 a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v6.19.2 upstream stable release
from git://git.kernel.org/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142112/+subscriptions
[Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
Hi,
I'm experiencing the exact same problem as @C6H6 (c6h6vita).
Sorry for bringing up an older bug report again.
In my case, ModemManager was installed automatically alongside KDE when
I installed Kubuntu 25.10.
The newest version (from 18.02.2026) available from the repository for me is:
modemmanager/questing 1.24.2-0ubuntu1 amd64. This one contains the problem.
In another thread, @C6H6 (c6h6vita) mentioned that they installed the package from the following URL:
https://mega.nz/file/CZtzWBZL#VR727-LE12Y9lkicp9eXssQ3AH3qge6KgWIA6BVkHlc
I took a look into the package (because I don't know where they got it from) and then tested it on my system.
Their provided package fixed that issue.
If needed, I'm willing to provide additional information.
Other thread was that one:
https://answers.launchpad.net/ubuntu/+question/819637#5
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1950282
Title:
Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in libmbim package in Ubuntu:
Fix Released
Status in libqmi package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Status in modemmanager package in Ubuntu:
Fix Released
Status in libmbim source package in Jammy:
Fix Released
Status in libqmi source package in Jammy:
Fix Released
Status in linux source package in Jammy:
Confirmed
Status in modemmanager source package in Jammy:
Fix Released
Bug description:
* Impact
Fibocom FM350 modems aren't working with the current version of
modemmanager in 22.04.
* Test case
- install modemmanager, libmbim, and libqmi from -proposed
- reboot and try WWAN function to see if any regression there.
- perform dogfooding of its reverse dependencies (network-
manager, gnome-control-center etc.)
The verification should be done on FM350 to ensure it's correctly
handled but also on other hardware to verify that there are no
regressions
* Regression potential
The SRU does an update to new modemmanager serie so we should do a
complete round of testing on different hardware and confirm there are
no regression.
-------------------------------
0000:55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01)
Subsystem: Hewlett-Packard Company Device [103c:8914]
https://lore.kernel.org/linux-
wireless/20211101035635.26999-1-ricardo.martinez@linux.intel.com/
Modemmanager requires >= 1.19.1, the detail info is in
lp:1962525
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
Dependencies:
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-07-13 (119 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
MachineType: Intel Corporation Alder Lake Client Platform
Package: linux-firmware 1.187.20+staging.31
PackageArchitecture: all
ProcFB: 0 i915
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.14.0-9007-oem N/A
linux-backports-modules-5.14.0-9007-oem N/A
linux-firmware 1.187.20+staging.31
Tags: focal
Uname: Linux 5.14.0-9007-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 08/23/2021
dmi.bios.vendor: Intel Corporation
dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: AlderLake-M LP5 RVP
dmi.board.vendor: Intel Corporation
dmi.board.version: 1
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 0.1
dmi.ec.firmware.release: 1.43
dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku0100000100020000:
dmi.product.family: Alder Lake Client System
dmi.product.name: Alder Lake Client Platform
dmi.product.sku: 0100000100020000
dmi.product.version: 0.1
dmi.sys.vendor: Intel Corporation
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1950282/+subscriptions
I'm experiencing the exact same problem as @C6H6 (c6h6vita).
Sorry for bringing up an older bug report again.
In my case, ModemManager was installed automatically alongside KDE when
I installed Kubuntu 25.10.
The newest version (from 18.02.2026) available from the repository for me is:
modemmanager/questing 1.24.2-0ubuntu1 amd64. This one contains the problem.
In another thread, @C6H6 (c6h6vita) mentioned that they installed the package from the following URL:
https://mega.nz/file/CZtzWBZL#VR727-LE12Y9lkicp9eXssQ3AH3qge6KgWIA6BVkHlc
I took a look into the package (because I don't know where they got it from) and then tested it on my system.
Their provided package fixed that issue.
If needed, I'm willing to provide additional information.
Other thread was that one:
https://answers.launchpad.net/ubuntu/+question/819637#5
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1950282
Title:
Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in libmbim package in Ubuntu:
Fix Released
Status in libqmi package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Status in modemmanager package in Ubuntu:
Fix Released
Status in libmbim source package in Jammy:
Fix Released
Status in libqmi source package in Jammy:
Fix Released
Status in linux source package in Jammy:
Confirmed
Status in modemmanager source package in Jammy:
Fix Released
Bug description:
* Impact
Fibocom FM350 modems aren't working with the current version of
modemmanager in 22.04.
* Test case
- install modemmanager, libmbim, and libqmi from -proposed
- reboot and try WWAN function to see if any regression there.
- perform dogfooding of its reverse dependencies (network-
manager, gnome-control-center etc.)
The verification should be done on FM350 to ensure it's correctly
handled but also on other hardware to verify that there are no
regressions
* Regression potential
The SRU does an update to new modemmanager serie so we should do a
complete round of testing on different hardware and confirm there are
no regression.
-------------------------------
0000:55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01)
Subsystem: Hewlett-Packard Company Device [103c:8914]
https://lore.kernel.org/linux-
wireless/20211101035635.26999-1-ricardo.martinez@linux.intel.com/
Modemmanager requires >= 1.19.1, the detail info is in
lp:1962525
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
Dependencies:
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-07-13 (119 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
MachineType: Intel Corporation Alder Lake Client Platform
Package: linux-firmware 1.187.20+staging.31
PackageArchitecture: all
ProcFB: 0 i915
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.14.0-9007-oem N/A
linux-backports-modules-5.14.0-9007-oem N/A
linux-firmware 1.187.20+staging.31
Tags: focal
Uname: Linux 5.14.0-9007-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 08/23/2021
dmi.bios.vendor: Intel Corporation
dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: AlderLake-M LP5 RVP
dmi.board.vendor: Intel Corporation
dmi.board.version: 1
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 0.1
dmi.ec.firmware.release: 1.43
dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku0100000100020000:
dmi.product.family: Alder Lake Client System
dmi.product.name: Alder Lake Client Platform
dmi.product.sku: 0100000100020000
dmi.product.version: 0.1
dmi.sys.vendor: Intel Corporation
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1950282/+subscriptions
[Bug 2142118] [NEW] Kernel 6.8.0-100: route cache corrupts external IPs as broadcast on systems with VLAN interfaces
Public bug reported:
Description:
- Regression from: 6.8.0-94 (works) to 6.8.0-100 (broken)
- Setup: Dual default routes — physical interface (enp0s31f6, DHCP, metric 100) + VLAN (enp0s31f6.3, static, metric 200)
- Symptom: ip route get 8.8.8.8 returns broadcast 8.8.8.8 ... cache <local,brd> — kernel classifies external unicast IPs as
broadcast, blocking all outbound UDP/ICMP
- Impact: All outbound DNS, NTP, ping fail with "Permission denied"
- Workaround: sudo ip route flush cache temporarily fixes it, but it recurs
- Confirmed: Booting into 6.8.0-94 resolves the issue
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "apport.linux-image-6.8.0-100-generic.nqq2zom5.apport"
https://bugs.launchpad.net/bugs/2142118/+attachment/5947014/+files/apport.linux-image-6.8.0-100-generic.nqq2zom5.apport
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142118
Title:
Kernel 6.8.0-100: route cache corrupts external IPs as broadcast on
systems with VLAN interfaces
Status in linux package in Ubuntu:
New
Bug description:
Description:
- Regression from: 6.8.0-94 (works) to 6.8.0-100 (broken)
- Setup: Dual default routes — physical interface (enp0s31f6, DHCP, metric 100) + VLAN (enp0s31f6.3, static, metric 200)
- Symptom: ip route get 8.8.8.8 returns broadcast 8.8.8.8 ... cache <local,brd> — kernel classifies external unicast IPs as
broadcast, blocking all outbound UDP/ICMP
- Impact: All outbound DNS, NTP, ping fail with "Permission denied"
- Workaround: sudo ip route flush cache temporarily fixes it, but it recurs
- Confirmed: Booting into 6.8.0-94 resolves the issue
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142118/+subscriptions
Description:
- Regression from: 6.8.0-94 (works) to 6.8.0-100 (broken)
- Setup: Dual default routes — physical interface (enp0s31f6, DHCP, metric 100) + VLAN (enp0s31f6.3, static, metric 200)
- Symptom: ip route get 8.8.8.8 returns broadcast 8.8.8.8 ... cache <local,brd> — kernel classifies external unicast IPs as
broadcast, blocking all outbound UDP/ICMP
- Impact: All outbound DNS, NTP, ping fail with "Permission denied"
- Workaround: sudo ip route flush cache temporarily fixes it, but it recurs
- Confirmed: Booting into 6.8.0-94 resolves the issue
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "apport.linux-image-6.8.0-100-generic.nqq2zom5.apport"
https://bugs.launchpad.net/bugs/2142118/+attachment/5947014/+files/apport.linux-image-6.8.0-100-generic.nqq2zom5.apport
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142118
Title:
Kernel 6.8.0-100: route cache corrupts external IPs as broadcast on
systems with VLAN interfaces
Status in linux package in Ubuntu:
New
Bug description:
Description:
- Regression from: 6.8.0-94 (works) to 6.8.0-100 (broken)
- Setup: Dual default routes — physical interface (enp0s31f6, DHCP, metric 100) + VLAN (enp0s31f6.3, static, metric 200)
- Symptom: ip route get 8.8.8.8 returns broadcast 8.8.8.8 ... cache <local,brd> — kernel classifies external unicast IPs as
broadcast, blocking all outbound UDP/ICMP
- Impact: All outbound DNS, NTP, ping fail with "Permission denied"
- Workaround: sudo ip route flush cache temporarily fixes it, but it recurs
- Confirmed: Booting into 6.8.0-94 resolves the issue
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142118/+subscriptions
[Bug 2141216] Re: Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT (andgpu SMU resume failure)
Hi Mike, sorry but I needed to re-create the package as I made a mistake
and didn't want to give you a non-working kernel.
This should work now
https://launchpad.net/~alessiofaina/+archive/ubuntu/launchpad-
bug-2141216/
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141216
Title:
Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT
(andgpu SMU resume failure)
Status in linux package in Ubuntu:
New
Status in linux source package in Questing:
Triaged
Bug description:
Summary: Suspend/resume broken after latest Ubuntu update on AMD RX
What Happens: After suspend, system wakes but display remains black. VT switching (Ctrl–Alt–F3) does not work. Only hard reboot recovers.
Regression: This started immediately after a recent Ubuntu update
Hardware: AMD RX 960 XT (Nav 44) + AMD Raphael iGPU
Relevant logs: SMU resume failure. GPU ring timeouts, GPU ring timeouts, devcoredump created (already captured by ubuntu-bug tool)
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-12-generic 6.17.0-12.12
ProcVersionSignature: Ubuntu 6.17.0-12.12-generic 6.17.2
Uname: Linux 6.17.0-12-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 7 17:54:17 2026
InstallationDate: Installed on 2025-10-20 (110 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: ASUS System Product Name
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-12-generic root=UUID=3412c7b3-e116-4927-b603-3da7641a647b ro quiet splash mem_sleep_default=s2idle crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2025
dmi.bios.release: 32.65
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3265
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B650E-E WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3265:bd06/11/2025:br32.65:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650E-EWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141216/+subscriptions
and didn't want to give you a non-working kernel.
This should work now
https://launchpad.net/~alessiofaina/+archive/ubuntu/launchpad-
bug-2141216/
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141216
Title:
Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT
(andgpu SMU resume failure)
Status in linux package in Ubuntu:
New
Status in linux source package in Questing:
Triaged
Bug description:
Summary: Suspend/resume broken after latest Ubuntu update on AMD RX
What Happens: After suspend, system wakes but display remains black. VT switching (Ctrl–Alt–F3) does not work. Only hard reboot recovers.
Regression: This started immediately after a recent Ubuntu update
Hardware: AMD RX 960 XT (Nav 44) + AMD Raphael iGPU
Relevant logs: SMU resume failure. GPU ring timeouts, GPU ring timeouts, devcoredump created (already captured by ubuntu-bug tool)
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-12-generic 6.17.0-12.12
ProcVersionSignature: Ubuntu 6.17.0-12.12-generic 6.17.2
Uname: Linux 6.17.0-12-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 7 17:54:17 2026
InstallationDate: Installed on 2025-10-20 (110 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: ASUS System Product Name
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-12-generic root=UUID=3412c7b3-e116-4927-b603-3da7641a647b ro quiet splash mem_sleep_default=s2idle crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2025
dmi.bios.release: 32.65
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3265
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B650E-E WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3265:bd06/11/2025:br32.65:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650E-EWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141216/+subscriptions
[Bug 1966620] Re: statx09 in ubuntu_ltp_syscalls failed on Focal 5.4
Test no longer fails for focal generic in our regression testing.
** Tags removed: verification-needed-focal-linux
** Tags added: verification-done-focal-linux
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1966620
Title:
statx09 in ubuntu_ltp_syscalls failed on Focal 5.4
Status in ubuntu-kernel-tests:
Confirmed
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Committed
Bug description:
Issue found on F-azure-5.4.0-1074.77
This is a new test case.
INFO: Test start time: Sat Mar 26 04:49:49 UTC 2022
COMMAND: /opt/ltp/bin/ltp-pan -q -e -S -a 877593 -n 877593 -f /tmp/ltp-biWtOBHU4a/alltests -l /dev/null -C /dev/null -T /dev/null
LOG File: /dev/null
FAILED COMMAND File: /dev/null
TCONF COMMAND File: /dev/null
Running tests.......
tst_kconfig.c:82: TINFO: Parsing kernel config '/lib/modules/5.4.0-1074-azure/build/.config'
tst_cmd.c:285: TINFO: Parsing mkfs.ext4 version
tst_device.c:88: TINFO: Found free device 3 '/dev/loop3'
tst_test.c:996: TINFO: Formatting /dev/loop3 with ext4 opts='-O verity' extra opts=''
mke2fs 1.45.5 (07-Jan-2020)
tst_test.c:1456: TINFO: Timeout per run is 0h 05m 00s
statx09.c:43: TPASS: statx(AT_FDCWD, mnt_point/test_file1, 0, 0, &buf) passed
statx09.c:50: TFAIL: STATX_ATTR_VERITY flag is not set
statx09.c:57: TPASS: statx(AT_FDCWD, mnt_point/test_file2, 0, 0, &buf) passed
statx09.c:61: TPASS: STATX_ATTR_VERITY flag is not set
Summary:
passed 3
failed 1
broken 0
skipped 0
warnings 0
INFO: ltp-pan reported some tests FAIL
LTP Version: 20220121
INFO: Test end time: Sat Mar 26 04:49:49 UTC 2022
https://github.com/linux-test-project/ltp/commit/681f89d97b195a72b6c796890402b4a29630cc22
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1966620/+subscriptions
** Tags removed: verification-needed-focal-linux
** Tags added: verification-done-focal-linux
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1966620
Title:
statx09 in ubuntu_ltp_syscalls failed on Focal 5.4
Status in ubuntu-kernel-tests:
Confirmed
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Committed
Bug description:
Issue found on F-azure-5.4.0-1074.77
This is a new test case.
INFO: Test start time: Sat Mar 26 04:49:49 UTC 2022
COMMAND: /opt/ltp/bin/ltp-pan -q -e -S -a 877593 -n 877593 -f /tmp/ltp-biWtOBHU4a/alltests -l /dev/null -C /dev/null -T /dev/null
LOG File: /dev/null
FAILED COMMAND File: /dev/null
TCONF COMMAND File: /dev/null
Running tests.......
tst_kconfig.c:82: TINFO: Parsing kernel config '/lib/modules/5.4.0-1074-azure/build/.config'
tst_cmd.c:285: TINFO: Parsing mkfs.ext4 version
tst_device.c:88: TINFO: Found free device 3 '/dev/loop3'
tst_test.c:996: TINFO: Formatting /dev/loop3 with ext4 opts='-O verity' extra opts=''
mke2fs 1.45.5 (07-Jan-2020)
tst_test.c:1456: TINFO: Timeout per run is 0h 05m 00s
statx09.c:43: TPASS: statx(AT_FDCWD, mnt_point/test_file1, 0, 0, &buf) passed
statx09.c:50: TFAIL: STATX_ATTR_VERITY flag is not set
statx09.c:57: TPASS: statx(AT_FDCWD, mnt_point/test_file2, 0, 0, &buf) passed
statx09.c:61: TPASS: STATX_ATTR_VERITY flag is not set
Summary:
passed 3
failed 1
broken 0
skipped 0
warnings 0
INFO: ltp-pan reported some tests FAIL
LTP Version: 20220121
INFO: Test end time: Sat Mar 26 04:49:49 UTC 2022
https://github.com/linux-test-project/ltp/commit/681f89d97b195a72b6c796890402b4a29630cc22
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1966620/+subscriptions
[Bug 1893921] Re: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x
Test no longer fails on s390x for focal generic.
** Tags removed: verification-needed-focal-linux
** Tags added: verification-done-focal-linux
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1893921
Title:
ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Won't Fix
Status in linux source package in Hirsute:
Won't Fix
Status in linux source package in Impish:
Won't Fix
Status in linux source package in Jammy:
In Progress
Status in linux source package in Kinetic:
Won't Fix
Status in linux source package in Noble:
Fix Committed
Bug description:
Testing failed on:
s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200901_162956_a95df@/log.gz
The ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x:
15:45:23 DEBUG| [stdout] # selftests: net: rtnetlink.sh
15:45:23 DEBUG| [stdout] # PASS: policy routing
15:45:23 DEBUG| [stdout] # PASS: route get
15:45:28 DEBUG| [stdout] # PASS: preferred_lft addresses have expired
15:45:28 DEBUG| [stdout] # PASS: promote_secondaries complete
15:45:28 DEBUG| [stdout] # PASS: tc htb hierarchy
15:45:29 DEBUG| [stdout] # PASS: gre tunnel endpoint
15:45:29 DEBUG| [stdout] # PASS: gretap
15:45:29 DEBUG| [stdout] # PASS: ip6gretap
15:45:29 DEBUG| [stdout] # PASS: erspan
15:45:29 DEBUG| [stdout] # PASS: ip6erspan
15:45:30 DEBUG| [stdout] # PASS: bridge setup
15:45:31 DEBUG| [stdout] # PASS: ipv6 addrlabel
15:45:31 DEBUG| [stdout] # PASS: set ifalias b14b1d80-dc0b-4a9b-9256-3ec3f86aa891 for test-dummy0
15:45:31 DEBUG| [stdout] # PASS: vrf
15:45:31 DEBUG| [stdout] # PASS: vxlan
15:45:31 DEBUG| [stdout] # FAIL: can't add fou port 7777, skipping test
15:45:31 DEBUG| [stdout] # PASS: macsec
15:45:32 DEBUG| [stdout] # PASS: ipsec
15:45:33 DEBUG| [stdout] # 3,7c3,7
15:45:33 DEBUG| [stdout] # < sa[0] spi=0x00000009 proto=0x32 salt=0x64636261 crypt=1
15:45:33 DEBUG| [stdout] # < sa[0] key=0x31323334 35363738 39303132 33343536
15:45:33 DEBUG| [stdout] # < sa[1] rx ipaddr=0x00000000 00000000 00000000 c0a87b03
15:45:33 DEBUG| [stdout] # < sa[1] spi=0x00000009 proto=0x32 salt=0x64636261 crypt=1
15:45:33 DEBUG| [stdout] # < sa[1] key=0x31323334 35363738 39303132 33343536
15:45:33 DEBUG| [stdout] # ---
15:45:33 DEBUG| [stdout] # > sa[0] spi=0x00000009 proto=0x32 salt=0x61626364 crypt=1
15:45:33 DEBUG| [stdout] # > sa[0] key=0x34333231 38373635 32313039 36353433
15:45:33 DEBUG| [stdout] # > sa[1] rx ipaddr=0x00000000 00000000 00000000 037ba8c0
15:45:33 DEBUG| [stdout] # > sa[1] spi=0x00000009 proto=0x32 salt=0x61626364 crypt=1
15:45:33 DEBUG| [stdout] # > sa[1] key=0x34333231 38373635 32313039 36353433
15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload incorrect driver data
15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload
15:45:33 DEBUG| [stdout] # PASS: bridge fdb get
15:45:33 DEBUG| [stdout] # PASS: neigh get
15:45:33 DEBUG| [stdout] not ok 11 selftests: net: rtnetlink.sh # exit=1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1893921/+subscriptions
** Tags removed: verification-needed-focal-linux
** Tags added: verification-done-focal-linux
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1893921
Title:
ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Won't Fix
Status in linux source package in Hirsute:
Won't Fix
Status in linux source package in Impish:
Won't Fix
Status in linux source package in Jammy:
In Progress
Status in linux source package in Kinetic:
Won't Fix
Status in linux source package in Noble:
Fix Committed
Bug description:
Testing failed on:
s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200901_162956_a95df@/log.gz
The ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x:
15:45:23 DEBUG| [stdout] # selftests: net: rtnetlink.sh
15:45:23 DEBUG| [stdout] # PASS: policy routing
15:45:23 DEBUG| [stdout] # PASS: route get
15:45:28 DEBUG| [stdout] # PASS: preferred_lft addresses have expired
15:45:28 DEBUG| [stdout] # PASS: promote_secondaries complete
15:45:28 DEBUG| [stdout] # PASS: tc htb hierarchy
15:45:29 DEBUG| [stdout] # PASS: gre tunnel endpoint
15:45:29 DEBUG| [stdout] # PASS: gretap
15:45:29 DEBUG| [stdout] # PASS: ip6gretap
15:45:29 DEBUG| [stdout] # PASS: erspan
15:45:29 DEBUG| [stdout] # PASS: ip6erspan
15:45:30 DEBUG| [stdout] # PASS: bridge setup
15:45:31 DEBUG| [stdout] # PASS: ipv6 addrlabel
15:45:31 DEBUG| [stdout] # PASS: set ifalias b14b1d80-dc0b-4a9b-9256-3ec3f86aa891 for test-dummy0
15:45:31 DEBUG| [stdout] # PASS: vrf
15:45:31 DEBUG| [stdout] # PASS: vxlan
15:45:31 DEBUG| [stdout] # FAIL: can't add fou port 7777, skipping test
15:45:31 DEBUG| [stdout] # PASS: macsec
15:45:32 DEBUG| [stdout] # PASS: ipsec
15:45:33 DEBUG| [stdout] # 3,7c3,7
15:45:33 DEBUG| [stdout] # < sa[0] spi=0x00000009 proto=0x32 salt=0x64636261 crypt=1
15:45:33 DEBUG| [stdout] # < sa[0] key=0x31323334 35363738 39303132 33343536
15:45:33 DEBUG| [stdout] # < sa[1] rx ipaddr=0x00000000 00000000 00000000 c0a87b03
15:45:33 DEBUG| [stdout] # < sa[1] spi=0x00000009 proto=0x32 salt=0x64636261 crypt=1
15:45:33 DEBUG| [stdout] # < sa[1] key=0x31323334 35363738 39303132 33343536
15:45:33 DEBUG| [stdout] # ---
15:45:33 DEBUG| [stdout] # > sa[0] spi=0x00000009 proto=0x32 salt=0x61626364 crypt=1
15:45:33 DEBUG| [stdout] # > sa[0] key=0x34333231 38373635 32313039 36353433
15:45:33 DEBUG| [stdout] # > sa[1] rx ipaddr=0x00000000 00000000 00000000 037ba8c0
15:45:33 DEBUG| [stdout] # > sa[1] spi=0x00000009 proto=0x32 salt=0x61626364 crypt=1
15:45:33 DEBUG| [stdout] # > sa[1] key=0x34333231 38373635 32313039 36353433
15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload incorrect driver data
15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload
15:45:33 DEBUG| [stdout] # PASS: bridge fdb get
15:45:33 DEBUG| [stdout] # PASS: neigh get
15:45:33 DEBUG| [stdout] not ok 11 selftests: net: rtnetlink.sh # exit=1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1893921/+subscriptions
[Bug 2142112] [NEW] Resolute update: v6.19.2 upstream stable release
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 a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v6.19.2 upstream stable release
from git://git.kernel.org/
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: linux (Ubuntu Resolute)
Importance: Undecided
Status: Confirmed
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Resolute)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142112
Title:
Resolute update: v6.19.2 upstream stable release
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Resolute:
Confirmed
Bug description:
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 a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v6.19.2 upstream stable release
from git://git.kernel.org/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142112/+subscriptions
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 a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v6.19.2 upstream stable release
from git://git.kernel.org/
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: linux (Ubuntu Resolute)
Importance: Undecided
Status: Confirmed
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Resolute)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142112
Title:
Resolute update: v6.19.2 upstream stable release
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Resolute:
Confirmed
Bug description:
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 a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v6.19.2 upstream stable release
from git://git.kernel.org/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142112/+subscriptions
[Bug 2142111] [NEW] Resolute update: v6.19.1 upstream stable release
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 a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v6.19.1 upstream stable release
from git://git.kernel.org/
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: linux (Ubuntu Resolute)
Importance: Undecided
Status: Confirmed
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Resolute)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142111
Title:
Resolute update: v6.19.1 upstream stable release
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Resolute:
Confirmed
Bug description:
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 a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v6.19.1 upstream stable release
from git://git.kernel.org/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142111/+subscriptions
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 a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v6.19.1 upstream stable release
from git://git.kernel.org/
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: linux (Ubuntu Resolute)
Importance: Undecided
Status: Confirmed
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Resolute)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142111
Title:
Resolute update: v6.19.1 upstream stable release
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Resolute:
Confirmed
Bug description:
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 a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v6.19.1 upstream stable release
from git://git.kernel.org/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142111/+subscriptions
[Bug 2141298] Re: AppArmor blocks write(2) to network sockets with Linux 6.19
there was a patch submitted to the kernel-team ml last Thu/Fri, applied
to git now
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu)
Status: Fix Committed => In Progress
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141298
Title:
AppArmor blocks write(2) to network sockets with Linux 6.19
Status in snapd:
Confirmed
Status in apparmor package in Ubuntu:
Confirmed
Status in chromium-browser package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
In Progress
Bug description:
Ubuntu 26.04 (pre-release) with snapd 2.74 has a regression where
AppArmor blocks network receive operations for Electron-based snaps
with strict confinement, causing all HTTPS connections to fail.
All Electron-based snaps with strict confinement are completely broken
- unable to connect to any HTTPS endpoints.
AFFECTED APPLICATIONS:
- element (tested, confirmed broken)
- prospect-mail (tested, confirmed broken)
- teams-for-linux (tested, confirmed broken)
- Potentially: VS Code, Slack, Discord, and all other Electron snaps
- sbuild+unshare (LP: #2141364)
SYMPTOMS:
1. SSL handshake fails: net_error -10 (ERR_CERT_AUTHORITY_INVALID)
2. App error: "Failed to load URL: https://... with error: ERR_ACCESS_DENIED"
3. Blank page displayed instead of web content
ROOT CAUSE:
AppArmor could be denying network receive operations on IPv6 HTTPS (port 443):
apparmor="DENIED" operation="file_perm" class="net"
profile="snap.teams-for-linux.teams-for-linux"
faddr=2603:1063:27:1::14 fport=443 family="inet6"
sock_type="stream" protocol=6
requested="receive" denied="receive"
SYSTEM INFO:
- Ubuntu: 26.04 (pre-release)
- snapd: 2.74+ubuntu26.04
- Kernel: 6.19.0-3-generic
- snap version output: 2.74
REGRESSION:
- Broken: Ubuntu 26.04 with today update and restart.
STEPS TO REPRODUCE:
1. Install Ubuntu 26.04 (pre-release)
2. Install teams-for-linux snap: snap install teams-for-linux
3. Launch: teams-for-linux
4. Observe SSL errors and AppArmor denials: journalctl -b | grep apparmor | grep DENIED
EXPECTED: Electron snaps can establish HTTPS connections
ACTUAL: AppArmor blocks network receive, all HTTPS connections fail
WORKAROUND:
Use classic confinement (defeats security purpose)
FULL APPARMOR LOG for teams-for-linux:
Feb 09 12:20:52 kernel: audit: type=1400 audit(1770636052.778:4101):
apparmor="DENIED" operation="file_perm" class="net"
profile="snap.teams-for-linux.teams-for-linux" pid=133551
comm="Chrome_ChildIOT" laddr=2a02:8109:a09e:2d00:a71a:d52c:a574:cd43
lport=53180 faddr=2a00:1450:4008:806::200e fport=443 family="inet6"
sock_type="stream" protocol=6 requested="receive" denied="receive"
Log for prospect-mail:
$ prospect-mail
(prospect-mail:150690): Gtk-WARNING **: 12:37:44.087: Theme parsing
error: gtk.css:1413:23: 'font-feature-settings' is not a valid
property name
(prospect-mail:150690): Gtk-WARNING **: 12:37:44.091: Theme parsing
error: gtk.css:3286:25: 'font-feature-settings' is not a valid
property name
(prospect-mail:150690): Gtk-WARNING **: 12:37:44.092: Theme parsing error: gtk.css:3748:23: 'font-feature-settings' is not a valid property name
Loaded settings {
mainMailServiceUrl: 'https://outlook.office.com/mail',
deeplinkUrls: [
'outlook.live.com/mail/deeplink',
'outlook.office365.com/mail/deeplink',
'outlook.office.com/mail/deeplink',
'outlook.office.com/calendar/deeplink',
'to-do.office.com/tasks'
],
mailServicesUrls: [ 'outlook.live.com', 'outlook.office365.com', 'outlook.office.com' ],
safelinksUrls: [
'outlook.office.com/mail/safelink.html',
'safelinks.protection.outlook.com'
]
}
libGL error: MESA-LOADER: failed to open iris (search paths /snap/prospect-mail/75/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open swrast (search paths /snap/prospect-mail/75/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
libGL error: failed to load driver: swrast
[150913:0209/123744.785246:ERROR:ui/gl/angle_platform_impl.cc:42] Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
ERR: Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[150913:0209/123744.785366:ERROR:ui/gl/egl_util.cc:92] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[150913:0209/123744.785399:ERROR:ui/gl/gl_display.cc:639] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[150913:0209/123744.786076:ERROR:ui/gl/angle_platform_impl.cc:42] Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
ERR: Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[150913:0209/123744.786133:ERROR:ui/gl/egl_util.cc:92] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[150913:0209/123744.786156:ERROR:ui/gl/gl_display.cc:639] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[150913:0209/123744.786176:ERROR:ui/gl/gl_display.cc:674] Initialization of all EGL display types failed.
[150913:0209/123744.786200:ERROR:ui/ozone/common/gl_ozone_egl.cc:26] GLDisplayEGL::Initialize failed.
[150913:0209/123744.788284:ERROR:ui/gl/angle_platform_impl.cc:42] Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
ERR: Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[150913:0209/123744.788352:ERROR:ui/gl/egl_util.cc:92] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[150913:0209/123744.788392:ERROR:ui/gl/gl_display.cc:639] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[150913:0209/123744.789184:ERROR:ui/gl/angle_platform_impl.cc:42] Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
ERR: Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[150913:0209/123744.789231:ERROR:ui/gl/egl_util.cc:92] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[150913:0209/123744.789258:ERROR:ui/gl/gl_display.cc:639] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[150913:0209/123744.789284:ERROR:ui/gl/gl_display.cc:674] Initialization of all EGL display types failed.
[150913:0209/123744.789309:ERROR:ui/ozone/common/gl_ozone_egl.cc:26] GLDisplayEGL::Initialize failed.
[150913:0209/123744.829927:ERROR:components/viz/service/main/viz_main_impl.cc:189] Exiting GPU process due to errors during initialization
Custom User Agent: Mozilla/5.0 X11; Linux x86_64 AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36 Edg/143.0.0.0
(prospect-mail:150690): Gtk-WARNING **: 12:37:44.993: Theme parsing
error: gtk-dark.css:1413:23: 'font-feature-settings' is not a valid
property name
(prospect-mail:150690): Gtk-WARNING **: 12:37:44.995: Theme parsing
error: gtk-dark.css:3286:25: 'font-feature-settings' is not a valid
property name
(prospect-mail:150690): Gtk-WARNING **: 12:37:44.996: Theme parsing error: gtk-dark.css:3748:23: 'font-feature-settings' is not a valid property name
libGL error: MESA-LOADER: failed to open iris (search paths /snap/prospect-mail/75/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open swrast (search paths /snap/prospect-mail/75/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
libGL error: failed to load driver: swrast
[150950:0209/123745.102046:ERROR:ui/gl/angle_platform_impl.cc:42] Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
ERR: Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[150950:0209/123745.102146:ERROR:ui/gl/egl_util.cc:92] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[150950:0209/123745.102186:ERROR:ui/gl/gl_display.cc:639] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[150950:0209/123745.102800:ERROR:ui/gl/angle_platform_impl.cc:42] Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
ERR: Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[150950:0209/123745.102830:ERROR:ui/gl/egl_util.cc:92] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[150950:0209/123745.102854:ERROR:ui/gl/gl_display.cc:639] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[150950:0209/123745.102878:ERROR:ui/gl/gl_display.cc:674] Initialization of all EGL display types failed.
[150950:0209/123745.102904:ERROR:ui/ozone/common/gl_ozone_egl.cc:26] GLDisplayEGL::Initialize failed.
[150950:0209/123745.105119:ERROR:ui/gl/angle_platform_impl.cc:42] Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
ERR: Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[150950:0209/123745.105188:ERROR:ui/gl/egl_util.cc:92] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[150950:0209/123745.105210:ERROR:ui/gl/gl_display.cc:639] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[150950:0209/123745.105798:ERROR:ui/gl/angle_platform_impl.cc:42] Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
ERR: Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[150950:0209/123745.105826:ERROR:ui/gl/egl_util.cc:92] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[150950:0209/123745.105847:ERROR:ui/gl/gl_display.cc:639] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[150950:0209/123745.105867:ERROR:ui/gl/gl_display.cc:674] Initialization of all EGL display types failed.
[150950:0209/123745.105886:ERROR:ui/ozone/common/gl_ozone_egl.cc:26] GLDisplayEGL::Initialize failed.
[150950:0209/123745.106596:ERROR:components/viz/service/main/viz_main_impl.cc:189] Exiting GPU process due to errors during initialization
MESA-LOADER: failed to open iris (search paths /snap/prospect-mail/75/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
failed to load driver: iris
MESA-LOADER: failed to open kms_swrast (search paths /snap/prospect-mail/75/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast (search paths /snap/prospect-mail/75/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
failed to load swrast driver
[150920:0209/123745.290838:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[150920:0209/123745.299953:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
(node:150690) electron: Failed to load URL: https://outlook.office.com/mail with error: ERR_ACCESS_DENIED
(Use `prospect-mail --trace-warnings ...` to show where the warning was created)
Prepare 'main.css' to be injected.
Prepare 'unread-number-observer.js' to be injected.
(node:150690) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
Log for teams-for-linux:
$ teams-for-linux
No config file found (user or system-wide), using default values
all good with screenSharingThumbnail you aren't using them
all good with screenLockInhibitionMethod you aren't using them
all good with ssoInTuneEnabled you aren't using them
all good with ssoInTuneAuthUser you aren't using them
Initialising logger with config: {"transports":{"console":{"level":"info"},"file":{"level":false}}}
12:39:48.904 › configPath: /home/alarconj/snap/teams-for-linux/1155/.config/teams-for-linux
12:39:48.906 › Running under Wayland, disabling GPU composition (default behavior)...
12:39:48.906 › Enabling PipeWire for screen sharing...
12:39:48.906 › Disabling GPU support...
dbus-send: /snap/teams-for-linux/1155/lib/x86_64-linux-gnu/libdbus-1.so.3: version `LIBDBUS_PRIVATE_1.12.20' not found (required by dbus-send)
12:39:48.932 › [CustomNotificationManager] Initialized and listening on "notification-show-toast" channel
(teams-for-linux:152814): Gtk-WARNING **: 12:39:48.956: Theme parsing
error: gtk.css:1413:23: 'font-feature-settings' is not a valid
property name
(teams-for-linux:152814): Gtk-WARNING **: 12:39:48.959: Theme parsing
error: gtk.css:3286:25: 'font-feature-settings' is not a valid
property name
(teams-for-linux:152814): Gtk-WARNING **: 12:39:48.959: Theme parsing error: gtk.css:3748:23: 'font-feature-settings' is not a valid property name
[152814:0209/123949.008056:ERROR:dbus/object_proxy.cc:573] Failed to call method: org.freedesktop.Secret.Service.ReadAlias: object_path= /org/freedesktop/secrets: org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.1388" (uid=1000 pid=152814 comm="/snap/teams-for-linux/1155/teams-for-linux --ozone" label="snap.teams-for-linux.teams-for-linux (enforce)") interface="org.freedesktop.Secret.Service" member="ReadAlias" error name="(unset)" requested_reply="0" destination="org.freedesktop.secrets" (uid=1000 pid=3716 comm="/usr/bin/gnome-keyring-daemon --foreground --compo" label="unconfined")
MESA-LOADER: failed to open iris (search paths /snap/teams-for-linux/1155/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
failed to load driver: iris
MESA-LOADER: failed to open kms_swrast (search paths /snap/teams-for-linux/1155/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast (search paths /snap/teams-for-linux/1155/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
failed to load swrast driver
12:39:49.059 › 🔒 IPC Security: Channel allowlisting enabled
12:39:49.059 › 🔒 IPC Security: 50 channels allowlisted
(teams-for-linux:152814): Gtk-WARNING **: 12:39:49.082: Theme parsing
error: gtk-dark.css:1413:23: 'font-feature-settings' is not a valid
property name
(teams-for-linux:152814): Gtk-WARNING **: 12:39:49.084: Theme parsing
error: gtk-dark.css:3286:25: 'font-feature-settings' is not a valid
property name
(teams-for-linux:152814): Gtk-WARNING **: 12:39:49.085: Theme parsing error: gtk-dark.css:3748:23: 'font-feature-settings' is not a valid property name
[152915:0209/123949.124882:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152814:0209/123949.161887:ERROR:dbus/object_proxy.cc:573] Failed to call method: org.freedesktop.login1.Manager.Inhibit: object_path= /org/freedesktop/login1: org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.599" (uid=1000 pid=152814 comm="/snap/teams-for-linux/1155/teams-for-linux --ozone" label="snap.teams-for-linux.teams-for-linux (enforce)") interface="org.freedesktop.login1.Manager" member="Inhibit" error name="(unset)" requested_reply="0" destination="org.freedesktop.login1" (uid=0 pid=1528 comm="/usr/lib/systemd/systemd-logind" label="unconfined")
[152915:0209/123949.206210:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152915:0209/123949.732665:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152915:0209/123950.248492:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152915:0209/123950.768544:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152915:0209/123951.289729:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152915:0209/123951.833859:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152915:0209/123952.348596:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152915:0209/123952.868749:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152915:0209/123953.397271:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152915:0209/123953.997766:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152915:0209/123954.550755:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
12:39:54.584 › assignOnDidFailLoadEventHandler : {} - -10 - ERR_ACCESS_DENIED
12:39:54.584 › (node:152814) electron: Failed to load URL: https://teams.cloud.microsoft/ with error: ERR_ACCESS_DENIED
(Use `teams-for-linux --trace-warnings ...` to show where the warning was created)
12:39:54.660 › (node:152814) UnhandledPromiseRejectionWarning: Error: Script failed to execute, this normally means an error was thrown. Check the renderer console for the error.
at node:electron/js2c/renderer_init:2:19969
at IpcRendererInternal.<anonymous> (node:electron/js2c/renderer_init:2:14304)
at IpcRendererInternal.emit (node:events:519:28)
at Object.onMessage (node:electron/js2c/renderer_init:2:13382)
12:39:54.661 › (node:152814) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
RELATED snapd 2.74 CHANGE:
"snap-confine: update AppArmor profile to allow read/write to journal as workaround for snap-confine fd inheritance prevented by newer AppArmor"
This suggests AppArmor policies were updated but network receive was
inadvertently blocked.
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2141298/+subscriptions
to git now
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu)
Status: Fix Committed => In Progress
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141298
Title:
AppArmor blocks write(2) to network sockets with Linux 6.19
Status in snapd:
Confirmed
Status in apparmor package in Ubuntu:
Confirmed
Status in chromium-browser package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
In Progress
Bug description:
Ubuntu 26.04 (pre-release) with snapd 2.74 has a regression where
AppArmor blocks network receive operations for Electron-based snaps
with strict confinement, causing all HTTPS connections to fail.
All Electron-based snaps with strict confinement are completely broken
- unable to connect to any HTTPS endpoints.
AFFECTED APPLICATIONS:
- element (tested, confirmed broken)
- prospect-mail (tested, confirmed broken)
- teams-for-linux (tested, confirmed broken)
- Potentially: VS Code, Slack, Discord, and all other Electron snaps
- sbuild+unshare (LP: #2141364)
SYMPTOMS:
1. SSL handshake fails: net_error -10 (ERR_CERT_AUTHORITY_INVALID)
2. App error: "Failed to load URL: https://... with error: ERR_ACCESS_DENIED"
3. Blank page displayed instead of web content
ROOT CAUSE:
AppArmor could be denying network receive operations on IPv6 HTTPS (port 443):
apparmor="DENIED" operation="file_perm" class="net"
profile="snap.teams-for-linux.teams-for-linux"
faddr=2603:1063:27:1::14 fport=443 family="inet6"
sock_type="stream" protocol=6
requested="receive" denied="receive"
SYSTEM INFO:
- Ubuntu: 26.04 (pre-release)
- snapd: 2.74+ubuntu26.04
- Kernel: 6.19.0-3-generic
- snap version output: 2.74
REGRESSION:
- Broken: Ubuntu 26.04 with today update and restart.
STEPS TO REPRODUCE:
1. Install Ubuntu 26.04 (pre-release)
2. Install teams-for-linux snap: snap install teams-for-linux
3. Launch: teams-for-linux
4. Observe SSL errors and AppArmor denials: journalctl -b | grep apparmor | grep DENIED
EXPECTED: Electron snaps can establish HTTPS connections
ACTUAL: AppArmor blocks network receive, all HTTPS connections fail
WORKAROUND:
Use classic confinement (defeats security purpose)
FULL APPARMOR LOG for teams-for-linux:
Feb 09 12:20:52 kernel: audit: type=1400 audit(1770636052.778:4101):
apparmor="DENIED" operation="file_perm" class="net"
profile="snap.teams-for-linux.teams-for-linux" pid=133551
comm="Chrome_ChildIOT" laddr=2a02:8109:a09e:2d00:a71a:d52c:a574:cd43
lport=53180 faddr=2a00:1450:4008:806::200e fport=443 family="inet6"
sock_type="stream" protocol=6 requested="receive" denied="receive"
Log for prospect-mail:
$ prospect-mail
(prospect-mail:150690): Gtk-WARNING **: 12:37:44.087: Theme parsing
error: gtk.css:1413:23: 'font-feature-settings' is not a valid
property name
(prospect-mail:150690): Gtk-WARNING **: 12:37:44.091: Theme parsing
error: gtk.css:3286:25: 'font-feature-settings' is not a valid
property name
(prospect-mail:150690): Gtk-WARNING **: 12:37:44.092: Theme parsing error: gtk.css:3748:23: 'font-feature-settings' is not a valid property name
Loaded settings {
mainMailServiceUrl: 'https://outlook.office.com/mail',
deeplinkUrls: [
'outlook.live.com/mail/deeplink',
'outlook.office365.com/mail/deeplink',
'outlook.office.com/mail/deeplink',
'outlook.office.com/calendar/deeplink',
'to-do.office.com/tasks'
],
mailServicesUrls: [ 'outlook.live.com', 'outlook.office365.com', 'outlook.office.com' ],
safelinksUrls: [
'outlook.office.com/mail/safelink.html',
'safelinks.protection.outlook.com'
]
}
libGL error: MESA-LOADER: failed to open iris (search paths /snap/prospect-mail/75/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open swrast (search paths /snap/prospect-mail/75/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
libGL error: failed to load driver: swrast
[150913:0209/123744.785246:ERROR:ui/gl/angle_platform_impl.cc:42] Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
ERR: Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[150913:0209/123744.785366:ERROR:ui/gl/egl_util.cc:92] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[150913:0209/123744.785399:ERROR:ui/gl/gl_display.cc:639] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[150913:0209/123744.786076:ERROR:ui/gl/angle_platform_impl.cc:42] Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
ERR: Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[150913:0209/123744.786133:ERROR:ui/gl/egl_util.cc:92] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[150913:0209/123744.786156:ERROR:ui/gl/gl_display.cc:639] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[150913:0209/123744.786176:ERROR:ui/gl/gl_display.cc:674] Initialization of all EGL display types failed.
[150913:0209/123744.786200:ERROR:ui/ozone/common/gl_ozone_egl.cc:26] GLDisplayEGL::Initialize failed.
[150913:0209/123744.788284:ERROR:ui/gl/angle_platform_impl.cc:42] Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
ERR: Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[150913:0209/123744.788352:ERROR:ui/gl/egl_util.cc:92] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[150913:0209/123744.788392:ERROR:ui/gl/gl_display.cc:639] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[150913:0209/123744.789184:ERROR:ui/gl/angle_platform_impl.cc:42] Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
ERR: Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[150913:0209/123744.789231:ERROR:ui/gl/egl_util.cc:92] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[150913:0209/123744.789258:ERROR:ui/gl/gl_display.cc:639] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[150913:0209/123744.789284:ERROR:ui/gl/gl_display.cc:674] Initialization of all EGL display types failed.
[150913:0209/123744.789309:ERROR:ui/ozone/common/gl_ozone_egl.cc:26] GLDisplayEGL::Initialize failed.
[150913:0209/123744.829927:ERROR:components/viz/service/main/viz_main_impl.cc:189] Exiting GPU process due to errors during initialization
Custom User Agent: Mozilla/5.0 X11; Linux x86_64 AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36 Edg/143.0.0.0
(prospect-mail:150690): Gtk-WARNING **: 12:37:44.993: Theme parsing
error: gtk-dark.css:1413:23: 'font-feature-settings' is not a valid
property name
(prospect-mail:150690): Gtk-WARNING **: 12:37:44.995: Theme parsing
error: gtk-dark.css:3286:25: 'font-feature-settings' is not a valid
property name
(prospect-mail:150690): Gtk-WARNING **: 12:37:44.996: Theme parsing error: gtk-dark.css:3748:23: 'font-feature-settings' is not a valid property name
libGL error: MESA-LOADER: failed to open iris (search paths /snap/prospect-mail/75/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open swrast (search paths /snap/prospect-mail/75/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
libGL error: failed to load driver: swrast
[150950:0209/123745.102046:ERROR:ui/gl/angle_platform_impl.cc:42] Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
ERR: Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[150950:0209/123745.102146:ERROR:ui/gl/egl_util.cc:92] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[150950:0209/123745.102186:ERROR:ui/gl/gl_display.cc:639] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[150950:0209/123745.102800:ERROR:ui/gl/angle_platform_impl.cc:42] Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
ERR: Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[150950:0209/123745.102830:ERROR:ui/gl/egl_util.cc:92] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[150950:0209/123745.102854:ERROR:ui/gl/gl_display.cc:639] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[150950:0209/123745.102878:ERROR:ui/gl/gl_display.cc:674] Initialization of all EGL display types failed.
[150950:0209/123745.102904:ERROR:ui/ozone/common/gl_ozone_egl.cc:26] GLDisplayEGL::Initialize failed.
[150950:0209/123745.105119:ERROR:ui/gl/angle_platform_impl.cc:42] Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
ERR: Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[150950:0209/123745.105188:ERROR:ui/gl/egl_util.cc:92] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[150950:0209/123745.105210:ERROR:ui/gl/gl_display.cc:639] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[150950:0209/123745.105798:ERROR:ui/gl/angle_platform_impl.cc:42] Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
ERR: Display.cpp:1093 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[150950:0209/123745.105826:ERROR:ui/gl/egl_util.cc:92] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[150950:0209/123745.105847:ERROR:ui/gl/gl_display.cc:639] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[150950:0209/123745.105867:ERROR:ui/gl/gl_display.cc:674] Initialization of all EGL display types failed.
[150950:0209/123745.105886:ERROR:ui/ozone/common/gl_ozone_egl.cc:26] GLDisplayEGL::Initialize failed.
[150950:0209/123745.106596:ERROR:components/viz/service/main/viz_main_impl.cc:189] Exiting GPU process due to errors during initialization
MESA-LOADER: failed to open iris (search paths /snap/prospect-mail/75/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
failed to load driver: iris
MESA-LOADER: failed to open kms_swrast (search paths /snap/prospect-mail/75/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast (search paths /snap/prospect-mail/75/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
failed to load swrast driver
[150920:0209/123745.290838:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[150920:0209/123745.299953:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
(node:150690) electron: Failed to load URL: https://outlook.office.com/mail with error: ERR_ACCESS_DENIED
(Use `prospect-mail --trace-warnings ...` to show where the warning was created)
Prepare 'main.css' to be injected.
Prepare 'unread-number-observer.js' to be injected.
(node:150690) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
Log for teams-for-linux:
$ teams-for-linux
No config file found (user or system-wide), using default values
all good with screenSharingThumbnail you aren't using them
all good with screenLockInhibitionMethod you aren't using them
all good with ssoInTuneEnabled you aren't using them
all good with ssoInTuneAuthUser you aren't using them
Initialising logger with config: {"transports":{"console":{"level":"info"},"file":{"level":false}}}
12:39:48.904 › configPath: /home/alarconj/snap/teams-for-linux/1155/.config/teams-for-linux
12:39:48.906 › Running under Wayland, disabling GPU composition (default behavior)...
12:39:48.906 › Enabling PipeWire for screen sharing...
12:39:48.906 › Disabling GPU support...
dbus-send: /snap/teams-for-linux/1155/lib/x86_64-linux-gnu/libdbus-1.so.3: version `LIBDBUS_PRIVATE_1.12.20' not found (required by dbus-send)
12:39:48.932 › [CustomNotificationManager] Initialized and listening on "notification-show-toast" channel
(teams-for-linux:152814): Gtk-WARNING **: 12:39:48.956: Theme parsing
error: gtk.css:1413:23: 'font-feature-settings' is not a valid
property name
(teams-for-linux:152814): Gtk-WARNING **: 12:39:48.959: Theme parsing
error: gtk.css:3286:25: 'font-feature-settings' is not a valid
property name
(teams-for-linux:152814): Gtk-WARNING **: 12:39:48.959: Theme parsing error: gtk.css:3748:23: 'font-feature-settings' is not a valid property name
[152814:0209/123949.008056:ERROR:dbus/object_proxy.cc:573] Failed to call method: org.freedesktop.Secret.Service.ReadAlias: object_path= /org/freedesktop/secrets: org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.1388" (uid=1000 pid=152814 comm="/snap/teams-for-linux/1155/teams-for-linux --ozone" label="snap.teams-for-linux.teams-for-linux (enforce)") interface="org.freedesktop.Secret.Service" member="ReadAlias" error name="(unset)" requested_reply="0" destination="org.freedesktop.secrets" (uid=1000 pid=3716 comm="/usr/bin/gnome-keyring-daemon --foreground --compo" label="unconfined")
MESA-LOADER: failed to open iris (search paths /snap/teams-for-linux/1155/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
failed to load driver: iris
MESA-LOADER: failed to open kms_swrast (search paths /snap/teams-for-linux/1155/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast (search paths /snap/teams-for-linux/1155/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
failed to load swrast driver
12:39:49.059 › 🔒 IPC Security: Channel allowlisting enabled
12:39:49.059 › 🔒 IPC Security: 50 channels allowlisted
(teams-for-linux:152814): Gtk-WARNING **: 12:39:49.082: Theme parsing
error: gtk-dark.css:1413:23: 'font-feature-settings' is not a valid
property name
(teams-for-linux:152814): Gtk-WARNING **: 12:39:49.084: Theme parsing
error: gtk-dark.css:3286:25: 'font-feature-settings' is not a valid
property name
(teams-for-linux:152814): Gtk-WARNING **: 12:39:49.085: Theme parsing error: gtk-dark.css:3748:23: 'font-feature-settings' is not a valid property name
[152915:0209/123949.124882:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152814:0209/123949.161887:ERROR:dbus/object_proxy.cc:573] Failed to call method: org.freedesktop.login1.Manager.Inhibit: object_path= /org/freedesktop/login1: org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.599" (uid=1000 pid=152814 comm="/snap/teams-for-linux/1155/teams-for-linux --ozone" label="snap.teams-for-linux.teams-for-linux (enforce)") interface="org.freedesktop.login1.Manager" member="Inhibit" error name="(unset)" requested_reply="0" destination="org.freedesktop.login1" (uid=0 pid=1528 comm="/usr/lib/systemd/systemd-logind" label="unconfined")
[152915:0209/123949.206210:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152915:0209/123949.732665:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152915:0209/123950.248492:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152915:0209/123950.768544:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152915:0209/123951.289729:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152915:0209/123951.833859:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152915:0209/123952.348596:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152915:0209/123952.868749:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152915:0209/123953.397271:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152915:0209/123953.997766:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
[152915:0209/123954.550755:ERROR:net/socket/ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -10
12:39:54.584 › assignOnDidFailLoadEventHandler : {} - -10 - ERR_ACCESS_DENIED
12:39:54.584 › (node:152814) electron: Failed to load URL: https://teams.cloud.microsoft/ with error: ERR_ACCESS_DENIED
(Use `teams-for-linux --trace-warnings ...` to show where the warning was created)
12:39:54.660 › (node:152814) UnhandledPromiseRejectionWarning: Error: Script failed to execute, this normally means an error was thrown. Check the renderer console for the error.
at node:electron/js2c/renderer_init:2:19969
at IpcRendererInternal.<anonymous> (node:electron/js2c/renderer_init:2:14304)
at IpcRendererInternal.emit (node:events:519:28)
at Object.onMessage (node:electron/js2c/renderer_init:2:13382)
12:39:54.661 › (node:152814) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
RELATED snapd 2.74 CHANGE:
"snap-confine: update AppArmor profile to allow read/write to journal as workaround for snap-confine fd inheritance prevented by newer AppArmor"
This suggests AppArmor policies were updated but network receive was
inadvertently blocked.
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2141298/+subscriptions
[Bug 2065153] Re: [qxl] Ubuntu 24.04 VM guest console freezes after some hours
Kernel 6.8.0-39 is in Ubuntu 24.04 repos and does not contain this bug.
Installing and pointing GRUB to it can be another temporary fix.
I found an interesting thread in the Proxmox forum (
https://forum.proxmox.com/threads/ttm-buffer-eviction-failed.152720 )
that contains the following sentence:
"...the bug was introduced in the upstream linux kernel over 3 years ago
through simplification of the kvm/qemu QXL guest video driver and has
propagated from there. The bug was removed briefly by reverting the
prior change (via the upstream linux kernel, but pulled into the kernel
of many distros, e.g. 6.8.0-38 and -39 in Ubuntu and derivatives) before
being re-introduced because the developer said the reverted,
unsimplified code caused crashes in their testing environments..."
Thus:
- versions 6.8.0-38 and -39 in Ubuntu and derivatives do not contain the bug
- what the developer said when he knowingly reintroduced the bug explains well why the fix is so long overdue and why it will not likely materialize anytime soon
As explained in my first post here, I have an Ubuntu 24.04 VPS server under Openstack with this bug, cannot switch to Virtio, neither can increase the VRAM, because my VPS provider does not allow me to do so.
So I tried the following:
0- took a snapshot of my VPS, just in case
1- installed kernel 6.8.0-39, which is compatible with Ubuntu 24.04:
apt-get install linux-image-6.8.0-39-generic
2- marked this kernel as 'hold':
apt-mark hold linux-image-6.8.0-39-generic
3- changed GRUB conf file to point by default to this kernel:
nano /etc/default/grub; edited the GRUB_DEFAULT=... line as follows
(in my server, it could be different in yours; check the 'menuentry' and 'submenu' lines in your /boot/grub/grub.cfg to find out):
commented the current GRUB_DEFAULT line, and added:
GRUB_DEFAULT="Advanced options for Ubuntu>Ubuntu, with Linux
6.8.0-39-generic"
saved
4- updated GRUB:
update-grub
5- rebooted
6- checked:
uname -r
expected output: 6.8.0-39-generic
Since then, now for several weeks, I have never received the "Buffer
eviction failed" error, nor have I had malfunctions with the QXL/Spice
console nor any other problems, whereas with other kernels I had to
reboot every couple of days.
Installing a superseded kernel is obviously not a proper solution of our
problem but it could be a useful temporary fix for those who cannot
switch from QXL/Spice to other virtual consoles or go 'headless' or
downgrade to Ubuntu 22.04.
Reverting the temporary fix is straightforward:
1. revert changes in /etc/default/grub
2. update-grub
3. reboot
4. uname -r
(5. apt-mark unhold linux-image-6.8.0-39-generic)
Hope this helps.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2065153
Title:
[qxl] Ubuntu 24.04 VM guest console freezes after some hours
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Confirmed
Status in linux source package in Noble:
Confirmed
Bug description:
Thank you @dreibh for reporting the original description and reporting
the bug!
[ Impact ]
* The qxl driver currently has a bug that causes console freezes on qxl paravirtualized GPUs. This issue does not cause a full system hang since the system is still accessible via other means such as SSH, but it does cause the virtual console output to hang. The following dmesg output is seen when the issue occurs:
[ 280.618452] [TTM] Buffer eviction failed
[ 280.618463] qxl 0000:00:01.0: object_init failed for (3149824, 0x00000001)
[ 280.618466] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO
* The issue was caused by commit: (5a838e5d5825 "drm/qxl: simplify qxl_fence_wait") Which does not add any new code but tries to simplify the already existing function.
This commit due to the problems it has caused, has been reverted upstream with: 07ed11afb68d Revert ("drm/qxl: simplify qxl_fence_wait"). The commit also adds back the DMA_FENCE_WARN macro due to it's usage in the reverted functions. The macro was originally removed with: d72277b6c37d ("dma-buf: nuke DMA_FENCE_TRACE macros v2").
[ Test Plan ]
To Reproduce the bug follow the below steps:
1. Install a Ubuntu version with an affected kernel in a VM and make
sure that the QXL video driver is in use instead of virtio. The server
edition is enough for the reproducer no need for a DE to be installed.
The issue is reproducible on Jammy 5.15 and above except Plucky since
the fix is included in kernel 6.14.
2. Create a script and make it executable with the following content:
```
#!/bin/bash
chvt 3
for j in $(seq 80); do
echo "$(date) starting round $j"
if [ "$(journalctl --boot | grep "failed to allocate VRAM BO")" != "" ];
then
echo "bug was reproduced after $j tries"
exit 1
fi
for i in $(seq 100); do
dmesg > /dev/tty3
done
done
echo "bug could not be reproduced"
exit 0
```
3. Execute the script from the virtual console and from an SSH session, monitor the dmesg logs until you see the following:
[ 280.618452] [TTM] Buffer eviction failed
[ 280.618463] qxl 0000:00:01.0: object_init failed for (3149824, 0x00000001)
[ 280.618466] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO
[ Where problems could occur ]
* Virtual displays might still freeze or hang
* Warning messages related to the qxl driver might occur.
[ Other Info]
* The patch does cause a warning message to show up on boot when using
the qxl video driver. The warning itself is harmless and does not seem
to have any negative effects in my testing:
[ 5.011445] WARNING: CPU: 15 PID: 822 at kernel/workqueue.c:2985 check_flush_dependency.part.0+0xde/0x140
[ 5.011449] Modules linked in: qrtr cfg80211 binfmt_misc intel_rapl_msr intel_rapl_common intel_uncore_frequency_common intel_pmc_core intel_vsec pmt_telemetry pmt_class kvm_intel kvm snd_hda_codec_generic irqbypass snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi rapl snd_hda_codec snd_hda_core snd_hwdep snd_pcm joydev snd_timer snd qxl i2c_i801 soundcore drm_ttm_helper i2c_smbus lpc_ich ttm input_leds mac_hid serio_raw sch_fq_codel dm_multipath msr efi_pstore nfnetlink dmi_sysfs qemu_fw_cfg ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 hid_generic usbhid hid crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel sha256_ssse3 ahci sha1_ssse3 libahci psmouse virtio_rng xhci_pci xhci_pci_renesas aesni_intel crypto_simd cryptd
[ 5.011493] CPU: 15 PID: 822 Comm: kworker/u65:1 Not tainted 6.8.0-999-generic #70
[ 5.011495] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[ 5.011496] Workqueue: ttm ttm_bo_delayed_delete [ttm]
[ 5.011501] RIP: 0010:check_flush_dependency.part.0+0xde/0x140
[ 5.011502] Code: 24 18 4d 89 f0 49 8d 8d b0 00 00 00 48 c7 c7 e0 8f e6 8a c6 05 f3 90 8c 02 01 48 8b 70 08 48 81 c6 b0 00 00 00 e8 a2 5e fd ff <0f> 0b eb 91 0f b6 1d d9 90 8c 02 80 fb 01 0f 87 38 57 0a 01 83 e3
[ 5.011503] RSP: 0018:ffffbd85c0ce7c28 EFLAGS: 00010046
[ 5.011505] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
[ 5.011506] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 5.011506] RBP: ffffbd85c0ce7c48 R08: 0000000000000000 R09: 0000000000000000
[ 5.011507] R10: 0000000000000000 R11: 0000000000000000 R12: ffff9f308158a540
[ 5.011508] R13: ffff9f30801cea00 R14: ffffffffc0946570 R15: 0000000000000000
[ 5.011509] FS: 0000000000000000(0000) GS:ffff9f31f7d80000(0000) knlGS:0000000000000000
[ 5.011510] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 5.011510] CR2: 000000c000a02000 CR3: 0000000108cf8000 CR4: 0000000000750ef0
[ 5.011514] PKRU: 55555554
[ 5.011514] Call Trace:
[ 5.011516] <TASK>
[ 5.011518] ? show_regs+0x6d/0x80
[ 5.011521] ? __warn+0x89/0x160
[ 5.011523] ? check_flush_dependency.part.0+0xde/0x140
[ 5.011524] ? report_bug+0x17e/0x1b0
[ 5.011527] ? handle_bug+0x6e/0xb0
[ 5.011529] ? exc_invalid_op+0x18/0x80
[ 5.011532] ? asm_exc_invalid_op+0x1b/0x20
[ 5.011535] ? __pfx_qxl_gc_work+0x10/0x10 [qxl]
[ 5.011539] ? check_flush_dependency.part.0+0xde/0x140
[ 5.011540] ? check_flush_dependency.part.0+0xde/0x140
[ 5.011541] start_flush_work+0xba/0x340
[ 5.011543] flush_work+0x5f/0xb0
[ 5.011545] qxl_queue_garbage_collect+0x8c/0x90 [qxl]
[ 5.011548] qxl_fence_wait+0xa3/0x1b0 [qxl]
[ 5.011552] dma_fence_wait_timeout+0x64/0x140
[ 5.011555] dma_resv_wait_timeout+0x7f/0xf0
[ 5.011556] ttm_bo_delayed_delete+0x2a/0xc0 [ttm]
[ 5.011560] process_one_work+0x181/0x3a0
[ 5.011562] worker_thread+0x306/0x440
[ 5.011563] ? __pfx_worker_thread+0x10/0x10
[ 5.011565] kthread+0xef/0x120
[ 5.011569] ? __pfx_kthread+0x10/0x10
[ 5.011572] ret_from_fork+0x44/0x70
[ 5.011574] ? __pfx_kthread+0x10/0x10
[ 5.011578] ret_from_fork_asm+0x1b/0x30
[ 5.011581] </TASK>
[ 5.011582] ---[ end trace 0000000000000000 ]---
* The Jammy version of the patch (5.15) does not need the re-
introduction of the DMA_FENCE_WARN macro since it already exist.
[Original Description]
I made simple Ubuntu 24.04 LTS Server installations as guests in an up-to-date Proxmox. No Xorg/Wayland, just CLI! The virtual graphics card is qml, 16 MiB memory (standard settings). Opening the console in the Proxmox GUI, or via remote-viewer initially is fine. However, after some time (usually: hours), the console just locks up. However, SSH into the guest machine remains fine.
Ubuntu 22.04, or 20.04 are fine, the issue only occurs with the new
Ubuntu 24.04. The issue is reproducible with all Ubuntu 24.04 VMs. A
reboot the the VM makes the console usable again, until the issue
occurs again (usually after some hours).
Unusual observation from dmesg:
...
[522890.748557] [TTM] Buffer eviction failed
[522890.748981] qxl 0000:00:01.0: object_init failed for (4096, 0x00000001)
[522890.749336] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO
[522906.108616] [TTM] Buffer eviction failed
[522906.109045] qxl 0000:00:01.0: object_init failed for (4096, 0x00000001)
[522906.109386] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO
[522921.468729] [TTM] Buffer eviction failed
[522921.469154] qxl 0000:00:01.0: object_init failed for (4096, 0x00000001)
[522921.469512] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO
[522936.828783] [TTM] Buffer eviction failed
[522936.829207] qxl 0000:00:01.0: object_init failed for (4096, 0x00000001)
[522936.829630] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO
...
nornetpp@hansa:~$ uname -a
Linux hansa.management.crnalab.net 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
nornetpp@hansa:~$ lsmod | grep qxl
qxl 86016 0
drm_ttm_helper 12288 1 qxl
ttm 110592 2 qxl,drm_ttm_helper
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed May 8 11:05:07 2024
InstallationDate: Installed on 2024-03-12 (57 days ago)
InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily amd64 (20240312)
ProcEnviron:
LANG=en_IE.UTF-8
LANGUAGE=nb:de:en_US
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065153/+subscriptions
Installing and pointing GRUB to it can be another temporary fix.
I found an interesting thread in the Proxmox forum (
https://forum.proxmox.com/threads/ttm-buffer-eviction-failed.152720 )
that contains the following sentence:
"...the bug was introduced in the upstream linux kernel over 3 years ago
through simplification of the kvm/qemu QXL guest video driver and has
propagated from there. The bug was removed briefly by reverting the
prior change (via the upstream linux kernel, but pulled into the kernel
of many distros, e.g. 6.8.0-38 and -39 in Ubuntu and derivatives) before
being re-introduced because the developer said the reverted,
unsimplified code caused crashes in their testing environments..."
Thus:
- versions 6.8.0-38 and -39 in Ubuntu and derivatives do not contain the bug
- what the developer said when he knowingly reintroduced the bug explains well why the fix is so long overdue and why it will not likely materialize anytime soon
As explained in my first post here, I have an Ubuntu 24.04 VPS server under Openstack with this bug, cannot switch to Virtio, neither can increase the VRAM, because my VPS provider does not allow me to do so.
So I tried the following:
0- took a snapshot of my VPS, just in case
1- installed kernel 6.8.0-39, which is compatible with Ubuntu 24.04:
apt-get install linux-image-6.8.0-39-generic
2- marked this kernel as 'hold':
apt-mark hold linux-image-6.8.0-39-generic
3- changed GRUB conf file to point by default to this kernel:
nano /etc/default/grub; edited the GRUB_DEFAULT=... line as follows
(in my server, it could be different in yours; check the 'menuentry' and 'submenu' lines in your /boot/grub/grub.cfg to find out):
commented the current GRUB_DEFAULT line, and added:
GRUB_DEFAULT="Advanced options for Ubuntu>Ubuntu, with Linux
6.8.0-39-generic"
saved
4- updated GRUB:
update-grub
5- rebooted
6- checked:
uname -r
expected output: 6.8.0-39-generic
Since then, now for several weeks, I have never received the "Buffer
eviction failed" error, nor have I had malfunctions with the QXL/Spice
console nor any other problems, whereas with other kernels I had to
reboot every couple of days.
Installing a superseded kernel is obviously not a proper solution of our
problem but it could be a useful temporary fix for those who cannot
switch from QXL/Spice to other virtual consoles or go 'headless' or
downgrade to Ubuntu 22.04.
Reverting the temporary fix is straightforward:
1. revert changes in /etc/default/grub
2. update-grub
3. reboot
4. uname -r
(5. apt-mark unhold linux-image-6.8.0-39-generic)
Hope this helps.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2065153
Title:
[qxl] Ubuntu 24.04 VM guest console freezes after some hours
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Confirmed
Status in linux source package in Noble:
Confirmed
Bug description:
Thank you @dreibh for reporting the original description and reporting
the bug!
[ Impact ]
* The qxl driver currently has a bug that causes console freezes on qxl paravirtualized GPUs. This issue does not cause a full system hang since the system is still accessible via other means such as SSH, but it does cause the virtual console output to hang. The following dmesg output is seen when the issue occurs:
[ 280.618452] [TTM] Buffer eviction failed
[ 280.618463] qxl 0000:00:01.0: object_init failed for (3149824, 0x00000001)
[ 280.618466] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO
* The issue was caused by commit: (5a838e5d5825 "drm/qxl: simplify qxl_fence_wait") Which does not add any new code but tries to simplify the already existing function.
This commit due to the problems it has caused, has been reverted upstream with: 07ed11afb68d Revert ("drm/qxl: simplify qxl_fence_wait"). The commit also adds back the DMA_FENCE_WARN macro due to it's usage in the reverted functions. The macro was originally removed with: d72277b6c37d ("dma-buf: nuke DMA_FENCE_TRACE macros v2").
[ Test Plan ]
To Reproduce the bug follow the below steps:
1. Install a Ubuntu version with an affected kernel in a VM and make
sure that the QXL video driver is in use instead of virtio. The server
edition is enough for the reproducer no need for a DE to be installed.
The issue is reproducible on Jammy 5.15 and above except Plucky since
the fix is included in kernel 6.14.
2. Create a script and make it executable with the following content:
```
#!/bin/bash
chvt 3
for j in $(seq 80); do
echo "$(date) starting round $j"
if [ "$(journalctl --boot | grep "failed to allocate VRAM BO")" != "" ];
then
echo "bug was reproduced after $j tries"
exit 1
fi
for i in $(seq 100); do
dmesg > /dev/tty3
done
done
echo "bug could not be reproduced"
exit 0
```
3. Execute the script from the virtual console and from an SSH session, monitor the dmesg logs until you see the following:
[ 280.618452] [TTM] Buffer eviction failed
[ 280.618463] qxl 0000:00:01.0: object_init failed for (3149824, 0x00000001)
[ 280.618466] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO
[ Where problems could occur ]
* Virtual displays might still freeze or hang
* Warning messages related to the qxl driver might occur.
[ Other Info]
* The patch does cause a warning message to show up on boot when using
the qxl video driver. The warning itself is harmless and does not seem
to have any negative effects in my testing:
[ 5.011445] WARNING: CPU: 15 PID: 822 at kernel/workqueue.c:2985 check_flush_dependency.part.0+0xde/0x140
[ 5.011449] Modules linked in: qrtr cfg80211 binfmt_misc intel_rapl_msr intel_rapl_common intel_uncore_frequency_common intel_pmc_core intel_vsec pmt_telemetry pmt_class kvm_intel kvm snd_hda_codec_generic irqbypass snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi rapl snd_hda_codec snd_hda_core snd_hwdep snd_pcm joydev snd_timer snd qxl i2c_i801 soundcore drm_ttm_helper i2c_smbus lpc_ich ttm input_leds mac_hid serio_raw sch_fq_codel dm_multipath msr efi_pstore nfnetlink dmi_sysfs qemu_fw_cfg ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 hid_generic usbhid hid crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel sha256_ssse3 ahci sha1_ssse3 libahci psmouse virtio_rng xhci_pci xhci_pci_renesas aesni_intel crypto_simd cryptd
[ 5.011493] CPU: 15 PID: 822 Comm: kworker/u65:1 Not tainted 6.8.0-999-generic #70
[ 5.011495] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[ 5.011496] Workqueue: ttm ttm_bo_delayed_delete [ttm]
[ 5.011501] RIP: 0010:check_flush_dependency.part.0+0xde/0x140
[ 5.011502] Code: 24 18 4d 89 f0 49 8d 8d b0 00 00 00 48 c7 c7 e0 8f e6 8a c6 05 f3 90 8c 02 01 48 8b 70 08 48 81 c6 b0 00 00 00 e8 a2 5e fd ff <0f> 0b eb 91 0f b6 1d d9 90 8c 02 80 fb 01 0f 87 38 57 0a 01 83 e3
[ 5.011503] RSP: 0018:ffffbd85c0ce7c28 EFLAGS: 00010046
[ 5.011505] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
[ 5.011506] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 5.011506] RBP: ffffbd85c0ce7c48 R08: 0000000000000000 R09: 0000000000000000
[ 5.011507] R10: 0000000000000000 R11: 0000000000000000 R12: ffff9f308158a540
[ 5.011508] R13: ffff9f30801cea00 R14: ffffffffc0946570 R15: 0000000000000000
[ 5.011509] FS: 0000000000000000(0000) GS:ffff9f31f7d80000(0000) knlGS:0000000000000000
[ 5.011510] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 5.011510] CR2: 000000c000a02000 CR3: 0000000108cf8000 CR4: 0000000000750ef0
[ 5.011514] PKRU: 55555554
[ 5.011514] Call Trace:
[ 5.011516] <TASK>
[ 5.011518] ? show_regs+0x6d/0x80
[ 5.011521] ? __warn+0x89/0x160
[ 5.011523] ? check_flush_dependency.part.0+0xde/0x140
[ 5.011524] ? report_bug+0x17e/0x1b0
[ 5.011527] ? handle_bug+0x6e/0xb0
[ 5.011529] ? exc_invalid_op+0x18/0x80
[ 5.011532] ? asm_exc_invalid_op+0x1b/0x20
[ 5.011535] ? __pfx_qxl_gc_work+0x10/0x10 [qxl]
[ 5.011539] ? check_flush_dependency.part.0+0xde/0x140
[ 5.011540] ? check_flush_dependency.part.0+0xde/0x140
[ 5.011541] start_flush_work+0xba/0x340
[ 5.011543] flush_work+0x5f/0xb0
[ 5.011545] qxl_queue_garbage_collect+0x8c/0x90 [qxl]
[ 5.011548] qxl_fence_wait+0xa3/0x1b0 [qxl]
[ 5.011552] dma_fence_wait_timeout+0x64/0x140
[ 5.011555] dma_resv_wait_timeout+0x7f/0xf0
[ 5.011556] ttm_bo_delayed_delete+0x2a/0xc0 [ttm]
[ 5.011560] process_one_work+0x181/0x3a0
[ 5.011562] worker_thread+0x306/0x440
[ 5.011563] ? __pfx_worker_thread+0x10/0x10
[ 5.011565] kthread+0xef/0x120
[ 5.011569] ? __pfx_kthread+0x10/0x10
[ 5.011572] ret_from_fork+0x44/0x70
[ 5.011574] ? __pfx_kthread+0x10/0x10
[ 5.011578] ret_from_fork_asm+0x1b/0x30
[ 5.011581] </TASK>
[ 5.011582] ---[ end trace 0000000000000000 ]---
* The Jammy version of the patch (5.15) does not need the re-
introduction of the DMA_FENCE_WARN macro since it already exist.
[Original Description]
I made simple Ubuntu 24.04 LTS Server installations as guests in an up-to-date Proxmox. No Xorg/Wayland, just CLI! The virtual graphics card is qml, 16 MiB memory (standard settings). Opening the console in the Proxmox GUI, or via remote-viewer initially is fine. However, after some time (usually: hours), the console just locks up. However, SSH into the guest machine remains fine.
Ubuntu 22.04, or 20.04 are fine, the issue only occurs with the new
Ubuntu 24.04. The issue is reproducible with all Ubuntu 24.04 VMs. A
reboot the the VM makes the console usable again, until the issue
occurs again (usually after some hours).
Unusual observation from dmesg:
...
[522890.748557] [TTM] Buffer eviction failed
[522890.748981] qxl 0000:00:01.0: object_init failed for (4096, 0x00000001)
[522890.749336] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO
[522906.108616] [TTM] Buffer eviction failed
[522906.109045] qxl 0000:00:01.0: object_init failed for (4096, 0x00000001)
[522906.109386] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO
[522921.468729] [TTM] Buffer eviction failed
[522921.469154] qxl 0000:00:01.0: object_init failed for (4096, 0x00000001)
[522921.469512] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO
[522936.828783] [TTM] Buffer eviction failed
[522936.829207] qxl 0000:00:01.0: object_init failed for (4096, 0x00000001)
[522936.829630] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO
...
nornetpp@hansa:~$ uname -a
Linux hansa.management.crnalab.net 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
nornetpp@hansa:~$ lsmod | grep qxl
qxl 86016 0
drm_ttm_helper 12288 1 qxl
ttm 110592 2 qxl,drm_ttm_helper
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed May 8 11:05:07 2024
InstallationDate: Installed on 2024-03-12 (57 days ago)
InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily amd64 (20240312)
ProcEnviron:
LANG=en_IE.UTF-8
LANGUAGE=nb:de:en_US
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065153/+subscriptions
[Bug 2142010] Re: Freezing pc after ubuntu 25.10 upgrade
Almost identical situation here. I have narrowed it down to the Dart
Code VSCode extension. Are you by any chance using it as well?
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142010
Title:
Freezing pc after ubuntu 25.10 upgrade
Status in linux package in Ubuntu:
Confirmed
Bug description:
After upgrading to Ubuntu 25.10 the system freezes during heavy usage
(VS Code, browser, AI tools). The laptop heats up before freezing and
requires hard shutdown. Logs show amdgpu LOAD_TA failure. Issue did
not exist before upgrade.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-14-generic 6.17.0-14.14
ProcVersionSignature: Ubuntu 6.17.0-14.14-generic 6.17.9
Uname: Linux 6.17.0-14-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: cephas-anane 38378 F.... wireplumber
/dev/snd/controlC0: cephas-anane 38378 F.... wireplumber
/dev/snd/seq: cephas-anane 38361 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 17 11:12:05 2026
InstallationDate: Installed on 2025-10-10 (130 days ago)
InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
MachineType: LENOVO 20NMS2QR00
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-14-generic root=UUID=19e221de-c3bd-42b5-a82d-3e64a430cc02 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: Upgraded to questing on 2026-02-10 (7 days ago)
dmi.bios.date: 03/01/2024
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: R13ET56W(1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20NMS2QR00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.30
dmi.modalias: dmi:bvnLENOVO:bvrR13ET56W(1.30):bd03/01/2024:br1.30:efr1.30:svnLENOVO:pn20NMS2QR00:pvrThinkPadX395:rvnLENOVO:rn20NMS2QR00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NM_BU_Think_FM_ThinkPadX395:
dmi.product.family: ThinkPad X395
dmi.product.name: 20NMS2QR00
dmi.product.sku: LENOVO_MT_20NM_BU_Think_FM_ThinkPad X395
dmi.product.version: ThinkPad X395
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142010/+subscriptions
Code VSCode extension. Are you by any chance using it as well?
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142010
Title:
Freezing pc after ubuntu 25.10 upgrade
Status in linux package in Ubuntu:
Confirmed
Bug description:
After upgrading to Ubuntu 25.10 the system freezes during heavy usage
(VS Code, browser, AI tools). The laptop heats up before freezing and
requires hard shutdown. Logs show amdgpu LOAD_TA failure. Issue did
not exist before upgrade.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-14-generic 6.17.0-14.14
ProcVersionSignature: Ubuntu 6.17.0-14.14-generic 6.17.9
Uname: Linux 6.17.0-14-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: cephas-anane 38378 F.... wireplumber
/dev/snd/controlC0: cephas-anane 38378 F.... wireplumber
/dev/snd/seq: cephas-anane 38361 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 17 11:12:05 2026
InstallationDate: Installed on 2025-10-10 (130 days ago)
InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
MachineType: LENOVO 20NMS2QR00
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-14-generic root=UUID=19e221de-c3bd-42b5-a82d-3e64a430cc02 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: Upgraded to questing on 2026-02-10 (7 days ago)
dmi.bios.date: 03/01/2024
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: R13ET56W(1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20NMS2QR00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.30
dmi.modalias: dmi:bvnLENOVO:bvrR13ET56W(1.30):bd03/01/2024:br1.30:efr1.30:svnLENOVO:pn20NMS2QR00:pvrThinkPadX395:rvnLENOVO:rn20NMS2QR00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NM_BU_Think_FM_ThinkPadX395:
dmi.product.family: ThinkPad X395
dmi.product.name: 20NMS2QR00
dmi.product.sku: LENOVO_MT_20NM_BU_Think_FM_ThinkPad X395
dmi.product.version: ThinkPad X395
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142010/+subscriptions
Подписаться на:
Комментарии (Atom)