[РЕШЕНО] Ошибка № ...

вторник

[Bug 2152248] Re: Internal keyboard completely dead (no IRQ 1 interrupts) on Lenovo Yoga Slim 7 Ultra (Meteor Lake)

** 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/2152248 Title: Internal keyboard completely dead (no IRQ 1 interrupts) on Lenovo Yoga Slim 7 Ultra (Meteor Lake) Status in linux package in Ubuntu: New Bug description: The internal keyboard on my Lenovo Yoga Slim 7 Ultra 14IHP11 works in GRUB but is completely unresponsive in Ubuntu 26.04 (tested on both mainline and linux-oem-24.04d kernels). Following a recent BIOS update via Windows, the i8042 controller successfully probes and mounts the keyboard without the Error -5 crashes it had previously. dmesg confirms the mount: [ 0.503092] serio: i8042 KBD port at 0x60,0x64 irq 1 However, evtest and raw TTY terminals register zero input. The driver is loaded, but physical keystrokes trigger no interrupts. This appears to be an ACPI table or IRQ routing issue specific to this Meteor Lake motherboard where IRQ 1 is not reaching the OS. Failed workarounds: i8042 parameters (nopnp, reset, dumbkbd, unlock) irqpoll noapic (causes instant bootloop) pci=nocrs (breaks NVMe storage) ACPI spoofing (acpi_osi="Windows 2020") Unloading ideapad_laptop and intel_vbtn modules 60-second EC hard reset ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: frederik 4735 F.... wireplumber /dev/snd/seq: frederik 4724 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 12 16:28:38 2026 InstallationDate: Installed on 2026-05-12 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 83QK ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=e8997083-b546-4f9c-8043-d73207eb565c ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M i8042.nopnp i8042.reset SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2026 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: SHCN31WW 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 Ultra 14IPH11 dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrSHCN31WW:bd03/18/2026:br1.31:efr1.31:svnLENOVO:pn83QK:pvrYogaSlim7Ultra14IPH11:rvnLENOVO:rnLNVNB161216:rvrSDK0T76574WIN:cvnLENOVO:ct10:cvrYogaSlim7Ultra14IPH11:skuLENOVO_MT_83QK_BU_idea_FM_YogaSlim7Ultra14IPH11:pfaYogaSlim7Ultra14IPH11: dmi.product.family: Yoga Slim 7 Ultra 14IPH11 dmi.product.name: 83QK dmi.product.sku: LENOVO_MT_83QK_BU_idea_FM_Yoga Slim 7 Ultra 14IPH11 dmi.product.version: Yoga Slim 7 Ultra 14IPH11 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152248/+subscriptions

[Bug 2152152] Re: KHO: Failed to reserve lowmem scratch buffer on every boot (Ubuntu 26.04)

** 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/2152152 Title: KHO: Failed to reserve lowmem scratch buffer on every boot (Ubuntu 26.04) Status in linux package in Ubuntu: New Bug description: On every boot/reboot, the kernel logs this error: KHO: Failed to reserve lowmem scratch buffer This appears to be related to the Kexec HandOver (KHO) feature for kernel live updates. System details: - Ubuntu 26.04 LTS - Kernel: 7.0.0-15-generic - kexec-tools is installed but kexec is not configured or in use - The error appears in journalctl logs but system appears to function normally otherwise Steps to reproduce: 1. Boot Ubuntu 26.04 (with kexec-tools installed but not configured) 2. Run: journalctl -b -p err 3. Observe the KHO error message Expected result: No kernel errors on clean boot when kexec is not in use Actual result: KHO lowmem scratch buffer reservation fails during kernel init ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k7.0.0-15-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass Date: Sun May 10 13:36:50 2026 InstallationDate: Installed on 2026-04-26 (15 days ago) InstallationMedia: Ubuntu-Server 26.04 "Resolute Raccoon" - Release amd64 (20260420.1) MachineType: LENOVO 1066AJU ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-15-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro rd.luks.key=/luks/usb_keyfile:UUID=1b6d77f7-1a51-4316-8969-186acf70a5a4 rd.luks.key.tout=30 rd.retry=30 rd.timeout=60 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2011 dmi.bios.release: 1.66 dmi.bios.vendor: LENOVO dmi.bios.version: 44CN42WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.41 dmi.modalias: dmi:bvnLENOVO:bvr44CN42WW:bd09/22/2011:br1.66:efr1.41:svnLENOVO:pn1066AJU:pvrLenovoV570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:skuSystemSKUNumber:pfaHuronRiverSystem: dmi.product.family: HuronRiver System dmi.product.name: 1066AJU dmi.product.sku: System SKUNumber dmi.product.version: Lenovo V570 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152152/+subscriptions

