[Bug 2150819] Re: Internal webcam does not work on Lenovo 21Q7000LBR after fresh Ubuntu 26.04 install.

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150819 Title: Internal webcam does not work on Lenovo 21Q7000LBR after fresh Ubuntu 26.04 install. Status in linux package in Ubuntu: Confirmed Bug description: Internal webcam does not work on Lenovo 21Q7000LBR after fresh Ubuntu 26.04 install. This appears related to Ubuntu bug #2107320: https://bugs.launchpad.net/bugs/2107320 That bug added support for the Sony IMX471 / SONY471A camera sensor on Intel IPU7 platforms. My system detects the same SONY471A sensor, but the IPU7 bridge fails with a duplicate software node error before camera/media devices are created. System: - Lenovo 21Q7000LBR - Ubuntu 26.04 LTS - Kernel: 7.0.0-15-generic - intel-ipu7-dkms: 0~git202602091007.a88b1909-0ubuntu1 - Sensor appears to be Sony IMX471 / SONY471A - BIOS IntegratedCameraAccess: Enable Problem: - No /dev/video* devices are created - No /dev/media* devices are created - Camera apps cannot see the internal webcam Relevant kernel log: Found supported sensor SONY471A:00 sysfs: cannot create duplicate filename '/kernel/software_nodes/SONY471A-0' kobject: kobject_add_internal failed for SONY471A-0 with -EEXIST intel-ipu7 0000:00:05.0: error -EEXIST: IPU bridge init failed intel-ipu7 0000:00:05.0: probe with driver intel-ipu7 failed with error -17 Expected behavior: The IPU7 driver should bind the IMX471 sensor and create camera/media devices, similar to the expected working path from Ubuntu bug #2107320: Found supported sensor SONY471A:00 Connected 1 cameras bind imx471 ... All sensor registration completed 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: portugal 3618 F.... pipewire portugal 3640 F.... wireplumber /dev/snd/seq: portugal 3618 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 2 11:18:01 2026 InstallationDate: Installed on 2026-05-02 (1 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 21Q7000LBR ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=57b10f72-ea94-4402-b27e-a35bf6019678 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux StagingDrivers: intel_ipu7 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2025 dmi.bios.release: 1.12 dmi.bios.vendor: LENOVO dmi.bios.version: N4CET36W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 21Q7000LBR dmi.board.vendor: LENOVO dmi.board.version: SDK0T76576 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN4CET36W(1.12):bd03/06/2025:br1.12:efr1.8:svnLENOVO:pn21Q7000LBR:pvrThinkPadX9-15Gen1:rvnLENOVO:rn21Q7000LBR:rvrSDK0T76576WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21Q7_BU_Think_FM_ThinkPadX9-15Gen1:pfaThinkPadX9-15Gen1: dmi.product.family: ThinkPad X9-15 Gen 1 dmi.product.name: 21Q7000LBR dmi.product.sku: LENOVO_MT_21Q7_BU_Think_FM_ThinkPad X9-15 Gen 1 dmi.product.version: ThinkPad X9-15 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150819/+subscriptions

[Bug 2153556] Re: Kernel regression (6.8.0-117.generic)

** Tags removed: verification-done-jammy-linux verification-done-noble-linux verification-done-questing-linux ** Tags added: verification-done-jammy verification-done-noble verification-done-questing -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2153556 Title: Kernel regression (6.8.0-117.generic) Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Noble: Fix Committed Status in linux source package in Questing: Fix Committed Bug description: There is a regression for the CVE-2026-31419 patch in kernel 117.generic that was supposed to fix a vulnerability in bonding mode 3. This patch caused mode 3 bonding to completely break on a production cluster. We were able to recover services by booting on a .111 fallback. Hardware is ConnectX-6 at 100G, all interfaces, links and bonding status appear to be up but no packets are passed. Unfortunately, this is a production system so it's now on an older kernel so testing isn't possible. If necessary, I can bring up a pair of VMs to run some tests for this. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2153556/+subscriptions

[Bug 2154748] Comment bridged from LTC Bugzilla

