[Bug 2171467] Re: Ptyxis creates systemd inhibitor blocks system emergency shutdown

If you want to argue that holding a session inhibitor for foreground terminal processes is wrong, that's fine. But the argument cannot be that such inhibitor causes hardware damage. That necessarily means some lower part of the stack is broken. We cannot go and patch every single application out there to remove their inhibitors because inhibition is broken; instead we shall make logout inhibitors not broken. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171467 Title: Ptyxis creates systemd inhibitor blocks system emergency shutdown Status in gnome-session package in Ubuntu: Opinion Status in linux package in Ubuntu: New Status in ptyxis package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Ptyxis on 26.04 introduced new feature from upstream https://gitlab.gnome.org/chergert/ptyxis/-/merge_requests/123#note_2569421 The ptyxis will create a systemd inhibitor to block shutdown process from all users including privileged users. Step to reproduce: 1. Launch a ptyxis terminal 2. run a random foreground command such as "less or top" 3. observe result of command "systemd-inhibitor --list" as below to confirm a inhibitor been created user 1000 user 4811 gnome-session-s shutdown user session inhibited block 4. trigger a critical thermal zone by following command in a root console "echo 200000 > /sys/class/thermal/thermal_zone0/emul_temp" Please note that the critical temperature may be varied per OEM bios setup Expected result: The system should perform emergency shutdown immediately due to critical temperature Actual result: System stays up and running, and following kernel message appears kernel: thermal thermal_zone0: acpitz: critical temperature reached kernel: reboot: HARDWARE PROTECTION shutdown (Temperature too high) Summary: The system inhibitor created by Ptyxis should not block emergency shutdown or from a privileged user. Although there is a configuration to turn of the ptyxis behavior not to create a system inhibitor, however this is not current default setting. Potential fix: [1] The default setting on Fedora is now set to false not to create systemd inhibitor as a shorten mitigation https://discussion.fedoraproject.org/t/cant-shutdown-with-systemctl-command-anymore/189839 [2] kernel shutdown command should add parameters to by pass inhibitor blocks as permanent solution. such as "systemctl poweroff -i" ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: ptyxis 50.1-1ubuntu2 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Oct 20 11:45:40 2026 InstallationDate: Installed on 2026-07-06 (106 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) SourcePackage: ptyxis UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2171467/+subscriptions

[Bug 2171463] Re: audio issues via HDMI