[Bug 2152194] Re: perf_cpu_map__merge fails to compile on ppc46el, s390x on noble linux

Firstly reported (and corrected) by @Stefan Bader (smb) on hwe-next-7.0 ** Project changed: kernel-sru-workflow => linux ** Project changed: linux => linux (Ubuntu) ** 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/2152194 Title: perf_cpu_map__merge fails to compile on ppc46el, s390x on noble linux Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: For some odd reason trying to pass an "(int) * (size_t)" to malloc is throwing an exception in the argument checking for malloc. This only happens on s390x and ppc64el. This results in the following compilation error: tools/lib/perf/cpumap.c, function perf_cpu_map__merge (line 464): cpumap.c:464:20: error: argument 1 range [18446744065119617024, 18446744073709551612] exceeds maximum object size 9223372036854775807 [-Werror=alloc-size-larger-than=] 464 | tmp_cpus = malloc(tmp_len * sizeof(struct perf_cpu)); To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152194/+subscriptions

[Bug 2145171] Re: [SRU] MIPI camera is not working after upgrading to 6.17-oem

This bug is awaiting verification that the linux-azure/6.8.0-1056.62 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-azure' to 'verification-done-noble- linux-azure'. If the problem still exists, change the tag 'verification- needed-noble-linux-azure' to 'verification-failed-noble-linux-azure'. 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-azure-v2 verification-needed-noble-linux-azure -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2145171 Title: [SRU] MIPI camera is not working after upgrading to 6.17-oem Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Deferred Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux source package in Questing: In Progress Status in linux-oem-6.17 source package in Questing: Invalid Status in linux source package in Resolute: Fix Released Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: SRU Justification: [Impact] Upstream v6.18-rc1 commit 4405a214df146775338a1e6232701a29024b82e1 "ACPI: scan: Add Intel CVS ACPI HIDs to acpi_ignore_dep_ids[]" (also backported to v6.17.8, v6.12.58), which in effect reverts a not yet upstreamed Intel MIPI camera patch titled "ACPI: scan: Update HID for new platform" meant for bug 2090932, and therefore they share the same symptom: [ 4.484426] ov02c10 i2c-OVTI02C1:00: chip id mismatch: 560243!=0 [ 4.484432] ov02c10 i2c-OVTI02C1:00: failed to find sensor: -6 [Fix] While this should really be fixed by upstream Intel's CVS driver and remove the two platforms from acpi_ignore_dep_ids, a sauced change is made to preserve the honor effect and yet don't introduce potential conflict with the upstream before any further progress is made. [Test Plan] 1. Install the kernel from -proposed pocket and reboot into it. 2. Check dmesg has no aforementioned error, 3. Make sure the device appears in the gstreamer device enumeration: $ gst-inspect-1.0 icamerasrc ..... device-name : The input devices name queried from HAL flags: readable, writable Enum "GstCamerasrcDeviceName" Default: 0, "ov02c10-uf" (0): ov02c10-uf - ov02c10 as sensor. [Where problems could occur] No. This restores the hardware enablement effort for the affected platforms only. For Ubuntu, CVS driver is always available along with the kernel, and therefore for a device declared _DEP to the two ACPI devices, the driver can be installed either through ubuntu-drivers or through oem meta packages. [Other Info] While this has been backported to v6.17.8, it affects R and Q. And while this has also been backported to v6.12.58, and linux-6.8/noble is tracking stable 6.8 fixes, Noble will be affected soon or later. Nominate for N, Q and R accordingly. ========== original bug report ========== [Summary] During the kernel SRU testing, we found out that 3 xps13-9350 camera-related tests failed. I saw following in dmesg. ov02c10 i2c-OVTI02C1:00: failed to find sensor: -6 [Reproduce steps] 1. Install GM image 2. Run dist-upgrade to upgrade to 6.17-oem kerenl 3. Run checkbox sru test plan or use https://webcamtests.com/ to test the camera [Failure rate] 1/1 [Affected machines] 202507-36962 202407-34215 202407-34216 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.17.0-1014-oem 6.17.0-1014.14 ProcVersionSignature: Ubuntu 6.17.0-1014.14-oem 6.17.13 Uname: Linux 6.17.0-1014-oem x86_64 ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1597 F.... pipewire ubuntu 1600 F.... wireplumber /dev/snd/seq: ubuntu 1597 F.... pipewire CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Mon Mar 23 05:41:57 2026 DistributionChannelDescriptor: # This is the distribution channel descriptor for Ubuntu 24.04 for Dell # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-noble-oem-24.04b-proposed-20241224-151 InstallationDate: Installed on 2026-03-04 (19 days ago) InstallationMedia: Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20241223) IwConfig: lo no wireless extensions. enx00e04ca9f5c8 no wireless extensions. wlp0s20f3 no wireless extensions. MachineType: Dell Inc. XPS 13 9350 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=screen-256color ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-1014-oem root=UUID=6acf835d-3bec-4909-9cf9-8848785f287d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.17.0-1014-oem N/A linux-backports-modules-6.17.0-1014-oem N/A linux-firmware 20240318.git3b128b60-0ubuntu2.26 SourcePackage: linux-oem-6.17 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2024 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 07NFRM dmi.board.vendor: Dell Inc. dmi.board.version: X05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd12/06/2024:br1.7:efr1.16:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07NFRM:rvrX05:cvnDellInc.:ct10:cvr:sku0CC9: dmi.product.family: XPS dmi.product.name: XPS 13 9350 dmi.product.sku: 0CC9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2145171/+subscriptions

