[Bug 2131607] Re: High-resolution scrolling breaks when waking from suspend

https://github.com/torvalds/linux/commit/d6f4941f1b4f3e701e422dfbfee024264294f91f
is part of Linux kernel release 6.19, so this should be closed.

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2131607

Title:
High-resolution scrolling breaks when waking from suspend

Status in linux package in Ubuntu:
Confirmed

Bug description:
Scrolling is extremely slow after resuming from suspend. This issue
affects various devices that utilize high-resolution scrolling, such
as the Ultimate Hacking Keyboard.

A kernel patch has already been made, but no one has picked it up, so
I kindly request that anyone who's in charge push it:

https://lore.kernel.org/linux-
input/20251007203544.9963-1-kupper.benedek@gmail.com/T/#u

Your help is much appreciated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2131607/+subscriptions

[Bug 2141298] Re: AppArmor blocks write(2) to network sockets with Linux 6.19

Another confirmation that sbuild is still broken, originally reported as
LP: #2141364. I am running 6.19.0-6.6.

--
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:
Fix Released
Status in linux package in Ubuntu:
Fix Released

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 2141298] Re: AppArmor blocks write(2) to network sockets with Linux 6.19

I was running 6.19.0-6.6 before, and it doesn't make sbuild work for me

--
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:
Fix Released
Status in linux package in Ubuntu:
Fix Released

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 2142789] [NEW] Noble update: upstream stable patchset 2026-02-26

Public bug reported:


SRU Justification

Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:

upstream stable patchset 2026-02-26
from git://git.kernel.org/

** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed

** Affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New


** Tags: kernel-stable-tracking-bug

** Changed in: linux (Ubuntu)
Status: New => Confirmed

** Also affects: linux (Ubuntu Noble)
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/2142789

Title:
Noble update: upstream stable patchset 2026-02-26

Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Noble:
New

Bug description:

SRU Justification

Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:

upstream stable patchset 2026-02-26
from git://git.kernel.org/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142789/+subscriptions

[Bug 2142783] Re: Suspend-Resume Failure on Kernel 6.17.0-14 on Linux Mint 22.3

** Attachment added: "lspci-vnvn log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142783/+attachment/5948748/+files/lspci-vnvn.log

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142783

Title:
Suspend-Resume Failure on Kernel 6.17.0-14 on Linux Mint 22.3

Status in linux package in Ubuntu:
New

Bug description:
Suspend-Resume Failure on Kernel 6.17.0-14 on Linux Mint 22.3
Regressive Behavior: System fails to maintain S3 state and freezes upon immediate auto-resume.

Immediate Wakeup: Upon initiating suspend, the system attempts to
enter sleep but triggers an immediate wakeup event without user input.

Kernel/Driver Lockup: On the involuntary resume, the system becomes
completely unresponsive (Hard Lockup).

Keyboard State: NumLock LED remains illuminated/static, but HID inputs
(keyboard/mouse) are ignored.

No Display: The monitor typically stays in power-save mode or shows a
black screen.

Reverting to Kernel 6.14.0-37 issue is gone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142783/+subscriptions

[Bug 2142336] Re: Coresight fails to build on 6.8.0-101 due to 'atomic_t' member accessed as 'int'

This bug is awaiting verification that the linux-nvidia-
tegra/6.8.0-1018.18 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-noble-linux-nvidia-tegra' to
'verification-done-noble-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-noble-linux-nvidia-tegra' to
'verification-failed-noble-linux-nvidia-tegra'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-noble-linux-nvidia-tegra-v2 verification-needed-noble-linux-nvidia-tegra

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142336

Title:
Coresight fails to build on 6.8.0-101 due to 'atomic_t' member
accessed as 'int'

Status in linux package in Ubuntu:
New
Status in linux source package in Noble:
New

Bug description:
SRU Justification:

[Impact]

When CONFIG_CORESIGHT is enabled, noble 6.8.0-101 fails to build with
the following errors:

```
drivers/hwtracing/coresight/coresight-catu.c: In function 'catu_enable':
drivers/hwtracing/coresight/coresight-catu.c:465:27: error: invalid operands to binary == (have 'atomic_t' and 'int')
  465 | if (csdev->refcnt == 0) {
      | ~~~~~~~~~~~~~ ^~
      | |
      | atomic_t
drivers/hwtracing/coresight/coresight-catu.c:471:30: error: wrong type argument to increment
  471 | csdev->refcnt++;
      | ^~
drivers/hwtracing/coresight/coresight-catu.c: In function 'catu_disable':
drivers/hwtracing/coresight/coresight-catu.c:498:13: error: wrong type argument to decrement
  498 | if (--csdev->refcnt == 0) {
      | ^~
```

These errors are a result of including the following patch in upstream stable
updates, but missing some dependencies from the original patch set:

  Error description: refcnt accessed as int but defined as atomic_t
  Break commit: n/linux 0e2198d37507 ("coresight: catu: Introduce refcount and spinlock for enabling/disabling")
  Missing commit: 4545b38ef004 ("coresight: Remove atomic type from refcnt")
  Patch series: "coresight: Separate sysfs and Perf usage and some other cleanups"
                (https://lists.infradead.org/pipermail/linux-arm-kernel/2024-January/899269.html)

[Fix]

Cherry-pick upstream commit:
4545b38ef004 ("coresight: Remove atomic type from refcnt")
which requires a few context fixups due to missing commits from the original
patchset. Those missing patches are not required for this commit, so we can
just fix and apply it alone to reduce the number of changes.

NOTE: These are the missing dependent patches for a clean application:

a0fef3f05cf3 ("coresight: Make language around "activated" sinks consistent")
a11ebe138b8d ("coresight: Remove ops callback checks")
9cae77cf23e3 ("coresight: Move mode to struct coresight_device")
d5e83f97eb56 ("coresight: Remove the 'enable' field.")
1f5149c7751c ("coresight: Move all sysfs code to sysfs file")

These contain pretty significant refactoring and cleanup (although they don't
alter behaviour) so they were omitted to reduce changes to a stable kernel.

[Test Plan]

Ensure CONFIG_CORESIGHT and CONFIG_CORESIGHT_CATU are enabled, then
compile test.

[Where problems could occur]

There is a low chance of regression since this patch is purely cleanup and
does not modify observable behaviour, as stated by the author in the original
patch set. Additionally, coresight failed to build before this, so this is
a guaranteed improvement in that respect. There is a risk of breakage if I
missed some dependent commits, or if my fixups were incorrect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142336/+subscriptions

[Bug 2142337] Re: Coresight fails to build on 6.8.0-102 due to missing function and arg definitions

This bug is awaiting verification that the linux-nvidia-
tegra/6.8.0-1018.18 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-noble-linux-nvidia-tegra' to
'verification-done-noble-linux-nvidia-tegra'. If the problem still
exists, change the tag 'verification-needed-noble-linux-nvidia-tegra' to
'verification-failed-noble-linux-nvidia-tegra'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-noble-linux-nvidia-tegra-v2 verification-needed-noble-linux-nvidia-tegra

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142337

Title:
Coresight fails to build on 6.8.0-102 due to missing function and arg
definitions

Status in linux package in Ubuntu:
New
Status in linux source package in Noble:
New

Bug description:
SRU Justification:

[Impact]

When CONFIG_CORESIGHT is enabled, noble 6.8.0-102 fails to build with
the following errors:

```
drivers/hwtracing/coresight/coresight-catu.c: In function 'catu_init':
drivers/hwtracing/coresight/coresight-catu.c:728:15: error: implicit declaration of function 'coresight_init_driver' [-Werror=implicit-function-declaration]
728 | ret = coresight_init_driver("catu", &catu_driver, &catu_platform_driver);
| ^~~~~~~~~~~~~~~~~~~~~
drivers/hwtracing/coresight/coresight-catu.c: In function 'catu_exit':
drivers/hwtracing/coresight/coresight-catu.c:736:9: error: implicit declaration of function 'coresight_remove_driver'; did you mean 'coresight_remove_links'? [-Werror=implicit-function-declaration]
736 | coresight_remove_driver(&catu_driver, &catu_platform_driver);
| ^~~~~~~~~~~~~~~~~~~~~~~
| coresight_remove_links
...
drivers/hwtracing/coresight/coresight-tmc-core.c: In function '__tmc_probe':
drivers/hwtracing/coresight/coresight-tmc-core.c:500:65: error: 'id' undeclared (first use in this function); did you mean 'fd'?
500 | coresight_get_uci_data(id));
| ^~
| fd
drivers/hwtracing/coresight/coresight-tmc-core.c:500:65: note: each undeclared identifier is reported only once for each function it appears in
...
drivers/hwtracing/coresight/coresight-tmc-core.c: In function 'tmc_init':
drivers/hwtracing/coresight/coresight-tmc-core.c:728:16: error: implicit declaration of function 'coresight_init_driver' [-Werror=implicit-function-declaration]
728 | return coresight_init_driver("tmc", &tmc_driver, &tmc_platform_driver);
| ^~~~~~~~~~~~~~~~~~~~~
drivers/hwtracing/coresight/coresight-tmc-core.c: In function 'tmc_exit':
drivers/hwtracing/coresight/coresight-tmc-core.c:733:9: error: implicit declaration of function 'coresight_remove_driver'; did you mean 'coresight_remove_links'? [-Werror=implicit-function-declaration]
733 | coresight_remove_driver(&tmc_driver, &tmc_platform_driver);
| ^~~~~~~~~~~~~~~~~~~~~~~
| coresight_remove_links
...
drivers/hwtracing/coresight/coresight-tpdm.c: In function 'tpdm_enable':
drivers/hwtracing/coresight/coresight-tpdm.c:299:14: error: implicit declaration of function 'coresight_take_mode'; did you mean 'coresight_make_links'? [-Werror=implicit-function-declaration]
299 | if (!coresight_take_mode(csdev, mode)) {
| ^~~~~~~~~~~~~~~~~~~
| coresight_make_links
drivers/hwtracing/coresight/coresight-tpdm.c: In function 'tpdm_disable':
drivers/hwtracing/coresight/coresight-tpdm.c:345:9: error: implicit declaration of function 'coresight_set_mode'; did you mean 'coresight_get_pid'? [-Werror=implicit-function-declaration]
345 | coresight_set_mode(csdev, CS_MODE_DISABLED);
| ^~~~~~~~~~~~~~~~~~
| coresight_get_pid
drivers/hwtracing/coresight/coresight-dummy.c: In function 'dummy_source_enable':
drivers/hwtracing/coresight/coresight-dummy.c:26:14: error: implicit declaration of function 'coresight_take_mode'; did you mean 'coresight_make_links'? [-Werror=implicit-function-declaration]
26 | if (!coresight_take_mode(csdev, mode))
| ^~~~~~~~~~~~~~~~~~~
| coresight_make_links
drivers/hwtracing/coresight/coresight-dummy.c: In function 'dummy_source_disable':
drivers/hwtracing/coresight/coresight-dummy.c:37:9: error: implicit declaration of function 'coresight_set_mode'; did you mean 'coresight_get_pid'? [-Werror=implicit-function-declaration]
37 | coresight_set_mode(csdev, CS_MODE_DISABLED);
| ^~~~~~~~~~~~~~~~~~
| coresight_get_pid
```

These errors are a result of including the following patches in
upstream stable updates, but missing some dependencies from the
original patch sets:

Error description: __tmc_probe:id not defined
Break commit: n/linux aaf260b9572e ("coresight: tmc: Move ACPI support from AMBA driver to platform driver")
Missing commit: 852e9a32058a ("coresight: stm: Extract device name from AMBA pid based table lookup")
3ab210297c31 ("coresight: tmc: Extract device properties from AMBA pid based table lookup")
Patch series: "coresight: Move remaining AMBA ACPI devices into platform driver"
(https://lists-ec2.linaro.org/archives/list/coresight@lists.linaro.org/thread/XGJAJMHSDE5P7YSX33CIW5DHKR6C343L/)

Error description: catu,tmc: coresight_{init,remove}_driver not defined
Break commit: n/linux aaf260b9572e ("coresight: tmc: Move ACPI support from AMBA driver to platform driver")
n/linux cf08211db65c ("coresight: catu: Move ACPI support from AMBA driver to platform driver")
Missing commit: 075b7cd7ad7d ("coresight: Add helpers registering/removing both AMBA and platform drivers")
Patch series: "coresight: Move remaining AMBA ACPI devices into platform driver"
(https://lists-ec2.linaro.org/archives/list/coresight@lists.linaro.org/thread/XGJAJMHSDE5P7YSX33CIW5DHKR6C343L/)

Error description: tpdm,dummy: coresight_{set,take}_mode not defined
Break commit: n/linux f30974e15e66 ("Coresight: Set correct cs_mode for TPDM to fix disable issue")
n/linux e76e67682488 ("Coresight: Set correct cs_mode for dummy source to fix disable issue")
Missing commit: d724f65218b9 ("coresight: Add helper for atomically taking the device")
Patch series: "coresight: Separate sysfs and Perf usage and some other cleanups"
(https://lists.infradead.org/pipermail/linux-arm-kernel/2024-January/899269.html)

[Fix]

Revert the break commits.

[Test Plan]

Ensure CONFIG_CORESIGHT and CONFIG_CORESIGHT_CATU are enabled, then
compile test.

[Where problems could occur]

These reverts are technically removing fixes from the tree, which have the
potential to cause behaviour changes or regressions. However, the generic
kernel has never been able to build these coresight features, and thus we have
not observed any examples of the issue the patches intended to fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142337/+subscriptions

[Bug 1784156] Re: [regression][amdgpu] analog output stops working on R9 380/Tonga Pro after upgrading to Ubuntu 18.04

I'm running an AMD Radeon R9 380 (Tonga, GCN 1.2) on Ubuntu 24.04-based
system with kernel 6.17.0-14-generic.

I'm experiencing HDMI resume instability when DC is enabled. After
suspend-to-RAM (deep), the system wakes but the screen returns either
blank or with corrupted output. Input devices respond (cursor moves),
but the session is unusable and requires forced reboot.

The issue is completely resolved by adding:

amdgpu.dc=0

to the kernel parameters.

This reminds me of historical Tonga/DC regressions such as bug #1784156,
where disabling DC restored proper output detection and signal behavior.

Given that Tonga (GCN 1.2) is a legacy architecture, it may not be
receiving the same level of DC resume-path validation as newer RDNA
GPUs. This might indicate a DC-specific regression affecting older GCN
display pipelines during resume.

I can provide additional logs (dmesg before/after suspend, drm debug
logs, etc.) if needed.

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1784156

Title:
[regression][amdgpu] analog output stops working on R9 380/Tonga Pro
after upgrading to Ubuntu 18.04

Status in linux package in Ubuntu:
Triaged
Status in linux source package in Bionic:
Triaged
Status in linux source package in Cosmic:
Won't Fix

Bug description:
After upgrading to Ubuntu 18.04 (and thus from Linux 4.13 to Linux
4.15) the Monitor connected via VGA (through DVI-I) shows a 'No
Signal' message after amdgpu takes over from efifb and turns off.

The monitor worked fine in Ubuntu 17.10 and Linux 4.13.

When looking at the output of xrandr, the analog monitor is now
detected as DVI-D instead of DVI-I and thus probably won't receive an
analog signal anymore.

After some investigation, it turns out the monitor will light up when
adding the `amdgpu.dc=0` kernel parameter.

I've tried Linux 4.18-rc6 from the mainline ppa and the issue persists
unless I add the kernel parameter to disable DC.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-generic 4.15.0.29.31
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/pcmC0D0p: benpicco 2151 F...m pulseaudio
/dev/snd/controlC0: benpicco 2151 F.... pulseaudio
/dev/snd/controlC1: benpicco 2151 F.... pulseaudio
CurrentDesktop: MATE
Date: Sat Jul 28 17:55:35 2018
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=ef400a46-b237-4272-b4a7-f866e92d00a0
InstallationDate: Installed on 2016-08-06 (720 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IwConfig:
lo no wireless extensions.

eno1 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=8e6b0d6a-eb87-44cf-8fc3-b13bd97b71d2 ro amdgpu.dc=0
RelatedPackageVersions:
linux-restricted-modules-4.15.0-29-generic N/A
linux-backports-modules-4.15.0-29-generic N/A
linux-firmware 1.173.1
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-07-28 (0 days ago)
dmi.bios.date: 11/09/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3603
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z68-V
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784156/+subscriptions

[Bug 2138568] Re: kernel BUG at fs/dcache.c:920

Any update please?

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2138568

Title:
kernel BUG at fs/dcache.c:920

Status in linux package in Ubuntu:
New
Status in linux source package in Jammy:
New

Bug description:
Jan 1 09:39:34 XXX.domain.tld kernel: ------------[ cut here
]------------ Jan 1 09:39:34 XXX.domain.tld kernel: kernel BUG at
fs/dcache.c:920! Jan 1 09:39:34 XXX.domain.tld kernel: invalid opcode:
0000 [#1] PREEMPT SMP NOPTI Jan 1 09:39:34 XXX.domain.tld kernel: CPU:
103 PID: 1327569 Comm: worker_thread Tainted: G W
6.8.0-90-generic #91~22.04.1-Ubuntu Jan 1 09:39:34 XXX.domain.tld
kernel: Hardware name: Supermicro SYS-120H-TNR/X12DHM-6, BIOS 2.4
09/06/2025 Jan 1 09:39:34 XXX.domain.tld kernel: RIP:
0010:dget_parent+0xb8/0xc0 Jan 1 09:39:34 XXX.domain.tld kernel: Code:
89 44 24 64 e8 f9 ec d1 00 4c 89 e0 5b 41 5c 41 5d 41 5e 5d 31 ff c3
cc cc cc cc 4c 89 ef e8 df ec d1 00 e8 7a 78 cc ff eb a5 <0f> 0b 66 0f
1f 44 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 Jan 1 09:39:34
XXX.domain.tld kernel: RSP: 0018:ff5bae76562eb8d8 EFLAGS: 00010246 --
Boot 4056bcd8c09a4979b2920da4c567266a --


Random freeze of server every few days, only hard reboot helps.
Problem starts after we do:
A) bios to latest (2.1 -> 2.4)
B) change kernel 5.15 to HWE 6.8

CPU:
2x Intel(R) Xeon(R) Gold 5320 CPU - microcode: 0xd000410

Memory:
2TB (32x M393A8G40AB2-CWE 64GB) - memtest negative

I believe, it looks like bug/incompatibility in kernel 6.8 with this setup.
After we switch back to 5.15 problem not appeared again.

Supermicro suggested to fill kernel report.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-164-generic 5.15.0-164.174
ProcVersionSignature: Ubuntu 5.15.0-164.174-generic 5.15.193
Uname: Linux 5.15.0-164-generic x86_64
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Jan 18 02:46 seq
crw-rw---- 1 root audio 116, 33 Jan 18 02:46 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.10
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: Sun Jan 18 10:11:23 2026
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Supermicro SYS-120H-TNR
PciMultimedia:

ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-164-generic root=/dev/mapper/vg0-root ro intel_idle.max_cstate=1 ipv6.disable=1 fsck.mode=skip
RelatedPackageVersions:
linux-restricted-modules-5.15.0-164-generic N/A
linux-backports-modules-5.15.0-164-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.40
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/06/2025
dmi.bios.release: 5.22
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 2.4
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: X12DHM-6
dmi.board.vendor: Supermicro
dmi.board.version: 1.02A
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.4:bd09/06/2025:br5.22:svnSupermicro:pnSYS-120H-TNR:pvr0123456789:rvnSupermicro:rnX12DHM-6:rvr1.02A:cvnSupermicro:ct17:cvr0123456789:skuTobefilledbyO.E.M.:
dmi.product.family: Family
dmi.product.name: SYS-120H-TNR
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2138568/+subscriptions

[Bug 2142783] Re: Suspend-Resume Failure on Kernel 6.17.0-14 on Linux Mint 22.3

** Package changed: ubuntu => linux (Ubuntu)

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142783

Title:
Suspend-Resume Failure on Kernel 6.17.0-14 on Linux Mint 22.3

Status in linux package in Ubuntu:
New

Bug description:
Suspend-Resume Failure on Kernel 6.17.0-14 on Linux Mint 22.3
Regressive Behavior: System fails to maintain S3 state and freezes upon immediate auto-resume.

Immediate Wakeup: Upon initiating suspend, the system attempts to
enter sleep but triggers an immediate wakeup event without user input.

Kernel/Driver Lockup: On the involuntary resume, the system becomes
completely unresponsive (Hard Lockup).

Keyboard State: NumLock LED remains illuminated/static, but HID inputs
(keyboard/mouse) are ignored.

No Display: The monitor typically stays in power-save mode or shows a
black screen.

Reverting to Kernel 6.14.0-37 issue is gone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142783/+subscriptions

[Bug 2142783] [NEW] Suspend-Resume Failure on Kernel 6.17.0-14 on Linux Mint 22.3

You have been subscribed to a public bug:

Suspend-Resume Failure on Kernel 6.17.0-14 on Linux Mint 22.3
Regressive Behavior: System fails to maintain S3 state and freezes upon immediate auto-resume.

Immediate Wakeup: Upon initiating suspend, the system attempts to enter
sleep but triggers an immediate wakeup event without user input.

Kernel/Driver Lockup: On the involuntary resume, the system becomes
completely unresponsive (Hard Lockup).

Keyboard State: NumLock LED remains illuminated/static, but HID inputs
(keyboard/mouse) are ignored.

No Display: The monitor typically stays in power-save mode or shows a
black screen.

Reverting to Kernel 6.14.0-37 issue is gone.

** Affects: linux (Ubuntu)
Importance: Undecided
Status: New

--
Suspend-Resume Failure on Kernel 6.17.0-14 on Linux Mint 22.3
https://bugs.launchpad.net/bugs/2142783
You received this bug notification because you are subscribed to linux in Ubuntu.

[Bug 2142510] Re: Regression: ip route get intermittently returns broadcast … for public IPs on 6.8.0-100 (breaks outbound TCP/Docker pulls)

So that's what was causing all these weird network issues all of a
sudden here. Looks like 6.8.0-101-generic is likewise affected.

Sending wake-on-LAN packets also broke for me coincidentally with this.
That is, my NAS (now also running 6.8.0-101) could still receive WOL
packets sent from a server running 6.8.0-79, but none sent from my
desktop (running 6.8.0-101). After downgrading the desktop back to
6.8.0-94, WOL packets sent from it were again immediately picked up by
the NAS.

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142510

Title:
Regression: ip route get intermittently returns broadcast …
<local,brd> for public IPs on 6.8.0-100 (breaks outbound TCP/Docker
pulls)

Status in linux package in Ubuntu:
Confirmed

Bug description:
Summary / Regression
This is a regression between Ubuntu kernels on an Ubuntu VM (Proxmox/QEMU/KVM, bridged networking, DHCP reservation). With 6.8.0-100-generic, ip -details route get <public-ip> intermittently returns an invalid cached result marking public IPs as broadcast/local (cache <local,brd>). When it enters this state, outbound TCP fails with "Network is unreachable" and Docker/Portainer pulls fail. Booting 6.8.0-90-generic on the same VM fixes it (route lookups remain unicast).

Environment

Ubuntu VM on Proxmox VE (QEMU/KVM), bridge vmbr0, DHCP reservation.

Reproduced across configuration changes: virtio/e1000 NIC, cpu
host/kvm64, cloud-init disabled; persists specifically with 6.8.0-100
and disappears with 6.8.0-90.

Evidence (6.8.0-100-generic)
Running repeatedly:
ip -details route get 1.1.1.1
shows flapping between correct unicast and incorrect broadcast classification:

unicast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache
broadcast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache <local,brd>
broadcast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache <local,brd>

When the broadcast … <local,brd> state appears, outbound TCP
connections to public IPs fail ("Network is unreachable"), and ubuntu-
bug linux upload also sometimes fails with urlopen error [Errno 101]
Network is unreachable.

Expected
Public IPs should never be classified as broadcast … <local,brd> in route lookup; outbound TCP should stay stable.

Workaround
Boot kernel 6.8.0-90-generic (issue disappears). Flushing caches (ip route flush cache and ip neigh flush dev ens18) temporarily restores correct behavior on 6.8.0-100.

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: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon Feb 23 19:39:48 2026
InstallationDate: Installed on 2025-03-13 (347 days ago)
InstallationMedia: Ubuntu-Server 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm
ProcFB: 0 bochs-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-100-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro usbcore.autosuspend=-1
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.22
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-9.2
dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-9.2:cvnQEMU:ct1:cvrpc-i440fx-9.2:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-9.2
dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142510/+subscriptions

[Bug 2060217] Re: NFSv4 fails to mount in noble/s390x

Dropping release notes task since this was fixed in the kernel, and
resolute shouldn't be affected anymore.

** Changed in: ubuntu-release-notes
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/2060217

Title:
NFSv4 fails to mount in noble/s390x

Status in Release Notes for Ubuntu:
Fix Released
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in nfs-utils package in Ubuntu:
Invalid

Bug description:
https://autopkgtest.ubuntu.com/packages/n/nfs-utils/noble/s390x

Looks like it has been failing for a long time already.

Log: https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/s390x/n/nfs-utils/20240404_145924_ef255@/log.gz

339s autopkgtest [14:41:04]: test local-server-client: [-----------------------
340s Killed
340s autopkgtest [14:41:05]: test process requested reboot with marker boot1
364s autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds...
372s FAIL: nfs_home not mounted
373s autopkgtest [14:41:38]: test local-server-client: -----------------------]
373s local-server-client FAIL non-zero exit status 1

and

934s autopkgtest [14:50:59]: test kerberos-mount: [-----------------------
935s Initializing database '/var/lib/krb5kdc/principal' for realm 'DEP8',
935s master key name 'K/M@DEP8'
935s Authenticating as principal root/admin@DEP8 with password.
935s Principal "nfs/nfs-server.dep8@DEP8" created.
935s Authenticating as principal root/admin@DEP8 with password.
935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption type aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption type aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
935s Authenticating as principal root/admin@DEP8 with password.
935s Principal "host/nfs-server.dep8@DEP8" created.
935s Authenticating as principal root/admin@DEP8 with password.
935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption type aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption type aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
936s exporting *:/storage
938s mount.nfs: mount system call failed for /mnt
938s umount: /mnt: not mounted.
938s autopkgtest [14:51:02]: test kerberos-mount: -----------------------]
939s kerberos-mount FAIL non-zero exit status 32

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2060217/+subscriptions