- 1Password (22,000+ AppArmor denials)
- Telegram Desktop (3,400+ denials)
- Rider IDE (73 denials)
- Snap Store (50 denials)
- Thunderbird (4 denials)
--
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:
Confirmed
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 2141531] Re: Network unstable on 6.8.0-100.100
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Noble)
Status: New => Fix Committed
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141531
Title:
Network unstable on 6.8.0-100.100
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Fix Committed
Bug description:
Ever since this upgrade was installed the network has been unstable.
Doing network speed tests the uploads almost always fail, often quoted
a socket error.
6.8.0-94 works fine. A DFNS check worked fine, but fails on -100.
Another windows PC on the same network works fine. ISP says all is
good.
I am on Ubuntu 24.04.3 LTS
I have reported via ubuntu-bug linux, which I had to rune twice due to network issues, but I think it still failed:
[6807:6882:0211/091954.614735:ERROR:chromium/crypto/nss_util.cc:346] After loading Root Certs, loaded==false: NSS error code: -8018
[6807:6841:0211/091959.425462:ERROR:chromium/google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
Fontconfig error: Cannot load default config file: File not found
[6807:6841:0211/092019.885790:ERROR:chromium/google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
[6807:6841:0211/092102.440061:ERROR:chromium/google_apis/gcm/engine/registration_request.cc:275] Registration URL fetching failed.
[6807:6841:0211/092250.190043:ERROR:chromium/google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-100-generic 6.8.0-100.100
ProcVersionSignature: Ubuntu 6.8.0-100.100-generic 6.8.12
Uname: Linux 6.8.0-100-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: crusty 3495 F.... wireplumber
/dev/snd/controlC0: crusty 3495 F.... wireplumber
/dev/snd/seq: crusty 3492 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 11 09:19:27 2026
InstallationDate: Installed on 2023-10-03 (862 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2)
MachineType: Simply NUC CBM2r6RB
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-100-generic root=UUID=06468786-eea9-495d-a09b-030c5866af52 ro quiet splash fsck.mode=force fsck.repair=yes loglevel=3 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-100-generic N/A
linux-backports-modules-6.8.0-100-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.23
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2024-09-02 (527 days ago)
dmi.bios.date: 05/17/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: P1.30A
dmi.board.name: 4X4-5000 Series
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.30A:bd05/17/2022:br5.19:svnSimplyNUC:pnCBM2r6RB:pvrToBeFilledByO.E.M.:rvnASRock:rn4X4-5000Series:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: CBM2r6RB
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: Simply NUC
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141531/+subscriptions
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Noble)
Status: New => Fix Committed
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141531
Title:
Network unstable on 6.8.0-100.100
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Fix Committed
Bug description:
Ever since this upgrade was installed the network has been unstable.
Doing network speed tests the uploads almost always fail, often quoted
a socket error.
6.8.0-94 works fine. A DFNS check worked fine, but fails on -100.
Another windows PC on the same network works fine. ISP says all is
good.
I am on Ubuntu 24.04.3 LTS
I have reported via ubuntu-bug linux, which I had to rune twice due to network issues, but I think it still failed:
[6807:6882:0211/091954.614735:ERROR:chromium/crypto/nss_util.cc:346] After loading Root Certs, loaded==false: NSS error code: -8018
[6807:6841:0211/091959.425462:ERROR:chromium/google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
Fontconfig error: Cannot load default config file: File not found
[6807:6841:0211/092019.885790:ERROR:chromium/google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
[6807:6841:0211/092102.440061:ERROR:chromium/google_apis/gcm/engine/registration_request.cc:275] Registration URL fetching failed.
[6807:6841:0211/092250.190043:ERROR:chromium/google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-100-generic 6.8.0-100.100
ProcVersionSignature: Ubuntu 6.8.0-100.100-generic 6.8.12
Uname: Linux 6.8.0-100-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: crusty 3495 F.... wireplumber
/dev/snd/controlC0: crusty 3495 F.... wireplumber
/dev/snd/seq: crusty 3492 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 11 09:19:27 2026
InstallationDate: Installed on 2023-10-03 (862 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2)
MachineType: Simply NUC CBM2r6RB
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-100-generic root=UUID=06468786-eea9-495d-a09b-030c5866af52 ro quiet splash fsck.mode=force fsck.repair=yes loglevel=3 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-100-generic N/A
linux-backports-modules-6.8.0-100-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.23
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2024-09-02 (527 days ago)
dmi.bios.date: 05/17/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: P1.30A
dmi.board.name: 4X4-5000 Series
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.30A:bd05/17/2022:br5.19:svnSimplyNUC:pnCBM2r6RB:pvrToBeFilledByO.E.M.:rvnASRock:rn4X4-5000Series:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: CBM2r6RB
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: Simply NUC
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141531/+subscriptions
[Bug 2141880] [NEW] Please enable CONFIG_RCU_LAZY
Public bug reported:
Please enable CONFIG_RCU_LAZY=y and CONFIG_RCU_LAZY_DEFAULT_OFF=y in
Ubuntu RT kernels.
CONFIG_RCU_LAZY allows (but doesn't require) us to delay RCU grace
period start by 10s or so when the system is idle in order to conserve
battery power. GP start is expedited when system load appears. Android
uses CONFIG_RCU_LAZY, combined with full RCU offload, to avoid
unnecessary wakeups under load and saves about 10-15% power in the idle
static-image-display scenario. I'd like to use lazy RCU on my laptop for
the same reason. While the regular Ubuntu kernel enables
CONFIG_RCU_LAZY, the RT kernel does not.
With CONFIG_RCU_LAZY_DEFAULT_OFF=y, kernel defaults to disabling lazy
RCU, resulting in no change of RT kernel relative to today.
** 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/2141880
Title:
Please enable CONFIG_RCU_LAZY
Status in linux package in Ubuntu:
New
Bug description:
Please enable CONFIG_RCU_LAZY=y and CONFIG_RCU_LAZY_DEFAULT_OFF=y in
Ubuntu RT kernels.
CONFIG_RCU_LAZY allows (but doesn't require) us to delay RCU grace
period start by 10s or so when the system is idle in order to conserve
battery power. GP start is expedited when system load appears. Android
uses CONFIG_RCU_LAZY, combined with full RCU offload, to avoid
unnecessary wakeups under load and saves about 10-15% power in the
idle static-image-display scenario. I'd like to use lazy RCU on my
laptop for the same reason. While the regular Ubuntu kernel enables
CONFIG_RCU_LAZY, the RT kernel does not.
With CONFIG_RCU_LAZY_DEFAULT_OFF=y, kernel defaults to disabling lazy
RCU, resulting in no change of RT kernel relative to today.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141880/+subscriptions
Please enable CONFIG_RCU_LAZY=y and CONFIG_RCU_LAZY_DEFAULT_OFF=y in
Ubuntu RT kernels.
CONFIG_RCU_LAZY allows (but doesn't require) us to delay RCU grace
period start by 10s or so when the system is idle in order to conserve
battery power. GP start is expedited when system load appears. Android
uses CONFIG_RCU_LAZY, combined with full RCU offload, to avoid
unnecessary wakeups under load and saves about 10-15% power in the idle
static-image-display scenario. I'd like to use lazy RCU on my laptop for
the same reason. While the regular Ubuntu kernel enables
CONFIG_RCU_LAZY, the RT kernel does not.
With CONFIG_RCU_LAZY_DEFAULT_OFF=y, kernel defaults to disabling lazy
RCU, resulting in no change of RT kernel relative to today.
** 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/2141880
Title:
Please enable CONFIG_RCU_LAZY
Status in linux package in Ubuntu:
New
Bug description:
Please enable CONFIG_RCU_LAZY=y and CONFIG_RCU_LAZY_DEFAULT_OFF=y in
Ubuntu RT kernels.
CONFIG_RCU_LAZY allows (but doesn't require) us to delay RCU grace
period start by 10s or so when the system is idle in order to conserve
battery power. GP start is expedited when system load appears. Android
uses CONFIG_RCU_LAZY, combined with full RCU offload, to avoid
unnecessary wakeups under load and saves about 10-15% power in the
idle static-image-display scenario. I'd like to use lazy RCU on my
laptop for the same reason. While the regular Ubuntu kernel enables
CONFIG_RCU_LAZY, the RT kernel does not.
With CONFIG_RCU_LAZY_DEFAULT_OFF=y, kernel defaults to disabling lazy
RCU, resulting in no change of RT kernel relative to today.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141880/+subscriptions
[Bug 2141298] Re: AppArmor blocks write(2) to network sockets with Linux 6.19
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2141716
It is related I think.
--
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:
Confirmed
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
It is related I think.
--
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:
Confirmed
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 2141723] Re: microphone silent with snd_soc_avs
** Description changed:
Something caused `blacklist snd_soc_avs` to be required on
6.17.0-14-generic. 6.17.0-12-generic was working as it had
`snd_hda_intel`.
From https://askubuntu.com/q/1563887/1004020 and
https://forums.linuxmint.com/viewtopic.php?t=463122 .
1) cat /proc/version_signature
Ubuntu 6.17.0-14.14-generic 6.17.9
2) sudo lspci -vnvn | grep snd
- Kernel driver in use: snd_hda_intel (after blacklisting snd_soc_avs)
+ Kernel driver in use: snd_hda_intel (even if snd_soc_avs is not
+ blacklisted)
1) The release of Ubuntu [they] are using
Kubuntu 25.10
2) The version of the package [they] are using
Bad version: 6.17.0-14-generic
Good version: 6.17.0-12-generic
3) What you expected to happen
The microphone should always work in Chrome, Firefox, and Brave.
4) What happened instead
> During calls, people cannot hear me. I can hear them perfectly. Sometimes browser shows "Mic not found". Happens with and without headphones. Restarting PipeWire sometimes temporarily fixes it.
> Hardware appears functional. ALSA layer is functional. [comment: probably config not data worked] PipeWire source node exists. Browser does not create capture stream. Restarting services sometimes restores mic temporarily.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141723
Title:
microphone silent with snd_soc_avs
Status in linux package in Ubuntu:
Confirmed
Bug description:
Something caused `blacklist snd_soc_avs` to be required on
6.17.0-14-generic. 6.17.0-12-generic was working as it had
`snd_hda_intel`.
From https://askubuntu.com/q/1563887/1004020 and
https://forums.linuxmint.com/viewtopic.php?t=463122 .
1) cat /proc/version_signature
Ubuntu 6.17.0-14.14-generic 6.17.9
2) sudo lspci -vnvn | grep snd
Kernel driver in use: snd_hda_intel (even if snd_soc_avs is not
blacklisted)
1) The release of Ubuntu [they] are using
Kubuntu 25.10
2) The version of the package [they] are using
Bad version: 6.17.0-14-generic
Good version: 6.17.0-12-generic
3) What you expected to happen
The microphone should always work in Chrome, Firefox, and Brave.
4) What happened instead
> During calls, people cannot hear me. I can hear them perfectly. Sometimes browser shows "Mic not found". Happens with and without headphones. Restarting PipeWire sometimes temporarily fixes it.
> Hardware appears functional. ALSA layer is functional. [comment: probably config not data worked] PipeWire source node exists. Browser does not create capture stream. Restarting services sometimes restores mic temporarily.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141723/+subscriptions
Something caused `blacklist snd_soc_avs` to be required on
6.17.0-14-generic. 6.17.0-12-generic was working as it had
`snd_hda_intel`.
From https://askubuntu.com/q/1563887/1004020 and
https://forums.linuxmint.com/viewtopic.php?t=463122 .
1) cat /proc/version_signature
Ubuntu 6.17.0-14.14-generic 6.17.9
2) sudo lspci -vnvn | grep snd
- Kernel driver in use: snd_hda_intel (after blacklisting snd_soc_avs)
+ Kernel driver in use: snd_hda_intel (even if snd_soc_avs is not
+ blacklisted)
1) The release of Ubuntu [they] are using
Kubuntu 25.10
2) The version of the package [they] are using
Bad version: 6.17.0-14-generic
Good version: 6.17.0-12-generic
3) What you expected to happen
The microphone should always work in Chrome, Firefox, and Brave.
4) What happened instead
> During calls, people cannot hear me. I can hear them perfectly. Sometimes browser shows "Mic not found". Happens with and without headphones. Restarting PipeWire sometimes temporarily fixes it.
> Hardware appears functional. ALSA layer is functional. [comment: probably config not data worked] PipeWire source node exists. Browser does not create capture stream. Restarting services sometimes restores mic temporarily.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141723
Title:
microphone silent with snd_soc_avs
Status in linux package in Ubuntu:
Confirmed
Bug description:
Something caused `blacklist snd_soc_avs` to be required on
6.17.0-14-generic. 6.17.0-12-generic was working as it had
`snd_hda_intel`.
From https://askubuntu.com/q/1563887/1004020 and
https://forums.linuxmint.com/viewtopic.php?t=463122 .
1) cat /proc/version_signature
Ubuntu 6.17.0-14.14-generic 6.17.9
2) sudo lspci -vnvn | grep snd
Kernel driver in use: snd_hda_intel (even if snd_soc_avs is not
blacklisted)
1) The release of Ubuntu [they] are using
Kubuntu 25.10
2) The version of the package [they] are using
Bad version: 6.17.0-14-generic
Good version: 6.17.0-12-generic
3) What you expected to happen
The microphone should always work in Chrome, Firefox, and Brave.
4) What happened instead
> During calls, people cannot hear me. I can hear them perfectly. Sometimes browser shows "Mic not found". Happens with and without headphones. Restarting PipeWire sometimes temporarily fixes it.
> Hardware appears functional. ALSA layer is functional. [comment: probably config not data worked] PipeWire source node exists. Browser does not create capture stream. Restarting services sometimes restores mic temporarily.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141723/+subscriptions
[Bug 2141723] Re: microphone silent with snd_soc_avs
I can reproduce this issue in Kubuntu 25.10 (questing) under Wayland (if
that matters?). The issue started when updating from linux-
image-6.17.0-12-generic to linux-image-6.17.0-14-generic. Under linux-
image-6.17.0-14-generic it goes away when I blacklist the driver
snd_soc_avs.
** Description changed:
Something caused `blacklist snd_soc_avs` to be required on
6.17.0-14-generic. 6.17.0-12-generic was working as it had
`snd_hda_intel`.
From https://askubuntu.com/q/1563887/1004020 and
https://forums.linuxmint.com/viewtopic.php?t=463122 .
1) cat /proc/version_signature
- Not my computer
+ Ubuntu 6.17.0-14.14-generic 6.17.9
- 2) sudo lspci -vnvn
+ 2) sudo lspci -vnvn | grep snd
- Not my computer
+ Kernel driver in use: snd_hda_intel after blacklisting snd_soc_avs.
1) The release of Ubuntu [they] are using
- Unknown whether 24.04 or 25.10.
+ Kubuntu 25.10.
2) The version of the package [they] are using
Bad version: 6.17.0-14-generic
Good version: 6.17.0-12-generic
3) What you expected to happen
The microphone should always work in Chrome, Firefox, and Brave.
4) What happened instead
> During calls, people cannot hear me. I can hear them perfectly. Sometimes browser shows "Mic not found". Happens with and without headphones. Restarting PipeWire sometimes temporarily fixes it.
> Hardware appears functional. ALSA layer is functional. [comment: probably config not data worked] PipeWire source node exists. Browser does not create capture stream. Restarting services sometimes restores mic temporarily.
** Description changed:
Something caused `blacklist snd_soc_avs` to be required on
6.17.0-14-generic. 6.17.0-12-generic was working as it had
`snd_hda_intel`.
From https://askubuntu.com/q/1563887/1004020 and
https://forums.linuxmint.com/viewtopic.php?t=463122 .
1) cat /proc/version_signature
Ubuntu 6.17.0-14.14-generic 6.17.9
2) sudo lspci -vnvn | grep snd
- Kernel driver in use: snd_hda_intel after blacklisting snd_soc_avs.
+ Kernel driver in use: snd_hda_intel (after blacklisting snd_soc_avs)
1) The release of Ubuntu [they] are using
Kubuntu 25.10.
2) The version of the package [they] are using
Bad version: 6.17.0-14-generic
Good version: 6.17.0-12-generic
3) What you expected to happen
The microphone should always work in Chrome, Firefox, and Brave.
4) What happened instead
> During calls, people cannot hear me. I can hear them perfectly. Sometimes browser shows "Mic not found". Happens with and without headphones. Restarting PipeWire sometimes temporarily fixes it.
> Hardware appears functional. ALSA layer is functional. [comment: probably config not data worked] PipeWire source node exists. Browser does not create capture stream. Restarting services sometimes restores mic temporarily.
** Description changed:
Something caused `blacklist snd_soc_avs` to be required on
6.17.0-14-generic. 6.17.0-12-generic was working as it had
`snd_hda_intel`.
From https://askubuntu.com/q/1563887/1004020 and
https://forums.linuxmint.com/viewtopic.php?t=463122 .
1) cat /proc/version_signature
Ubuntu 6.17.0-14.14-generic 6.17.9
2) sudo lspci -vnvn | grep snd
Kernel driver in use: snd_hda_intel (after blacklisting snd_soc_avs)
1) The release of Ubuntu [they] are using
- Kubuntu 25.10.
+ Kubuntu 25.10
2) The version of the package [they] are using
Bad version: 6.17.0-14-generic
Good version: 6.17.0-12-generic
3) What you expected to happen
The microphone should always work in Chrome, Firefox, and Brave.
4) What happened instead
> During calls, people cannot hear me. I can hear them perfectly. Sometimes browser shows "Mic not found". Happens with and without headphones. Restarting PipeWire sometimes temporarily fixes it.
> Hardware appears functional. ALSA layer is functional. [comment: probably config not data worked] PipeWire source node exists. Browser does not create capture stream. Restarting services sometimes restores mic temporarily.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141723
Title:
microphone silent with snd_soc_avs
Status in linux package in Ubuntu:
Confirmed
Bug description:
Something caused `blacklist snd_soc_avs` to be required on
6.17.0-14-generic. 6.17.0-12-generic was working as it had
`snd_hda_intel`.
From https://askubuntu.com/q/1563887/1004020 and
https://forums.linuxmint.com/viewtopic.php?t=463122 .
1) cat /proc/version_signature
Ubuntu 6.17.0-14.14-generic 6.17.9
2) sudo lspci -vnvn | grep snd
Kernel driver in use: snd_hda_intel (after blacklisting snd_soc_avs)
1) The release of Ubuntu [they] are using
Kubuntu 25.10
2) The version of the package [they] are using
Bad version: 6.17.0-14-generic
Good version: 6.17.0-12-generic
3) What you expected to happen
The microphone should always work in Chrome, Firefox, and Brave.
4) What happened instead
> During calls, people cannot hear me. I can hear them perfectly. Sometimes browser shows "Mic not found". Happens with and without headphones. Restarting PipeWire sometimes temporarily fixes it.
> Hardware appears functional. ALSA layer is functional. [comment: probably config not data worked] PipeWire source node exists. Browser does not create capture stream. Restarting services sometimes restores mic temporarily.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141723/+subscriptions
that matters?). The issue started when updating from linux-
image-6.17.0-12-generic to linux-image-6.17.0-14-generic. Under linux-
image-6.17.0-14-generic it goes away when I blacklist the driver
snd_soc_avs.
** Description changed:
Something caused `blacklist snd_soc_avs` to be required on
6.17.0-14-generic. 6.17.0-12-generic was working as it had
`snd_hda_intel`.
From https://askubuntu.com/q/1563887/1004020 and
https://forums.linuxmint.com/viewtopic.php?t=463122 .
1) cat /proc/version_signature
- Not my computer
+ Ubuntu 6.17.0-14.14-generic 6.17.9
- 2) sudo lspci -vnvn
+ 2) sudo lspci -vnvn | grep snd
- Not my computer
+ Kernel driver in use: snd_hda_intel after blacklisting snd_soc_avs.
1) The release of Ubuntu [they] are using
- Unknown whether 24.04 or 25.10.
+ Kubuntu 25.10.
2) The version of the package [they] are using
Bad version: 6.17.0-14-generic
Good version: 6.17.0-12-generic
3) What you expected to happen
The microphone should always work in Chrome, Firefox, and Brave.
4) What happened instead
> During calls, people cannot hear me. I can hear them perfectly. Sometimes browser shows "Mic not found". Happens with and without headphones. Restarting PipeWire sometimes temporarily fixes it.
> Hardware appears functional. ALSA layer is functional. [comment: probably config not data worked] PipeWire source node exists. Browser does not create capture stream. Restarting services sometimes restores mic temporarily.
** Description changed:
Something caused `blacklist snd_soc_avs` to be required on
6.17.0-14-generic. 6.17.0-12-generic was working as it had
`snd_hda_intel`.
From https://askubuntu.com/q/1563887/1004020 and
https://forums.linuxmint.com/viewtopic.php?t=463122 .
1) cat /proc/version_signature
Ubuntu 6.17.0-14.14-generic 6.17.9
2) sudo lspci -vnvn | grep snd
- Kernel driver in use: snd_hda_intel after blacklisting snd_soc_avs.
+ Kernel driver in use: snd_hda_intel (after blacklisting snd_soc_avs)
1) The release of Ubuntu [they] are using
Kubuntu 25.10.
2) The version of the package [they] are using
Bad version: 6.17.0-14-generic
Good version: 6.17.0-12-generic
3) What you expected to happen
The microphone should always work in Chrome, Firefox, and Brave.
4) What happened instead
> During calls, people cannot hear me. I can hear them perfectly. Sometimes browser shows "Mic not found". Happens with and without headphones. Restarting PipeWire sometimes temporarily fixes it.
> Hardware appears functional. ALSA layer is functional. [comment: probably config not data worked] PipeWire source node exists. Browser does not create capture stream. Restarting services sometimes restores mic temporarily.
** Description changed:
Something caused `blacklist snd_soc_avs` to be required on
6.17.0-14-generic. 6.17.0-12-generic was working as it had
`snd_hda_intel`.
From https://askubuntu.com/q/1563887/1004020 and
https://forums.linuxmint.com/viewtopic.php?t=463122 .
1) cat /proc/version_signature
Ubuntu 6.17.0-14.14-generic 6.17.9
2) sudo lspci -vnvn | grep snd
Kernel driver in use: snd_hda_intel (after blacklisting snd_soc_avs)
1) The release of Ubuntu [they] are using
- Kubuntu 25.10.
+ Kubuntu 25.10
2) The version of the package [they] are using
Bad version: 6.17.0-14-generic
Good version: 6.17.0-12-generic
3) What you expected to happen
The microphone should always work in Chrome, Firefox, and Brave.
4) What happened instead
> During calls, people cannot hear me. I can hear them perfectly. Sometimes browser shows "Mic not found". Happens with and without headphones. Restarting PipeWire sometimes temporarily fixes it.
> Hardware appears functional. ALSA layer is functional. [comment: probably config not data worked] PipeWire source node exists. Browser does not create capture stream. Restarting services sometimes restores mic temporarily.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141723
Title:
microphone silent with snd_soc_avs
Status in linux package in Ubuntu:
Confirmed
Bug description:
Something caused `blacklist snd_soc_avs` to be required on
6.17.0-14-generic. 6.17.0-12-generic was working as it had
`snd_hda_intel`.
From https://askubuntu.com/q/1563887/1004020 and
https://forums.linuxmint.com/viewtopic.php?t=463122 .
1) cat /proc/version_signature
Ubuntu 6.17.0-14.14-generic 6.17.9
2) sudo lspci -vnvn | grep snd
Kernel driver in use: snd_hda_intel (after blacklisting snd_soc_avs)
1) The release of Ubuntu [they] are using
Kubuntu 25.10
2) The version of the package [they] are using
Bad version: 6.17.0-14-generic
Good version: 6.17.0-12-generic
3) What you expected to happen
The microphone should always work in Chrome, Firefox, and Brave.
4) What happened instead
> During calls, people cannot hear me. I can hear them perfectly. Sometimes browser shows "Mic not found". Happens with and without headphones. Restarting PipeWire sometimes temporarily fixes it.
> Hardware appears functional. ALSA layer is functional. [comment: probably config not data worked] PipeWire source node exists. Browser does not create capture stream. Restarting services sometimes restores mic temporarily.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141723/+subscriptions
[Bug 2141723] Re: microphone silent with snd_soc_avs
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141723
Title:
microphone silent with snd_soc_avs
Status in linux package in Ubuntu:
Confirmed
Bug description:
Something caused `blacklist snd_soc_avs` to be required on
6.17.0-14-generic. 6.17.0-12-generic was working as it had
`snd_hda_intel`.
From https://askubuntu.com/q/1563887/1004020 and
https://forums.linuxmint.com/viewtopic.php?t=463122 .
1) cat /proc/version_signature
Not my computer
2) sudo lspci -vnvn
Not my computer
1) The release of Ubuntu [they] are using
Unknown whether 24.04 or 25.10.
2) The version of the package [they] are using
Bad version: 6.17.0-14-generic
Good version: 6.17.0-12-generic
3) What you expected to happen
The microphone should always work in Chrome, Firefox, and Brave.
4) What happened instead
> During calls, people cannot hear me. I can hear them perfectly. Sometimes browser shows "Mic not found". Happens with and without headphones. Restarting PipeWire sometimes temporarily fixes it.
> Hardware appears functional. ALSA layer is functional. [comment: probably config not data worked] PipeWire source node exists. Browser does not create capture stream. Restarting services sometimes restores mic temporarily.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141723/+subscriptions
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141723
Title:
microphone silent with snd_soc_avs
Status in linux package in Ubuntu:
Confirmed
Bug description:
Something caused `blacklist snd_soc_avs` to be required on
6.17.0-14-generic. 6.17.0-12-generic was working as it had
`snd_hda_intel`.
From https://askubuntu.com/q/1563887/1004020 and
https://forums.linuxmint.com/viewtopic.php?t=463122 .
1) cat /proc/version_signature
Not my computer
2) sudo lspci -vnvn
Not my computer
1) The release of Ubuntu [they] are using
Unknown whether 24.04 or 25.10.
2) The version of the package [they] are using
Bad version: 6.17.0-14-generic
Good version: 6.17.0-12-generic
3) What you expected to happen
The microphone should always work in Chrome, Firefox, and Brave.
4) What happened instead
> During calls, people cannot hear me. I can hear them perfectly. Sometimes browser shows "Mic not found". Happens with and without headphones. Restarting PipeWire sometimes temporarily fixes it.
> Hardware appears functional. ALSA layer is functional. [comment: probably config not data worked] PipeWire source node exists. Browser does not create capture stream. Restarting services sometimes restores mic temporarily.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141723/+subscriptions
суббота
[Bug 2141216] Re: Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT (andgpu SMU resume failure)
Well that's unfortunate it doesn't crash in a way the crash kernel
works.
I think you'll have to wait for someone from the canonical kernel team
to help you with some test kernels for the next steps.
--
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
works.
I think you'll have to wait for someone from the canonical kernel team
to help you with some test kernels for the next steps.
--
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 2141216] Re: Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT (andgpu SMU resume failure)
Mario:
1) I confirmed crashkernel is present on my kernel command line:
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
2) I checked /var/crash and only see a small kexec_cmd file.
mike-cooper@Max:~$ ls -lh /var/crash
total 4.0K
-rw-r--r-- 1 root whoopsie 318 Feb 14 11:02 kexec_cmd
3) Can you tell me the exact Ubuntu kernel version/package you want me to test (or provide a link to the debs / proposed kernel)? I'm happy to install it and report results. Though I may be getting out of my depth at some point
--
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
1) I confirmed crashkernel is present on my kernel command line:
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
2) I checked /var/crash and only see a small kexec_cmd file.
mike-cooper@Max:~$ ls -lh /var/crash
total 4.0K
-rw-r--r-- 1 root whoopsie 318 Feb 14 11:02 kexec_cmd
3) Can you tell me the exact Ubuntu kernel version/package you want me to test (or provide a link to the debs / proposed kernel)? I'm happy to install it and report results. Though I may be getting out of my depth at some point
--
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 2141861] [NEW] system locks up following bad page state error
Public bug reported:
Since updating my kernel three days ago to linux-generic 6.17.0-14.14, I
have been confronted twice my system locking up out of the blue. The
screen looks frozen input devices and I cannot log in from other
devices.
I have not been able to trace down the cause of the first occurrence but
the more recent one logged this (see the last line):
Feb 14 21:34:33 Dapple rtkit-daemon[2365]: Supervising 13 threads of 10 processes of 1 users.
Feb 14 21:34:33 Dapple rtkit-daemon[2365]: Supervising 13 threads of 10 processes of 1 users.
Feb 14 21:34:49 Dapple rtkit-daemon[2365]: Supervising 13 threads of 10 processes of 1 users.
Feb 14 21:34:49 Dapple rtkit-daemon[2365]: Supervising 13 threads of 10 processes of 1 users.
Feb 14 21:34:49 Dapple rtkit-daemon[2365]: Successfully made thread 78865 of process 76994 owned by '1002' RT at priority 10.
Feb 14 21:34:49 Dapple rtkit-daemon[2365]: Supervising 14 threads of 11 processes of 1 users.
Feb 14 21:35:01 Dapple CRON[78909]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Feb 14 21:35:01 Dapple CRON[78911]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 14 21:35:01 Dapple CRON[78909]: pam_unix(cron:session): session closed for user root
Feb 14 21:35:06 Dapple rtkit-daemon[2365]: Supervising 14 threads of 11 processes of 1 users.
Feb 14 21:35:06 Dapple rtkit-daemon[2365]: Supervising 14 threads of 11 processes of 1 users.
Feb 14 21:35:07 Dapple rtkit-daemon[2365]: Supervising 14 threads of 11 processes of 1 users.
Feb 14 21:35:07 Dapple rtkit-daemon[2365]: Supervising 14 threads of 11 processes of 1 users.
Feb 14 21:35:07 Dapple rtkit-daemon[2365]: Successfully made thread 78982 of process 77245 owned by '1002' RT at priority 10.
Feb 14 21:35:07 Dapple rtkit-daemon[2365]: Supervising 15 threads of 12 processes of 1 users.
Feb 14 21:35:21 Dapple smartd[1532]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 74 to 76
Feb 14 21:36:22 Dapple kernel: BUG: Bad page state in process MediaSu~sor #55 pfn:469b46
After three full passes of memtest86+, I have not found any indication
that the issue could be bad RAM. Neither does dmesg show any trace of
other hardware troubles. This does look like a kernel bug introduced by
the latest update.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-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
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: codey 4795 F.... wireplumber
/dev/snd/controlC1: codey 4795 F.... wireplumber
/dev/snd/seq: codey 4785 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 14 23:47:33 2026
InstallationDate: Installed on 2025-05-09 (281 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3)
MachineType: Micro-Star International Co., Ltd. MS-7B79
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 nvidia-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-14-generic root=UUID=1c50859e-37c8-46a8-a823-c658ef7af467 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to questing on 2025-10-30 (107 days ago)
dmi.bios.date: 04/14/2025
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: H.L0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 3.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 3.0
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrH.L0:bd04/14/2025:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B79:pvr3.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPLUSMAX(MS-7B79):rvr3.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr3.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B79
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 3.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug questing wayland-session
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141861
Title:
system locks up following bad page state error
Status in linux package in Ubuntu:
New
Bug description:
Since updating my kernel three days ago to linux-generic 6.17.0-14.14,
I have been confronted twice my system locking up out of the blue. The
screen looks frozen input devices and I cannot log in from other
devices.
I have not been able to trace down the cause of the first occurrence
but the more recent one logged this (see the last line):
Feb 14 21:34:33 Dapple rtkit-daemon[2365]: Supervising 13 threads of 10 processes of 1 users.
Feb 14 21:34:33 Dapple rtkit-daemon[2365]: Supervising 13 threads of 10 processes of 1 users.
Feb 14 21:34:49 Dapple rtkit-daemon[2365]: Supervising 13 threads of 10 processes of 1 users.
Feb 14 21:34:49 Dapple rtkit-daemon[2365]: Supervising 13 threads of 10 processes of 1 users.
Feb 14 21:34:49 Dapple rtkit-daemon[2365]: Successfully made thread 78865 of process 76994 owned by '1002' RT at priority 10.
Feb 14 21:34:49 Dapple rtkit-daemon[2365]: Supervising 14 threads of 11 processes of 1 users.
Feb 14 21:35:01 Dapple CRON[78909]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Feb 14 21:35:01 Dapple CRON[78911]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 14 21:35:01 Dapple CRON[78909]: pam_unix(cron:session): session closed for user root
Feb 14 21:35:06 Dapple rtkit-daemon[2365]: Supervising 14 threads of 11 processes of 1 users.
Feb 14 21:35:06 Dapple rtkit-daemon[2365]: Supervising 14 threads of 11 processes of 1 users.
Feb 14 21:35:07 Dapple rtkit-daemon[2365]: Supervising 14 threads of 11 processes of 1 users.
Feb 14 21:35:07 Dapple rtkit-daemon[2365]: Supervising 14 threads of 11 processes of 1 users.
Feb 14 21:35:07 Dapple rtkit-daemon[2365]: Successfully made thread 78982 of process 77245 owned by '1002' RT at priority 10.
Feb 14 21:35:07 Dapple rtkit-daemon[2365]: Supervising 15 threads of 12 processes of 1 users.
Feb 14 21:35:21 Dapple smartd[1532]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 74 to 76
Feb 14 21:36:22 Dapple kernel: BUG: Bad page state in process MediaSu~sor #55 pfn:469b46
After three full passes of memtest86+, I have not found any indication
that the issue could be bad RAM. Neither does dmesg show any trace of
other hardware troubles. This does look like a kernel bug introduced
by the latest update.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-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
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: codey 4795 F.... wireplumber
/dev/snd/controlC1: codey 4795 F.... wireplumber
/dev/snd/seq: codey 4785 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 14 23:47:33 2026
InstallationDate: Installed on 2025-05-09 (281 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3)
MachineType: Micro-Star International Co., Ltd. MS-7B79
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 nvidia-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-14-generic root=UUID=1c50859e-37c8-46a8-a823-c658ef7af467 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to questing on 2025-10-30 (107 days ago)
dmi.bios.date: 04/14/2025
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: H.L0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 3.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 3.0
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrH.L0:bd04/14/2025:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B79:pvr3.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPLUSMAX(MS-7B79):rvr3.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr3.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B79
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 3.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141861/+subscriptions
Since updating my kernel three days ago to linux-generic 6.17.0-14.14, I
have been confronted twice my system locking up out of the blue. The
screen looks frozen input devices and I cannot log in from other
devices.
I have not been able to trace down the cause of the first occurrence but
the more recent one logged this (see the last line):
Feb 14 21:34:33 Dapple rtkit-daemon[2365]: Supervising 13 threads of 10 processes of 1 users.
Feb 14 21:34:33 Dapple rtkit-daemon[2365]: Supervising 13 threads of 10 processes of 1 users.
Feb 14 21:34:49 Dapple rtkit-daemon[2365]: Supervising 13 threads of 10 processes of 1 users.
Feb 14 21:34:49 Dapple rtkit-daemon[2365]: Supervising 13 threads of 10 processes of 1 users.
Feb 14 21:34:49 Dapple rtkit-daemon[2365]: Successfully made thread 78865 of process 76994 owned by '1002' RT at priority 10.
Feb 14 21:34:49 Dapple rtkit-daemon[2365]: Supervising 14 threads of 11 processes of 1 users.
Feb 14 21:35:01 Dapple CRON[78909]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Feb 14 21:35:01 Dapple CRON[78911]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 14 21:35:01 Dapple CRON[78909]: pam_unix(cron:session): session closed for user root
Feb 14 21:35:06 Dapple rtkit-daemon[2365]: Supervising 14 threads of 11 processes of 1 users.
Feb 14 21:35:06 Dapple rtkit-daemon[2365]: Supervising 14 threads of 11 processes of 1 users.
Feb 14 21:35:07 Dapple rtkit-daemon[2365]: Supervising 14 threads of 11 processes of 1 users.
Feb 14 21:35:07 Dapple rtkit-daemon[2365]: Supervising 14 threads of 11 processes of 1 users.
Feb 14 21:35:07 Dapple rtkit-daemon[2365]: Successfully made thread 78982 of process 77245 owned by '1002' RT at priority 10.
Feb 14 21:35:07 Dapple rtkit-daemon[2365]: Supervising 15 threads of 12 processes of 1 users.
Feb 14 21:35:21 Dapple smartd[1532]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 74 to 76
Feb 14 21:36:22 Dapple kernel: BUG: Bad page state in process MediaSu~sor #55 pfn:469b46
After three full passes of memtest86+, I have not found any indication
that the issue could be bad RAM. Neither does dmesg show any trace of
other hardware troubles. This does look like a kernel bug introduced by
the latest update.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-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
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: codey 4795 F.... wireplumber
/dev/snd/controlC1: codey 4795 F.... wireplumber
/dev/snd/seq: codey 4785 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 14 23:47:33 2026
InstallationDate: Installed on 2025-05-09 (281 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3)
MachineType: Micro-Star International Co., Ltd. MS-7B79
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 nvidia-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-14-generic root=UUID=1c50859e-37c8-46a8-a823-c658ef7af467 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to questing on 2025-10-30 (107 days ago)
dmi.bios.date: 04/14/2025
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: H.L0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 3.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 3.0
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrH.L0:bd04/14/2025:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B79:pvr3.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPLUSMAX(MS-7B79):rvr3.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr3.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B79
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 3.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug questing wayland-session
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141861
Title:
system locks up following bad page state error
Status in linux package in Ubuntu:
New
Bug description:
Since updating my kernel three days ago to linux-generic 6.17.0-14.14,
I have been confronted twice my system locking up out of the blue. The
screen looks frozen input devices and I cannot log in from other
devices.
I have not been able to trace down the cause of the first occurrence
but the more recent one logged this (see the last line):
Feb 14 21:34:33 Dapple rtkit-daemon[2365]: Supervising 13 threads of 10 processes of 1 users.
Feb 14 21:34:33 Dapple rtkit-daemon[2365]: Supervising 13 threads of 10 processes of 1 users.
Feb 14 21:34:49 Dapple rtkit-daemon[2365]: Supervising 13 threads of 10 processes of 1 users.
Feb 14 21:34:49 Dapple rtkit-daemon[2365]: Supervising 13 threads of 10 processes of 1 users.
Feb 14 21:34:49 Dapple rtkit-daemon[2365]: Successfully made thread 78865 of process 76994 owned by '1002' RT at priority 10.
Feb 14 21:34:49 Dapple rtkit-daemon[2365]: Supervising 14 threads of 11 processes of 1 users.
Feb 14 21:35:01 Dapple CRON[78909]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Feb 14 21:35:01 Dapple CRON[78911]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 14 21:35:01 Dapple CRON[78909]: pam_unix(cron:session): session closed for user root
Feb 14 21:35:06 Dapple rtkit-daemon[2365]: Supervising 14 threads of 11 processes of 1 users.
Feb 14 21:35:06 Dapple rtkit-daemon[2365]: Supervising 14 threads of 11 processes of 1 users.
Feb 14 21:35:07 Dapple rtkit-daemon[2365]: Supervising 14 threads of 11 processes of 1 users.
Feb 14 21:35:07 Dapple rtkit-daemon[2365]: Supervising 14 threads of 11 processes of 1 users.
Feb 14 21:35:07 Dapple rtkit-daemon[2365]: Successfully made thread 78982 of process 77245 owned by '1002' RT at priority 10.
Feb 14 21:35:07 Dapple rtkit-daemon[2365]: Supervising 15 threads of 12 processes of 1 users.
Feb 14 21:35:21 Dapple smartd[1532]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 74 to 76
Feb 14 21:36:22 Dapple kernel: BUG: Bad page state in process MediaSu~sor #55 pfn:469b46
After three full passes of memtest86+, I have not found any indication
that the issue could be bad RAM. Neither does dmesg show any trace of
other hardware troubles. This does look like a kernel bug introduced
by the latest update.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-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
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: codey 4795 F.... wireplumber
/dev/snd/controlC1: codey 4795 F.... wireplumber
/dev/snd/seq: codey 4785 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 14 23:47:33 2026
InstallationDate: Installed on 2025-05-09 (281 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3)
MachineType: Micro-Star International Co., Ltd. MS-7B79
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 nvidia-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-14-generic root=UUID=1c50859e-37c8-46a8-a823-c658ef7af467 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to questing on 2025-10-30 (107 days ago)
dmi.bios.date: 04/14/2025
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: H.L0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X470 GAMING PLUS MAX (MS-7B79)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 3.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 3.0
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrH.L0:bd04/14/2025:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B79:pvr3.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPLUSMAX(MS-7B79):rvr3.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr3.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B79
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 3.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141861/+subscriptions
[Bug 2141584] Re: Sending wakeonlan magic packet from kernel 6.8.0-100-generic no longer works (UDP broadcast wrong destination address)
Was pointed towards this bug after mistakingly responding to a different bug. I also had this problem and reverted back to -94 and wakeonlan functionality instantly returned.
I noticed it right after updating because my backup device wasn't waking up anymore (done through a cronjob) causing the cronjob that follows 5 minutes after to fail.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141584
Title:
Sending wakeonlan magic packet from kernel 6.8.0-100-generic no longer
works (UDP broadcast wrong destination address)
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Questing:
Fix Released
Bug description:
I'm using the "wakeonlan" tool to wake up some PCs by sending a magic packet from Ubuntu 24.04.
After upgrading to kernel 6.8.0-100-generic, I'm unable to wake up all PCs, because the destination UDP address is no longer FF:FF:FF:FF:FF:FF
---
This is a tcpdump of a working magic packet, generated with the previous kernel
Kernel 6.8.0-90-generic
root@apps1:~# wakeonlan 20:88:10:74:9f:4d
In another terminal window:
root@apps1:~# tcpdump -n -i ens192 port 9 -e
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on ens192, link-type EN10MB (Ethernet), snapshot length 262144 bytes
18:54:22.016746 00:50:56:a7:d3:1b > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 144: 192.168.98.22.56625 > 255.255.255.255.9: UDP, length 102
everything is fine, and the destination PC wakes up.
With the latest 6.8.0-100-generic kernel, the magic packet is no
longer sent to the ethernet broadcast address. It is sent to a
specific mac address, in my case this is the default gateway mac
address! See below.
Kernel 6.8.0-100-generic
root@apps1:~# wakeonlan 20:88:10:74:9f:4d
In another terminal window:
root@apps1:~# tcpdump -n -i ens192 port 9 -e
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on ens192, link-type EN10MB (Ethernet), snapshot length 262144 bytes
19:00:19.581282 00:50:56:a7:d3:1b > 00:e2:69:59:27:42, ethertype IPv4 (0x0800), length 144: 192.168.98.22.55456 > 255.255.255.255.9: UDP, length 102
As you can see, the destination MAC address is no longer
ff:ff:ff:ff:ff:ff. It's now my default gateway MAC address.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-100-generic 6.8.0-100.100
ProcVersionSignature: Ubuntu 6.8.0-100.100-generic 6.8.12
Uname: Linux 6.8.0-100-generic x86_64
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 feb 11 19:00 seq
crw-rw---- 1 root audio 116, 33 feb 11 19:00 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: unknown
Date: Wed Feb 11 19:32:07 2026
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
PciMultimedia:
ProcFB: 0 vmwgfxdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-100-generic root=UUID=5f9c0200-f23e-11e8-8f30-000c29534382 ro maybe-ubiquity
RelatedPackageVersions:
linux-restricted-modules-6.8.0-100-generic N/A
linux-backports-modules-6.8.0-100-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.23
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2024-09-02 (527 days ago)
dmi.bios.date: 11/12/2020
dmi.bios.release: 4.6
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.ec.firmware.release: 0.0
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141584/+subscriptions
I noticed it right after updating because my backup device wasn't waking up anymore (done through a cronjob) causing the cronjob that follows 5 minutes after to fail.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141584
Title:
Sending wakeonlan magic packet from kernel 6.8.0-100-generic no longer
works (UDP broadcast wrong destination address)
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Questing:
Fix Released
Bug description:
I'm using the "wakeonlan" tool to wake up some PCs by sending a magic packet from Ubuntu 24.04.
After upgrading to kernel 6.8.0-100-generic, I'm unable to wake up all PCs, because the destination UDP address is no longer FF:FF:FF:FF:FF:FF
---
This is a tcpdump of a working magic packet, generated with the previous kernel
Kernel 6.8.0-90-generic
root@apps1:~# wakeonlan 20:88:10:74:9f:4d
In another terminal window:
root@apps1:~# tcpdump -n -i ens192 port 9 -e
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on ens192, link-type EN10MB (Ethernet), snapshot length 262144 bytes
18:54:22.016746 00:50:56:a7:d3:1b > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 144: 192.168.98.22.56625 > 255.255.255.255.9: UDP, length 102
everything is fine, and the destination PC wakes up.
With the latest 6.8.0-100-generic kernel, the magic packet is no
longer sent to the ethernet broadcast address. It is sent to a
specific mac address, in my case this is the default gateway mac
address! See below.
Kernel 6.8.0-100-generic
root@apps1:~# wakeonlan 20:88:10:74:9f:4d
In another terminal window:
root@apps1:~# tcpdump -n -i ens192 port 9 -e
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on ens192, link-type EN10MB (Ethernet), snapshot length 262144 bytes
19:00:19.581282 00:50:56:a7:d3:1b > 00:e2:69:59:27:42, ethertype IPv4 (0x0800), length 144: 192.168.98.22.55456 > 255.255.255.255.9: UDP, length 102
As you can see, the destination MAC address is no longer
ff:ff:ff:ff:ff:ff. It's now my default gateway MAC address.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-100-generic 6.8.0-100.100
ProcVersionSignature: Ubuntu 6.8.0-100.100-generic 6.8.12
Uname: Linux 6.8.0-100-generic x86_64
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 feb 11 19:00 seq
crw-rw---- 1 root audio 116, 33 feb 11 19:00 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: unknown
Date: Wed Feb 11 19:32:07 2026
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
PciMultimedia:
ProcFB: 0 vmwgfxdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-100-generic root=UUID=5f9c0200-f23e-11e8-8f30-000c29534382 ro maybe-ubiquity
RelatedPackageVersions:
linux-restricted-modules-6.8.0-100-generic N/A
linux-backports-modules-6.8.0-100-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.23
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2024-09-02 (527 days ago)
dmi.bios.date: 11/12/2020
dmi.bios.release: 4.6
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.ec.firmware.release: 0.0
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141584/+subscriptions
[Bug 2140491] Re: noble-update linux-tool-generic missing dependent package
Ah! Thanks @marnixrijnart (I don't know how to tag people here). I
spent days searching and never found that bug's page :( .
I will only have to figure out how to "unignore" the -100 kernel (I
suspect Mint will want to see -100 first before heading to 103).
Thanks once again for pointing me in the right direction.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2140491
Title:
noble-update linux-tool-generic missing dependent package
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Noble:
Confirmed
Bug description:
Metapackage linux-tool-generic in the noble-updates suite is missing
the dependent linux-tools-6.8.0-100-generic package. This package is
still tagged to the noble-proposed.
apt fails to install linux-tools-generic
# apt-get install linux-tools-generic
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
linux-tools-generic : Depends: linux-tools-6.8.0-100-generic but it is not installable
E: Unable to correct problems, you have held broken packages
# dpkg-deb --info linux-tools-generic_6.8.0-100.100_arm64.deb
new Debian package, version 2.0.
size 10930 bytes: control archive=451 bytes.
388 bytes, 13 lines control
166 bytes, 2 lines md5sums
Package: linux-tools-generic
Source: linux-meta
Version: 6.8.0-100.100
Architecture: arm64
Maintainer: Ubuntu Kernel Team <kernel-team@lists.ubuntu.com>
Installed-Size: 17
Depends: linux-tools-6.8.0-100-generic
Provides: linux-tools
Section: kernel
Priority: optional
Description: Generic Linux kernel tools
This package will always depend on the latest generic kernel tools
available.
# apt policy linux-tools-6.8.0-100-generic
linux-tools-6.8.0-100-generic:
Installed: (none)
Candidate: (none)
Version table:
# apt policy linux-tools-generic
linux-tools-generic:
Installed: 6.8.0-94.96
Candidate: 6.8.0-100.100
Version table:
6.8.0-100.100 500
500 https://artifacts-deploy-prod-use1.pinadmin.com/artifactory/ports-ubuntu-deb-apt-prod-remote noble-updates/main arm64 Packages
*** 6.8.0-94.96 500
500 https://artifacts-deploy-prod-use1.pinadmin.com/artifactory/ports-ubuntu-deb-apt-prod-remote noble-security/main arm64 Packages
100 /var/lib/dpkg/status
6.8.0-31.31 500
500 https://artifacts-deploy-prod-use1.pinadmin.com/artifactory/ports-ubuntu-deb-apt-prod-remote noble/main arm64 Packages
But, on a system with noble-proposed defined
# apt policy linux-tools-6.8.0-100-generic
linux-tools-6.8.0-100-generic:
Installed: (none)
Candidate: 6.8.0-100.100
Version table:
6.8.0-100.100 500
500 https://artifacts-deploy-prod-use1.pinadmin.com/artifactory/ports-ubuntu-deb-apt-prod-remote noble-proposed/main arm64 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2140491/+subscriptions
spent days searching and never found that bug's page :( .
I will only have to figure out how to "unignore" the -100 kernel (I
suspect Mint will want to see -100 first before heading to 103).
Thanks once again for pointing me in the right direction.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2140491
Title:
noble-update linux-tool-generic missing dependent package
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Noble:
Confirmed
Bug description:
Metapackage linux-tool-generic in the noble-updates suite is missing
the dependent linux-tools-6.8.0-100-generic package. This package is
still tagged to the noble-proposed.
apt fails to install linux-tools-generic
# apt-get install linux-tools-generic
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
linux-tools-generic : Depends: linux-tools-6.8.0-100-generic but it is not installable
E: Unable to correct problems, you have held broken packages
# dpkg-deb --info linux-tools-generic_6.8.0-100.100_arm64.deb
new Debian package, version 2.0.
size 10930 bytes: control archive=451 bytes.
388 bytes, 13 lines control
166 bytes, 2 lines md5sums
Package: linux-tools-generic
Source: linux-meta
Version: 6.8.0-100.100
Architecture: arm64
Maintainer: Ubuntu Kernel Team <kernel-team@lists.ubuntu.com>
Installed-Size: 17
Depends: linux-tools-6.8.0-100-generic
Provides: linux-tools
Section: kernel
Priority: optional
Description: Generic Linux kernel tools
This package will always depend on the latest generic kernel tools
available.
# apt policy linux-tools-6.8.0-100-generic
linux-tools-6.8.0-100-generic:
Installed: (none)
Candidate: (none)
Version table:
# apt policy linux-tools-generic
linux-tools-generic:
Installed: 6.8.0-94.96
Candidate: 6.8.0-100.100
Version table:
6.8.0-100.100 500
500 https://artifacts-deploy-prod-use1.pinadmin.com/artifactory/ports-ubuntu-deb-apt-prod-remote noble-updates/main arm64 Packages
*** 6.8.0-94.96 500
500 https://artifacts-deploy-prod-use1.pinadmin.com/artifactory/ports-ubuntu-deb-apt-prod-remote noble-security/main arm64 Packages
100 /var/lib/dpkg/status
6.8.0-31.31 500
500 https://artifacts-deploy-prod-use1.pinadmin.com/artifactory/ports-ubuntu-deb-apt-prod-remote noble/main arm64 Packages
But, on a system with noble-proposed defined
# apt policy linux-tools-6.8.0-100-generic
linux-tools-6.8.0-100-generic:
Installed: (none)
Candidate: 6.8.0-100.100
Version table:
6.8.0-100.100 500
500 https://artifacts-deploy-prod-use1.pinadmin.com/artifactory/ports-ubuntu-deb-apt-prod-remote noble-proposed/main arm64 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2140491/+subscriptions
[Bug 2141628] Re: 6.17.0-14 generic kernel causes stutter and complete freezes in certain games
Is anyone even looking at these?
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141628
Title:
6.17.0-14 generic kernel causes stutter and complete freezes in
certain games
Status in linux package in Ubuntu:
New
Bug description:
I'll preface this by the fact that I am a noob and I have no fucking
idea what I'm doing with clis and stuff so don't expect me to know all
the linux things.
Was trying to make a post on git:
https://github.com/issues/created?q=is%3Aissue%20author%3A%40me%20sort%3Aupdated-
desc&issue=linuxmint%7Clinuxmint%7C848
Am on mint 22.3, after updating from 6.14.0-37 to 6.17.0-14 I started
to notice terrible stutter in games. If I swap back to .14 everything
returns to normal and if I swap to .17 everything starts bugging
again. Today I noticed that some games just won't load while I move
the mouse and this can go on practically forever until mouse movement
is stopped (this was probably always the case but you don't always run
circles with mouse so it was just stuttering).
Might be the same issue as this:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2140502
I tried to do this:
1) cat /proc/version_signature > version.log
2) sudo lspci -vnvn > lspci-vnvn.log
but it gives me nothing for first command and pcilib: sysfs_read_vpd: read failed: No such device for second.
Tbh am a bit panicked since .14 support expires at the end of the month and this makes games borderline unplayable.
If you need anything else please do ask and I'll try my best to accommodate.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141628/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141628
Title:
6.17.0-14 generic kernel causes stutter and complete freezes in
certain games
Status in linux package in Ubuntu:
New
Bug description:
I'll preface this by the fact that I am a noob and I have no fucking
idea what I'm doing with clis and stuff so don't expect me to know all
the linux things.
Was trying to make a post on git:
https://github.com/issues/created?q=is%3Aissue%20author%3A%40me%20sort%3Aupdated-
desc&issue=linuxmint%7Clinuxmint%7C848
Am on mint 22.3, after updating from 6.14.0-37 to 6.17.0-14 I started
to notice terrible stutter in games. If I swap back to .14 everything
returns to normal and if I swap to .17 everything starts bugging
again. Today I noticed that some games just won't load while I move
the mouse and this can go on practically forever until mouse movement
is stopped (this was probably always the case but you don't always run
circles with mouse so it was just stuttering).
Might be the same issue as this:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2140502
I tried to do this:
1) cat /proc/version_signature > version.log
2) sudo lspci -vnvn > lspci-vnvn.log
but it gives me nothing for first command and pcilib: sysfs_read_vpd: read failed: No such device for second.
Tbh am a bit panicked since .14 support expires at the end of the month and this makes games borderline unplayable.
If you need anything else please do ask and I'll try my best to accommodate.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141628/+subscriptions
Подписаться на:
Комментарии (Atom)