[Bug 2143100] Re: Got black screen after clicked logout button

[Bug 2152124] Re: Hard crash of Wayland session (back to login/initramfs screen) when scrolling emails in Thunderbird.

Hi Daniel, As requested, I have attached the prevboot.txt log from a crash that occurred just now. This was reproduced on a clean Ubuntu 26.04 setup (standard session) under the 7.X kernel. Let me know if you need more logs or if there is anything else I should test while I am in this unstable environment. To be more specific: the crash occurred during a Print to PDF operation in Remmina (RDP). I was printing from the remote application to a shared folder in my Ubuntu home directory. The print job seemed to finish, but as soon as I dismissed the 'Open file' dialog, the cursor froze and the system crashed. Interestingly, the PDF file was never actually created on the disk, suggesting the system failed during the I/O or final sync process. I am providing the log form this exact event. Milan ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152124/+attachment/5969673/+files/prevboot.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152124 Title: Hard crash of Wayland session (back to login/initramfs screen) when scrolling emails in Thunderbird. Status in linux package in Ubuntu: Incomplete Bug description: When using Thunderbird under Wayland on Ubuntu 26.04 (Intel GPU, ASUS Zenbook UX310UA), pressing the Up/Down arrow keys to scroll through emails causes an immediate and hard crash of the GNOME Shell / Wayland compositor. The system drops connection to xwayland and crashes back to the disk decryption/login screen. The issue is 100% reproducible on Wayland. Workaround: Switching the session to "Ubuntu on Xorg" completely resolves the issue and Thunderbird works normally. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: gnome-shell 50.1-0ubuntu1 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:32:06 2026 DisplayManager: gdm3 InstallationDate: Installed on 2025-05-25 (350 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3) ProcEnviron: LANG=cs_CZ.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> RelatedPackageVersions: mutter-common 50.1-0ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to resolute on 2026-05-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152124/+subscriptions

[Bug 2144060] Re: ADATA SU680 causes repeated SATA resets and I/O errors on Ubuntu unless link power management is forced to max_performance

