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

суббота

After further investigation, this is not a kernel bug. The issue is caused by NVIDIA driver 595.71.05. The xHCI resume failure on the TU116 USB 3.1 Host Controller (10de:1aec at 0000:01:00.2) persists across kernels 7.0.0-14 and 7.0.0-15, but is resolved by reverting the NVIDIA driver to 595.58.03. With 595.58.03 and kernel 7.0.0-15, Bluetooth devices reconnect normally after suspend. Marking as Invalid. Will file a bug with NVIDIA for the 595.71.05 regression. ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150759 Title: Bug Report: xHCI resume failure after upgrade to 7.0.0-15-generic Status in linux package in Ubuntu: Invalid Bug description: ## Description After upgrading from kernel 7.0.0-14-generic to 7.0.0-15-generic, the NVIDIA TU116 USB 3.1 Host Controller (01:00.2) fails to resume from suspend. This causes all USB devices behind that controller to become unavailable after resume, including the Bluetooth adapter (Intel AX201), which prevents Bluetooth peripherals from reconnecting. Reverting to kernel 7.0.0-14-generic resolves the issue — suspend/resume works correctly and Bluetooth devices reconnect as expected. ## Steps to Reproduce 1. Install kernel 7.0.0-15-generic on a system with an NVIDIA TU116 USB controller 2. Suspend the system (suspend-to-RAM / deep) 3. Resume ## Expected Result xHCI controller resumes successfully; Bluetooth (and other USB) devices reconnect. ## Actual Result xHCI controller fails to resume with error: ``` xhci_hcd 0000:01:00.2: xHC error in resume, USBSTS 0x401, Reinit ``` Bluetooth device (Logitech MX Master 3S via Intel AX201) does not reconnect. Requires reboot to restore functionality. ## Relevant Journal Logs (kernel 7.0.0-15, boot -1) ``` Apr 29 21:07:10 iaw kernel: PM: suspend entry (deep) Apr 30 17:19:03 iaw kernel: xhci_hcd 0000:01:00.2: xHC error in resume, USBSTS 0x401, Reinit Apr 30 17:19:03 iaw kernel: PM: suspend exit ``` ## Regression - **Working kernel:** 7.0.0-14-generic - **Broken kernel:** 7.0.0-15-generic - Upgrade performed: 2026-04-29 19:43 via `apt upgrade` ## System Information - **Distro:** Ubuntu 26.04 LTS (Resolute Raccoon) - **System:** Alienware Area-51m R2 - **Affected controller:** NVIDIA Corporation TU116 USB 3.1 Host Controller [10de:1aec] (rev a1) at 01:00.2 - **Bluetooth adapter:** Intel Corp. AX201 (8087:0026) on bus 001 - **Other USB controllers (unaffected):** - Intel Comet Lake USB 3.1 xHCI [8086:06ed] at 00:14.0 - Intel JHL7540 Thunderbolt 3 [8086:15e9] at 3f:00.0 - **NVIDIA driver:** 595.71.05 (unchanged, installed Apr 26) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150759/+subscriptions

[Bug 2058573] Re: alsa/realtek: adjust max output valume for headphone on 2 LG machines

[Bug 2114174] Re: [UBUNTU 24.04] s390/pci: Fix immediate re-add of PCI function after remove