------- Comment From Boris.mail@de.ibm.com 2026-06-18 06:13 EDT------- That's awesome Massimiliano, thanks a lot for your work! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154748 Title: [Ubuntu 26.04] Severe Performance Degradation on kernel 7.0.0-15 Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: [ Impact ] s390 selects GENERIC_LOCKBREAK if PREEMPT is enabled. Reason is a historic 18 years old commit [1] which fixed a compile error for PREEMPT enabled kernels. Back than only PREEMPT_NONE and PREEMPT_VOLUNTARY kernels were considered to be important for s390. PREEMPT should "just work". However, since recently PREEMPT is always enabled [2], which also causes GENERIC_LOCKBREAK to be always enabled. For some workloads this leads to massive performance degradation; e.g. a simple kernel compile on machines with many CPUs may take up to four times longer. To fix this just remove the GENERIC_LOCKBREAK from s390's Kconfig, since the compile error from 18 years ago does not exist anymore. [1] commit b6b40c532a36 ("[S390] Define GENERIC_LOCKBREAK.") [2] commit 7dadeaa6e851 ("sched: Further restrict the preemption modes") [ Fix ] Backport commit: 1f57f68c4dd1 ("s390: Remove GENERIC_LOCKBREAK Kconfig option") [ Test Plan ] Compile and boot tested. Tested performance by compiling a kernel and monitoring execution with perf. [ Regression Potential ] The regression potential of the patch is low. It affects only s390x spinlock implementation. --- == Comment: #2 - Mete Durlu <Mete.Durlu@ibm.com> - 2026-06-01 08:59:07 == ---Problem Description--- Ubuntu 26.04 shows massive performance degradation. On large machines with more than 20 COREs (40 CPUs with SMT) CPU bound workloads suffer greatly. Ex: linux kernel compilation takes >10x more time Resource utilization shows up to 100% system time during the workload. perf top output indicates excessive lock contention in the kernel. $ make -j$(nproc) $ perf top   52.41% [kernel] [k] arch_spin_trylock_retry    8.76% [kernel] [k] _raw_spin_lock_irqsave    2.03% [kernel] [k] arch_spin_relax    1.09% cc1 [.] ht_lookup_with_hash(ht*, unsigned char    0.97% [kernel] [k] diag49c    0.95% [kernel] [k] lru_gen_add_folio    0.80% [kernel] [k] post_alloc_hook.localalias    0.77% [kernel] [k] lru_gen_del_folio.constprop.0    0.63% cc1 [.] htab_find_slot_with_hash    0.60% [kernel] [k] folios_put_refs    0.49% [kernel] [k] arch_vcpu_is_preempted    0.48% cc1 [.] ggc_internal_alloc_no_dtor(unsigned lo    0.44% cc1 [.] _cpp_lex_direct ... The lock contention seems to be linked directly to the thread count on the workload; # on a system with 34 COREs (68 CPUs w SMT) $ make -j20   perf top shows no arch_spin_trylock_retry $ make -j25   perf top shows ~2% arch_spin_trylock_retry $ make -j30   perf top shows ~5% arch_spin_trylock_retry $ make -j34 # thread count = core count   perf top shows ~15% arch_spin_trylock_retry $ make -j40 # thread count > core count   perf top shows >30% arch_spin_trylock_retry There has also been hints of delays on workqueue execution in dmesg output: ... [10600.136975] workqueue: vmstat_update hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND [10806.428576] workqueue: delayed_vfree_work hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND [10819.822422] workqueue: delayed_vfree_work hogged CPU for >10000us 5 times, consider switching to WQ_UNBOUND [10885.381900] workqueue: delayed_vfree_work hogged CPU for >10000us 7 times, consider switching to WQ_UNBOUND [10915.209117] workqueue: pcpu_balance_workfn hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND [11059.719121] workqueue: pcpu_balance_workfn hogged CPU for >10000us 5 times, consider switching to WQ_UNBOUND [20223.529295] workqueue: inode_switch_wbs_work_fn hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND [22584.374168] workqueue: mmput_async_fn hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND [22602.115559] workqueue: delayed_vfree_work hogged CPU for >10000us 11 times, consider switching to WQ_UNBOUND [22817.328172] workqueue: vmstat_update hogged CPU for >10000us 5 times, consider switching to WQ_UNBOUND [22840.202092] workqueue: delayed_vfree_work hogged CPU for >10000us 19 times, consider switching to WQ_UNBOUND [26834.512017] workqueue: delayed_vfree_work hogged CPU for >10000us 35 times, consider switching to WQ_UNBOUND [26883.480296] workqueue: vmstat_update hogged CPU for >10000us 7 times, consider switching to WQ_UNBOUND ... Systems with less COREs don't seem to be effected. The limit seems to be around 15 COREs (30 CPUs) ---uname output--- Linux localhost 7.0.0-15-generic #15-Ubuntu SMP PREEMPT Wed Apr 22 15:04:00 UTC 2026 s390x GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2154748/+subscriptions

[Bug 2147427] Re: Failed to add generic LLDP Rx filter on VSI 13 error

Hi Jeff, This bug can be closed -- we confirmed that the latest image already fixed it. Thanks. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2147427 Title: Failed to add generic LLDP Rx filter on VSI 13 error Status in linux package in Ubuntu: New Bug description: 1.Install Ubuntu 26.04/20260302/ (resolute-live-server-amd64) 2.Check dmesg and observe "Failed to add generic LLDP Rx filter on VSI 13 error: -5, falling back to specialized AQ control" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147427/+subscriptions

[Bug 2155161] Re: Jabra Evolve 2 85 headset keeps reconnecting via usb

Hi Alexander Thank you for your patience, I would like to ask you to do a test. please run the command: ``` echo "blacklist snd_usb_audio" | sudo tee /etc/modprobe.d/no-usb-audio.conf sudo reboot ``` After reboot, please help me to check if connection stable (no sound is expected). If yes, please remove the no-usb-audio.conf file and run command ``` echo "options snd-usb-audio quirk_flags=0b0e:24ca:SKIP_IFACE_SETUP" | \ sudo tee /etc/modprobe.d/jabra-audio-test.conf sudo reboot ``` See if issue happen again. BR An -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2155161 Title: Jabra Evolve 2 85 headset keeps reconnecting via usb Status in linux package in Ubuntu: New Bug description: As soon as i want to use any kind of usb connection with the headset the usb connects and reconnects over and over again. I made sure its not an issue of cable used or the usb hub in the docking station. by connecting it directly to the laptop. Although i could use usb with this headset on ubuntu lts 24 without any issues since i reinstalled with kubuntu 26 this occurs (guess it would happen in ubuntu 26 too) I gladly provide more info if needed. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jun 3 16:10:16 2026 InstallationDate: Installed on 2026-05-12 (22 days ago) InstallationMedia: Kubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423) IwDevWlp0s20f3Link: Not connected. MachineType: Dell Inc. Precision 3581 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-22-generic root=UUID=e1d7f812-2942-4efe-80f9-510636bb0378 ro quiet cryptdevice=UUID=24e90ca6-128d-41d3-be29-328e50acf97d:luks-24e90ca6-128d-41d3-be29-328e50acf97d root=/dev/mapper/luks-24e90ca6-128d-41d3-be29-328e50acf97d splash nvidia-drm.modeset=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2025 dmi.bios.release: 1.27 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.27.1 dmi.board.name: 0V8YXF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnDellInc.:bvr1.27.1:bd12/12/2025:br1.27:efr1.25:svnDellInc.:pnPrecision3581:pvr:rvnDellInc.:rn0V8YXF:rvrA00:cvnDellInc.:ct10:cvr:sku0C07:pfaPrecision: dmi.product.family: Precision dmi.product.name: Precision 3581 dmi.product.sku: 0C07 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2155161/+subscriptions

[Bug 2157079] [NEW] ubuntu 26.04 freeze on ThinkPad P1 Gen 8