This bug is awaiting verification that the linux-azure/6.17.0-1015.15 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-questing-linux-azure' to 'verification-done- questing-linux-azure'. If the problem still exists, change the tag 'verification-needed-questing-linux-azure' to 'verification-failed- questing-linux-azure'. 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-questing-linux-azure-v2 verification-needed-questing-linux-azure -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2144060 Title: ADATA SU680 causes repeated SATA resets and I/O errors on Ubuntu unless link power management is forced to max_performance Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Noble: In Progress Status in linux source package in Questing: In Progress Status in linux source package in Resolute: In Progress Bug description: A Dell Vostro 15 3510 running Ubuntu from an ADATA SU680 1TB SATA SSD (/dev/sda, firmware VE1R910D) experienced repeated storage instability that appears tied to Linux SATA link power management. The detailed evidence is attached in the archive file: sata_adata_bugreport_attachments.zip The attached archive contains the main incident report and supporting evidence files, including SMART output, filtered kernel logs from affected and clean boots, hardware/system identification output, storage-layout output, and SATA power-policy evidence. Observed symptoms included: - repeated WRITE/READ FPDMA QUEUED failures - Emask 0x4 (timeout) and Emask 0x10 (ATA bus error) - irq_stat 0x08000000, interface fatal error - SError: { PHYRdyChg CommWake } - SError: { UnrecovData CommWake Handshk } - ata1: hard resetting link - Sense Key : Aborted Command - I/O error, dev sda, sector ... - abnormal SMART Power_Cycle_Count / Lifetime Power-On Resets growth during normal Ubuntu runtime - one Windows-side symptom where the SATA disk appeared as if GPT/partition metadata might need initialization - user-visible effects including OS slowdowns, temporary hangs/freezes, and application instability This did not look like classic SSD media failure: - SMART overall health stayed PASSED - reallocated sectors stayed 0 - reported uncorrectables stayed 0 - UDMA CRC stayed 0 - reserve space stayed 100 - endurance used stayed 0 - SMART error log stayed empty - a full raw-disk read succeeded - a later extended SMART self-test completed successfully Important power-management evidence: Before the workaround, the observed Linux SATA power-related state was: /sys/class/scsi_host/host0/link_power_management_policy:min_power_with_partial /sys/class/scsi_host/host1/link_power_management_policy:min_power_with_partial /sys/class/block/sda/device/power/control:on The strongest evidence is that the issue stopped immediately after forcing: for f in /sys/class/scsi_host/host*/link_power_management_policy; do echo max_performance | sudo tee "$f" done After that: - SMART power/reset counter stabilized - later long boots became clean - extended SMART self-test passed - system responsiveness improved - earlier freeze/hang behavior stopped being observed This strongly suggests a Linux SATA ALPM / DIPM / AHCI / libata incompatibility with this SSD/platform combination rather than classic SSD NAND/media failure. Expected result: Ubuntu should run normally from the ADATA SU680 without repeated SATA transport resets, SMART reset-counter inflation, transient I/O errors, GPT/metadata instability, or broader runtime instability. Actual result: Under the default Linux storage-power behavior on this system, repeated SATA transport resets and I/O errors occurred across multiple boots, and the SMART reset counter increased during runtime without real reboot/shutdown. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.17.0-14-generic 6.17.0-14.14~24.04.1 ProcVersionSignature: Ubuntu 6.17.0-14.14~24.04.1-generic 6.17.9 Uname: Linux 6.17.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: khaled 2391 F.... wireplumber /dev/snd/seq: khaled 2388 F.... pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 13 00:55:34 2026 InstallationDate: Installed on 2026-03-07 (5 days ago) InstallationMedia: Ubuntu 24.04.4 LTS "Noble Numbat" - Release amd64 (20260210) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 17ef:60ac Lenovo Lenovo 300 Wireless Compact Mouse Bus 001 Device 003: ID 0c45:6730 Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Dell Inc. Vostro 15 3510 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-6.17.0-14-generic root=UUID=06fa0712-9df2-4153-9d2f-abd46d850c25 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.17.0-14-generic N/A linux-backports-modules-6.17.0-14-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.25 SourcePackage: linux-hwe-6.17 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/05/2026 dmi.bios.release: 1.44 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.44.0 dmi.board.name: 00NFD7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.44.0:bd01/05/2026:br1.44:svnDellInc.:pnVostro153510:pvr:rvnDellInc.:rn00NFD7:rvrA00:cvnDellInc.:ct10:cvr:sku0ADB: dmi.product.family: Vostro dmi.product.name: Vostro 15 3510 dmi.product.sku: 0ADB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144060/+subscriptions

