[Bug 1188608] Re: Wrong glyph variant for Bulgarian Cyrillic small letter b (б, U+0431)
** Project changed: ubuntu-font-family => fonts-ubuntu (Ubuntu) ** Changed in: fonts-ubuntu (Ubuntu) Status: New => Triaged ** Changed in: fonts-ubuntu (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1188608 Title: Wrong glyph variant for Bulgarian Cyrillic small letter b (б, U+0431) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-ubuntu/+bug/1188608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1188608] Re: Wrong glyph variant for Bulgarian Cyrillic small letter b (б, U+0431)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fonts-ubuntu (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1188608 Title: Wrong glyph variant for Bulgarian Cyrillic small letter b (б, U+0431) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-ubuntu/+bug/1188608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
Hi Aleksandr, sound more likely the other issue. Since this issue is fixed, could you please report the other with attaching logs? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1188608] [NEW] Wrong glyph variant for Bulgarian Cyrillic small letter b (б, U+0431)
You have been subscribed to a public bug: The current Ubuntu font family uses the Serbian/Macedonian glyph variant for the Cyrillic small letter b (б, U+0431) when text in Bulgarian is rendered. The affected fonts have a specific substitution table that replaces the default correct glyph with the wrong language specific one. This is related to https://bugs.launchpad.net/ubuntu-font- family/+bug/708578. As suggested in one of the last comments there, Bulgarian should use the exact same glyphs as Russian in all styles, including italic. No other font family uses the Serbian/Macedonian glyphs for Bulgarian, including pre-computer printed material. Example generated with: pango-view -o /tmp/bulgarian-b.pdf --font 'Ubuntu 24' --width=250 --markup --text "Expected glyphs: б б Actual glyphs: б б" ** Affects: fonts-ubuntu (Ubuntu) Importance: Undecided Status: New -- Wrong glyph variant for Bulgarian Cyrillic small letter b (б, U+0431) https://bugs.launchpad.net/bugs/1188608 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895283] Re: libdevel-declare-perl 0.006022-1 breaks libperl5i-perl 2.13.2-1
** Changed in: libperl5i-perl (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895283 Title: libdevel-declare-perl 0.006022-1 breaks libperl5i-perl 2.13.2-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdevel-declare-perl/+bug/1895283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977646] Re: Snap apps launch time are EXTREMELY slow
*** This bug is a duplicate of bug 1833004 *** https://bugs.launchpad.net/bugs/1833004 Thanks Islam for reporting this. I'm going to mark this as a duplicate, as we already have this issue reported as bug 1833004. ** This bug has been marked a duplicate of bug 1833004 Application SNAP is slower than DEB at first launch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977646 Title: Snap apps launch time are EXTREMELY slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1977646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778375] Re: All snap loops are being output for lsblk, blkid, and fdisk -l.
Hi Anthony, thanks for reporting this bug (I just found it accidentally while browsing through the existing bugs. I'm afraid that there's little we can do about the fact that these programs also list the mounted snaps -- there might be even scripts, by now, which rely on this behaviour. Where I think we could do something, it's about the fact that the same snap can appear twice, if there are two revisions of it installed; I guess we could avoid mounting the old one -- I'll check with the rest of the team to understand if there is a reason why it has to be this way. ** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Alberto Mardegan (mardy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778375 Title: All snap loops are being output for lsblk, blkid, and fdisk -l. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1778375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977701] Re: Update to latest upstream release 20220510 / IPU 2022.1 to fix multiple security vulnerabilities
** Changed in: intel-microcode (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: intel-microcode (Ubuntu Focal) Status: New => Fix Committed ** Changed in: intel-microcode (Ubuntu Impish) Status: New => Fix Committed ** Changed in: intel-microcode (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977701 Title: Update to latest upstream release 20220510 / IPU 2022.1 to fix multiple security vulnerabilities To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1977701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977701] [NEW] Update to latest upstream release 20220510 / IPU 2022.1 to fix multiple security vulnerabilities
Public bug reported: Intel released version 20220510 / IPU 2022.1 earlier in May to address multiple vulnerabilities, including: - CVE-2022-21151, INTEL-SA-00617 - CVE-2021-0146, INTEL-SA-00528 - CVE-2021-0127, INTEL-SA-00532 This version is already packaged in Ubuntu 22.10 (kinetic). Whilst this is a security update, to allow for increased testing before being more widely deployed the Ubuntu Security team are wishing to publish this first via -proposed and then to -updates at which point it will also then be published to -security. ** Affects: intel-microcode (Ubuntu) Importance: Undecided Status: New ** Affects: intel-microcode (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: intel-microcode (Ubuntu Focal) Importance: Undecided Status: New ** Affects: intel-microcode (Ubuntu Impish) Importance: Undecided Status: New ** Affects: intel-microcode (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: block-proposed-bionic block-proposed-focal block-proposed-impish block-proposed-jammy ** Also affects: intel-microcode (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: intel-microcode (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: intel-microcode (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: intel-microcode (Ubuntu Impish) Importance: Undecided Status: New ** Tags added: block-proposed-bionic ** Tags added: block-proposed-focal block-proposed-impish block- proposed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977701 Title: Update to latest upstream release 20220510 / IPU 2022.1 to fix multiple security vulnerabilities To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1977701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838433] Re: mate-panel crashes when re-ordering the window list applet
[Expired for mate-panel (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mate-panel (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838433 Title: mate-panel crashes when re-ordering the window list applet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1838433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868328] Re: Some windows draw slowly with nvidia-440 drivers
[Expired for marco (Ubuntu) because there has been no activity for 60 days.] ** Changed in: marco (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868328 Title: Some windows draw slowly with nvidia-440 drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1868328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855559] Re: all QT applications miss the menu under MATE/Marco
[Expired for marco (Ubuntu) because there has been no activity for 60 days.] ** Changed in: marco (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/189 Title: all QT applications miss the menu under MATE/Marco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858665] Re: clock-applet crashed with SIGSEGV in claim_op()
[Expired for mate-panel (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mate-panel (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858665 Title: clock-applet crashed with SIGSEGV in claim_op() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1858665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871004] Re: clock-applet crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
[Expired for mate-panel (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mate-panel (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871004 Title: clock-applet crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1871004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869529] Re: celluloid menubar and toolbar are transparent on loading
[Expired for ubuntu-mate-artwork (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-mate-artwork (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869529 Title: celluloid menubar and toolbar are transparent on loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/celluloid/+bug/1869529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872538] Re: Marco crashed after closing MATE Tweak panel
[Expired for marco (Ubuntu) because there has been no activity for 60 days.] ** Changed in: marco (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872538 Title: Marco crashed after closing MATE Tweak panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1872538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872363] Re: fish-applet assert failure: fish-applet: ../../src/xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
[Expired for mate-panel (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mate-panel (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872363 Title: fish-applet assert failure: fish-applet: ../../src/xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1872363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874425] Re: Sometimes hangup for 28 seconds at shutdown or reboot
[Expired for marco (Ubuntu) because there has been no activity for 60 days.] ** Changed in: marco (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874425 Title: Sometimes hangup for 28 seconds at shutdown or reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1874425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875202] Re: When Firefox titlebar is turned off windows controls are impacted.
[Expired for ubuntu-mate-artwork (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-mate-artwork (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875202 Title: When Firefox titlebar is turned off windows controls are impacted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1875202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875202] Re: When Firefox titlebar is turned off windows controls are impacted.
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875202 Title: When Firefox titlebar is turned off windows controls are impacted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1875202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906787] Re: clock-applet crashed with SIGSEGV in _g_closure_invoke_va()
[Expired for mate-panel (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mate-panel (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906787 Title: clock-applet crashed with SIGSEGV in _g_closure_invoke_va() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1906787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920798] Re: marco crashed with SIGSEGV
[Expired for marco (Ubuntu) because there has been no activity for 60 days.] ** Changed in: marco (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920798 Title: marco crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1920798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922422] Re: wnck-applet crashed with signal 5
[Expired for mate-panel (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mate-panel (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922422 Title: wnck-applet crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1922422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967829] Re: package tftpd-hpa 5.2+20150808-1.2build1 failed to install/upgrade: installed tftpd-hpa package post-installation script subprocess returned error exit status 1
[Expired for tftp-hpa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: tftp-hpa (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967829 Title: package tftpd-hpa 5.2+20150808-1.2build1 failed to install/upgrade: installed tftpd-hpa package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1967829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967894] Re: KVM IPI Virtualization support for SPR
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967894 Title: KVM IPI Virtualization support for SPR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974111] Re: Mute/mic LEDs no function on Elitebook 630
Install linux/5.15.0-36.37 on Elitebook 630 and mic mute/audio mute LEDS are working fine. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974111 Title: Mute/mic LEDs no function on Elitebook 630 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1974111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976613] Re: Enable Asus USB-BT500 Bluetooth dongle(0b05:190e)
** Description changed: [Impact] + To enable Asus USB-BT500 Bluetooth dongle(0b05:190e) [Fix] + 2 commits from v5.14 are required + 33404381c5e8 Bluetooth: btusb: Add 0x0b05:0x190e Realtek 8761BU (ASUS BT500) device. + 04896832c94a Bluetooth: btrtl: Add support for RTL8761B + + One more commit to fix the conflicts + 3e4e3f73b9f4 Bluetooth: btusb: Add flag to define wideband speech capability + + And this commit for linux-firmware + 7118987b rtl_bt: Add rtl8761b firmware [Test] + Verified on the machine with ASUS USB-BT500 dongle, it can scan devices. [Where problems could occur] + Adding new table and new ID for new device, should have no impact to old devices -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976613 Title: Enable Asus USB-BT500 Bluetooth dongle(0b05:190e) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1976613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977699] [NEW] zfs icp has deselected all optimized aes & gcm impls
Public bug reported: In an upgrade from Jammy kernel 5.15.0-27-generic to 5.15.0-35-generic on x86_64 (AMD threadripper pro 39x5wx series), a 40x performance regression in the first read of cached writes to an encrypted dataset revealed that zfs is no longer configured to choose any implementations from advanced instruction sets: $ grep . /sys/module/icp/parameters/*impl* /sys/module/icp/parameters/icp_aes_impl:cycle [fastest] generic x86_64 /sys/module/icp/parameters/icp_gcm_impl:cycle [fastest] generic With correct configuration, the output should read as follows: $ grep . /sys/module/icp/parameters/*impl* /sys/module/icp/parameters/icp_aes_impl:cycle [fastest] generic x86_64 aesni /sys/module/icp/parameters/icp_gcm_impl:cycle [fastest] avx generic pclmulqdq The immediate ill effects are the use of gcm_generic_mul instead of the dedicated instruction, consuming 50% CPU and slowing reads of data cached in ram to less than 20% of what they would be even reading directly from disk. openzfs changed its configure process to detect cpu features differently recently to adapt to the kernel api change. It seems that the upstream changes that unexport the needed symbols and the downstream changes in openzfs that stop using them were not cherrypicked in sync. https://github.com/openzfs/zfs/pull/13147 https://github.com/openzfs/zfs/pull/13236 ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977699 Title: zfs icp has deselected all optimized aes & gcm impls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1977699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970957] Re: suspend problem
Lenovo ThinkPad X1 Yoga 1st, Intel® Core™ i7-6600U CPU @ 2.60GHz × 4 , with Mesa Intel® HD Graphics 520 (SKL GT2), does not resume after suspending or closing the lid. Various suggested tweaks to the login XDM, etc. don't appear to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970957 Title: suspend problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971417] Re: Fix REG_WAIT timeout for Yellow Carp
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971417 Title: Fix REG_WAIT timeout for Yellow Carp To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1971417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946200] Re: With the Nvidia driver installed there is no option to use Wayland on the login screen
This issue should be fixed in latest gdm in 22.04. I tried the latest jammy + dist-upgrade, the option is there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946200 Title: With the Nvidia driver installed there is no option to use Wayland on the login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959721] Re: unchecked MSR access error: WRMSR to 0xd10
I am hitting this with 5.15.0-35-generic. ASUS Prime Z690M-PLUS D4 with i12600k CPU. Jun 05 17:42:38 deca kernel: unchecked MSR access error: WRMSR to 0xd10 (tried to write 0x) at rIP: 0xfff> Jun 05 17:42:38 deca kernel: Call Trace: Jun 05 17:42:38 deca kernel: Jun 05 17:42:38 deca kernel: ? cat_wrmsr+0x43/0x60 Jun 05 17:42:38 deca kernel: domain_add_cpu+0x2c9/0x470 Jun 05 17:42:38 deca kernel: ? domain_add_cpu+0x470/0x470 Jun 05 17:42:38 deca kernel: resctrl_online_cpu+0x4d/0xb0 Jun 05 17:42:38 deca kernel: cpuhp_invoke_callback+0x108/0x410 Jun 05 17:42:38 deca kernel: cpuhp_thread_fun+0xc0/0x1b0 Jun 05 17:42:38 deca kernel: smpboot_thread_fn+0xb7/0x150 Jun 05 17:42:38 deca kernel: ? smpboot_register_percpu_thread+0x130/0x130 Jun 05 17:42:38 deca kernel: kthread+0x127/0x150 Jun 05 17:42:38 deca kernel: ? set_kthread_struct+0x50/0x50 Jun 05 17:42:38 deca kernel: ret_from_fork+0x1f/0x30 Jun 05 17:42:38 deca kernel: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959721 Title: unchecked MSR access error: WRMSR to 0xd10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1959721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977694] Re: [CVE-2022-24713] Denial of service in compiler with rust-regex
The attachment "Proposed Jammy Patch" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977694 Title: [CVE-2022-24713] Denial of service in compiler with rust-regex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-regex/+bug/1977694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976330]
The [Bugbug](https://github.com/mozilla/bugbug/) bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976330 Title: No dropdown menu on bookmarks folder in trunk build under wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1976330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977695] [NEW] Black Screen on Boot with X11
Public bug reported: Description:Ubuntu 22.04 LTS Release:22.04 xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 1. Uncomment WaylandEnable=false in /etc/gdm3/custom.conf 2. Reboot. 3. See black screen after selecting Ubuntu at GRUB prompt. Login screen never loads. Unplugging any external monitors appears to have no effect on the bug. I am aware that most users of Ubuntu 22.04 see an option at the login screen to change the display manager. I have never seen such an option. My machine always uses Wayland unless I modify /etc/gdm3/custom.conf directly. Using Wayland is detrimental to my health, because the Night Light feature does nothing. I have nvidia-driver-510 installed. I am happy to provide further debugging information upon request. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.73.05 Sat May 7 05:30:26 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 5 15:47:31 2022 DistUpgraded: 2022-05-07 18:27:00,043 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8259] Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8259] InstallationDate: Installed on 2020-12-09 (543 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP OMEN by HP Laptop ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-35-generic root=UUID=13d7b775-7783-44fc-8e24-164127457fd4 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-05-08 (28 days ago) dmi.bios.date: 12/22/2020 dmi.bios.release: 15.56 dmi.bios.vendor: Insyde dmi.bios.version: F.56 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8259 dmi.board.vendor: HP dmi.board.version: 83.72 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 83.72 dmi.modalias: dmi:bvnInsyde:bvrF.56:bd12/22/2020:br15.56:efr83.72:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8259:rvr83.72:cvnHP:ct10:cvrChassisVersion:skuW2N35UAR#ABA: dmi.product.family: 103C_5335KV HP Omen dmi.product.name: OMEN by HP Laptop dmi.product.sku: W2N35UAR#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977695 Title: Black Screen on Boot with X11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1977695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977694] Re: [CVE-2022-24713] Denial of service in compiler with rust-regex
** Description changed:
There is a denial of service in rust-regex. Below is an SRU template to
prepare for patching CVE-2022-24713.
- https://ubuntu.com/security/CVE-2022-24713
- https://blog.rust-lang.org/2022/03/08/cve-2022-24713.html
-
https://github.com/rust-lang/regex/commit/ae70b41d4f46641dbc45c7a4f87954aea356283e
+ [Impact]
+
+ * The rust compile can compile a regex an empty sub-expression as many times
as wanted.
+ * Take '(?:){294967295}' - this would make the regex compiler compile
294967295 times.
+ * This results in a denial of service; there wouldnt be a crash but the
compiler would take forever and eventually get there.
+ * An attacker could use this amount of time it takes for the compiler to
parse this regex to perform DoS attacks
+
+ [Test Plan]
+
+ * Take a regex from the regex crate that is still vulnerable - get pre 1.5.5.
+ * Use one of the test cases provided in the fix commit
https://github.com/rust-lang/regex/commit/ae70b41d4f46641dbc45c7a4f87954aea356283e
or use this POC i made: https://github.com/ItzSwirlz/CVE-2022-24713-POC
+ * Building using the old regex would take forever, but the fix would take a
shorter time.
+
+ [Where problems could occur]
+
+ * An integer overflow might still be able to cause a regex overload
+ * Changes to the rust libraries/packages and other SRUs may create
regressions with updates that may outdate the library
+
+ * This fix adds a fake amount of memory any time a regex empty
sub-expression is compiiled, and then adds to the Inst in the existing indirect
heap usage.
+ * This means maybe an attacker could overload the amount of Regex's and make
compiling impossible? Memory may be lost in very specific situations, or a heap
buffer issue can occur
+
+ [Other Info]
+
+ * Impacts Focal, Impish, Jammy
+
+ * Links:
+
https://github.com/rust-lang/regex/commit/ae70b41d4f46641dbc45c7a4f87954aea356283e
+https://blog.rust-lang.org/2022/03/08/cve-2022-24713.html
+https://ubuntu.com/security/CVE-2022-24713
+https://github.com/rust-lang/regex/security/advisories/GHSA-m5pq-gvj9-9vr8
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: librust-regex-dev 1.5.4-1
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckMismatches: ./casper/filesystem.manifest-remove
CasperMD5CheckResult: fail
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sun Jun 5 18:26:32 2022
InstallationDate: Installed on 2022-04-22 (44 days ago)
InstallationMedia: Ubuntu Unity 22.04
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: rust-regex
UpgradeStatus: No upgrade log present (probably fresh install)
** Changed in: rust-regex (Ubuntu)
Assignee: (unassigned) => Joshua Peisach (itzswirlz)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977694
Title:
[CVE-2022-24713] Denial of service in compiler with rust-regex
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rust-regex/+bug/1977694/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977694] Re: [CVE-2022-24713] Denial of service in compiler with rust-regex
** Patch added: "Proposed Jammy Patch" https://bugs.launchpad.net/ubuntu/+source/rust-regex/+bug/1977694/+attachment/5594991/+files/rust-regex_1.5.4-1ubuntu0.1.debdiff ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977694 Title: [CVE-2022-24713] Denial of service in compiler with rust-regex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-regex/+bug/1977694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970507] Re: No security updates since release in all Ubuntu releases
I am going through the last XSA (XSA-400) and will, if a local build is successful, add a patch for Focal tomorrow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970507 Title: No security updates since release in all Ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1970507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
echo snap >> ~/.hidden Might be a default configuration for all new users if included in /etc/skel ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977619] Re: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC
** Summary changed: - NetworkManager 1.36.6 orders IPv6 addresses incorrectly + NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977619 Title: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907652] Re: postgresql packages in the removal blacklist making it hard to upgrade
It has been over a year and half since the bug is reported and confirmed. Any progress? The bug holds us back on upgrading a few PostgreSQL/Postgis servers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907652 Title: postgresql packages in the removal blacklist making it hard to upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1907652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970507] Re: No security updates since release in all Ubuntu releases
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-3639 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970507 Title: No security updates since release in all Ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1970507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959747] Re: [upstream] Very high CPU and slow responsiveness in Thunderbird 91
I'm having similar problems in 1:91.10.0+build1-0ubuntu0.20.04.1 with Thunderbird's CPU usage well over 25 % and for long periods and additionally causing root process Xorg to consume 15 % CPU. See also: https://bugzilla.mozilla.org/show_bug.cgi?id=1772673 The workaround for me is: gfx.webrender.force-disabled = true ** Bug watch added: Mozilla Bugzilla #1772673 https://bugzilla.mozilla.org/show_bug.cgi?id=1772673 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959747 Title: [upstream] Very high CPU and slow responsiveness in Thunderbird 91 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1959747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810499] Re: Provide a function to undo all upgrades of proposed packages
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810499 Title: Provide a function to undo all upgrades of proposed packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1810499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
Confirmed. #36 The switching to XORG has solved all keyboard layout issues. Also, it solved the "Double click on the window Title to expand a window" issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977687] Re: apache on Ubuntu 22.04 is several times slower than on other distros, according to Phoronix
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apache2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977687 Title: apache on Ubuntu 22.04 is several times slower than on other distros, according to Phoronix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1977687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947115] Re: VAAPI / HW-acceleration not working Snap-packaged Firefox
Ahh yeah, I just noticed that VAAPI works again now with Firefox 101.0-2 and Firefox 102.0b2-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947115 Title: VAAPI / HW-acceleration not working Snap-packaged Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970615] Re: WebGL does not work in snap firefox
It also appears to be working with Firefox 101.0-2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970615 Title: WebGL does not work in snap firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1970615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] Re: Ubuntu 22.04 unable to mount root partition
Thanks alot! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot
I tried with pci=nocrs on Linux 5.18 and now it works, just to let you know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly
** Description changed: Situation: - My network has both DHCPv6 and SLAAC for IPv6. From a privacy + My network has both DHCPv6 and SLAAC (autoconf) for IPv6. From a privacy perspective, for readability reasons and for network management policies, DHCPv6 should *always* be preferred over SLAAC addresses when available. And according to RFC 6724, the smaller /128 scope of the DHCPv6 address should be chosen over the larger /64 scope of the SLAAC address. NetworkManager has always been able to adhere to that by simply setting ip6.privacy=0 for the connection (in nm-connection-editor *not* selecting "Prefer temporary address" for IPv6 privacy extensions). Then it would use the DHCPv6 address as the source for all outgoing traffic. So if you would - for instance - run `curl ifconfig.co`, the DHCPv6 address would be used to connect to the outside world and be echoed back. Regression: Since the update to 1.36.6, this is no longer the case. NetworkManager now routes outgoing traffic through the SLAAC address, even if ip6.privacy=0 is set for the connection. Constantly removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's on the router are now the only ways to stop NetworkManager from preferring SLAAC over DHCPv6. None of the local options in NetworkManager 1.36.6 are able to restore the previous, desired and correct way of working: the SLAAC address should never be used as the preferred address if a DHCPv6 lease is given. Looking at the changelog of NetworkManager 1.36.6, multiple things regarding IP address order and temporary addresses have been changed in that release: * Fix a bug in synchronization of IP addresses with kernel that could lead to a wrong address order. * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag is set. * Ensure temporary IPv6 addresses are removed on disconnect and reapply. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS Steps to reproduce: 1. Connect to a network where the router sends "A" and "M" bits in the RA's and has a DHCPv6 server running (e.g. any OpenWrt router). 2. When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6 addresses. With NetworkManager 1.36.4 and earlier, this was not the case. (The Linux kernel uses the address highest in the list as preferred.) 3. When running something like `curl ifconfig.co`, the SLAAC address is being returned, which makes sense as that is now preferred by the kernel. (But it shouldn't be.) Desired behaviour: NetworkManager should always sort DHCPv6 addresses above SLAAC addresses, as is the case for all versions prior to 1.36.6 and also corrected again in 1.38.0. In case static addresses are manually set, - those should take first priority, with DHCPv6 second and SLAAC last. + those should take first priority, with DHCPv6 second and SLAAC/autoconf + last. Implications: This can break many real-life use cases. For instance, my router gives out static leases to my machines. Those addresses are whitelisted in all kinds of firewalls to allow me to access servers for my work. Now that the "wrong" address is being preferred for outgoing traffic (a SLAAC address that I have no influence on and cannot centrally configure), I am being locked out of the servers in question unless I forcefully remove the addresses or disable SLAAC on my router, so my outgoing traffic is being routed through the DHCPv6 address again. Note that "just disabling SLAAC RA's on the router" is not something everybody can do, as it requires root access to the device. Moreover, it would break IPv6 connectivity entirely for devices that don't support DHCPv6 (read: Android). Conclusion: So this update introduces a very breaking change in IPv6 source address selection to an LTS release, while LTS releases should be stable. I should note that the bug is not present in NetworkManager 1.38.0 on Debian sid. That just prefers DHCPv6 addresses when available, like it should. As that version is also used in Ubuntu kinetic, most likely this bug is not present there. Looking at the changelog of 1.38.0: * Fix bug setting priority for IP addresses. * Static IPv6 addresses from "ipv6.addresses" are now preferred over addresses from DHCPv6, which are preferred over addresses from autoconf. This affects IPv6 source address selection, if the rules from RFC 6724, section 5 don't give a exhaustive match. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-38/NEWS It looks like Ubuntu just introduced that bug by upgrading to 1.36.6. Please either backport the fix from 1.38.0 or revert to 1.36.4, which was working fine. System information: /etc/os-release: PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS
[Bug 1973317] Re: pam_chroot.so installed in wrong place - Not able to login after upgrade
** Description changed: The library pam_chroot.so is installed in the wrong location, therefore it cannot be loaded. This prevents anyone (incl. root) to log into systems that require that module. ``` ./auth.log:May 10 20:19:16 web-proxy sshd[981]: PAM unable to dlopen(pam_chroot.so): /lib/security/pam_chroot.so: cannot open shared object file: No such file or directory ./auth.log:May 10 20:19:16 web-proxy sshd[981]: PAM adding faulty module: pam_chroot.so ``` Current wrong location: `/usr/lib/x86_64-linux-gnu/pam_chroot.so` Correct location: /lib/security/pam_chroot.so -> /usr/lib/x86_64-linux-gnu/security/ + `ln -v -s -r -t /usr/lib/x86_64-linux-gnu/security/ /usr/lib/x86_64-linux-gnu/pam_chroot.so` Workaround: Boot from a live linux system and move/copy/link file to correct location. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libpam-chroot 0.9-5 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri May 13 12:12:36 2022 InstallationDate: Installed on 2020-12-07 (521 days ago) InstallationMedia: Ubuntu-Server 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: libpam-chroot UpgradeStatus: Upgraded to jammy on 2022-05-10 (2 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973317 Title: pam_chroot.so installed in wrong place - Not able to login after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpam-chroot/+bug/1973317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly
** Description changed: Situation: My network has both DHCPv6 and SLAAC for IPv6. From a privacy perspective, for readability reasons and for network management policies, DHCPv6 should *always* be preferred over SLAAC addresses when available. And according to RFC 6724, the smaller /128 scope of the DHCPv6 address should be chosen over the larger /64 scope of the SLAAC address. NetworkManager has always been able to adhere to that by simply setting ip6.privacy=0 for the connection (in nm-connection-editor *not* selecting "Prefer temporary address" for IPv6 privacy extensions). Then it would use the DHCPv6 address as the source for all outgoing traffic. So if you would - for instance - run `curl ifconfig.co`, the DHCPv6 address would be used to connect to the outside world and be echoed back. - Regression: Since the update to 1.36.6, this is no longer the case. NetworkManager now routes outgoing traffic through the SLAAC address, even if ip6.privacy=0 is set for the connection. Setting net.ipv6.conf.all.use_tempaddr=0 and net.ipv6.conf..use_tempaddr=0 with sysctl also no longer has any effect. Removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's on the router is the only way to stop NetworkManager from preferring SLAAC over DHCPv6 now. None of the local options in NetworkManager 1.36.6 are able to restore the previous, desired and correct way of working. Looking at the changelog of NetworkManager 1.36.6, multiple things regarding IP address order and temporary addresses have been changed in that release: * Fix a bug in synchronization of IP addresses with kernel that could lead to a wrong address order. * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag is set. * Ensure temporary IPv6 addresses are removed on disconnect and reapply. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS - Steps to reproduce: 1. Connect to a network where the router sends "A" and "M" bits in the RA's and has a DHCPv6 server running (e.g. any OpenWrt router). 2. When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6 addresses. With NetworkManager 1.36.4 and earlier, this was not the case. (The Linux kernel uses the address highest in the list as preferred.) 3. When running something like `curl ifconfig.co`, the SLAAC address is being returned, which makes sense as that is now preferred by the kernel. (But it shouldn't be.) - Desired behaviour: NetworkManager should always sort DHCPv6 addresses above SLAAC addresses, as is the case for all versions prior to 1.36.6 and also corrected again in 1.38.0. In case static addresses are manually set, those should take first priority, with DHCPv6 second and SLAAC last. - Implications: This can break many real-life use cases. For instance, my router gives out static leases to my machines. Those addresses are whitelisted in all kinds of firewalls to allow me to access servers for my work. Now that the "wrong" address is being preferred for outgoing traffic (a SLAAC address that I have no influence on and cannot centrally configure), I am being locked out of the servers in question unless I forcefully remove the addresses or disable SLAAC on my router, so my outgoing traffic is being routed through the DHCPv6 address again. + Note that "just disabling SLAAC RA's on the router" is not something + everybody can do, as it requires root access to the device. Moreover, it + would break IPv6 connectivity entirely for devices that don't support + DHCPv6 (read: Android). Conclusion: So this update introduces a very breaking change in IPv6 source address selection to an LTS release, while LTS releases should be stable. I should note that the bug is not present in NetworkManager 1.38.0 on Debian sid. That just prefers DHCPv6 addresses when available, like it should. As that version is also used in Ubuntu kinetic, most likely this bug is not present there. Looking at the changelog of 1.38.0: * Fix bug setting priority for IP addresses. * Static IPv6 addresses from "ipv6.addresses" are now preferred over addresses from DHCPv6, which are preferred over addresses from autoconf. This affects IPv6 source address selection, if the rules from RFC 6724, section 5 don't give a exhaustive match. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-38/NEWS So it looks like Ubuntu just introduced that bug by upgrading to 1.36.6. Please either backport the fix from 1.38.0 or revert to 1.36.4, which was working fine. - System information: /etc/os-release: PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/;
[Bug 1976341] Re: the .netrc man page neglects to disclose the format for the password string
Also note that wget checks the syntax of the ~/.netrc file every time it runs with default options, and it gives a warning when bash-style quoting is used for FTP & Fetchmail. Reported here: https://savannah.gnu.org/bugs/index.php?62586 ** Bug watch added: GNU Savannah Bug Tracker #62586 http://savannah.gnu.org/bugs/?62586 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976341 Title: the .netrc man page neglects to disclose the format for the password string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netkit-ftp/+bug/1976341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947475] Re: PAM: pam_chroot.so not accessible after upgrade 21.04 > 21.10
Still an issue with 22.04 LTS, see https://bugs.launchpad.net/ubuntu/+source/libpam-chroot/+bug/1973317 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947475 Title: PAM: pam_chroot.so not accessible after upgrade 21.04 > 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpam-chroot/+bug/1947475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977687] Re: apache on Ubuntu 22.04 is several times slower than on other distros, according to Phoronix
** Changed in: apache2 (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977687 Title: apache on Ubuntu 22.04 is several times slower than on other distros, according to Phoronix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1977687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977684] Re: After Upgrade to 22.04. System does not boot into graphical mode without being connected to the network
** Package changed: ubuntu => ubuntu-release-upgrader (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977684 Title: After Upgrade to 22.04. System does not boot into graphical mode without being connected to the network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1977684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977689] [NEW] Wrong error msg: "state file /var/lib/logrotate/status is world-readable" although it is not
Public bug reported: Ubuntu 22.04 logrotate 3.19.0-1ubuntu1.1 Every hour, I receive this wrong message: Subject:Cron >cd / && run-parts --report /etc/cron.hourly /etc/cron.hourly/logrotate: error: state file /var/lib/logrotate/status is world-readable and thus can be locked from other unprivileged users. Skipping lock acquisition... despite: # ls -al /var/lib/logrotate total 40 drwxr-x--- 2 root root 4096 Jun 5 17:17 . drwxr-xr-x 66 root root 4096 Jun 3 20:02 .. -rw-r- 1 root root 31974 Jun 5 17:17 status ** Affects: logrotate (Ubuntu) Importance: Undecided Status: New ** Description changed: Ubuntu 22.04 logrotate 3.19.0-1ubuntu1.1 Every hour, I receive this wrong message: + + Subject: Cron >cd / && run-parts --report /etc/cron.hourly /etc/cron.hourly/logrotate: error: state file /var/lib/logrotate/status is world-readable and thus can be locked from other unprivileged users. Skipping lock acquisition... despite: # ls -al /var/lib/logrotate total 40 drwxr-x--- 2 root root 4096 Jun 5 17:17 . drwxr-xr-x 66 root root 4096 Jun 3 20:02 .. -rw-r- 1 root root 31974 Jun 5 17:17 status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977689 Title: Wrong error msg: "state file /var/lib/logrotate/status is world- readable" although it is not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1977689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977688] [NEW] package shim-signed 1.51+15.4-0ubuntu9 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1
Public bug reported: When i want to install a decode video software, it is appeared ProblemType: Package DistroRelease: Ubuntu 21.04 Package: shim-signed 1.51+15.4-0ubuntu9 ProcVersionSignature: Ubuntu 5.11.0-49.55-generic 5.11.22 Uname: Linux 5.11.0-49-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled' ApportVersion: 2.20.11-0ubuntu65.4 AptOrdering: libfdk-aac2:amd64: Install gstreamer1.0-fdkaac:amd64: Install NULL: ConfigurePending Architecture: amd64 BootEFIContents: BOOTX64.CSV grub.cfg grubx64.efi mmx64.efi shimx64.efi CasperMD5CheckResult: unknown Date: Sun Jun 5 20:16:55 2022 DpkgHistoryLog: Start-Date: 2022-06-05 20:16:29 Commandline: packagekit role='install-packages' Requested-By: nilay (1000) Install: libfdk-aac2:amd64 (2.0.1-1, automatic), gstreamer1.0-fdkaac:amd64 (1.18.3-2build1) EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2: EFI variables are not supported on this system. EFITables: ErrorMessage: installed shim-signed package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.4ubuntu0.1 SourcePackage: shim-signed Title: package shim-signed 1.51+15.4-0ubuntu9 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977688 Title: package shim-signed 1.51+15.4-0ubuntu9 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1977688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly
** Description changed: - My network has both DHCPv6 and SLAAC for IPv6. From both a privacy - perspective and readability reasons, DHCPv6 should *always* be preferred - over SLAAC addresses when available. And according to RFC 6724 the - smaller /128 scope of the DHCPv6 address should be chosen over the - larger /64 scope of the SLAAC address. + Situation: + + My network has both DHCPv6 and SLAAC for IPv6. From a privacy + perspective, for readability reasons and for network management + policies, DHCPv6 should *always* be preferred over SLAAC addresses when + available. And according to RFC 6724, the smaller /128 scope of the + DHCPv6 address should be chosen over the larger /64 scope of the SLAAC + address. NetworkManager has always been able to adhere to that by simply setting ip6.privacy=0 for the connection (in nm-connection-editor *not* selecting "Prefer temporary address" for IPv6 privacy extensions). Then it would use the DHCPv6 address as the source for all outgoing traffic. So if you would - for instance - run `curl ifconfig.co`, the DHCPv6 address would be used to connect to the outside world and be echoed back. + + Regression: + Since the update to 1.36.6, this is no longer the case. NetworkManager now routes outgoing traffic through the SLAAC address, even if ip6.privacy=0 is set for the connection. Setting net.ipv6.conf.all.use_tempaddr=0 and net.ipv6.conf..use_tempaddr=0 with sysctl also no longer has any effect. Removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's - altogether is the only way to stop NetworkManager from preferring SLAAC - over DHCPv6 now. + on the router is the only way to stop NetworkManager from preferring + SLAAC over DHCPv6 now. None of the local options in NetworkManager + 1.36.6 are able to restore the previous, desired and correct way of + working. - Looking at the changelog of NetworkManager 1.36.6, things regarding IP - address order and temporary addresses have been changed in that release: + Looking at the changelog of NetworkManager 1.36.6, multiple things + regarding IP address order and temporary addresses have been changed in + that release: * Fix a bug in synchronization of IP addresses with kernel that could lead to a wrong address order. * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag is set. * Ensure temporary IPv6 addresses are removed on disconnect and reapply. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS - When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6 - addresses. With NetworkManager 1.36.4 this was not the case. (The Linux - kernel uses the address highest in the list as preferred.) + + Steps to reproduce: + + 1. Connect to a network where the router sends "A" and "M" bits in the + RA's and has a DHCPv6 server running (e.g. any OpenWrt router). + + 2. When running `ip -6 a`, the list now sorts SLAAC addresses above + DHCPv6 addresses. With NetworkManager 1.36.4 and earlier, this was not + the case. (The Linux kernel uses the address highest in the list as + preferred.) + + 3. When running something like `curl ifconfig.co`, the SLAAC address is + being returned, which makes sense as that is now preferred by the + kernel. (But it shouldn't be.) + + + Desired behaviour: + + NetworkManager should always sort DHCPv6 addresses above SLAAC + addresses, as is the case for all versions prior to 1.36.6 and also + corrected again in 1.38.0. In case static addresses are manually set, + those should take first priority, with DHCPv6 second and SLAAC last. + + + Implications: This can break many real-life use cases. For instance, my router gives out static leases to my machines. Those addresses are whitelisted in all kinds of firewalls to allow me to access servers for my work. Now that the "wrong" address is being preferred for outgoing traffic (a SLAAC - address that I have no influence on), I am being locked out of the - servers in question unless I forcefully remove the addresses or disable - SLAAC on my router, so my outgoing traffic is being routed through the - DHCPv6 address again. + address that I have no influence on and cannot centrally configure), I + am being locked out of the servers in question unless I forcefully + remove the addresses or disable SLAAC on my router, so my outgoing + traffic is being routed through the DHCPv6 address again. + + + Conclusion: So this update introduces a very breaking change in IPv6 source address selection to an LTS release, while LTS releases should be stable. I should note that the bug is not present in NetworkManager 1.38.0 on Debian sid. That just prefers DHCPv6 addresses when available, like it - should. + should. As that version is also used in Ubuntu kinetic, most likely this + bug is not present there. + + Looking at the changelog of 1.38.0: + + * Fix bug setting priority for IP addresses. + *
[Bug 1977687] [NEW] apache on Ubuntu 22.04 is several times slower than on other distros, according to Phoronix
Public bug reported: Dear Maintainer, according to this recent Phoronix test apache on Ubuntu 22.04 (as well as on Debian) is several times slower than on other distros: https://www.phoronix.com/scan.php?page=article=h1-2022-linux=7 It is not entirely clear how the test was performed, and given the test says version is 2.4.48 it may be using a custom build apache version and not the Ubuntu package. Also it may be an issue not strictly related to apache, since that test shows that other tests are also a lot slower on Ubuntu. Nonetheless, given that apache is a common work usage on Ubuntu server, I report this issue in case someone has interest in checking what's going on. Thanks. ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New ** Affects: apache2 (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #1012358 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012358 ** Also affects: apache2 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012358 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977687 Title: apache on Ubuntu 22.04 is several times slower than on other distros, according to Phoronix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1977687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly
** Description changed: My network has both DHCPv6 and SLAAC for IPv6. From both a privacy perspective and readability reasons, DHCPv6 should *always* be preferred over SLAAC addresses when available. And according to RFC 6724 the smaller /128 scope of the DHCPv6 address should be chosen over the larger /64 scope of the SLAAC address. NetworkManager has always been able to adhere to that by simply setting ip6.privacy=0 for the connection (in nm-connection-editor *not* selecting "Prefer temporary address" for IPv6 privacy extensions). Then it would use the DHCPv6 address as the source for all outgoing traffic. So if you would - for instance - run `curl ifconfig.co`, the DHCPv6 address would be used to connect to the outside world and be echoed back. Since the update to 1.36.6, this is no longer the case. NetworkManager now routes outgoing traffic through the SLAAC address, even if ip6.privacy=0 is set for the connection. Setting net.ipv6.conf.all.use_tempaddr=0 and net.ipv6.conf..use_tempaddr=0 with sysctl also no longer has any effect. Removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's altogether is the only way to stop NetworkManager from preferring SLAAC over DHCPv6 now. Looking at the changelog of NetworkManager 1.36.6, things regarding IP address order and temporary addresses have been changed in that release: + + * Fix a bug in synchronization of IP addresses with kernel that could lead to a wrong address order. + * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag is set. + * Ensure temporary IPv6 addresses are removed on disconnect and reapply. + https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6 addresses. With NetworkManager 1.36.4 this was not the case. (The Linux kernel uses the address highest in the list as preferred.) This can break many real-life use cases. For instance, my router gives out static leases to my machines. Those addresses are whitelisted in all kinds of firewalls to allow me to access servers for my work. Now that the "wrong" address is being preferred for outgoing traffic (a SLAAC address that I have no influence on), I am being locked out of the servers in question unless I forcefully remove the addresses or disable SLAAC on my router, so my outgoing traffic is being routed through the DHCPv6 address again. So this update introduces a very breaking change in IPv6 source address selection to an LTS release, while LTS releases should be stable. I should note that the bug is not present in NetworkManager 1.38.0 on Debian sid. That just prefers DHCPv6 addresses when available, like it should. /etc/os-release: PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy nmcli -v: nmcli tool, version 1.36.6 Looking at the changelog of 1.38.0: * Fix bug setting priority for IP addresses. * Static IPv6 addresses from "ipv6.addresses" are now preferred over addresses from DHCPv6, which are preferred over addresses from autoconf. This affects IPv6 source address selection, if the rules from RFC 6724, section 5 don't give a exhaustive match. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-38/NEWS So it looks like Ubuntu just introduced that bug by upgrading to 1.36.6. Please either backport the fix from 1.38.0 or revert to 1.36.4, which was working fine. More background here: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1974428/comments/11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977619 Title: NetworkManager 1.36.6 orders IPv6 addresses incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834771] Re: No HDMI-audio after kernel 4.15.-0.50
Apologies Uriel Tunn for not getting back to you on your message #74.
I must not have received the email notification at the time.
Anyway, i tried what you suggested and no luck...
e4310:~$ aplay -l
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: 92HD81B1X5 Analog [92HD81B1X5 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
e4310:~$ card=0
e4310:~$ dev=7
e4310:~$ pulseaudio --kill
e4310:~$ sudo rm $HOME/.config/pulse/*
e4310:~$ sleep 2
e4310:~$ wait
e4310:~$ pulseaudio --start
e4310:~$ pacmd load-module module-alsa-sink device=hw:$card,$dev
e4310:~$ pacmd set-default-sink alsa_output.hw_${card}_${dev}
Sink alsa_output.hw_0_7 does not exist.
e4310:~$ pacmd set-sink-volume alsa_output.hw_${card}_${dev} 35000
No sink found by this name or index.
Tried with the latest Ubuntu 22.04 and Fedora 36 and same situation,
HDMI is not recognised for sound, but getting pictures is fine -> so nothing
wrong with the HDMI cable to the monitor.
Thankfully I've just connected a set of external speakers using the 3.5mm jack
and just accepted sound across hdmi will not work with kernel later than 4.15.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834771
Title:
No HDMI-audio after kernel 4.15.-0.50
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
Output of lspci. ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970074/+attachment/5594980/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970074 Title: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970074 Title: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
Output of inxi. ** Attachment added: "inxi.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970074/+attachment/5594979/+files/inxi.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970074 Title: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
Maybe we can figure out what's common between our systems since I imagine if everyone were getting this error then this bug would be getting more attention. I'll also note this started for me with 5.15. 5.13 and earlier did not exhibit this error. System seems to run fine though. No noticeable degradation in performance or functionality. Output of my inxi: System:Kernel: 5.15.0-33-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 5.2.7 Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal Machine: Type: Desktop Mobo: ASRock model: B550M-HDV serial: UEFI: American Megatrends LLC. v: P2.10 date: 02/24/2022 CPU: Topology: 12-Core model: AMD Ryzen 9 5900 bits: 64 type: MCP arch: Zen 3 rev: 2 L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 71865 Speed: 2233 MHz min/max: 2200/3000 MHz Core speeds (MHz): 1: 2233 2: 2269 3: 2200 4: 2308 5: 2196 6: 2252 7: 2282 8: 2226 9: 2200 10: 2198 11: 2202 12: 2197 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] vendor: ASRock driver: amdgpu v: kernel bus ID: 08:00.0 Display: x11 server: X.Org 1.20.13 driver: amdgpu resolution: 2560x1440_60.00~60Hz OpenGL: renderer: AMD Radeon RX 6600 (navi23 LLVM 14.0.0 DRM 3.42 5.15.0-33-generic) v: 4.6 Mesa 22.2.0-devel (git-b62dd20 2022-06-03 focal-oibaf-ppa) direct render: Yes Audio: Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel v: kernel bus ID: 08:00.1 Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 0a:00.4 Device-3: Logitech type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-3.4:6 Sound Server: ALSA v: k5.15.0-33-generic Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock driver: r8169 v: kernel port: d000 bus ID: 05:00.0 IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: IF-ID-1: virbr0 state: down mac: IF-ID-2: virbr0-nic state: down mac: Drives:Local Storage: total: 19.34 TiB used: 13.40 TiB (69.3%) ID-1: /dev/nvme0n1 vendor: A-Data model: SX8200PNP size: 238.47 GiB ID-2: /dev/sda vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB temp: 34 C ID-3: /dev/sdb vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB temp: 34 C ID-4: /dev/sdc vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB ID-5: /dev/sdd vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB ID-6: /dev/sde model: H W RAID5 size: 8.19 TiB ID-7: /dev/sdf model: H W RAID5 size: 8.19 TiB Partition: ID-1: / size: 931.04 GiB used: 113.35 GiB (12.2%) fs: btrfs dev: /dev/sdc2 ID-2: /home size: 931.04 GiB used: 113.35 GiB (12.2%) fs: btrfs dev: /dev/sdc2 Sensors: System Temperatures: cpu: 43.5 C mobo: N/A gpu: amdgpu temp: 36 C Fan Speeds (RPM): fan-1: 1032 fan-2: 1390 fan-3: 0 fan-4: 0 fan-5: 0 gpu: amdgpu fan: 1020 Info: Processes: 417 Uptime: 45m Memory: 31.28 GiB used: 3.08 GiB (9.9%) Init: systemd runlevel: 5 Compilers: gcc: 9.4.0 clang: 10.0.0-4ubuntu1 Shell: bash v: 5.0.17 inxi: 3.0.38 Output of lspci: 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc.
[Bug 1958019] Re: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all
Speakers are working for me now after installing the BIOS update from 2022-06-02. https://pcsupport.lenovo.com/de/en/products/laptops-and-netbooks/legion- series/legion-7-16achg6/downloads/driver-list/component?name=BIOS%2FUEFI I booted on windows, installed the update and after switching to Linux the speakers instantly worked without any problems. Not sure if installing the update alone did the trick since I tried a lot before without success... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965439] Re: applications can no longer launch when called by kdesu
Confirmed facing this bug. I managed to use the .desktop file workaround for Discover, but it does not seem to work for Muon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: applications can no longer launch when called by kdesu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971434] Re: Display powersave only blanks, but does not turn off
I had the same issue after upgrading to ubuntu 22.04 and the logs showed the following error. Failed to connect to the screen saver: Error al llamar StartSereviceByName para org.gnome.ScreenSaver: Failed to execute program org.gnome.ScreenSaver: No such file or directory The missing file was /usr/bin/gjs which I was able to solve by installing the gjs package. After restarting session the display powered off as espected. I hope your problem is the same and you can solve it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610826] Re: Some third party entries in your sources.list were disabled. You can re-enable them after the upgrade with the 'software-properties' tool or your package manager.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610826 Title: Some third party entries in your sources.list were disabled. You can re-enable them after the upgrade with the 'software-properties' tool or your package manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1610826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958267] Re: wpa can't connect to servers using TLS 1.1 or older
This bug was fixed in the package wpa - 2:2.10-9ubuntu1 --- wpa (2:2.10-9ubuntu1) kinetic; urgency=medium * debian/patches/lower_security_level_for_tls_1.patch: - set the OpenSSL security level to 0 if that is the only option to continue the TLS negotiation, i.e., when TLS 1.0/1.1 are still allowed in wpa_supplicant default configuration and OpenSSL 3.0 with the constraint on MD5-SHA1 use. Patch proposed by Jouni Malinen on the upstream mailinglist (lp: #1958267) -- Sebastien Bacher Tue, 31 May 2022 16:03:29 +0200 ** Changed in: wpa (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: wpa can't connect to servers using TLS 1.1 or older To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977685] [NEW] sound card Everest ESSX8336 not supported
Public bug reported: I work with Ubuntu 22.04 but the Everest semiconductor Co Ltd ESSX8336\1 sound card is not recognized. On the web a lot of people have the same problem. It's an annoying problem. Could you please help us to solve this problem. I have a Huawei Matebook D15 series Matebook D 15 (2021) i3 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: francois852 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 5 15:44:25 2022 InstallationDate: Installed on 2022-04-22 (43 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2022 dmi.bios.release: 1.41 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.41 dmi.board.asset.tag: NULL dmi.board.name: BOHB-WAX9-PCB-B2 dmi.board.vendor: HUAWEI dmi.board.version: M1340 dmi.chassis.asset.tag: NULL dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1340 dmi.ec.firmware.release: 1.41 dmi.modalias: dmi:bvnHUAWEI:bvr1.41:bd02/21/2022:br1.41:efr1.41:svnHUAWEI:pnBOHB-WAX9:pvrM1340:rvnHUAWEI:rnBOHB-WAX9-PCB-B2:rvrM1340:cvnHUAWEI:ct10:cvrM1340:skuC100: dmi.product.family: MateBook D dmi.product.name: BOHB-WAX9 dmi.product.sku: C100 dmi.product.version: M1340 dmi.sys.vendor: HUAWEI mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-06-04T20:59:26.778687 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977685 Title: sound card Everest ESSX8336 not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1977685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977684] [NEW] After Upgrade to 22.04. System does not boot into graphical mode without being connected to the network
Public bug reported: After long wait time many systemd services fail with a timeout. Connecting to a network via Ethernet does not make the boot continuing. When the network cable is connected before booting the boot process works fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Jun 5 15:32:01 2022 InstallationDate: Installed on 2022-01-25 (131 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to jammy on 2022-05-20 (15 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy ** Description changed: After long wait time many systemd services fail with a timeout. + Connecting to a network via Ethernet does not make the boot continuing. + When the network cable is connected before booting the boot process + works fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Jun 5 15:32:01 2022 InstallationDate: Installed on 2022-01-25 (131 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to jammy on 2022-05-20 (15 days ago) VarLogDistupgradeTermlog: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977684 Title: After Upgrade to 22.04. System does not boot into graphical mode without being connected to the network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1977684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955940] Re: package timidity-daemon 2.14.0-8build1 failed to install/upgrade: installed timidity-daemon package post-installation script subprocess returned error exit status 5
This bug affects me to. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955940 Title: package timidity-daemon 2.14.0-8build1 failed to install/upgrade: installed timidity-daemon package post-installation script subprocess returned error exit status 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1955940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977678] Re: Crash on close
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1977678 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977678 Title: Crash on close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1977678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977676] Re: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977676 Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1977676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977683] Re: Lubuntu error has_option: command not found / no ssh-agent after updating to 22.04
Thank you for taking the time to report this bug and helping to make Ubuntu better. Lubuntu has used sddm for all LXQt releases (ie. since Lubuntu 18.10), and the upgrade from an release that used lightdm/LXDE is unsupported due to breakage as was warned about in documentation, eg. https://lubuntu.me/focal-2-released/ "Note, due to the extensive changes required for the shift in desktop environments, the Lubuntu team does not support upgrading from 18.04 or below to any greater release. Doing so will result in a broken system. If you are on 18.04 or below and would like to upgrade, please do a fresh install." The error you are describing is a user-created issue by using unsupported upgrade procedures that were documented as creating issues later, and this is warned about breakage. The fresh install would have prevented this. As such I've marked this bug report as "opinion". If you believe I'm in error, please leave a comment explaining why and the bug report can then be returned to "New" (you may find it'll then be marked as "Won't Fix") ** Changed in: lightdm (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977683 Title: Lubuntu error has_option: command not found / no ssh-agent after updating to 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1977683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977683] [NEW] Lubuntu error has_option: command not found / no ssh-agent after updating to 22.04
Public bug reported: Hi, I have updated several machines from Lubuntu 20.04 to Lubuntu 22.04 with do-release-update -d On all but one machine this worked well, but one machine, that formerly worked without problems, now has no ssh-agent running after login, and the ~/.xsession-errors shows several xsession files to fail for the same reason: /etc/X11/Xsession.d/30x11-common_xresources: Zeile 16: has_option: Befehl nicht gefunden /etc/X11/Xsession.d/75dbus_dbus-launch: Zeile 9: has_option: Befehl nicht gefunden /etc/X11/Xsession.d/90x11-common_ssh-agent: Zeile 9: has_option: Befehl nicht gefunden (german for: has_option: command not found) Formerly mentioned in bug #1922414 (marked as solved) and its duplicate #1940779 , but it isn't solved. That's why there is no ssh-agent. I have done some debugging to find, why it works on all but one of my machines, and what's the reason. Reason: has_option is not a command, but a shell function defined in /etc/X11/Xsession On the good machines, the display manager is sddm, which seems to do the job well. The machine, that fails, is somewhat older and had formerly 18.04 running and been updated to 20.04 then. It runs the display manager lightdm. That's the problem: lightdm runs /usr/bin/lxqt-session and /usr/bin/lxqt-session directly opens and executes the scripts in /etc/X11/Xsession.d without running /etc/X11/Xsession. Therefore, the shell function has_optionis never defined, but used in the scripts, which do fail then. Therefore, either lxqt-session needs to be made compatible with /etc/X11/Xsession, or the upgrade-procedure 20.04 to 22.04 must replace lightdm by sddm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lightdm 1.30.0-0ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sun Jun 5 14:48:42 2022 InstallationDate: Installed on 2018-04-28 (1498 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: lightdm UpgradeStatus: Upgraded to jammy on 2022-06-04 (0 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977683 Title: Lubuntu error has_option: command not found / no ssh-agent after updating to 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1977683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965592] Re: python-argcomplete: FTBFS: several TestTcsh failures
This bug was fixed in the package python-argcomplete - 2.0.0-1ubuntu1 --- python-argcomplete (2.0.0-1ubuntu1) kinetic; urgency=medium * Restore changes accidentally lost in the 1.12.3-0.1 NMU: + debian/rules: Set LC_ALL to C.UTF-8 instead of unsetting it + debian/rules: Unexport TERM to avoid test failure (LP: #1965592) -- Graham Inggs Sun, 05 Jun 2022 07:52:19 + ** Changed in: python-argcomplete (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965592 Title: python-argcomplete: FTBFS: several TestTcsh failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-argcomplete/+bug/1965592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976110] Re: `tmux -d -x ... -y ...` does not respect sizing
just curious -- will this land in jammy? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976110 Title: `tmux -d -x ... -y ...` does not respect sizing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/1976110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976619] Re: Version 7.81 breaks support for multi-line header
This bug was fixed in the package curl - 7.83.1-1ubuntu1 --- curl (7.83.1-1ubuntu1) kinetic; urgency=medium * Apply upstream patch to fix multi-line header support (LP: #1976619) -- Olivier Gayot Thu, 02 Jun 2022 13:44:50 +0200 ** Changed in: curl (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976619 Title: Version 7.81 breaks support for multi-line header To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1976619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977641] Re: mailfromd: undefined symbol: mu_stream_getline
This is/was a bug in mailutils 3.14 (see https://bugs.debian.org/1003755) which had an ABI change (over 3.13), but did not bump the abiversion. mailutils 3.15 fixed this issue. In Debian I triggered a binary rebuild of mailfromd after mailutils 3.15 was released, but Ubuntu seems to have not noticed this requirement. Since I yesterday uploaded a new version of mailfromd (8.13-2) to the Debian archive, I expect Ubuntu to pull in this version soon, which will freshly compile mailfromd with mailutils 3.15, which should fix this issue in Ubuntu, too. ** Bug watch added: Debian Bug tracker #1003755 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003755 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977641 Title: mailfromd: undefined symbol: mu_stream_getline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailfromd/+bug/1977641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975410] Re: Maximized window border under status bar in Wayland / Mutter
Also happens with non-maximized windows (cf. attached screenshot). ** Attachment added: "Screenshot from 2022-06-05 12-33-52.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975410/+attachment/5594953/+files/Screenshot%20from%202022-06-05%2012-33-52.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975410 Title: Maximized window border under status bar in Wayland / Mutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968519] Re: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04
Hello, I confirm that the incident is resolved. I updated Ubuntu 22.04 server remotely via SSH (on a Dell PowerEdge R210 II server with a Matrox MGA G200eW WPCM450 internal card) and the local console (by plugging a monitor into the server's VGA port) works fine. $ uname -a Linux serveur 5.15.0-35-generic #36-Ubuntu SMP Sat May 21 02:24:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Thanks, Vivien -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968519 Title: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977680] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977680 Title: Cam Link 4K disconnects, kernel warning, OBS video input frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970674] Re: New bug fix releases 3.4.11, 4.2.7 and 4.4.2
Complete log for all tests in 18.04. All .err files are either attached or in lena_test_errors.tar.xz. ** Attachment added: "ffmpeg_test_log" https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1970674/+attachment/5594952/+files/ffmpeg_test_log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970674 Title: New bug fix releases 3.4.11, 4.2.7 and 4.4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1970674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970674] Re: New bug fix releases 3.4.11, 4.2.7 and 4.4.2
** Attachment added: "sub2video.err" https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1970674/+attachment/5594951/+files/sub2video.err -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970674 Title: New bug fix releases 3.4.11, 4.2.7 and 4.4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1970674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977680] Re: Cam Link 4K disconnects, kernel warning, OBS video input frozen
** Description changed: We have two cameras connected to Cam Link 4K and using OBS for live- streaming. Suddenly during the live-stream the video input went to black. The kernel message shows that the USB disconnect at 2332.127976s (but we did not unplug anything). Some seconds later the kernel shows warnings (2440.834346). Since I did not want to stop the live stream, I unplugged the affected Cam Link 4K and plugged it back in, but this did not help. The video input that was in use when the incident happened kept frozen. At the end, I closed OBS, but a zombie process remained: $ ps auxff | grep ob[s] USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND tontech+ 28535 0.0 0.0 0 0 ?Z11:30 0:00 | \_ [obs-cli] + This is the third time happening. + ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-39-generic 5.13.0-39.44 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: tontechnik 2101 F pulseaudio - /dev/snd/controlC0: tontechnik 2101 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: tontechnik 2101 F pulseaudio + /dev/snd/controlC0: tontechnik 2101 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sun Jun 5 11:39:21 2022 InstallationDate: Installed on 2020-08-14 (659 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: - lono wireless extensions. - - enp4s0no wireless extensions. + lono wireless extensions. + + enp4s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B550M AORUS PRO ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic root=UUID=182c25dd-5701-40ff-8ac5-e0a623a2204f ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.13.0-39-generic N/A - linux-backports-modules-5.13.0-39-generic N/A - linux-firmware 1.201.5 + linux-restricted-modules-5.13.0-39-generic N/A + linux-backports-modules-5.13.0-39-generic N/A + linux-firmware 1.201.5 RfKill: - + SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-11-14 (202 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F13g dmi.board.asset.tag: Default string dmi.board.name: B550M AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x 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.:bvrF13g:bd03/25/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550MAORUSPRO:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550MAORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550M AORUS PRO dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977680 Title: Cam Link 4K disconnects, kernel warning, OBS video input frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977680] [NEW] Cam Link 4K disconnects, kernel warning, OBS video input frozen
Public bug reported: We have two cameras connected to Cam Link 4K and using OBS for live- streaming. Suddenly during the live-stream the video input went to black. The kernel message shows that the USB disconnect at 2332.127976s (but we did not unplug anything). Some seconds later the kernel shows warnings (2440.834346). Since I did not want to stop the live stream, I unplugged the affected Cam Link 4K and plugged it back in, but this did not help. The video input that was in use when the incident happened kept frozen. At the end, I closed OBS, but a zombie process remained: $ ps auxff | grep ob[s] USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND tontech+ 28535 0.0 0.0 0 0 ?Z11:30 0:00 | \_ [obs-cli] This is the third time happening. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-39-generic 5.13.0-39.44 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: tontechnik 2101 F pulseaudio /dev/snd/controlC0: tontechnik 2101 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sun Jun 5 11:39:21 2022 InstallationDate: Installed on 2020-08-14 (659 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B550M AORUS PRO ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic root=UUID=182c25dd-5701-40ff-8ac5-e0a623a2204f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-39-generic N/A linux-backports-modules-5.13.0-39-generic N/A linux-firmware 1.201.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-11-14 (202 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F13g dmi.board.asset.tag: Default string dmi.board.name: B550M AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x 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.:bvrF13g:bd03/25/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550MAORUSPRO:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550MAORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550M AORUS PRO dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977680 Title: Cam Link 4K disconnects, kernel warning, OBS video input frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947525] Re: Accessibilty Zoom causes crash/logout
This bit me... Thanks for at least documenting how the get back to normal! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947525 Title: Accessibilty Zoom causes crash/logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958019]
Yeah, both the speaker and headphones work fine with correct channel. And still work after resuming from suspend/hibernate. Also fine after hotplug events, whatever it is playing or not. Thanks for your patch a lot! (In reply to Cameron Berkenpas from comment #627) > Great! > > Some probably silly questions: > 1) Do both speakers work? Do you get left channel sound out of the left > speaker and right channel sound out of the right speaker? > > 2) After resuming from suspend/hibernate, does your sound still work? > > 3) What if you insert headphones and remove them? Does sound still work? > Try removing the headphones both while sound is not playing and while > it's not. > > Given that this old quirk works for your laptop, I think all of the > above will be fine and I can work toward getting this submitted. > > > On 6/3/2022 5:34 PM, bugzilla-dae...@kernel.org wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > > > --- Comment #626 from Songine (donglingluoy...@gmail.com) --- > > (In reply to Cameron Berkenpas from comment #625) > >> Did you test this yourself? > >> > >> On 6/3/22 00:11, bugzilla-dae...@kernel.org wrote: > >>> https://bugzilla.kernel.org/show_bug.cgi?id=208555 > >>> > >>> Songine (donglingluoy...@gmail.com) changed: > >>> > >>> What|Removed |Added > >>> > >> > > >>>CC| > >>>|donglingluoy...@gmail.com > >>> > >>> --- Comment #624 from Songine (donglingluoy...@gmail.com) --- > >>> (In reply to Cameron Berkenpas from comment #429) > Created attachment 298789 [details] > linux-legion-sound-0.0.13.patch > > auto mute is now properly disabled as per Takashi's suggestion. > > This patch is against the latest Linus tree, but applies against 5.14.3 > >> just > fine. > > This patch includes the presumptive commit message and credit given to > various people. > > Going through the Linux commit log, it seems full names and email > >> addresses > aren't needed, so I have a thank you list in the patch with the > following: > Andreas Holzer, Vincent Morel, sycxyc, Max Christian Pohle > > If you want to be mentioned (or if you know of someone who you think > that > should be included), please let me know! > > Here's a link to the patch submission: > > >> > https://mailman.alsa-project.org/pipermail/alsa-devel/2021-September/189698. > html > >>> Hello, there is a device could use the patch, could you help me add it to > >> the > >>> patch file? > >>> > >>> SND_PCI_QUIRK(0x17aa, 0x3802, "Lenovo Yoga DuetITL 2021", > >>> ALC287_FIXUP_YOGA7_14ITL_SPEAKERS), > >>> > > Yes, tested, and I am enjoging my speaker now.�[U+1F603]� > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958019]
Great! Some probably silly questions: 1) Do both speakers work? Do you get left channel sound out of the left speaker and right channel sound out of the right speaker? 2) After resuming from suspend/hibernate, does your sound still work? 3) What if you insert headphones and remove them? Does sound still work? Try removing the headphones both while sound is not playing and while it's not. Given that this old quirk works for your laptop, I think all of the above will be fine and I can work toward getting this submitted. On 6/3/2022 5:34 PM, bugzilla-dae...@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > --- Comment #626 from Songine (donglingluoy...@gmail.com) --- > (In reply to Cameron Berkenpas from comment #625) >> Did you test this yourself? >> >> On 6/3/22 00:11, bugzilla-dae...@kernel.org wrote: >>> https://bugzilla.kernel.org/show_bug.cgi?id=208555 >>> >>> Songine (donglingluoy...@gmail.com) changed: >>> >>> What|Removed |Added >>> >> >>>CC| >>>|donglingluoy...@gmail.com >>> >>> --- Comment #624 from Songine (donglingluoy...@gmail.com) --- >>> (In reply to Cameron Berkenpas from comment #429) Created attachment 298789 [details] linux-legion-sound-0.0.13.patch auto mute is now properly disabled as per Takashi's suggestion. This patch is against the latest Linus tree, but applies against 5.14.3 >> just fine. This patch includes the presumptive commit message and credit given to various people. Going through the Linux commit log, it seems full names and email >> addresses aren't needed, so I have a thank you list in the patch with the following: Andreas Holzer, Vincent Morel, sycxyc, Max Christian Pohle If you want to be mentioned (or if you know of someone who you think that should be included), please let me know! Here's a link to the patch submission: >> https://mailman.alsa-project.org/pipermail/alsa-devel/2021-September/189698. html >>> Hello, there is a device could use the patch, could you help me add it to >> the >>> patch file? >>> >>> SND_PCI_QUIRK(0x17aa, 0x3802, "Lenovo Yoga DuetITL 2021", >>> ALC287_FIXUP_YOGA7_14ITL_SPEAKERS), >>> > Yes, tested, and I am enjoging my speaker now.�[U+1F603]� > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966580] Re: Erroneously huge mouse pointer with snap-packaged firefox in jammy
Laptop: HP Spectre x360 Convertible 14-ea0xxx Graphics: Intel TigerLake-LP GT2 [Iris Xe Graphics] Resolution: 3000x2000 Mostly uncustomized out-of-the-box Ubuntu, the one notable choice being to use the gnome-xorg session type (declining to use the Ubuntu customisations to gnome-session, declining to use Wayland) More than that, I can't give you, as I've long since uninstalled snapd, and am unwilling to reinstall it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966580 Title: Erroneously huge mouse pointer with snap-packaged firefox in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly
** Description changed: My network has both DHCPv6 and SLAAC for IPv6. From both a privacy perspective and readability reasons, DHCPv6 should *always* be preferred - over SLAAC addresses when available. + over SLAAC addresses when available. And according to RFC 6724 the + smaller /128 scope of the DHCPv6 address should be chosen over the + larger /64 scope of the SLAAC address. NetworkManager has always been able to adhere to that by simply setting - ip6.privacy=0 for the connection. Then it would not generate temporary - addresses and use the DHCPv6 address as the source for outgoing traffic. + ip6.privacy=0 for the connection (in nm-connection-editor called "Prefer + temporary address"). Then it would use the DHCPv6 address as the source + for all outgoing traffic. So if you would - for instance - run `curl ifconfig.co`, the DHCPv6 address would be used to connect to the outside world and be echoed back. Since the update to 1.36.6, this is no longer the case. NetworkManager now routes outgoing traffic through the SLAAC address, even if ip6.privacy=0 is set for the connection. Setting net.ipv6.conf.all.use_tempaddr=0 and net.ipv6.conf..use_tempaddr=0 with sysctl also no longer has any effect. Removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's altogether is the only way to stop NetworkManager from preferring SLAAC over DHCPv6 now. Looking at the changelog of NetworkManager 1.36.6, things regarding IP address order and temporary addresses have been changed in that release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6 addresses. With NetworkManager 1.36.4 this was not the case. (The Linux kernel uses the address highest in the list as preferred.) This can break many real-life use cases. For instance, my router gives out static leases to my machines. Those addresses are whitelisted in all kinds of firewalls to allow me to access servers for my work. Now that the "wrong" address is being preferred for outgoing traffic (a SLAAC address that I have no influence on), I am being locked out of the servers in question unless I forcefully remove the addresses or disable SLAAC on my router, so my outgoing traffic is being routed through the DHCPv6 address again. So this update introduces a very breaking change in IPv6 source address selection to an LTS release, while LTS releases should be stable. I should note that the bug is not present in NetworkManager 1.38.0 on Debian sid. That just prefers DHCPv6 addresses when available, like it should. /etc/os-release: PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy nmcli -v: nmcli tool, version 1.36.6 Looking at the changelog of 1.38.0: * Fix bug setting priority for IP addresses. * Static IPv6 addresses from "ipv6.addresses" are now preferred over addresses from DHCPv6, which are preferred over addresses from autoconf. This affects IPv6 source address selection, if the rules from RFC 6724, section 5 don't give a exhaustive match. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-38/NEWS So it looks like Ubuntu just introduced that bug by upgrading to 1.36.6. Please either backport the fix from 1.38.0 or revert to 1.36.4, which was working fine. More background here: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1974428/comments/11 ** Description changed: My network has both DHCPv6 and SLAAC for IPv6. From both a privacy perspective and readability reasons, DHCPv6 should *always* be preferred over SLAAC addresses when available. And according to RFC 6724 the smaller /128 scope of the DHCPv6 address should be chosen over the larger /64 scope of the SLAAC address. NetworkManager has always been able to adhere to that by simply setting - ip6.privacy=0 for the connection (in nm-connection-editor called "Prefer - temporary address"). Then it would use the DHCPv6 address as the source - for all outgoing traffic. + ip6.privacy=0 for the connection (in nm-connection-editor *not* + selecting "Prefer temporary address" for IPv6 privacy extensions). Then + it would use the DHCPv6 address as the source for all outgoing traffic. So if you would - for instance - run `curl ifconfig.co`, the DHCPv6 address would be used to connect to the outside world and be echoed back. Since the update to 1.36.6, this is no longer the case. NetworkManager now routes outgoing traffic through the SLAAC
[Bug 1977679] Re: Firefox opens KML file in neverending loop if associated with "System Handler"
** Attachment added: "Screenshot from 2022-06-05 11-04-35.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1977679/+attachment/5594931/+files/Screenshot%20from%202022-06-05%2011-04-35.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977679 Title: Firefox opens KML file in neverending loop if associated with "System Handler" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1977679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977679] [NEW] Firefox opens KML file in neverending loop if associated with "System Handler"
Public bug reported: Found when trying open a KML export file from Google Timeline. It can be reproduced even with an empty KML file. Steps: * Create an empty file "test.kml" (run "$ touch test.kml") * Open the application "Files" * Right click on the test.kml and open it with Firefox * Open with "System Handler" and check the option "Do this automatically for files like this from now on" (see "Screenshot from 2022-06-05 11-13-23.png") Expected result: * No infinite opening Actual result: * Firefox starts opening the file again and again (see "Screenshot from 2022-06-05 11-04-35.png") Used SW: * Ubuntu 22.04 LTS * Firefox 101.0 * Files 42.1.1 ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2022-06-05 11-13-23.png" https://bugs.launchpad.net/bugs/1977679/+attachment/5594930/+files/Screenshot%20from%202022-06-05%2011-13-23.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977679 Title: Firefox opens KML file in neverending loop if associated with "System Handler" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1977679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977678] [NEW] Crash on close
Public bug reported: ``` GNU Image Manipulation Program version 2.10.30 git-describe: GIMP_2_10_30 Build: unknown rev 0 for linux # C compiler # Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 11.2.0-16ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-11 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-11-O5cEXJ/gcc-11-11.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-11-O5cEXJ/gcc-11-11.2.0/debian/tmp-gcn/usr --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-serialization=2 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 11.2.0 (Ubuntu 11.2.0-16ubuntu1) # Libraries # using babl version 0.1.92 (compiled against version 0.1.88) using GEGL version 0.4.34 (compiled against version 0.4.34) using GLib version 2.72.1 (compiled against version 2.71.1) using GdkPixbuf version 2.42.8 (compiled against version 2.42.6) using GTK+ version 2.24.33 (compiled against version 2.24.33) using Pango version 1.50.6 (compiled against version 1.50.3) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Speicherzugriffsfehler Stack trace: ``` # Stack traces obtained from PID 5848 - Thread 5848 # [New LWP 5849] [New LWP 5850] [New LWP 5851] [New LWP 5852] [New LWP 5853] [New LWP 5854] [New LWP 5855] [New LWP 5856] [New LWP 5857] [New LWP 5858] [New LWP 5859] [New LWP 5871] [New LWP 5872] [New LWP 5887] [New LWP 6094] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __GI___libc_read (nbytes=256, buf=0x7ffee02ebe90, fd=16) at ../sysdeps/unix/sysv/linux/read.c:26 Id Target Id Frame * 1Thread 0x7fddcd062e80 (LWP 5848) "gimp-2.10" __GI___libc_read (nbytes=256, buf=0x7ffee02ebe90, fd=16) at ../sysdeps/unix/sysv/linux/read.c:26 2Thread 0x7fddcc65f640 (LWP 5849) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 3Thread 0x7fddcbe5e640 (LWP 5850) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 4Thread 0x7fddc365d640 (LWP 5851) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 5Thread 0x7fddcb65d640 (LWP 5852) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 6Thread 0x7fddcae5c640 (LWP 5853) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 7Thread 0x7fddca65b640 (LWP 5854) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 8Thread 0x7fddc9e5a640 (LWP 5855) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 9Thread 0x7fddc9659640 (LWP 5856) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 10 Thread 0x7fddc8e58640 (LWP 5857) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 11 Thread 0x7fddc3fff640 (LWP 5858) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 12 Thread 0x7fddc2e5c640 (LWP 5859) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 13 Thread 0x7fdd69ffb640 (LWP 5871) "gmain" 0x7fddcdd63d7f in __GI___poll (fds=0x56243753e0a0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 14 Thread 0x7fdd6a7fc640 (LWP 5872) "gdbus" 0x7fddcdd63d7f in __GI___poll (fds=0x56243755c030, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 15 Thread 0x7fdd26ff5640 (LWP 5887) "async" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 16 Thread 0x7fdd267f4640 (LWP 6094) "swap writer" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 Thread 16 (Thread
[Bug 1970957] Re: suspend problem
Lenovo T460S affected. Tested 5.18 kernel as well - id has NOT fixed the issue. Also tested Fedora 36. Seems, that Fedora is NOT affected by this bug, as suspension works correctly on the same laptop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970957 Title: suspend problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly
** Description changed: My network has both DHCPv6 and SLAAC for IPv6. From both a privacy perspective and readability reasons, DHCPv6 should *always* be preferred over SLAAC addresses when available. NetworkManager has always been able to adhere to that by simply setting ip6.privacy=0 for the connection. Then it would not generate temporary addresses and use the DHCPv6 address as the source for outgoing traffic. So if you would - for instance - run `curl ifconfig.co`, the DHCPv6 address would be used to connect to the outside world and be echoed back. Since the update to 1.36.6, this is no longer the case. NetworkManager now routes outgoing traffic through the SLAAC address, even if ip6.privacy=0 is set for the connection. Setting net.ipv6.conf.all.use_tempaddr=0 and net.ipv6.conf..use_tempaddr=0 with sysctl also no longer has any effect. Removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's altogether is the only way to stop NetworkManager from preferring SLAAC over DHCPv6 now. Looking at the changelog of NetworkManager 1.36.6, things regarding IP address order and temporary addresses have been changed in that release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6 addresses. With NetworkManager 1.36.4 this was not the case. (The Linux kernel uses the address highest in the list as preferred.) This can break many real-life use cases. For instance, my router gives out static leases to my machines. Those addresses are whitelisted in all kinds of firewalls to allow me to access servers for my work. Now that the "wrong" address is being preferred for outgoing traffic (a SLAAC address that I have no influence on), I am being locked out of the servers in question unless I forcefully remove the addresses or disable SLAAC on my router, so my outgoing traffic is being routed through the DHCPv6 address again. So this update introduces a very breaking change in IPv6 source address selection to an LTS release, while LTS releases should be stable. I should note that the bug is not present in NetworkManager 1.38.0 on Debian sid. That just prefers DHCPv6 addresses when available, like it should. /etc/os-release: PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy nmcli -v: nmcli tool, version 1.36.6 + + Looking at the changelog of 1.38.0: + + * Fix bug setting priority for IP addresses. + * Static IPv6 addresses from "ipv6.addresses" are now preferred over addresses from DHCPv6, which are preferred over addresses from autoconf. This affects IPv6 source address selection, if the rules from RFC 6724, section 5 don't give a exhaustive match. + + https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-38/NEWS + + So it looks like Ubuntu just introduced that bug by upgrading to 1.36.6. + Please either backport the fix from 1.38.0 or revert to 1.36.4, which + was working fine. ** Description changed: My network has both DHCPv6 and SLAAC for IPv6. From both a privacy perspective and readability reasons, DHCPv6 should *always* be preferred over SLAAC addresses when available. NetworkManager has always been able to adhere to that by simply setting ip6.privacy=0 for the connection. Then it would not generate temporary addresses and use the DHCPv6 address as the source for outgoing traffic. So if you would - for instance - run `curl ifconfig.co`, the DHCPv6 address would be used to connect to the outside world and be echoed back. Since the update to 1.36.6, this is no longer the case. NetworkManager now routes outgoing traffic through the SLAAC address, even if ip6.privacy=0 is set for the connection. Setting net.ipv6.conf.all.use_tempaddr=0 and net.ipv6.conf..use_tempaddr=0 with sysctl also no longer has any effect. Removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's altogether is the only way to stop NetworkManager from preferring SLAAC over DHCPv6 now. Looking at the changelog of NetworkManager 1.36.6, things regarding IP address order and temporary addresses have been changed in that release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6 addresses. With NetworkManager 1.36.4 this was not the case. (The Linux kernel uses the address highest in the list as preferred.) This can break many real-life use cases. For