Public bug reported: I just left my laptop with lock screen, the 26.04 is freeze when I return. Kernel: 7.0.0-22-generic BIOS: N4EET22W (1.08 ) Jun 18 11:19:49 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* Timeout waiting for DDI BUF A to get active Jun 18 11:19:50 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* Timed out waiting for DP idle patterns Jun 18 11:20:00 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] flip_done timed out Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in pixel_rate (expected 604999, found 45891) Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in dpll_hw_state·· Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* expected: Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* cx0pll_hw_state: lane_count: 4, ssc_enabled: no, use_c10: yes, tbt_mode: no Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* c10pll_hw_state: clock: 810000, fracen: yes,· Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* quot: 61440, rem: 0, den: 1, Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* multiplier: 210, tx_clk_div: 0. Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* c10pll_rawhw_state: Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* tx: 0x10, cmn: 0x21 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[0] = 0x34, pll[1] = 0x0, pll[2] = 0x84, pll[3] = 0x1 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[4] = 0x0, pll[5] = 0x0, pll[6] = 0x0, pll[7] = 0x0 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[8] = 0x0, pll[9] = 0x1, pll[10] = 0x0, pll[11] = 0x0 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[12] = 0xf0, pll[13] = 0x0, pll[14] = 0x0, pll[15] = 0x0 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[16] = 0x84, pll[17] = 0xf, pll[18] = 0xe5, pll[19] = 0x23 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* found: Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* cx0pll_hw_state: lane_count: 4, ssc_enabled: no, use_c10: yes, tbt_mode: no Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* c10pll_hw_state: clock: 61440, fracen: no,· Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* multiplier: 16, tx_clk_div: 0. Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* c10pll_rawhw_state: Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* tx: 0x0, cmn: 0x0 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[0] = 0x0, pll[1] = 0x0, pll[2] = 0x0, pll[3] = 0x0 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[4] = 0x0, pll[5] = 0x0, pll[6] = 0x0, pll[7] = 0x0 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[8] = 0x0, pll[9] = 0x0, pll[10] = 0x0, pll[11] = 0x0 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[12] = 0x0, pll[13] = 0x0, pll[14] = 0x0, pll[15] = 0x0 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[16] = 0x0, pll[17] = 0x0, pll[18] = 0x0, pll[19] = 0x0 Jun 18 11:20:01 Curie2 kernel: ------------[ cut here ]------------ Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] pipe state doesn't match! Jun 18 11:20:01 Curie2 kernel: WARNING: drivers/gpu/drm/i915/display/intel_modeset_verify.c:225 at verify_crtc_state+0x349/0x5c0 [i915], CPU#1: KMS thread/4149 Jun 18 11:20:01 Curie2 kernel: Call Trace: Jun 18 11:20:01 Curie2 kernel: <TASK> Jun 18 11:20:01 Curie2 kernel: intel_modeset_verify_crtc+0x4f/0xb0 [i915] Jun 18 11:20:01 Curie2 kernel: intel_atomic_commit_tail+0x8a3/0xc50 [i915] Jun 18 11:20:01 Curie2 kernel: intel_atomic_commit+0x28e/0x2e0 [i915] Jun 18 11:20:01 Curie2 kernel: drm_atomic_commit+0xad/0xf0 Jun 18 11:20:01 Curie2 kernel: ? __pfx___drm_printfn_info+0x10/0x10 Jun 18 11:20:01 Curie2 kernel: drm_mode_atomic_ioctl+0x7d1/0x910 Jun 18 11:20:01 Curie2 kernel: ? __pfx_drm_mode_atomic_ioctl+0x10/0x10 Jun 18 11:20:01 Curie2 kernel: drm_ioctl_kernel+0xb5/0x110 Jun 18 11:20:01 Curie2 kernel: drm_ioctl+0x309/0x5f0 Jun 18 11:20:01 Curie2 kernel: ? __pfx_drm_mode_atomic_ioctl+0x10/0x10 Jun 18 11:20:01 Curie2 kernel: __x64_sys_ioctl+0xa3/0x100 Jun 18 11:20:01 Curie2 kernel: x64_sys_call+0x103b/0x2390 Jun 18 11:20:01 Curie2 kernel: do_syscall_64+0x115/0x5a0 Jun 18 11:20:01 Curie2 kernel: ? check_heap_object+0x146/0x1c0 Jun 18 11:20:01 Curie2 kernel: ? __check_object_size+0x86/0xf0 Jun 18 11:20:01 Curie2 kernel: ? ptep_set_access_flags+0x4a/0x70 Jun 18 11:20:01 Curie2 kernel: ? wp_page_reuse+0x97/0xc0 Jun 18 11:20:01 Curie2 kernel: ? do_wp_page+0x4ee/0x6f0 Jun 18 11:20:01 Curie2 kernel: ? handle_pte_fault+0x1d8/0x1f0 Jun 18 11:20:01 Curie2 kernel: ? __handle_mm_fault+0x493/0x720 Jun 18 11:20:01 Curie2 kernel: ? count_memcg_events+0x103/0x250 Jun 18 11:20:01 Curie2 kernel: ? handle_mm_fault+0x1c0/0x2e0 Jun 18 11:20:01 Curie2 kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0x100 Jun 18 11:20:01 Curie2 kernel: ? irqentry_exit+0x97/0x5a0 Jun 18 11:20:01 Curie2 kernel: ? exc_page_fault+0x94/0x1e0 Jun 18 11:20:01 Curie2 kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e Jun 18 11:20:01 Curie2 kernel: RIP: 0033:0x76eaf7f32cbd ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "crash.log" https://bugs.launchpad.net/bugs/2157079/+attachment/5977950/+files/crash.log -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2157079 Title: ubuntu 26.04 freeze on ThinkPad P1 Gen 8 Status in linux package in Ubuntu: New Bug description: I just left my laptop with lock screen, the 26.04 is freeze when I return. Kernel: 7.0.0-22-generic BIOS: N4EET22W (1.08 ) Jun 18 11:19:49 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* Timeout waiting for DDI BUF A to get active Jun 18 11:19:50 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* Timed out waiting for DP idle patterns Jun 18 11:20:00 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] flip_done timed out Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in pixel_rate (expected 604999, found 45891) Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in dpll_hw_state·· Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* expected: Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* cx0pll_hw_state: lane_count: 4, ssc_enabled: no, use_c10: yes, tbt_mode: no Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* c10pll_hw_state: clock: 810000, fracen: yes,· Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* quot: 61440, rem: 0, den: 1, Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* multiplier: 210, tx_clk_div: 0. Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* c10pll_rawhw_state: Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* tx: 0x10, cmn: 0x21 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[0] = 0x34, pll[1] = 0x0, pll[2] = 0x84, pll[3] = 0x1 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[4] = 0x0, pll[5] = 0x0, pll[6] = 0x0, pll[7] = 0x0 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[8] = 0x0, pll[9] = 0x1, pll[10] = 0x0, pll[11] = 0x0 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[12] = 0xf0, pll[13] = 0x0, pll[14] = 0x0, pll[15] = 0x0 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[16] = 0x84, pll[17] = 0xf, pll[18] = 0xe5, pll[19] = 0x23 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* found: Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* cx0pll_hw_state: lane_count: 4, ssc_enabled: no, use_c10: yes, tbt_mode: no Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* c10pll_hw_state: clock: 61440, fracen: no,· Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* multiplier: 16, tx_clk_div: 0. Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* c10pll_rawhw_state: Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* tx: 0x0, cmn: 0x0 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[0] = 0x0, pll[1] = 0x0, pll[2] = 0x0, pll[3] = 0x0 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[4] = 0x0, pll[5] = 0x0, pll[6] = 0x0, pll[7] = 0x0 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[8] = 0x0, pll[9] = 0x0, pll[10] = 0x0, pll[11] = 0x0 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[12] = 0x0, pll[13] = 0x0, pll[14] = 0x0, pll[15] = 0x0 Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[16] = 0x0, pll[17] = 0x0, pll[18] = 0x0, pll[19] = 0x0 Jun 18 11:20:01 Curie2 kernel: ------------[ cut here ]------------ Jun 18 11:20:01 Curie2 kernel: i915 0000:00:02.0: [drm] pipe state doesn't match! Jun 18 11:20:01 Curie2 kernel: WARNING: drivers/gpu/drm/i915/display/intel_modeset_verify.c:225 at verify_crtc_state+0x349/0x5c0 [i915], CPU#1: KMS thread/4149 Jun 18 11:20:01 Curie2 kernel: Call Trace: Jun 18 11:20:01 Curie2 kernel: <TASK> Jun 18 11:20:01 Curie2 kernel: intel_modeset_verify_crtc+0x4f/0xb0 [i915] Jun 18 11:20:01 Curie2 kernel: intel_atomic_commit_tail+0x8a3/0xc50 [i915] Jun 18 11:20:01 Curie2 kernel: intel_atomic_commit+0x28e/0x2e0 [i915] Jun 18 11:20:01 Curie2 kernel: drm_atomic_commit+0xad/0xf0 Jun 18 11:20:01 Curie2 kernel: ? __pfx___drm_printfn_info+0x10/0x10 Jun 18 11:20:01 Curie2 kernel: drm_mode_atomic_ioctl+0x7d1/0x910 Jun 18 11:20:01 Curie2 kernel: ? __pfx_drm_mode_atomic_ioctl+0x10/0x10 Jun 18 11:20:01 Curie2 kernel: drm_ioctl_kernel+0xb5/0x110 Jun 18 11:20:01 Curie2 kernel: drm_ioctl+0x309/0x5f0 Jun 18 11:20:01 Curie2 kernel: ? __pfx_drm_mode_atomic_ioctl+0x10/0x10 Jun 18 11:20:01 Curie2 kernel: __x64_sys_ioctl+0xa3/0x100 Jun 18 11:20:01 Curie2 kernel: x64_sys_call+0x103b/0x2390 Jun 18 11:20:01 Curie2 kernel: do_syscall_64+0x115/0x5a0 Jun 18 11:20:01 Curie2 kernel: ? check_heap_object+0x146/0x1c0 Jun 18 11:20:01 Curie2 kernel: ? __check_object_size+0x86/0xf0 Jun 18 11:20:01 Curie2 kernel: ? ptep_set_access_flags+0x4a/0x70 Jun 18 11:20:01 Curie2 kernel: ? wp_page_reuse+0x97/0xc0 Jun 18 11:20:01 Curie2 kernel: ? do_wp_page+0x4ee/0x6f0 Jun 18 11:20:01 Curie2 kernel: ? handle_pte_fault+0x1d8/0x1f0 Jun 18 11:20:01 Curie2 kernel: ? __handle_mm_fault+0x493/0x720 Jun 18 11:20:01 Curie2 kernel: ? count_memcg_events+0x103/0x250 Jun 18 11:20:01 Curie2 kernel: ? handle_mm_fault+0x1c0/0x2e0 Jun 18 11:20:01 Curie2 kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0x100 Jun 18 11:20:01 Curie2 kernel: ? irqentry_exit+0x97/0x5a0 Jun 18 11:20:01 Curie2 kernel: ? exc_page_fault+0x94/0x1e0 Jun 18 11:20:01 Curie2 kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e Jun 18 11:20:01 Curie2 kernel: RIP: 0033:0x76eaf7f32cbd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2157079/+subscriptions