[Bug 2152161] [NEW] Ubuntu26.04 - HVPIPE ioctl generates trace and returns failure

You have been subscribed to a public bug: == Comment: #0 - Haren Myneni <hbabu@us.ibm.com> - 2026-05-09 19:31:07 == ---Problem Description--- HVPIPE ioctl generates trace and returns failure ---Steps to Reproduce--- - Open HVPIPE (/dev/papr-hvpipe) - ioctl to get FD for the specific HMC : It should cause oops. ---Debugger--- A debugger is not configured Contact Information = hbabu@us.ibm.com Machine Type = pseries ---uname output--- Ubuntu 26.04 Stack trace output: -- GPR12: 0000000000000000 c00000027fff7f00 0000000000000000 0000000000000000 GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 GPR20: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 GPR24: 0000000000000000 0000000000000007 c000000003de93a8 c000000040aba200 GPR28: 0000000000000007 c00000000395d8b0 0000000002000006 c0000000079c6540 [ 14.466430] NIP [c0000000001f64a0] papr_hvpipe_dev_create_handle+0x280/0x360 [ 14.466437] LR [c0000000001f635c] papr_hvpipe_dev_create_handle+0x13c/0x360 [ 14.466442] Call Trace: [ 14.466444] [c00000004e87fad0] [c0000000001f6338] papr_hvpipe_dev_create_handle+0x118/0x360 (unreliable) [ 14.466450] [c00000004e87fb70] [c0000000001f6638] papr_hvpipe_dev_ioctl+0xb8/0x1c8 [ 14.466455] [c00000004e87fbb0] [c000000000919a14] sys_ioctl+0x174/0x1d0 [ 14.466459] [c00000004e87fc10] [c000000000035e50] system_call_exception+0xf0/0x2d0 [ 14.466464] [c00000004e87fe50] [c00000000000d05c] system_call_vectored_common+0x15c/0x2ec [ 14.466470] ---- interrupt: 3000 at 0x7edb1af6776c [ 14.466474] NIP: 00007edb1af6776c LR: 00007edb1af6776c CTR: 0000000000000000 [ 14.466477] REGS: c00000004e87fe80 TRAP: 3000 Not tainted (7.0.0-14-generic) [ 14.466480] MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR: 44002404 XER: 00000000 [ 14.466490] IRQMASK: 0 GPR00: 0000000000000036 00007edb18dbe020 00007edb1b077000 0000000000000006 GPR04: 000000008004b209 00007edb18dbe124 0600000000000000 00007edb19781190 Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for hbabu@us.ibm.com: -Attach sysctl -a output output to the bug. == Comment: #1 - Haren Myneni <hbabu@us.ibm.com> - 2026-05-09 19:40:33 == This issue is caused by the upstream commit in 7.0 kernel - so inbandRMC use should affect on Ubuntu 26.04. commit 6d3789d347a7af5c4b0b2da3af47b8d9da607ab2 Author: Christian Brauner <brauner@kernel.org> Date: Sun Nov 23 17:33:51 2025 +0100 papr-hvpipe: convert papr_hvpipe_dev_create_handle() to FD_PREPARE() Fixes a UAF for src_info as well. Link: https://patch.msgid.link/20251123-work-fd-prepare-v4-33-b6efa1706cfd@kernel.org Signed-off-by: Christian Brauner <brauner@kernel.org> Ritesh submitted fix upstream and should be expecting in upstream 7.1. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-218892 severity-critical targetmilestone-inin2610 -- Ubuntu26.04 - HVPIPE ioctl generates trace and returns failure https://bugs.launchpad.net/bugs/2152161 You received this bug notification because you are subscribed to linux in Ubuntu.

[Bug 2146027] Re: Virtual Machine Performance Impacted