I can reproduce the same HDMI audio stuttering issue on a MacBook Pro (Mid 2014) running Ubuntu 26.04.1. - Intel HDMI audio controller: 8086:0a0c - Kernels tested: 7.0.0-34-generic and 7.0.0-38-generic - Both kernels exhibit the same HDMI audio stuttering. - The internal speakers work normally. - The TV is correctly detected, with valid ELD information. - PipeWire repeatedly logs: `spa.alsa: hdmi:1p: snd_pcm_avail after recover: Broken pipe` - `pw-top` ERR increases during HDMI playback. - Tested `snoop=0` and `position_fix=0`, `1`, `2`, and `6`; the issue persists. This appears consistent with the reported unstable DMA position handling in the Intel Haswell HDMI audio driver. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171463 Title: audio issues via HDMI Status in linux package in Ubuntu: New Bug description: /home/flavio/audio_hdmi/informe_bug.md /home/flavio/audio_hdmi/testar.sh /home/flavio/audio_hdmi/tono440.wav /home/flavio/audio_hdmi/tono441.wav - Problem: HDMI audio cuts out constantly (robotic sound), while the analog output on the same machine—using the same stream—sounds perfect. Furthermore, the same cable/port provides clear audio in Windows, ruling out both the cable and the monitor. - Reproduction: Running `pw-play --target alsa_output.pci-0000_00_03.0.hdmi-stereo tono441.wav` shows the `trigger_time` changing 8–10 times per second (cycling through RUNNING → XRUN → SETUP); using `aplay` directly results in an `EIO` error on the first write. - Key log entry: `spa.alsa: hdmi:1p: snd_pcm_avail after recover: EPIPE (Broken pipe)` - Measurements: `hw_params` sets a buffer of 32,768 samples, but the pointer bounces back at ~8,192, regressing ~15 times over 2 seconds (e.g., 8232 → 48). This results in 126 anomalies per second, which aligns with the 860 `ERR` count reported by `pw-top`. The analog driver, by contrast, shows 0 anomalies. - Environment: Ubuntu 26.04.1, kernel 7.0.0-38.38, X240 with BIOS GIET99WW, 8086:0a0c Haswell HDMI, PipeWire 1.6.2-1ubuntu1.2; ELD is stable, PCI power management is ruled out (`runtime_suspend_time=0`), and the issue is unrelated to resampling. - Workarounds tested: Setting `quantum` to 4096 (no change); `power_save=0` (already applied). ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: flavio 6833 F.... wireplumber /dev/snd/controlC0: flavio 6833 F.... wireplumber /dev/snd/seq: flavio 6824 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 19 22:35:59 2026 InstallationDate: Installed on 2026-09-25 (25 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: LENOVO 20AMS19100 ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=3bc1e362-ec2c-4bb4-96c1-189873600ba3 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2020 dmi.bios.release: 2.49 dmi.bios.vendor: LENOVO dmi.bios.version: GIET99WW (2.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AMS19100 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrGIET99WW(2.49):bd03/17/2020:br2.49:efr1.17:svnLENOVO:pn20AMS19100:pvrThinkPadX240:rvnLENOVO:rn20AMS19100:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AM_BU_Think_FM_ThinkPadX240:pfaThinkPadX240: dmi.product.family: ThinkPad X240 dmi.product.name: 20AMS19100 dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171463/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-meta/6.8.0-149.149)

All autopkgtests for the newly accepted linux-meta (6.8.0-149.149) for noble have finished running. The following regressions have been reported in tests triggered by the package: bpftrace/0.20.2-1ubuntu4.3 (amd64) dkms/3.0.11-1ubuntu13 (amd64, arm64, i386, ppc64el, s390x) dpdk-kmods/0~20230205+git-1 (amd64) initramfs-tools/0.142ubuntu25.8 (arm64, ppc64el) libvirt/unknown (amd64) snapd/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/noble/update_excuses.html#linux-meta [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions

[Bug 2172194] Re: ext4/fscrypt memory corruption after online "tune2fs -O encrypt" — please backport "ext4: don't enable large folios on encrypted inodes" (7.0.0-38)

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2172194 Title: ext4/fscrypt memory corruption after online "tune2fs -O encrypt" — please backport "ext4: don't enable large folios on encrypted inodes" (7.0.0-38) Status in linux package in Ubuntu: New Bug description: Kernel: 7.0.0-38-generic (Ubuntu 26.04, linux-image-generic 7.0.0-38.38) Enabling the ext4 "encrypt" feature with tune2fs on a mounted filesystem and then writing through an fscrypt v2 policy corrupts kernel memory ("Bad pagetable" oopses, then a fault in aes_xts_encrypt_* under fscrypt_encrypt_pagecache_blocks <- ext4_bio_write_folio, then panic). Reproduced in seconds in a plain QEMU VM on an untainted kernel; hit two bare-metal machines as well. Unmount/remount after tune2fs avoids it. Reproducer: truncate -s 4G /root/t.img && mkfs.ext4 -q -F /root/t.img mkdir -p /mnt/t && mount -o loop /root/t.img /mnt/t tune2fs -O encrypt "$(findmnt -n -o SOURCE /mnt/t)" # no remount mkdir /mnt/t/enc # then add a v2 key + v2 policy, e.g. fscryptctl dd if=/dev/zero of=/mnt/t/enc/z bs=16M count=64 conv=fsync Upstream (Eric Biggers, linux-ext4/linux-fscrypt, 2026-10-25) says this is fixed in 7.2 by "ext4: don't enable large folios on encrypted inodes": https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-7.2.y&id=40554d1221e3d2ff2e0d192b74a05d89eb3620e7 7.0 upstream is EOL, so please carry this fix in the Ubuntu 7.0 kernel. The 7.0.0-38 changelog does not include it. Full oops logs (pstore, two machines) available on request. Environment: /proc/version_signature: Ubuntu 7.0.0-38.38-generic 7.0.14 Release: Ubuntu 26.04.1 LTS Package: linux-image-7.0.0-38-generic 7.0.0-38.38 e2fsprogs: 1.47.2 Expected: writes through an fscrypt policy work normally (as they do after an unmount/remount following tune2fs -O encrypt). Actual: kernel memory corruption within seconds, then panic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172194/+subscriptions

[Bug 2172197] Re: [amdgpu] RX 9060 XT: green flickering and horizontal artifacts at 1440p 180 Hz, absent so far at 120 Hz

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2172197 Title: [amdgpu] RX 9060 XT: green flickering and horizontal artifacts at 1440p 180 Hz, absent so far at 120 Hz Status in linux package in Ubuntu: New Bug description: Summary Green flickering and horizontal stripes appear across multiple applications on Ubuntu 26.04.1 LTS with a Radeon RX 9060 XT and a Xiaomi 27-inch monitor connected via DisplayPort at 2560x1440 180 Hz. Switching the Ubuntu desktop appearance/theme triggers the same artifacts. After switching only the refresh rate to approximately 120 Hz, the display appears normal. This is a short observation, not yet a long-duration stability test. Steps to reproduce 1. Start the Ubuntu GNOME Wayland session. 2. Set the DisplayPort monitor to 2560x1440 at 180 Hz, fixed refresh (VRR is not selected). 3. Open applications such as Chrome, Discord, LimCore, or the ChatGPT desktop application. 4. Switch the Ubuntu desktop theme/appearance and observe the display. Actual result Green flickering and horizontal stripe artifacts in multiple applications. Expected result No image corruption when using the monitor's advertised 180 Hz mode or switching desktop appearance. Workaround tested Use 2560x1440 at 119.9976 Hz instead of 179.9996 Hz. Artifacts appear to stop. Resolution, scale (100%), and VRR selection were not changed. Intermediate refresh rates have not been tested. Environment Ubuntu 26.04.1 LTS (resolute) Kernel: 7.0.0-38-generic, package 7.0.0-38.38 /proc/version_signature: Ubuntu 7.0.0-38.38-generic 7.0.14 GPU: Sapphire AMD Radeon RX 9060 XT, 16 GB (Navi 44 / gfx1200) PCI ID: 1002:7590, subsystem 1da2:a493, revision c0 Kernel driver: amdgpu Mesa: 26.0.8-1ubuntu0.3 GNOME Shell: 50.1-0ubuntu1.4 Mutter common: 50.1-0ubuntu2.5 linux-firmware: 20260319.git217ca6e4.1ubuntu Session: Ubuntu GNOME on Wayland Monitor: Xiaomi Corporation 27-inch / Mi Monitor Connection: DP-1, DisplayPort Resolution: 2560x1440, scale 1.0 Affected mode: 179.9996 Hz, fixed refresh Workaround mode: 119.9976 Hz, fixed refresh Additional investigation - Rounded Window Corners Reborn version 25 initially generated errors. Disabling it appeared to help briefly, but artifacts returned when switching the desktop theme. - The issue persisted after logging out and back in with this extension disabled, so it does not depend solely on stale extension state. - Other enabled extensions: Ubuntu Dock, Desktop Icons NG, Tiling Assistant. A session with all extensions disabled has not been tested. - Discord uses native Wayland; the ChatGPT desktop application uses X11/XWayland. Both were affected. - GPU temperatures sampled during investigation were approximately 32-35 degrees Celsius; no load or VRAM stress test was run. - No GPU reset, ring timeout, or GPU VM fault was found in the inspected current/previous boot logs. - Repeated kernel warnings were observed: workqueue: dm_handle_vmin_vmax_update [amdgpu] hogged CPU for >10000us ... consider switching to WQ_UNBOUND. Their relationship to the visible corruption is unconfirmed. - No alternate DisplayPort cable, GPU port, or monitor has been tested. Driver/compositor and physical display-link causes have not yet been distinguished. - No screenshot or video of the corruption is available yet. Suggested initial component: linux (amdgpu display); please reassign if investigation points to Mutter or Mesa. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172197/+subscriptions

[Bug 2172227] Re: USB-C external monitor not detected after upgrade to Ubuntu 26.04; restored by full power reset

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2172227 Title: USB-C external monitor not detected after upgrade to Ubuntu 26.04; restored by full power reset Status in linux package in Ubuntu: New Bug description: ## System information - Laptop: HP ZBook Firefly 14 inch G11 A Mobile Workstation PC - GPU: AMD HawkPoint1 (1002:1900), using `amdgpu` - BIOS: W82 Ver. 01.09.02 (2026-08-21) - OS: Ubuntu 26.04, upgraded from Ubuntu 24.04 - Kernels tested: 7.0.0-38-generic and 7.0.0-31-generic - Session: GNOME Wayland - External monitor: Ilyama monitor connected via USB-C, with integrated USB dock ## Problem The external monitor was no longer detected via USB-C after upgrading from Ubuntu 24.04 to Ubuntu 26.04. The same configuration had worked before the upgrade. USB keyboard and mouse connected to the monitor's integrated dock continued to work. Connecting the monitor directly via HDMI also worked. ## Diagnostics while the display was not working All external DisplayPort connectors under `/sys/class/drm/` reported `disconnected`. Only the internal display (`card1-eDP-1`) reported `connected`. Further Diagnostics: - `/sys/class/typec/` was empty. - The ACPI device `USBC000:00` existed with modalias `acpi:USBC000:PNP0CA0:` and ACPI status `15`. - The modules `ucsi_acpi`, `typec_ucsi`, `typec`, and `thunderbolt` were loaded. - The `ucsi_acpi` driver was not bound to `USBC000:00`. - Attempting to bind it manually returned `No such device (os error 19)`. - Setting `driver_override` to `ucsi_acpi` and repeating the bind attempt produced the same error. - Reloading `ucsi_acpi` did not change the result. - The kernel log contained entries for the HP UCSI ACPI tables but no further UCSI-specific messages. The kernel log also contained an `amdgpu` warning: ``` REG_WAIT timeout 1us * 100 tries - dcn31_program_compbuf_size line:141 ``` ## Tests and recovery Rebooting with the older Ubuntu kernel `7.0.0-31-generic` did not restore the USB-C display. The problem was also present with `7.0.0-38-generic`. A full power reset of the laptop (disconnecting external power, pressing power button for 15 seconds), restored the USB-C display. ## Diagnostics after recovery With the external monitor working again: ``` /sys/class/drm/card1-DP-2/status: connected /sys/class/drm/card1-eDP-1/status: connected ``` However: - `/sys/class/typec/` remained empty. - `USBC000:00` remained unbound to any driver. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: josias 9084 F.... wireplumber /dev/snd/controlC0: josias 9084 F.... wireplumber /dev/snd/seq: josias 9064 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 26 13:02:18 2026 InstallationDate: Installed on 2024-10-04 (752 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) MachineType: HP HP ZBook Firefly 14 inch G11 A Mobile Workstation PC ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro amdgpu.dcdebugmask=0x10 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-10-19 (7 days ago) dmi.bios.date: 08/21/2026 dmi.bios.release: 9.2 dmi.bios.vendor: HP dmi.bios.version: W82 Ver. 01.09.02 dmi.board.name: 8C6F dmi.board.vendor: HP dmi.board.version: KBC Version 04.55.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 4.85 dmi.modalias: dmi:bvnHP:bvrW82Ver.01.09.02:bd08/21/2026:br9.2:efr4.85:svnHP:pnHPZBookFirefly14inchG11AMobileWorkstationPC:pvrSBKPFV3:rvnHP:rn8C6F:rvrKBCVersion04.55.00:cvnHP:ct10:cvr:skuA3YW4ET#ABH:pfa103C_5336ANHPZBook: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Firefly 14 inch G11 A Mobile Workstation PC dmi.product.sku: A3YW4ET#ABH dmi.product.version: SBKPFV3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172227/+subscriptions

[Bug 2172229] Re: AppArmor: profile attachment fails for diff-encoded xmatch DFAs (leftmatch_fb ignores MATCH_FLAG_DIFF_ENCODE) - firefox profile never attaches

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2172229 Title: AppArmor: profile attachment fails for diff-encoded xmatch DFAs (leftmatch_fb ignores MATCH_FLAG_DIFF_ENCODE) - firefox profile never attaches Status in linux package in Ubuntu: New Bug description: [Impact] Profiles whose attachment pattern compiles to a differentially encoded DFA never attach. The exec stays "unconfined", and because no conflict is involved, nothing is audited. Visible example: /etc/apparmor.d/firefox (from the apparmor package) profile firefox /{usr/lib/firefox{,-esr,-beta,-devedition,-nightly},opt/firefox}/firefox{,-esr,-bin} flags=(unconfined) { userns, ... } never attaches to /usr/lib/firefox/firefox-bin (Firefox .deb from packages.mozilla.org). Firefox therefore runs unconfined and is moved to unprivileged_userns, which denies CAP_SYS_ADMIN. Its content sandbox loses user-namespace isolation: apparmor="AUDIT" operation="userns_create" info="Userns create - transitioning profile" profile="unconfined" comm="firefox-bin" target="unprivileged_userns" execpath="/usr/lib/firefox/firefox-bin" apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" comm="firefox-bin" capability=21 capname="sys_admin" ps -eo label,args shows "unconfined" for every firefox-bin process, although "firefox (unconfined)" is loaded. [Cause] security/apparmor/match.c: leftmatch_fb(), used by aa_dfa_leftmatch() and therefore by find_attach(), takes the default transition as if (check[pos] == state) state = next[pos]; else state = def[state]; and moves on to the next input character. It does not handle MATCH_FLAG_DIFF_ENCODE. match_char(), used by aa_dfa_match() for file rules, does: for a diff-encoded state it follows def[state] and retries the SAME character. apparmor_parser emits diff-encoded DFAs by default whenever the kernel advertises policy/diff_encode (it does), so larger attachment patterns end in a non-accepting state. File rules are not affected, since they go through match_char(). Simple attachments (plain paths, "/a/{b,c}/x", "/a/x{,-y}", "/{,usr/}{,s}bin/unix_chkpwd") still attach. Larger or nested alternations fail. [Test case] The attached aa-repro.sh (run as root) loads the firefox profile's attachment pattern, relocated to a scratch directory, twice: once with default options and once with "-O no-diff-encode". It then executes a copy of dash under each path and prints /proc/$$/attr/current. Expected: enc -> repro_enc (unconfined) noenc -> repro_noenc (unconfined) Actual: enc -> unconfined noenc -> repro_noenc (unconfined) The two profiles differ only in diff encoding. Reproduced on the stock 7.0.0-38-generic kernel (output attached as repro- output-7.0.0-38-generic.txt). Further confirmation: Ubuntu's real firefox profile does not attach, while a copy with the simpler attachment /usr/lib/firefox/firefox{,-bin} does. [Workarounds] - Set "Optimize=no-diff-encode" in /etc/apparmor/parser.conf and reload all profiles. - Alternatively, add a local profile with a simpler attachment, e.g. /usr/lib/firefox/firefox{,-bin}. [Suggested fix - untested] In leftmatch_fb(), compute the input byte first (c = equiv[(u8) *str++] or (u8) *str++), then replace the open-coded transition with match_char(state, def, base, next, check, c), as aa_dfa_match() does. The is_loop() history and longest-left count logic should then be reviewed for diff-encoded default chains. Upstream report: https://gitlab.com/apparmor/apparmor- kernel/-/work_items/8 [Environment] Ubuntu 26.04.1 LTS (resolute) linux-image-7.0.0-38-generic 7.0.0-38.38 (/proc/version_signature: Ubuntu 7.0.0-38.38-generic 7.0.14) apparmor / libapparmor1 5.0.2-0ubuntu1~26.04.1 firefox 158.0.1~build1 (packages.mozilla.org) /sys/kernel/security/apparmor/features/policy/diff_encode: yes --- ProblemType: Bug ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: invarianz 1478 F.... wireplumber /dev/snd/controlC1: invarianz 1478 F.... wireplumber /dev/snd/seq: invarianz 1454 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 26.04 InstallationDate: Installed on 2026-06-27 (121 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 30DH00H7GE Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=3c69bedc-0154-4019-a8e3-99860442ddb8 ro quiet splash ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 RebootRequiredPkgs: Error: path contained symlinks. Tags: resolute wayland-session Uname: Linux 7.0.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sudo users _MarkForUpload: True dmi.bios.date: 03/21/2025 dmi.bios.release: 1.94 dmi.bios.vendor: LENOVO dmi.bios.version: S08KT5EA dmi.board.name: 1048 dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN 3305348596304 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrS08KT5EA:bd03/21/2025:br1.94:efr1.12:svnLENOVO:pn30DH00H7GE:pvrThinkStationP340:rvnLENOVO:rn1048:rvrSDK0T08861WIN3305348596304:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_30DH_BU_Think_FM_ThinkStationP340:pfaThinkStationP340: dmi.product.family: ThinkStation P340 dmi.product.name: 30DH00H7GE dmi.product.sku: LENOVO_MT_30DH_BU_Think_FM_ThinkStation P340 dmi.product.version: ThinkStation P340 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172229/+subscriptions

[Bug 2160493] Re: ubuntu_bpf failed to build in noble (error: redefinition of 'stack_load_preserves_const_precision')

This bug is awaiting verification that the linux-ibm-gt- tdx/6.8.0-1067.72+tdx1 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-ibm-gt-tdx' to 'verification-done-noble-linux-ibm-gt-tdx'. If the problem still exists, change the tag 'verification-needed-noble-linux-ibm-gt-tdx' to 'verification-failed-noble-linux-ibm-gt-tdx'. 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-ibm-gt-tdx-v2 verification-needed-noble-linux-ibm-gt-tdx -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160493 Title: ubuntu_bpf failed to build in noble (error: redefinition of 'stack_load_preserves_const_precision') Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: On kernel generic 6.8.0-136.136 ubuntu_bfp build fails with: 16592 CLNG-BPF [test_progs] verifier_search_pruning.bpf.o 16593 CLNG-BPF [test_progs] verifier_sock.bpf.o 16594 CLNG-BPF [test_progs] verifier_spill_fill.bpf.o 16595 progs/verifier_spill_fill.c:780:14: error: redefinition of 'stack_load_preserves_const_precision' 16596 780 | __naked void stack_load_preserves_const_precision(void) 16597 | ^ 16598 progs/verifier_spill_fill.c:626:14: note: previous definition is here 16599 626 | __naked void stack_load_preserves_const_precision(void) 16600 | ^ 16601 progs/verifier_spill_fill.c:855:14: error: redefinition of 'stack_load_preserves_const_precision_subreg' 16602 855 | __naked void stack_load_preserves_const_precision_subreg(void) 16603 | ^ 16604 progs/verifier_spill_fill.c:701:14: note: previous definition is here 16605 701 | __naked void stack_load_preserves_const_precision_subreg(void) 16606 | ^ 16607 2 errors generated. 16608 make[1]: Leaving directory '/var/tmp/bpf_build/linux/tools/testing/selftests/bpf' 16609 make[1]: *** [Makefile:637: /var/tmp/bpf_build/linux/tools/testing/selftests/bpf/verifier_spill_fill.bpf.o] Error 1 16610 make: Leaving directory '/var/tmp/bpf_build/linux/tools/testing/selftests' 16611 make: *** [Makefile:181: all] Error 2 Full log: http://ktdb.kernel:8080/test_suite_full_console_log/?test_suite_run_id=2778653#log_16616 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2160493/+subscriptions

[Bug 2162917] Re: Backport: "mm/gup: fix GUP-fast fallback for NULL-mapping order-0 folios"

This bug is awaiting verification that the linux-ibm-gt- tdx/6.8.0-1067.72+tdx1 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-ibm-gt-tdx' to 'verification-done-noble-linux-ibm-gt-tdx'. If the problem still exists, change the tag 'verification-needed-noble-linux-ibm-gt-tdx' to 'verification-failed-noble-linux-ibm-gt-tdx'. 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-ibm-gt-tdx-v2 verification-needed-noble-linux-ibm-gt-tdx -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162917 Title: Backport: "mm/gup: fix GUP-fast fallback for NULL-mapping order-0 folios" Status in linux package in Ubuntu: Fix Released Status in linux-nvidia package in Ubuntu: Invalid Status in linux-nvidia-bos package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-nvidia source package in Noble: Fix Committed Status in linux-nvidia-bos source package in Noble: Invalid Status in linux source package in Resolute: Fix Committed Status in linux-nvidia source package in Resolute: Fix Released Status in linux-nvidia-7.0 source package in Resolute: Invalid Status in linux-nvidia-bos source package in Resolute: Fix Released Status in linux source package in Stonking: Fix Released Status in linux-nvidia source package in Stonking: Invalid Status in linux-nvidia-bos source package in Stonking: Invalid Bug description: SRU Justification [Impact] There is a performance regression seen for calls to get_user_pages() on single-page NULL-mapping folios, introduced by commit f002882ca369 ("mm: merge folio_is_secretmem() and folio_fast_pin_allowed() into gup_fast_folio_allowed()"). When either CONFIG_SECRETMEM=y, or when the folio is a long-term writable pin, the current implementation requires that the mapping be checked as either a secretmem mapping or a file-backed one. If it is either, or if the mapping is NULL, the slow path is forced. However, when the mapping is NULL, the folio cannot be a secretmem mapping. Thus, as long as the folio is NOT a long-term writable pin, the fast path can still be used. This performance regression was initially observed during GPU Direct Storage (GDS) workloads. [Fix] The upstream commit c494788faffe ("mm/gup: fix GUP-fast fallback for NULL-mapping order-0 folios") resolves the performance regression by changing gup_fast_folio_allowed() to allow the fast path for the case described above, where the folio is NOT a long-term writable pin and its mapping field is NULL. [Test Plan] Build and boot tested. The performance regression and subsequent fix can be verified with a GDS workload. The original bug report also describes a test kernel module that uses the `alloc_page` + `vm_insert_page` + `pin_user_pages_fast(..., FOLL_WRITE, ...)` functions to emulate GDS behavior, and using `get_user_pages_fast_only()` on that to validate that the fast path is now allowed in this scenario. [Where problems could occur] The fix affects the get_user_pages*() path of the mm subsystem, which is used heavily. The fix has been reviewed and applied in upstream Linux. ------------------------------------------------------- Original report: Clean cherry-pick from linux-next: ``` (cherry picked from commit ae75e88d8c258fd849de594e7d468b5263e7b3e3 linux-next) ``` John Hubbard, Acked-by David Hildenbrand, applied by Andrew Morton. [Lore thread](https://lore.kernel.org/all/20260708005745.164928-1-jhubbard@nvidia.com/). ## Problem `f002882ca369` (present on this branch) made `gup_fast_folio_allowed()` bail to the slow path for *any* order-0 folio with a NULL `->mapping` when `CONFIG_SECRETMEM=y`. Pages from `alloc_page()` + `vm_insert_page()` legitimately have a NULL mapping, so every `pin_user_pages_fast()` over such a range misses the fast path — nvidia-fs (GPUDirect Storage) allocates its shadow buffers exactly this way. The NULL check was meant to catch truncated file-backed pages, not secretmem. Secretmem folios are published via `filemap_add_folio()`, which always sets `->mapping`, so a NULL mapping proves the folio is *not* secretmem. Returning `!reject_file_backed` keeps long-term writable pins on the slow path and restores the fast path otherwise — exactly the pre-`f002882ca369` behaviour. `CONFIG_SECRETMEM=y` on amd64 and arm64, so this is live on every flavour we ship. ## Measurement (GH200, 288 cores) A module reproducing the nvidia-fs pattern (`alloc_page` + `vm_insert_page`, then `pin_user_pages_fast(..., FOLL_WRITE, ...)`), with an anonymous-memory control the patch cannot affect. `get_user_pages_fast_only()` gives the GUP-fast verdict directly: **0/N unpatched, N/N patched**. Median ns/page, 512 pages/thread, 5 reps: | threads | 4K unpatched → patched | 64K unpatched → patched | |--------:|-----------------------:|------------------------:| | 1 | 34 → 34 (1.0x) | 33 → 30 (1.1x) | | 8 | 74 → 33 (**2.2x**) | 1920 → 31 (**62x**) | | 32 | 95 → 33 (**2.9x**) | 4792 → 33 (**145x**) | | 128 | 500 → 218 (noisy) | 16673 → 76 (**219x**) | The anon control held at 30-35 ns/page across all four kernels, so only the affected range moved. Stock `7.0.0-1015-nvidia-64k` independently reproduces the unpatched 64K numbers (8 threads: 1176 vs 37), so this isn't a test-config artefact. Single-threaded it's a wash; the win is under concurrency. `perf` on the unpatched 64K kernel shows the slow path is ~90% lock contention (`queued_spin_lock_slowpath` 72%), gone entirely once patched — contention that scales with thread count, not a fixed per-page cost. ## Risk Low. One line in a static function with three callers, all in GUP-fast. Only `reject_file_backed == false && check_secretmem && mapping == NULL` changes behaviour; long-term writable pins are untouched. A secretmem folio caught mid-truncate can't happen here: `secretmem_setattr()` refuses to shrink, there's no `.fallocate` (so no punch-hole), and `secretmem_migrate_folio()` returns `-EBUSY`. Only inode eviction remains, which requires every VMA gone — no VMA, no PTE for GUP-fast to walk. Raised by David Hildenbrand on v1 and resolved before he Acked. ## Testing Applies cleanly; built arm64 4K/64K and x86_64, no new warnings; verified in the binary (unpatched `mov w0, #0x0` vs patched `eor w0, w0, #0x1`); benchmarked as above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162917/+subscriptions

[Bug 2165732] Re: [UBUNTU 24.04] kernel: CPU hotplug unsupported by CPUMF

This bug is awaiting verification that the linux-ibm-gt- tdx/6.8.0-1067.72+tdx1 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-ibm-gt-tdx' to 'verification-done-noble-linux-ibm-gt-tdx'. If the problem still exists, change the tag 'verification-needed-noble-linux-ibm-gt-tdx' to 'verification-failed-noble-linux-ibm-gt-tdx'. 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-ibm-gt-tdx-v2 verification-needed-noble-linux-ibm-gt-tdx -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2165732 Title: [UBUNTU 24.04] kernel: CPU hotplug unsupported by CPUMF Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux source package in Resolute: Fix Committed Bug description: [Impact] s390/cpum_cf: Handle CPU hotplug via prepare/dead callbacks The command 'perf stat -e cycles -- <command>' crashes the kernel when CPUs are hotplug added during that run. Root cause is the allocation of struct cpu_cf_events at first event initialization. The allocation is dynamic and the first event that has task context creates such a structure for each online CPU. This is not sufficient. CPUs may be offline during event creation and can be set online during the perf run time. For example commands # echo 0 > /sys/devices/system/cpu/cpu1/online # perf stat -e cycles -i -- stress-ng -t10s --matrix X # sleep 1 # echo 1 > /sys/devices/system/cpu/cpu1/online create an event for CPUs 0,2-X. Since the events are created with task-context, the scheduler will eventually schedule the program on CPU1. This CPU has not created and initialized any per CPU event infrastructure as that CPU was not online at the time of the perf invocation. Thus when the scheduler runs stress-ng on CPU1, the function cpumf_pmu_add() refers to a NULL pointer: struct cpu_cf_events *cpuhw = this_cpu_cfhw(); This function call is invoked after the task stress-ng has been made runnable on CPU1. And this_cpu_cfhw() returns NULL. The result is a panic. The issue arises only in per-task context when the CPUMF facility is used and the scheduler picks a random CPU for such a process to run on. The scheduler enables the CPUMF infrastructure via PMU callback functions pmu::add() and pmu::del(). Introduce a CPU hotplug prepare/dead callback pair which creates and removes the per CPU counter data while the CPU is offline. Count the users which track every CPU (cpu == -1), that is perf_event_open() events with task context and /dev/hwctr device sessions, in the new counter cpu_cf_root::tskcnt, protected by pmc_reserve_mutex. This ensures the infrastructure is available when new CPU is selected to run the per-task context process. In cpum_cf_free_root() and cpum_cf_free_cpu() ensure the reference pointer to data structures is set to NULL before the data is freed to prevent interrupt handlers to access stale data. [Fix] Backport commit: - 337bd95507a1 ("s390/cpum_cf: Handle CPU hotplug via prepare/dead callbacks") [Test Plan] Run the following commands: # echo 0 > /sys/devices/system/cpu/cpu1/online # perf stat -e cycles -i -- stress-ng -t10s --matrix X # sleep 1 # echo 1 > /sys/devices/system/cpu/cpu1/online [Regression Potential] The change is confined to arch/s390/kernel/perf_cpum_cf.c, affecting only s390 systems using the CPU-Measurement Counter Facility PMU. It reworks locking and reference counting and adds two new CPU hotplug callbacks that now run on every hotplug transition on affected systems. A bookkeeping mismatch in the new tskctx counter or a lock-ordering error could reintroduce use-after-free or refcount bugs similar to the one being fixed. --- Description: kernel: CPU hotplug unsupported by CPUMF Symptom: The kernel crashes with a panic when CPU hotplug add is triggered during execution of command 'perf stat -- <command>' on LPAR. z/VM is not affected. Problem: CPU hotplug add does not allocate memory and does not initialise per-CPU variables required by the PMU device driver. Reproduction: Run the following commands # echo 0 > /sys/devices/system/cpu/cpu1/online # perf stat -e cycles -i -- stress-ng -t10s --matrix X # sleep 1 # echo 1 > /sys/devices/system/cpu/cpu1/online Solution: Install CPU hotplug handler function to support CPU hotplug add and delete operations. Upstream-ID: ddd52d6c635a2dc628a238c637d928425b0e3f53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2165732/+subscriptions

Updates to our Terms of Service and Privacy Policy

Hi Andy,   We’re constantly looking for ways to improve the Dropbox experience with new feature offerings and to ensure that our policies explain how our services work. So we’re letting you know about a few updates to our Terms of Service and Privacy Policy. Here’s a summary of the key changes:   Terms of Service We will begin allowing users to access multiple individual and team workspaces with a single account. We’ve revised our Terms to explain what it means if you use this feature. We’ve clarified that Dropbox may now only be used by those over 18. We’ve updated our policies on refunds, the notice period for changes to our fees, and users’ obligations if they don’t agree to updates to our Terms of Service. We’ve changed the time period of inactivity required before we may terminate non-paying accounts to 6 consecutive months. We’ll continue to provide notice before doing so. We’ve clarified what happens if you use your corporate email address to join a non-Team plan.    Privacy Policy We’ve added details on how your data is handled when you access multiple individual and team workspaces with a single account, including clarifying what team admins can see. We’ve further explained our collection and use of your data to better identify what data is being used for which purposes. We’ve included additional details on how to appeal decisions we make about how we handle your data.   Please take a look at the full Terms of Service and Privacy Policy. These will go into effect on January 1, 2027. By maintaining a Dropbox account after this date, you are agreeing to the new Terms. You can also find our previous Terms here. For more details, visit our Help Center.    Thanks!  -The Dropbox Team This email was sent to 0x13121337.sh1t@blogger.com Dropbox, Inc., PO Box 77767, San Francisco, CA 94107

[Bug 2172177] Re: [X1E80100] Yoga Slim 7x internal keyboard broken in 7.3.0-9: i2c-qcom-geni 32 MHz clock regression, needs 8cb5c17be3a2

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2172177 Title: [X1E80100] Yoga Slim 7x internal keyboard broken in 7.3.0-9: i2c-qcom- geni 32 MHz clock regression, needs 8cb5c17be3a2 Status in linux package in Ubuntu: New Bug description: Hardware: Lenovo Yoga Slim 7x 14Q8X9 (83ED), Snapdragon X Elite X1E80100, BIOS NHCN62WW Kernel: 7.3.0-9-generic (Ubuntu 7.3.0-9.9-generic 7.3.0-rc6), Ubuntu 26.10 arm64 The built-in I2C HID keyboard (ITE 048D:8987, i2c-hid at b80000.i2c addr 0x3a) does not work. The touchpad (06CB:CF00) on the same bus is marginal: after repeated access to the keyboard, the whole bus hung with "Bus proto err" until Windows reinitialised the devices. Typical log on 7.3.0-9-generic: i2c_hid_of 3-003a: device did not ack reset within 1000 ms (some boots) i2c_hid_of 3-003a: unexpected HID descriptor bcdVersion (0xffff) hid-generic 0018:FFFF:FFFF: item fetching failed at offset 24/176 i2c_hid_of 3-003a: probe with driver i2c_hid_of failed with error -22 i2c_hid_of 3-003a: i2c_hid_get_input: incomplete report (64/65285) geni_i2c b80000.i2c: Bus proto err, noisy/unexpected start/stop Raw reads with i2ctransfer show valid data that turns to 0xFF at random byte offsets. Regression: - The keyboard WORKS on the Ubuntu 26.04.1 live USB (7.0.0-30-generic) on the same machine. It also works in UEFI and in Windows. - On 7.0.0-30 the bus runs from a 19.2 MHz source clock (gcc_qupv3_wrap0_s0_clk = 19200000). - On 7.3.0-9 it runs from 32 MHz (gcc_qupv3_wrap0_s0_clk = 32000000 for b80000.i2c). The same applies to all other active GENI I2C buses (touchscreen, ps8830 retimers). Cause: upstream commit cb97bf3d4f91 "i2c: qcom-geni: Fix hardcoded clock index in SE_GENI_CLK_SEL" (v7.3-rc5) makes GENI I2C prefer the 32 MHz source clock. The I2C timing is then too tight for this keyboard. Fix: upstream commit 8cb5c17be3a2 "i2c: qcom-geni: Restore the source- clock selection policy" (Abel Vesa, Fixes: cb97bf3d4f91). Its commit message describes the same keyboard/touchpad probe failures on the X1E80100 CRD. It has been queued for stable 7.2.y and 6.18.y. Other users report that it fixes the Yoga Slim 7x keyboard: https://github.com/omacom/omarchy-pkgs/pull/990 Please backport 8cb5c17be3a2 to the 26.10 kernel (and to any other Ubuntu kernels that carry cb97bf3d4f91). Possibly related: hot-plugging a USB-C DP-alt-mode hub freezes the desktop on 7.3.0-9 but not on 7.0.0-30. I will file that separately. ProblemType: Bug DistroRelease: Ubuntu 26.10 Package: linux-image-7.3.0-9-generic 7.3.0-9.9 ProcVersionSignature: Ubuntu 7.3.0-9.9-generic 7.3.0-rc6 Uname: Linux 7.3.0-9-generic aarch64 ApportVersion: 2.36.0-0ubuntu1 Architecture: arm64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: xavier 6136 F.... pipewire xavier 6526 F.... wireplumber /dev/snd/seq: xavier 6136 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 26 03:48:06 2026 InstallationDate: Installed on 2026-10-25 (0 days ago) InstallationMedia: Ubuntu 26.10 "Stonking Stingray" - Official arm64 (20261010) Lspci-vt: -[0004:00]---00.0-[01-ff]----00.0 Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800] -[0006:00]---00.0-[01-ff]----00.0 Micron Technology Inc 2550 NVMe SSD (DRAM-less) MachineType: LENOVO 83ED ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.3.0-9-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro clk_ignore_unused pd_ignore_unused cma=128M efi=noruntime quiet splash console=tty0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 12/02/2025 dmi.bios.release: 1.62 dmi.bios.vendor: LENOVO dmi.bios.version: NHCN62WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76574 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14Q8X9 dmi.ec.firmware.release: 1.63 dmi.modalias: dmi:bvnLENOVO:bvrNHCN62WW:bd12/02/2025:br1.62:efr1.63:svnLENOVO:pn83ED:pvrYogaSlim714Q8X9:rvnLENOVO:rnLNVNB161216:rvrSDK0T76574WIN:cvnLENOVO:ct10:cvrYogaSlim714Q8X9:skuLENOVO_MT_83ED_BU_idea_FM_YogaSlim714Q8X9:pfaYogaSlim714Q8X9: dmi.product.family: Yoga Slim 7 14Q8X9 dmi.product.name: 83ED dmi.product.sku: LENOVO_MT_83ED_BU_idea_FM_Yoga Slim 7 14Q8X9 dmi.product.version: Yoga Slim 7 14Q8X9 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172177/+subscriptions

[Bug 2172182] Re: MSI Prestige 14H B12UCX: I2C-HID touchpad (MSNB0001:00 06CB:CEBD) stops after a few seconds; only stays alive with NVIDIA dGPU forced on

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2172182 Title: MSI Prestige 14H B12UCX: I2C-HID touchpad (MSNB0001:00 06CB:CEBD) stops after a few seconds; only stays alive with NVIDIA dGPU forced on Status in linux package in Ubuntu: New Bug description: Laptop: MSI Prestige 14H B12UCX BIOS: E14F1IMS.11E (also reproduced on E14F1IMS.117) OS: Ubuntu 26.04.1 LTS, kernel 7.0.0-38-generic (also 7.0.0-30) Touchpad: Synaptics I2C-HID, MSNB0001:00 06CB:CEBD, i2c_designware.0 (PCI 00:15.0) GPU: Intel Iris Xe + NVIDIA RTX 2050 (proprietary driver 595) Problem: The touchpad works for a few seconds after boot, then stops responding. It briefly works again after plugging/unplugging the charger or opening a fresh terminal, then stops again. The same touchpad works fine in Windows 11 on this laptop (dual boot). Behaviour by graphics mode (prime-select): - on-demand: works for a few seconds, then dies - intel (dGPU off): touchpad completely dead - nvidia (dGPU always on): touchpad stays alive (only workaround found) Observations when the touchpad is dead: - The kernel and libinput still list the touchpad device - No events from libinput debug-events - /proc/interrupts: the MSNB0001:00 IRQ count does not increase when touching the pad - Reading /dev/hidraw0 returns no data - No errors in dmesg at boot (hid-multitouch binds normally) - Unbind/bind of i2c_hid_acpi fails after it dies: "tigerlake-pinctrl INTC1055:00: pin 62 cannot be used as IRQ" "i2c_hid_acpi i2c-MSNB0001:00: Could not register for MSNB0001:00 interrupt" Things that did NOT help: - BIOS update to E14F1IMS.11E - Forcing runtime PM to "on" for the I2C device, i2c_designware.0 and PCI 00:15.0 - CPU load, and disabling deep C-states (cpuidle state2+) - Reloading i2c_hid_acpi / hid_multitouch modules Similar reports on this model: touchpad dying after ~5-15 seconds on openSUSE, Mint, Fedora and Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: lmnotsmurfing 3694 F.... pipewire lmnotsmurfing 3702 F.... wireplumber /dev/snd/seq: lmnotsmurfing 3694 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 25 20:33:13 2026 InstallationDate: Installed on 2026-10-23 (2 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: Micro-Star International Co., Ltd. Prestige 14H B12UCX ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=c916bbf7-72f4-43fc-96a4-d7d7bf356842 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/28/2024 dmi.bios.release: 1.30 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E14F1IMS.11E dmi.board.asset.tag: Default string dmi.board.name: MS-14F1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE14F1IMS.11E:bd03/28/2024:br1.30:svnMicro-StarInternationalCo.,Ltd.:pnPrestige14HB12UCX:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14F1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku14F1.1:pfaPrestige: dmi.product.family: Prestige dmi.product.name: Prestige 14H B12UCX dmi.product.sku: 14F1.1 dmi.product.version: REV:1.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/2172182/+subscriptions