[Bug 2144730] Re: ITS mitigation is not enabled on affected CPUs

This bug is awaiting verification that the linux-vmware-6.8/6.8.0-1003.3 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-jammy-linux-vmware-6.8' to 'verification-done- jammy-linux-vmware-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-vmware-6.8' to 'verification-failed- jammy-linux-vmware-6.8'. 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-jammy-linux-vmware-6.8-v2 verification-needed-jammy-linux-vmware-6.8 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2144730 Title: ITS mitigation is not enabled on affected CPUs Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Bug description: SRU Justification: [Impact] Noble upstream stable patchset 2025-10-29 (LP :#210277) included the following patch from upstream stable branch linux-6.12.y: * 68d59e9ba3842 ("x86/its: Enable Indirect Target Selection mitigation") The patch disables ITS mitigation if CONFIG_MITIGATION_RETPOLINE or CONFIG_MITIGATION_RETHUNK are not available: + if (!IS_ENABLED(CONFIG_MITIGATION_RETPOLINE) || + !IS_ENABLED(CONFIG_MITIGATION_RETHUNK)) { + pr_err("WARNING: ITS mitigation depends on retpoline and rethunk support\n"); + its_mitigation = ITS_MITIGATION_OFF; + goto out; + } However, while linux-6.12.y contains the following two commits, Noble does not: * aefb2f2e619b6 ("x86/bugs: Rename CONFIG_RETPOLINE => CONFIG_MITIGATION_RETPOLINE") * 0911b8c52c4d6 ("x86/bugs: Rename CONFIG_RETHUNK => CONFIG_MITIGATION_RETHUNK") This discrepancy will cause the runtime check from above to always fail in Noble, since the config options have not been renamed and therefore are undefined, even though we have both CONFIG_RETPOLINE and CONFIG_RETHUNK enabled through annotations. Consequently, ITS mitigation will not be enabled when it should be. On affected CPUs this will cause the kernel to warn about missing ITS mitigation: [ 0.966659] ITS: WARNING: ITS mitigation depends on retpoline and rethunk support [ 0.966851] ITS: Vulnerable [Fix] Backport the patches that rename CONFIG_RETPOLINE and CONFIG_RETHUNK to Noble: * aefb2f2e619b6 ("x86/bugs: Rename CONFIG_RETPOLINE => CONFIG_MITIGATION_RETPOLINE") * 0911b8c52c4d6 ("x86/bugs: Rename CONFIG_RETHUNK => CONFIG_MITIGATION_RETHUNK") [Test Plan] Boot on an affected CPU and check that ITS mitigation is enabled as expected: [ 3.642521] active return thunk: its_return_thunk [ 3.643523] ITS: Mitigation: Aligned branch/return thunks [Where problems could occur] Any present or future patch that relies on the old naming scheme for the two options will behave as if the features are unavailable which could cause critical mitigations to be either less effective or disabled completely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144730/+subscriptions