Updated commentary to include 6.8.0-111-generic ** Description changed: - Here's an ODD 'feature' of kernel 6.8.0 (-106,-107, -110) I'm running - into: + Here's an ODD 'feature' of kernel 6.8.0 (-106,-107,-110,-111) I'm + running into: I run VMware Workstation 17 Pro (17.6.4 build-24832109) and have used "Slices" to Assign Core Affinity for the Host OS, User Apps and VMs: System Slice = SMP Cores 0-3 User Slice = SMP Cores 4-7 This is done in order to maximize the performance of the VMs (CAElinux, Kubuntu, MS Windows 10/11 Pro, etc.) by modding the *.vmx files to map the VMs onto only the upper 4-cores of the processor. It works, Rock Solid (on -101). I've been running VMs in this manner for some time (years) now. When I run on -106 (and now -107) the VMs get REAL 'Choppy' and begin seeing audio breakup and are no longer capable of maximum "Core Utilization" on the upper 4-cores. I've observed the above in both OCCT and applications with 3D graphics and audio being run in both of the Windows VMs (I no longer run MS on Bare Metal). I have attached System Monitor History Screen Captures that illustrate the impact. OS: Kubuntu 24.04.4 (LTS) KDE Plasma: 5.27.12 KDE Frameworks: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.8.0-106-generic (64-bit) Graphics Platform: X11 Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor Memory: 15.7 GiB of RAM Graphics Processor: PITCAIRN Motherboard: Gigabyte Technology Co., Ltd. linux-image-6.8.0-106-generic: Installed: 6.8.0-106.106 Candidate: 6.8.0-106.106 Version table: *** 6.8.0-106.106 500 500 http://us.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu noble-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-106-generic 6.8.0-106.106 ProcVersionSignature: Ubuntu 6.8.0-106.106-generic 6.8.12 Uname: Linux 6.8.0-106-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: tamaster 3442 F.... wireplumber /dev/snd/controlC1: tamaster 3442 F.... wireplumber /dev/snd/seq: tamaster 3438 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Mar 24 11:56:40 2026 InstallationDate: Installed on 2020-10-10 (1991 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-106-generic root=UUID=4918d7fa-4d57-4dc6-a309-1e93b981ad68 ro iommu=soft quiet splash transparent_hugepage=never preempt=full nohz_full=all threadirqs vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-106-generic N/A linux-backports-modules-6.8.0-106-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.25 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-08-30 (571 days ago) dmi.bios.date: 05/28/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd05/28/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2146027 Title: Virtual Machine Performance Impacted Status in linux package in Ubuntu: New Bug description: Here's an ODD 'feature' of kernel 6.8.0 (-106,-107,-110,-111) I'm running into: I run VMware Workstation 17 Pro (17.6.4 build-24832109) and have used "Slices" to Assign Core Affinity for the Host OS, User Apps and VMs: System Slice = SMP Cores 0-3 User Slice = SMP Cores 4-7 This is done in order to maximize the performance of the VMs (CAElinux, Kubuntu, MS Windows 10/11 Pro, etc.) by modding the *.vmx files to map the VMs onto only the upper 4-cores of the processor. It works, Rock Solid (on -101). I've been running VMs in this manner for some time (years) now. When I run on -106 (and now -107) the VMs get REAL 'Choppy' and begin seeing audio breakup and are no longer capable of maximum "Core Utilization" on the upper 4-cores. I've observed the above in both OCCT and applications with 3D graphics and audio being run in both of the Windows VMs (I no longer run MS on Bare Metal). I have attached System Monitor History Screen Captures that illustrate the impact. OS: Kubuntu 24.04.4 (LTS) KDE Plasma: 5.27.12 KDE Frameworks: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.8.0-106-generic (64-bit) Graphics Platform: X11 Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor Memory: 15.7 GiB of RAM Graphics Processor: PITCAIRN Motherboard: Gigabyte Technology Co., Ltd. linux-image-6.8.0-106-generic: Installed: 6.8.0-106.106 Candidate: 6.8.0-106.106 Version table: *** 6.8.0-106.106 500 500 http://us.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu noble-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-106-generic 6.8.0-106.106 ProcVersionSignature: Ubuntu 6.8.0-106.106-generic 6.8.12 Uname: Linux 6.8.0-106-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: tamaster 3442 F.... wireplumber /dev/snd/controlC1: tamaster 3442 F.... wireplumber /dev/snd/seq: tamaster 3438 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Mar 24 11:56:40 2026 InstallationDate: Installed on 2020-10-10 (1991 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-106-generic root=UUID=4918d7fa-4d57-4dc6-a309-1e93b981ad68 ro iommu=soft quiet splash transparent_hugepage=never preempt=full nohz_full=all threadirqs vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-106-generic N/A linux-backports-modules-6.8.0-106-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.25 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-08-30 (571 days ago) dmi.bios.date: 05/28/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd05/28/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146027/+subscriptions