This bug is awaiting verification that the linux-azure- nvidia/6.8.0-1034.37 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-nvidia' to 'verification-done-noble-linux-azure-nvidia'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-failed-noble-linux-azure-nvidia'. 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-nvidia-v2 verification-needed-noble-linux-azure-nvidia -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2114174 Title: [UBUNTU 24.04] s390/pci: Fix immediate re-add of PCI function after remove Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux source package in Plucky: Fix Released Bug description: [ Impact ] s390/pci: Fix immediate re-add of PCI function after remove A PCI function may be reserved directly after being deconfigured. If it subsequently returns back in the standby state Linux may not be able to use the new instance generating a kernel warning about trying to create an already existing sysfs file for the IOMMU. The problem occurs because the new instance of the same underlying device is created before the prior instance is completely torn down. This happens because the lifetime of the PCI device representation in Linux is determined by reference counts. A driver, the network stack, or even user-space (including via vfio-pci) may be holding onto the device represenation even after the underlying device is gone. The solution to this is twofold. Firstly allow re-using the pre-existing struct zpci_dev and/or struct pci_dev for the newly re-added instance of the underlying device up until the point where the struct zpci_dev is fully removed. Secondly serialize the addition and removal of PCI functions such that re-adding a new instance, after the old one is already being removed, will wait for the removal to finish before adding the new instance. This fix also builds on prior upstream work of serializing state transitions for PCI devices e.g. from configured to standby. [ Fix ] Backport from mainline: - 0d48566d4b58 s390/pci: rename lock member in struct zpci_dev - bcb5d6c76903 s390/pci: introduce lock to synchronize state of zpci_dev's - 6ee600bfbe0f s390/pci: remove hotplug slot when releasing the device - c4a585e952ca s390/pci: Fix potential double remove of hotplug slot - 42420c50c68f s390/pci: Fix missing check for zpci_create_device() error return - 05a2538f2b48 s390/pci: Fix duplicate pci_dev_put() in disable_slot() when PF has child VFs - d76f96332967 s390/pci: Remove redundant bus removal and disable from zpci_release_device() - 47c397844869 s390/pci: Prevent self deletion in disable_slot() - 4b1815a52d7e s390/pci: Allow re-add of a reserved but not yet removed device - 774a1fa880bc s390/pci: Serialize device addition and removal [ Test Plan ] The issue can be reproduced looking at the behavior of the kernel wrt to NETH PCI functions. In fact, IBM Z firmware temporarily reserves NETH PCI functions to check for pending service when the last FID of a PCHID is deconfigured. When nothing is pending the PCI function is immediately returned in the standby state, thus triggering this issue quite reliably. [ Where Problems Could Occur ] The fix affects the PCI function lifecycle management in the s390 PCI hotplug infrastructure, specifically the serialization and reuse logic of zpci_dev and pci_dev structures during rapid remove and re-add cycles. An issue with this fix may introduce problems such as stale or incorrectly reused device state, leading to improper reinitialization of PCI functions. --- Description: s390/pci: Fix immediate re-add of PCI function after remove Symptom: A PCI function may be reserved directly after being deconfigured. If it subsequently returns back in the standby state Linux may not be able to use the new instance generating a kernel warning about trying to create an already existing sysfs file for the IOMMU. Problem: The problem occurs because the new instance of the same underlying device is created before the prior instance is completely torn down. This happens because the lifetime of the PCI device representation in Linux is determined by reference counts. A driver, the network stack, or even user-space (including via vfio-pci) may be holding onto the device represenation even after the underlying device is gone. Solution: The solution to this is twofold. Firstly allow re-using the pre-existing struct zpci_dev and/or struct pci_dev for the newly re-added instance of the underlying device up until the point where the struct zpci_dev is fully removed. Secondly serialize the addition and removal of PCI functions such that re-adding a new instance, after the old one is already being removed, will wait for the removal to finish before adding the new instance. This fix also builds on prior upstream work of serializing state transitions for PCI devices e.g. from configured to standby. Reproduction: This problem was originally found with firmware which temporarily reserves NETH PCI functions to check for pending service when the last FID of a PCHID is deconfigured. When nothing is pending the PCI function is immediately returned in the standby state, thus triggering this issue quite reliably. Upstream-ID: 0d48566d4b58946c8e1b0baac0347616060a81c9 bcb5d6c769039c8358a2359e7c3ea5d97ce93108 6ee600bfbe0f818ffb7748d99e9b0c89d0d9f02a c4a585e952ca403a370586d3f16e8331a7564901 42420c50c68f3e95e90de2479464f420602229fc 05a2538f2b48500cf4e8a0a0ce76623cc5bafcf1 d76f9633296785343d45f85199f4138cb724b6d2 47c397844869ad0e6738afb5879c7492f4691122 4b1815a52d7eb03b3e0e6742c6728bc16a4b2d1d 774a1fa880bc949d88b5ddec9494a13be733dfa8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2114174/+subscriptions

[Bug 2142389] Re: amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot

Subject: FINAL EVIDENCE: 3rd Git Bisect confirms Kernel Regression (AMD Tonga) Hi everyone, I’m posting this update to bring maximum visibility to this issue. After completing my third full git bisect to eliminate any margin of error, I have officially isolated the "first bad commit" responsible for the regressions on my AMD R9 380 (Tonga) system. The Smoking Gun: Commit: da1a055d01ed0c18402dd1f1934096ac4bb36ada Subject: lib/test_bpf: Call page_address() on page acquired with GFP_KERNEL flag Technical Context: The regression stems from replacing kmap() with page_address() in lib/test_bpf.c and removing the subsequent NULL checks. While this cleanup might be valid for most, it directly breaks stability for the Tonga architecture on kernels 6.6+. I have already engaged the upstream experts on GitLab (Ticket #5123), including @karolherbst, @daniel-schuermann, @agd5f (Alex Deucher), @sageofredondo, and @Venemo. I’m also calling the attention of @michaellarabel (Phoronix) to this case, as it highlights how a "minor" BPF cleanup can have unintended consequences for specific GCN 3.0 hardware generations. My Ask to the Ubuntu Kernel Team: I have done the heavy lifting of identifying the root cause through three separate bisections. We need reciprocity here. The community cannot be ignored when the evidence is this precise. To deny this regression now would be to invalidate the git bisect process itself. I am attaching the full technical report (Relatorio_Final_Bisect_Danilo.pdf) and bisection logs for verification. I am ready to test any patches to confirm the fix for Ubuntu users. Best regards, Danilo."The Tonga Guy" ** Attachment added: "[BOMBSHELL] Tonga R9 380 HDMI Dead on 6.8 LTS - Proof inside (Git Bisect + Logs)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142389/+attachment/5967460/+files/3%C2%BA%20Git%20Bisect.png -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2142389 Title: amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot Status in linux package in Ubuntu: New Bug description: AMDGPU suspend → display black / no video after resume on Radeon R9 380 (No EDID read) Summary: After system suspend from Zorin OS 18 (Ubuntu 24.10 base, kernel 6.17.0-14), the system sometimes resumes but the display remains black (no signal). System continues running (fans/LEDs active), but monitor shows no output. Only hard reboot restores video. Steps to reproduce: Boot Zorin OS 18 (Ubuntu 24.10 kernel 6.17). Suspend system (e.g., via GNOME “Suspend”). Wait short period. Attempt to resume (mouse/keyboard). System wakes but display either shows garbled video or no output. Observed behavior: System appears not crashed (fans/LEDs/keyboard continue). Screen stays black or displays remnants but no usable video. Sometimes resume works, sometimes fails. Relevant log excerpt: amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read. Hardware: Motherboard: Gigabyte B450 AORUS PRO WIFI CPU: AMD Ryzen 5 5500 GPU: AMD Radeon R9 380 Series (Tonga, amdgpu driver) Software environment: Zorin OS 18 Core (Ubuntu 24.10 base) kernel: 6.17.0-14-generic X11 session Workaround currently applied: Suspend disabled. System remains stable without suspend. Note: Bug appears related to video resume rather than system freeze; display subsystem (EDID handshake) may fail after suspend. Additional info: Similar reports of amdgpu black screen / suspend issues exist (e.g., Launchpad #2141216) and community discussions on black screen resume after suspend for AMD GPUs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142389/+subscriptions

[Bug 2028253] Re: update apparmor and LSM stacking patch set

пятница

[Bug 2150737] Re: M3800 keyboard backlight problem ubuntu 26.04

rom1@rom1-M3800:~$ lsmod | grep dell dell_laptop 40960 0 dell_wmi 28672 1 dell_laptop dell_smbios 36864 2 dell_wmi,dell_laptop dell_smm_hwmon 36864 0 dcdbas 24576 1 dell_smbios sparse_keymap 12288 1 dell_wmi dell_wmi_descriptor 20480 2 dell_wmi,dell_smbios dell_lis3lv02d 16384 0 dell_smo8800 16384 0 dell_rbtn 20480 0 video 77824 3 dell_wmi,dell_laptop,i915 wmi 36864 7 video,dell_wmi,wmi_bmof,dell_smm_hwmon,dell_smbios,dell_wmi_descriptor,mxm_wmi -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150737 Title: M3800 keyboard backlight problem ubuntu 26.04 Status in linux package in Ubuntu: New Bug description: Hi, I have a bug related to the keyboard backlight of my DELL M3800. If I use FN + F10 key combinaison all is working good. If I try to use the gnome setting or kde setting, nothing happens. rom1@rom1-M3800:~$ ls /sys/class/leds dell::kbd_backlight input3::capslock input3::numlock input3::scrolllock phy0-led rom1@rom1-M3800:~$ cat /sys/class/leds/dell::kbd_backlight/brightness 0 rom1@rom1-M3800:~$ cat /sys/class/leds/dell::kbd_backlight/max_brightness 2 rom1@rom1-M3800:~$ cat /sys/class/leds/dell::kbd_backlight/trigger [none] usb-gadget usb-host rfkill-any rfkill-none kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock disk-activity disk-read disk-write mtd nand-disk cpu cpu0 cpu1 cpu2 cpu3 cpu4 cpu5 cpu6 cpu7 panic ACAD-online BAT1-charging-or-full BAT1-charging BAT1-full BAT1-charging-blink-full-solid BAT1-charging-orange-full-green mmc0 rc-feedback bluetooth-power hci0-power rfkill0 rfkill1 phy0rx phy0tx phy0assoc phy0radio rfkill2 If I use the key combinaison I can see the value of brightness move from 0 to 2 or 1 and physically the keyboard backlight works well. If I try to force the value to 2 in the brightness using command line, nothing happens and the value foes back to 0. I tried with Ubuntu 26.04, Kubuntu 26.04 and Fedora 44 gnome + kde. All have the same behaviour. When writing to /sys/class/leds/dell::kbd_backlight/brightness via echo, the command returns without error but the value immediately reverts to 0. The file permission show -rw-r--r-- 1 root root. The driver appears to silently reject writes from userspace while accepting them from the ACPI firmware via FN + F10. Could you please fix this ? Best regards. 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/controlC1: rom1 3768 F.... wireplumber /dev/snd/controlC0: rom1 3768 F.... wireplumber /dev/snd/seq: rom1 3749 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 13:07:07 2026 InstallationDate: Installed on 2026-04-24 (6 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Dell Inc. Dell Precision M3800 ProcEnviron: LANG=fr_FR.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-15-generic root=UUID=1e291b4f-afed-45e8-ab4d-25bdbd06707a 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: 07/02/2020 dmi.bios.release: 65.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A14 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/02/2020:br65.14:svnDellInc.:pnDellPrecisionM3800:pvrA14:rvnDellInc.:rnDellPrecisionM3800:rvrA14:cvnDellInc.:ct8:cvrNotSpecified:skuDellPrecisionM3800:pfa: dmi.product.name: Dell Precision M3800 dmi.product.sku: Dell Precision M3800 dmi.product.version: A14 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150737/+subscriptions

[Bug 2112462] Re: Unexpected system reboot at loading GUI session on some AMD platforms

This bug is awaiting verification that the linux-azure- nvidia/6.8.0-1034.37 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-nvidia' to 'verification-done-noble-linux-azure-nvidia'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-failed-noble-linux-azure-nvidia'. 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-nvidia-v2 verification-needed-noble-linux-azure-nvidia -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2112462 Title: Unexpected system reboot at loading GUI session on some AMD platforms Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux-oem-6.14 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.11 source package in Noble: Fix Released Status in linux-oem-6.14 source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Status in linux source package in Oracular: Won't Fix Status in linux-oem-6.11 source package in Oracular: Invalid Status in linux-oem-6.14 source package in Oracular: Invalid Status in linux-oem-6.8 source package in Oracular: Invalid Status in linux source package in Plucky: Fix Released Status in linux-oem-6.11 source package in Plucky: Invalid Status in linux-oem-6.14 source package in Plucky: Invalid Status in linux-oem-6.8 source package in Plucky: Invalid Status in linux source package in Questing: Fix Released Status in linux-oem-6.11 source package in Questing: Invalid Status in linux-oem-6.14 source package in Questing: Invalid Status in linux-oem-6.8 source package in Questing: Invalid Bug description: [SRU Justification] [ Impact ] AMD Strix Halo devices experience unexpected reboots while starting GUI session every boot. This is caused by: * 689275140cb8e drm/amdgpu/hdp7.0: do a posting read when flushing HDP * abe1cbaec6cfe drm/amdgpu/hdp6.0: do a posting read when flushing HDP * f756dbac1ce1d drm/amdgpu/hdp5.2: do a posting read when flushing HDP * cf424020e040b drm/amdgpu/hdp5.0: do a posting read when flushing HDP * c9b8dcabb52af drm/amdgpu/hdp4.0: do a posting read when flushing HDP And fixed by: * 5a11a27677311 drm/amdgpu/hdp7: use memcfg register to post the write for HDP flush * ca28e80abe421 drm/amdgpu/hdp6: use memcfg register to post the write for HDP flush * dbc988c689333 drm/amdgpu/hdp5.2: use memcfg register to post the write for HDP flush * 0e33e0f339b91 drm/amdgpu/hdp5: use memcfg register to post the write for HDP flush * f690e3974755a drm/amdgpu/hdp4: use memcfg register to post the write for HDP flush [ Test Plan ] 1. Install -proposed kernel 2. Reboot to the installed kernel and check if the device may finish boot process to GUI session. [ Where problems could occur ] No. This fix a problem when reading back the whole mapped KFD_MMIO_REMAP_HDP_MEM_FLUSH_CNTL register by reading another register that also triggers the flush. [ Other Info ] The causing commits were first committed to v6.13-rc1 , and have also been backported to v6.12.5, v6.6.69, v6.1.120. The fixes are available in v6.15-rc6, also backported to v6.14.7, v6.12.29, v6.6.91, v6.1.139, therefore this affects following Ubuntu kernels: * linux/plucky: all (currently 6.14.0-22.22) * linux-oem-6.14/noble: all (currently 6.14.0-1005.5) * linux/oracular: 6.11.0-20.20 to latest (currently 6.11.0-28.28) * linux-oem-6.11/noble: 6.11.0-1017.17 to latest (currently 6.11.0-1024.24) * linux/noble: 6.8.0-58.60 to latest (currently 6.8.0-62.65) * linux-oem-6.8/noble: 6.8.0-1026.26 to latest (currently 6.8.0-1029.29) Nominate for linux/noble, linux-oem-6.8/noble, linux/oracular, linux- oem-6.11/noble, linux/plucky, and linux-oem-6.14/noble. ========== original bug report ========== With 5 v6.13-rc1 commits , also backported to v6.12.5, v6.6.69, v6.1.120, some (at least AMD Strix Halo) devices may experience unexpected reboots while starting GUI session every boot: * 689275140cb8e drm/amdgpu/hdp7.0: do a posting read when flushing HDP * abe1cbaec6cfe drm/amdgpu/hdp6.0: do a posting read when flushing HDP * f756dbac1ce1d drm/amdgpu/hdp5.2: do a posting read when flushing HDP * cf424020e040b drm/amdgpu/hdp5.0: do a posting read when flushing HDP * c9b8dcabb52af drm/amdgpu/hdp4.0: do a posting read when flushing HDP The fixes are available in v6.15-rc6, also backported to v6.14.7, v6.12.29, v6.6.91, v6.1.139: * 5a11a27677311 drm/amdgpu/hdp7: use memcfg register to post the write for HDP flush * ca28e80abe421 drm/amdgpu/hdp6: use memcfg register to post the write for HDP flush * dbc988c689333 drm/amdgpu/hdp5.2: use memcfg register to post the write for HDP flush * 0e33e0f339b91 drm/amdgpu/hdp5: use memcfg register to post the write for HDP flush * f690e3974755a drm/amdgpu/hdp4: use memcfg register to post the write for HDP flush This affects following Ubuntu kernels: * linux/plucky: all (currently 6.14.0-22.22) * linux-oem-6.14/noble: all (currently 6.14.0-1005.5) * linux/oracular: 6.11.0-20.20 to latest (currently 6.11.0-28.28) * linux-oem-6.11/noble: 6.11.0-1017.17 to latest (currently 6.11.0-1024.24) * linux/noble: 6.8.0-58.60 to latest (currently 6.8.0-62.65) * linux-oem-6.8/noble: 6.8.0-1026.26 to latest (currently 6.8.0-1029.29) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2112462/+subscriptions

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

суббота

[Bug 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

[Bug 2107336] Re: Missing upstream commits for LP: #2102181

[Bug 2067669] Re: Mute/mic LEDs no function on ProBook 440/460 G11

[Bug 2150759] Re: Bug Report: xHCI resume failure after upgrade to 7.0.0-15-generic