[Bug 2156936] Re: [BCM20702] Acer OMR272 BT-2 bluetooth mouse occasionally gets disconnected - workaround to reconnect: sudo /etc/init.d/bluetooth restart

** Summary changed: - Acer OMR272 BT-2 bluetooth mouse occasionally gets disconnected - workaround to reconnect: sudo /etc/init.d/bluetooth restart + [BCM20702] Acer OMR272 BT-2 bluetooth mouse occasionally gets disconnected - workaround to reconnect: sudo /etc/init.d/bluetooth restart -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156936 Title: [BCM20702] Acer OMR272 BT-2 bluetooth mouse occasionally gets disconnected - workaround to reconnect: sudo /etc/init.d/bluetooth restart Status in linux package in Ubuntu: New Bug description: Occassionally the mouse gets disconnected and then cannot reconnect by itself, even when it is powercycled. Workaround: sudo /etc/init.d/bluetooth restart solves the issue and the mouse will reconnect immediately again, no pairing is necessary. Also occasionally when listening music via bluetooth (Sennheiser Momentum 4), the sound is stuttering. The expectation is that bluetooth is stable and works reliable. michael@thinkpad:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 24.04.4 LTS Release: 24.04 Codename: noble michael@thinkpad:~$ uname -a Linux thinkpad 6.8.0-124-generic #124-Ubuntu SMP PREEMPT_DYNAMIC Tue May 26 13:00:45 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux michael@thinkpad:~$ michael@thinkpad:~$ aptitude show bluez Paket: bluez Version: 5.72-0ubuntu5.5 Zustand: Installiert Automatisch installiert: ja Multi-Arch: foreign Priorität: optional Bereich: admin Verwalter: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> Architektur: amd64 Unkomprimierte Größe: 4.564 k Hängt ab von: libasound2t64 (>= 1.0.17), libc6 (>= 2.38), libdbus-1-3 (>= 1.9.14), libdw1t64 (>= 0.127), libglib2.0-0t64 (>= 2.75.3), libreadline8t64 (>= 6.0), libudev1 (>= 196), kmod, udev, default-dbus-system-bus | dbus-system-bus Hängt ab (vorher) von: init-system-helpers (>= 1.54~) Schlägt vor: pulseaudio-module-bluetooth Kollidiert mit: bluez:i386 Liefert: bluez:i386 (= 5.72-0ubuntu5.5) Bereitgestellt von: bluez:i386 (5.72-0ubuntu5), bluez:i386 (5.72-0ubuntu5.5) Beschreibung: Bluetooth-Werkzeuge und -Dienste Das Paket enthält Werkzeuge und Systemdienste zur Benutzung von Bluetooth- Geräten. BlueZ ist der offizielle Linux-Bluetooth-Protokollstack. Es ist ein Open- Source-Projekt, das unter der GNU General Public License (GPL) verteilt wird. Homepage: http://www.bluez.org michael@thinkpad:~$ michael@thinkpad:~$ apt-cache policy bluez bluez: Installiert: 5.72-0ubuntu5.5 Installationskandidat: 5.72-0ubuntu5.5 Versionstabelle: *** 5.72-0ubuntu5.5 500 500 http://de.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 /var/lib/dpkg/status 5.72-0ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu noble/main amd64 Packages michael@thinkpad:~$ ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: bluez 5.72-0ubuntu5.5 ProcVersionSignature: Ubuntu 6.8.0-124.124-generic 6.8.12 Uname: Linux 6.8.0-124-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Jun 16 23:16:05 2026 InstallationDate: Installed on 2015-05-31 (4034 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 23946J3 ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-124-generic root=UUID=68625c01-008f-4127-84e0-ae6bb9e79b8a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to noble on 2024-10-14 (610 days ago) dmi.bios.date: 03/31/2015 dmi.bios.release: 2.64 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA4WW (2.64 ) dmi.board.asset.tag: Not Available dmi.board.name: 23946J3 dmi.board.vendor: LENOVO dmi.board.version: Not Defined 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.13 dmi.modalias: dmi:bvnLENOVO:bvrG4ETA4WW(2.64):bd03/31/2015:br2.64:efr1.13:svnLENOVO:pn23946J3:pvrThinkPadT530:rvnLENOVO:rn23946J3:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2394: dmi.product.family: ThinkPad T530 dmi.product.name: 23946J3 dmi.product.sku: LENOVO_MT_2394 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 80:56:F2:FF:DF:29 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:6171653 acl:326067 sco:0 events:9289 errors:0 TX bytes:40889 acl:1156 sco:0 commands:529 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156936/+subscriptions

[Bug 2156936] Re: bluetooth mouse occasionally gets disconnected - workaround to reconnect: sudo /etc/init.d/bluetooth restart