[Bug 2152163] Re: RX 7900 XTX: dcn32_program_compbuf_size REG_WAIT timeout causes system freeze on kernel 7.0.0-15 (RDNA3)

** 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/2152163 Title: RX 7900 XTX: dcn32_program_compbuf_size REG_WAIT timeout causes system freeze on kernel 7.0.0-15 (RDNA3) Status in linux package in Ubuntu: New Bug description: ## Summary System freezes with dcn32_program_compbuf_size REG_WAIT timeout on AMD RX 7900 XTX (RDNA3/Navi31) running kernel 7.0.0-15-generic on Ubuntu 26.04. ## Hardware - CPU: AMD Ryzen 9 9950X3D - GPU: Sapphire PULSE RX 7900 XTX (Navi31, rev c8) - RAM: 64GB - Display: HDMI ## Kernel errors observed amdgpu 0000:03:00.0: [drm] REG_WAIT timeout 1us * 100 tries - dcn32_program_compbuf_size line:147 amdgpu 0000:03:00.0: [drm] REG_WAIT timeout 1us * 100 tries - dcn32_program_compbuf_size line:148 workqueue: dm_handle_vmin_vmax_update [amdgpu] hogged CPU for >10000us 11 times ## Steps to reproduce 1. Boot Ubuntu 26.04 with RX 7900 XTX 2. Use GPU-accelerated applications (browser + VS Code + llama.cpp with ROCm) 3. System freezes within minutes to hours 4. REISUB required to recover ## Attempted workarounds (none fully resolved) - amdgpu.dcfeaturemask=0x8 (partial, reduces frequency) - amdgpu.dcdebugmask=0x10 (no effect) - amdgpu.gpu_recovery=1 (recovery attempt fails) ## Additional context - Bug appears related to DCN32 display compression buffer programming - Triggered more frequently under GPU compute load (ROCm/llama.cpp) - Previously reported upstream: https://gitlab.freedesktop.org/drm/amd/-/issues ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon May 11 09:55:17 2026 InstallationDate: Installed on 2026-05-03 (8 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASRock X870E Nova WiFi ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=5b6bf59c-b6e2-4ba8-8520-45b350ff8bad ro quiet splash amdgpu.dcfeaturemask=0x8 amdgpu.dcdebugmask=0x10 amdgpu.dc=1 amdgpu.abmlevel=0 acpi_enforce_resources=lax module_blacklist=btusb,bluetooth kho=off amdgpu.gpu_recovery=1 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. RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2026 dmi.bios.release: 5.41 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 4.20 dmi.board.asset.tag: Default string dmi.board.name: X870E Nova WiFi dmi.board.vendor: ASRock dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr4.20:bd04/16/2026:br5.41:svnASRock:pnX870ENovaWiFi:pvrDefaultstring:rvnASRock:rnX870ENovaWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: X870E Nova WiFi dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: ASRock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152163/+subscriptions

[Bug 2152256] Re: Kernel Panic on Suspend/Resume - jump_label_patch_code - ASUS TUF Gaming F15 (FX507ZR)