It appears something is going wrong at the hardware or kernel level: [250599.392438] Bluetooth: hci0: Received unexpected HCI Event 0x00 [250666.341586] Bluetooth: hci0: Unexpected continuation: 1 bytes [250666.341630] Bluetooth: hci0: unexpected event 0x06 length: 25 > 3 [250697.071728] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0) [250697.681619] input: OMR272 BT-2 Keyboard as /devices/virtual/misc/uhid/0005:248A:8266.002F/input/input108 [250697.708613] input: OMR272 BT-2 Mouse as /devices/virtual/misc/uhid/0005:248A:8266.002F/input/input109 [250697.711071] hid-generic 0005:248A:8266.002F: input,hidraw0: BLUETOOTH HID v0.01 Keyboard [OMR272 BT-2] on 80:56:f2:ff:df:29 ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Summary changed: - bluetooth mouse occasionally gets disconnected - workaround to reconnect: sudo /etc/init.d/bluetooth restart + Acer OMR272 BT-2 bluetooth mouse occasionally gets disconnected - workaround to reconnect: sudo /etc/init.d/bluetooth restart -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156936 Title: Acer OMR272 BT-2 bluetooth mouse occasionally gets disconnected - workaround to reconnect: sudo /etc/init.d/bluetooth restart Status in linux package in Ubuntu: New Bug description: Occassionally the mouse gets disconnected and then cannot reconnect by itself, even when it is powercycled. Workaround: sudo /etc/init.d/bluetooth restart solves the issue and the mouse will reconnect immediately again, no pairing is necessary. Also occasionally when listening music via bluetooth (Sennheiser Momentum 4), the sound is stuttering. The expectation is that bluetooth is stable and works reliable. michael@thinkpad:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 24.04.4 LTS Release: 24.04 Codename: noble michael@thinkpad:~$ uname -a Linux thinkpad 6.8.0-124-generic #124-Ubuntu SMP PREEMPT_DYNAMIC Tue May 26 13:00:45 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux michael@thinkpad:~$ michael@thinkpad:~$ aptitude show bluez Paket: bluez Version: 5.72-0ubuntu5.5 Zustand: Installiert Automatisch installiert: ja Multi-Arch: foreign Priorität: optional Bereich: admin Verwalter: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> Architektur: amd64 Unkomprimierte Größe: 4.564 k Hängt ab von: libasound2t64 (>= 1.0.17), libc6 (>= 2.38), libdbus-1-3 (>= 1.9.14), libdw1t64 (>= 0.127), libglib2.0-0t64 (>= 2.75.3), libreadline8t64 (>= 6.0), libudev1 (>= 196), kmod, udev, default-dbus-system-bus | dbus-system-bus Hängt ab (vorher) von: init-system-helpers (>= 1.54~) Schlägt vor: pulseaudio-module-bluetooth Kollidiert mit: bluez:i386 Liefert: bluez:i386 (= 5.72-0ubuntu5.5) Bereitgestellt von: bluez:i386 (5.72-0ubuntu5), bluez:i386 (5.72-0ubuntu5.5) Beschreibung: Bluetooth-Werkzeuge und -Dienste Das Paket enthält Werkzeuge und Systemdienste zur Benutzung von Bluetooth- Geräten. BlueZ ist der offizielle Linux-Bluetooth-Protokollstack. Es ist ein Open- Source-Projekt, das unter der GNU General Public License (GPL) verteilt wird. Homepage: http://www.bluez.org michael@thinkpad:~$ michael@thinkpad:~$ apt-cache policy bluez bluez: Installiert: 5.72-0ubuntu5.5 Installationskandidat: 5.72-0ubuntu5.5 Versionstabelle: *** 5.72-0ubuntu5.5 500 500 http://de.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 /var/lib/dpkg/status 5.72-0ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu noble/main amd64 Packages michael@thinkpad:~$ ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: bluez 5.72-0ubuntu5.5 ProcVersionSignature: Ubuntu 6.8.0-124.124-generic 6.8.12 Uname: Linux 6.8.0-124-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Jun 16 23:16:05 2026 InstallationDate: Installed on 2015-05-31 (4034 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 23946J3 ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-124-generic root=UUID=68625c01-008f-4127-84e0-ae6bb9e79b8a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to noble on 2024-10-14 (610 days ago) dmi.bios.date: 03/31/2015 dmi.bios.release: 2.64 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA4WW (2.64 ) dmi.board.asset.tag: Not Available dmi.board.name: 23946J3 dmi.board.vendor: LENOVO dmi.board.version: Not Defined 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.13 dmi.modalias: dmi:bvnLENOVO:bvrG4ETA4WW(2.64):bd03/31/2015:br2.64:efr1.13:svnLENOVO:pn23946J3:pvrThinkPadT530:rvnLENOVO:rn23946J3:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2394: dmi.product.family: ThinkPad T530 dmi.product.name: 23946J3 dmi.product.sku: LENOVO_MT_2394 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 80:56:F2:FF:DF:29 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:6171653 acl:326067 sco:0 events:9289 errors:0 TX bytes:40889 acl:1156 sco:0 commands:529 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156936/+subscriptions

[Bug 2156972] [NEW] Camera output is vague and color is abnormal