*** This bug is a duplicate of bug 2149963 *** https://bugs.launchpad.net/bugs/2149963 ** This bug has been marked a duplicate of bug 2149963 kernel 7.0.0-14 hangs on s2idle resume with nvidia-open on RTX 50-series (Blackwell); 6.17.0-22 works on same hw -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152256 Title: Kernel Panic on Suspend/Resume - jump_label_patch_code - ASUS TUF Gaming F15 (FX507ZR) Status in linux package in Ubuntu: New Bug description: *** System Environment *** - Laptop: ASUS TUF Gaming F15 (2022) Model FX507ZR - OS: Ubuntu 26.04 (Resolute) - Development Branch - CPU: Intel Core i7-12700H - GPU: NVIDIA GeForce RTX 3070 Laptop GPU - Driver: NVIDIA 595.58 (Proprietary) - Kernel: [Escribe aquí el resultado de poner 'uname -r' en tu terminal] *** Problem Description *** Every time the system attempts to suspend (via the UI menu or lid close), a Kernel Panic occurs. The screen briefly shows a traceback before freezing. The traceback specifically mentions: "RIP: 0010: jump_label_patch_code.cold+0x24/0x26" After the panic, the system briefly shows the lock screen but remains unresponsive to keyboard, mouse, or power button input. A hard reset (long press power button) is the only way to recover the system. *** Steps attempted to resolve (without success) *** - Added 'pcie_aspm=off' and 'mem_sleep_default=deep' to GRUB. - Enabled NVIDIA power management services (nvidia-suspend, nvidia-resume). - Set 'options iwlwifi power_save=0' to rule out WiFi card interference. - Tested with both NVIDIA 535 and 595 drivers. The issue seems related to how the current 26.04 kernel handles dynamic code patching (jump_label) during power state transitions on the Alder Lake (12th Gen Intel) platform. I have kernel panic pictures if you want ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: eriick 5274 F.... wireplumber /dev/snd/controlC0: eriick 5274 F.... wireplumber /dev/snd/controlC1: eriick 5274 F.... wireplumber /dev/snd/seq: eriick 5254 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 12 12:20:53 2026 InstallationDate: Installed on 2026-04-14 (28 days ago) InstallationMedia: Ubuntu 24.04.4 LTS "Noble Numbat" - Release amd64 (20260210) MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX507ZR_FX507ZR ProcFB: 0 i915drmfb 1 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=c630651a-7e5e-49fe-a591-35f35d5784f8 ro quiet splash pcie_aspm=off mem_sleep_default=deep no_hash_pointers acpi_sleep=nonvs crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-07 (5 days ago) dmi.bios.date: 05/03/2023 dmi.bios.release: 5.26 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FX507ZR.316 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX507ZR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX507ZR.316:bd05/03/2023:br5.26:efr3.7:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX507ZR_FX507ZR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX507ZR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSTUFGamingF15: dmi.product.family: ASUS TUF Gaming F15 dmi.product.name: ASUS TUF Gaming F15 FX507ZR_FX507ZR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152256/+subscriptions

[Bug 2152124] [NEW] Hard crash of Wayland session (back to login/initramfs screen) when scrolling emails in Thunderbird.

You have been subscribed to a public bug: When using Thunderbird under Wayland on Ubuntu 26.04 (Intel GPU, ASUS Zenbook UX310UA), pressing the Up/Down arrow keys to scroll through emails causes an immediate and hard crash of the GNOME Shell / Wayland compositor. The system drops connection to xwayland and crashes back to the disk decryption/login screen. The issue is 100% reproducible on Wayland. Workaround: Switching the session to "Ubuntu on Xorg" completely resolves the issue and Thunderbird works normally. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: gnome-shell 50.1-0ubuntu1 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:32:06 2026 DisplayManager: gdm3 InstallationDate: Installed on 2025-05-25 (350 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3) ProcEnviron: LANG=cs_CZ.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> RelatedPackageVersions: mutter-common 50.1-0ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to resolute on 2026-05-10 (0 days ago) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug i915 resolute wayland-session -- Hard crash of Wayland session (back to login/initramfs screen) when scrolling emails in Thunderbird. https://bugs.launchpad.net/bugs/2152124 You received this bug notification because you are subscribed to linux in Ubuntu.

понедельник

[Bug 2152194] [NEW] perf_cpu_map__merge fails to compile on ppc46el, s390x on noble linux

You have been subscribed to a public bug: For some odd reason trying to pass an "(int) * (size_t)" to malloc is throwing an exception in the argument checking for malloc. This only happens on s390x and ppc64el. This results in the following compilation error: tools/lib/perf/cpumap.c, function perf_cpu_map__merge (line 464): cpumap.c:464:20: error: argument 1 range [18446744065119617024, 18446744073709551612] exceeds maximum object size 9223372036854775807 [-Werror=alloc-size-larger-than=] 464 | tmp_cpus = malloc(tmp_len * sizeof(struct perf_cpu)); ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- perf_cpu_map__merge fails to compile on ppc46el, s390x on noble linux https://bugs.launchpad.net/bugs/2152194 You received this bug notification because you are subscribed to linux in Ubuntu.