Public bug reported: The camera output is abnormal, and it takes longer time to start the camera. I record the video by command: $ gst-launch-1.0 v4l2src ! videoconvert ! avimux ! filesink location=out.avi Some errors reported in the driver: kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Payload checksum (CRC) error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Payload checksum (CRC) error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected Proposed fix in https://github.com/intel/ipu6-drivers/pull/447. This affects kernel v6.10 and up, which added D-PHY implementation in commit 1e7eeb301696 ("media: intel/ipu6: add the CSI2 DPHY implementation") ** Affects: linux (Ubuntu) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux-oem-6.17 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-7.0 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.17 (Ubuntu Noble) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux-oem-7.0 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Questing) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux-oem-6.17 (Ubuntu Questing) Importance: Undecided Status: Invalid ** Affects: linux-oem-7.0 (Ubuntu Questing) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Resolute) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux-oem-6.17 (Ubuntu Resolute) Importance: Undecided Status: Invalid ** Affects: linux-oem-7.0 (Ubuntu Resolute) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux (Ubuntu Stonking) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux-oem-6.17 (Ubuntu Stonking) Importance: Undecided Status: Invalid ** Affects: linux-oem-7.0 (Ubuntu Stonking) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Stonking) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Questing) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: linux-oem-6.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-7.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.17 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-7.0 (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux-oem-7.0 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux-oem-7.0 (Ubuntu Questing) Status: New => Invalid ** Changed in: linux-oem-7.0 (Ubuntu Stonking) Status: New => Invalid ** Changed in: linux-oem-6.17 (Ubuntu Questing) Status: New => Invalid ** Changed in: linux-oem-6.17 (Ubuntu Resolute) Status: New => Invalid ** Changed in: linux-oem-6.17 (Ubuntu Stonking) Status: New => Invalid ** Changed in: linux-oem-6.17 (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-oem-6.17 (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux-oem-6.17 (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-7.0 (Ubuntu Resolute) Importance: Undecided => High ** Changed in: linux-oem-7.0 (Ubuntu Resolute) Status: New => In Progress ** Changed in: linux-oem-7.0 (Ubuntu Resolute) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Noble) Status: New => Invalid ** Changed in: linux (Ubuntu Questing) Importance: Undecided => High ** Changed in: linux (Ubuntu Questing) Status: New => In Progress ** Changed in: linux (Ubuntu Questing) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Resolute) Importance: Undecided => High ** Changed in: linux (Ubuntu Resolute) Status: New => In Progress ** Changed in: linux (Ubuntu Resolute) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Stonking) Importance: Undecided => High ** Changed in: linux (Ubuntu Stonking) Status: New => In Progress ** Changed in: linux (Ubuntu Stonking) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156972 Title: Camera output is vague and color is abnormal Status in linux package in Ubuntu: In Progress Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux-oem-7.0 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: In Progress Status in linux-oem-7.0 source package in Noble: Invalid Status in linux source package in Questing: In Progress Status in linux-oem-6.17 source package in Questing: Invalid Status in linux-oem-7.0 source package in Questing: Invalid Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Status in linux-oem-7.0 source package in Resolute: In Progress Status in linux source package in Stonking: In Progress Status in linux-oem-6.17 source package in Stonking: Invalid Status in linux-oem-7.0 source package in Stonking: Invalid Bug description: The camera output is abnormal, and it takes longer time to start the camera. I record the video by command: $ gst-launch-1.0 v4l2src ! videoconvert ! avimux ! filesink location=out.avi Some errors reported in the driver: kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Payload checksum (CRC) error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Payload checksum (CRC) error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected Proposed fix in https://github.com/intel/ipu6-drivers/pull/447. This affects kernel v6.10 and up, which added D-PHY implementation in commit 1e7eeb301696 ("media: intel/ipu6: add the CSI2 DPHY implementation") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156972/+subscriptions

[Bug 2156936] [NEW] bluetooth mouse occasionally gets disconnected - workaround to reconnect: sudo /etc/init.d/bluetooth restart

You have been subscribed to a public bug: Occassionally the mouse gets disconnected and then cannot reconnect by itself, even when it is powercycled. Workaround: sudo /etc/init.d/bluetooth restart solves the issue and the mouse will reconnect immediately again, no pairing is necessary. Also occasionally when listening music via bluetooth (Sennheiser Momentum 4), the sound is stuttering. The expectation is that bluetooth is stable and works reliable. michael@thinkpad:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 24.04.4 LTS Release: 24.04 Codename: noble michael@thinkpad:~$ uname -a Linux thinkpad 6.8.0-124-generic #124-Ubuntu SMP PREEMPT_DYNAMIC Tue May 26 13:00:45 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux michael@thinkpad:~$ michael@thinkpad:~$ aptitude show bluez Paket: bluez Version: 5.72-0ubuntu5.5 Zustand: Installiert Automatisch installiert: ja Multi-Arch: foreign Priorität: optional Bereich: admin Verwalter: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> Architektur: amd64 Unkomprimierte Größe: 4.564 k Hängt ab von: libasound2t64 (>= 1.0.17), libc6 (>= 2.38), libdbus-1-3 (>= 1.9.14), libdw1t64 (>= 0.127), libglib2.0-0t64 (>= 2.75.3), libreadline8t64 (>= 6.0), libudev1 (>= 196), kmod, udev, default-dbus-system-bus | dbus-system-bus Hängt ab (vorher) von: init-system-helpers (>= 1.54~) Schlägt vor: pulseaudio-module-bluetooth Kollidiert mit: bluez:i386 Liefert: bluez:i386 (= 5.72-0ubuntu5.5) Bereitgestellt von: bluez:i386 (5.72-0ubuntu5), bluez:i386 (5.72-0ubuntu5.5) Beschreibung: Bluetooth-Werkzeuge und -Dienste Das Paket enthält Werkzeuge und Systemdienste zur Benutzung von Bluetooth- Geräten. BlueZ ist der offizielle Linux-Bluetooth-Protokollstack. Es ist ein Open- Source-Projekt, das unter der GNU General Public License (GPL) verteilt wird. Homepage: http://www.bluez.org michael@thinkpad:~$ michael@thinkpad:~$ apt-cache policy bluez bluez: Installiert: 5.72-0ubuntu5.5 Installationskandidat: 5.72-0ubuntu5.5 Versionstabelle: *** 5.72-0ubuntu5.5 500 500 http://de.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 100 /var/lib/dpkg/status 5.72-0ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu noble/main amd64 Packages michael@thinkpad:~$ ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: bluez 5.72-0ubuntu5.5 ProcVersionSignature: Ubuntu 6.8.0-124.124-generic 6.8.12 Uname: Linux 6.8.0-124-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Jun 16 23:16:05 2026 InstallationDate: Installed on 2015-05-31 (4034 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 23946J3 ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-124-generic root=UUID=68625c01-008f-4127-84e0-ae6bb9e79b8a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to noble on 2024-10-14 (610 days ago) dmi.bios.date: 03/31/2015 dmi.bios.release: 2.64 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA4WW (2.64 ) dmi.board.asset.tag: Not Available dmi.board.name: 23946J3 dmi.board.vendor: LENOVO dmi.board.version: Not Defined 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.13 dmi.modalias: dmi:bvnLENOVO:bvrG4ETA4WW(2.64):bd03/31/2015:br2.64:efr1.13:svnLENOVO:pn23946J3:pvrThinkPadT530:rvnLENOVO:rn23946J3:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2394: dmi.product.family: ThinkPad T530 dmi.product.name: 23946J3 dmi.product.sku: LENOVO_MT_2394 dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 80:56:F2:FF:DF:29 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:6171653 acl:326067 sco:0 events:9289 errors:0 TX bytes:40889 acl:1156 sco:0 commands:529 errors:0 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- bluetooth mouse occasionally gets disconnected - workaround to reconnect: sudo /etc/init.d/bluetooth restart https://bugs.launchpad.net/bugs/2156936 You received this bug notification because you are subscribed to linux in Ubuntu.

[Bug 2156837] Re: seccomp-build failed in ubuntu_kernel_selftests on Resolute 7.0

** Summary changed: - seccomp_bpf fails to build on linux-oem-7.0 + seccomp-build failed in ubuntu_kernel_selftests on Resolute 7.0 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156837 Title: seccomp-build failed in ubuntu_kernel_selftests on Resolute 7.0 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Resolute: Confirmed Bug description: When we build seccomp testsuite on resolute:linux-oem-7.0, we had the following build error. 4478 03:54:42 DEBUG| Running 'make -C linux/tools/testing/selftests TARGETS=seccomp' 4479 03:54:42 DEBUG| [stdout] make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' 4480 03:54:42 DEBUG| [stdout] CC seccomp_bpf 4481 03:54:42 ERROR| [stderr] seccomp_bpf.c: In function ‘UPROBE_setup’: 4482 03:54:42 ERROR| [stderr] seccomp_bpf.c:5175:74: error: pointer type mismatch in conditional expression [-Wincompatible-pointer-types] 4483 03:54:42 ERROR| [stderr] 5175 | offset = get_uprobe_offset(variant->uretprobe ? probed_uretprobe : probed_uprobe); 4484 03:54:42 ERROR| [stderr] | ^ 4485 03:54:42 ERROR| [stderr] seccomp_bpf.c:5175:57: note: first expression has type ‘int (*)(void)’ 4486 03:54:42 ERROR| [stderr] 5175 | offset = get_uprobe_offset(variant->uretprobe ? probed_uretprobe : probed_uprobe); 4487 03:54:42 ERROR| [stderr] | ^~~~~~~~~~~~~~~~ 4488 03:54:42 ERROR| [stderr] seccomp_bpf.c:5175:76: note: second expression has type ‘int (__attribute__((nocf_check)) *)(void)’ 4489 03:54:42 ERROR| [stderr] 5175 | offset = get_uprobe_offset(variant->uretprobe ? probed_uretprobe : probed_uprobe); 4490 03:54:42 ERROR| [stderr] | ^~~~~~~~~~~~~ 4491 03:54:42 ERROR| [stderr] make[1]: *** [../lib.mk:225: /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/seccomp/seccomp_bpf] Error 1 4492 03:54:42 DEBUG| [stdout] make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' 4493 03:54:42 ERROR| [stderr] make: *** [Makefile:212: all] Error 2 [Steps to Reproduce] 1. Use an amd64 host. The defect is gated on x86_64 + CET (-fcf-protection, default on Ubuntu) AND a compiler where -Wincompatible-pointer-types is an error by default, i.e. gcc >= 14: - resolute/26.04 -> default gcc-15, reproduces directly. 2. Install the build dependencies the test harness uses: sudo apt install build-essential libcap-dev pkg-config # full suite also pulls: bc fuse kernel-wedge libfuse-dev 3. Obtain the linux-oem-7.0 source at the affected version (git tag Ubuntu-oem-7.0-7.0.0-1006.6, or "apt source linux-oem-7.0"). 4. Build the seccomp target exactly as the harness does: cd <linux-oem-7.0-source> # faithful (matches the test machine, gcc-15): make -C tools/testing/selftests TARGETS=seccomp # on noble, force the newer compiler to trigger the error: make -C tools/testing/selftests TARGETS=seccomp CC=gcc-14 [Expected Result] The seccomp target builds; seccomp_bpf binaries are produced and the tests execute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2156837/+subscriptions

[Bug 2156709] Re: Xubuntu 26.04 flickers on ThinkPad X1 Carbon Gen 14

Is `xe.enable_panel_replay=0` enough by itself? ** Tags added: psr ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Summary changed: - Xubuntu 26.04 flickers on ThinkPad X1 Carbon Gen 14 + OLED flickers on ThinkPad X1 Carbon Gen 14 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156709 Title: OLED flickers on ThinkPad X1 Carbon Gen 14 Status in linux package in Ubuntu: New Bug description: After a fresh installation of Xubuntu 26.04 on ThinkPad X1 Carbon Gen 14, flickers are observed when the mouse pointer moves. The flickers are random, and they seem to occur more often when the pointer moves over the edges of windows. The flickers become even more observable in google-chrome, where they occur (randomly) when the pointer moves over links. Thank you for taking a look. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: xorg 1:7.7+26ubuntu1 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: XFCE Date: Sun Jun 14 23:58:09 2026 DistUpgraded: Fresh install DistroCodename: resolute DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Panther Lake [Arc B390] [8086:b080] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2352] InstallationDate: Installed on 2026-06-11 (3 days ago) InstallationMedia: Xubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 21V7001BCD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=3cbf6b20-1752-432d-ac98-bf9b5a45453b ro xe.enable_panel_replay=0 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2026 dmi.bios.release: 1.12 dmi.bios.vendor: LENOVO dmi.bios.version: N4OET49W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 21V7001BCD dmi.board.vendor: LENOVO dmi.board.version: SDK0T76576 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrN4OET49W(1.12):bd05/14/2026:br1.12:efr1.9:svnLENOVO:pn21V7001BCD:pvrThinkPadX1CarbonGen14:rvnLENOVO:rn21V7001BCD:rvrSDK0T76576WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21V7_BU_Think_FM_ThinkPadX1CarbonGen14:pfaThinkPadX1CarbonGen14: dmi.product.family: ThinkPad X1 Carbon Gen 14 dmi.product.name: 21V7001BCD dmi.product.sku: LENOVO_MT_21V7_BU_Think_FM_ThinkPad X1 Carbon Gen 14 dmi.product.version: ThinkPad X1 Carbon Gen 14 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2026-06-11T23:53:25.761576 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.131-1 version.libgl1-mesa-dri: libgl1-mesa-dri 26.0.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.22-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.18-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156709/+subscriptions