[Bug 2060014] Re: CVE-2024-2947 command injection when deleting a sosreport with a crafted name
Backporters: I uploaded backports from noble-proposed to mantic and jammy. They didn't propagate yet due to noble being jammed so much, but we do validate them on both releases upstream. I'll let you decide whether to accept or stall them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060014 Title: CVE-2024-2947 command injection when deleting a sosreport with a crafted name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cockpit/+bug/2060014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059080] Re: Add Real-time Linux Analysis tool (rtla) to linux-tools
** Changed in: linux (Ubuntu Noble) 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/2059080 Title: Add Real-time Linux Analysis tool (rtla) to linux-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2045552] Re: nullboot 0.5.0: shim 15.7-0ubuntu1 update
Hello Julian, or anyone else affected, Accepted nullboot into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nullboot/0.5.0-0ubuntu0.22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nullboot (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2045552 Title: nullboot 0.5.0: shim 15.7-0ubuntu1 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nullboot/+bug/2045552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060080] Re: 23.13.9-2ubuntu5 is FTBFS on armhf
So something changed to add -Werror=implicit-function-declaration at build time (gcc didn't change so maybe dpkg?), which should have caused the other arches to fail as well but since they ran at different times they pulled different versions of build dependencies. This will likely get fixed on a rebuild and these are getting queued en masse, so I'm marking as invalid unless we have a reason to track this later. ** Changed in: accountsservice (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060080 Title: 23.13.9-2ubuntu5 is FTBFS on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2060080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2029934] Re: arm64 AWS host hangs during modprobe nvidia on lunar and mantic
Hi all, This should be fixed on the latest driver 550.67 - https://www.nvidia.com/Download/driverResults.aspx/223429/en-us/. Please help verify if this is resolved on your systems. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2029934 Title: arm64 AWS host hangs during modprobe nvidia on lunar and mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2029934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059847] Re: Input lag in native terminal on Nvidia desktops with X11
No need to reinstall the OS. I've posted a script for downgrading mutter packages for Ubuntu 23.10, 23.04, and 22.04 here: https://askubuntu.com/a/1509288/96411 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag in native terminal on Nvidia desktops with X11 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048983] Re: Tmux server crashed
[Expired for tmux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: tmux (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/2048983 Title: Tmux server crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/2048983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376140] Re: plymouthd crashed with SIGSEGV in ply_event_loop_stop_watching_fd()
*** This bug is a duplicate of bug 1284654 *** https://bugs.launchpad.net/bugs/1284654 ** This bug is no longer a duplicate of private bug 1051264 ** This bug has been marked a duplicate of private bug 1284654 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376140 Title: plymouthd crashed with SIGSEGV in ply_event_loop_stop_watching_fd() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1376140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1380924] Re: plymouthd crashed with SIGSEGV in ply_event_loop_stop_watching_fd()
*** This bug is a duplicate of bug 1284654 *** https://bugs.launchpad.net/bugs/1284654 ** This bug is no longer a duplicate of private bug 1051264 ** This bug has been marked a duplicate of private bug 1284654 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1380924 Title: plymouthd crashed with SIGSEGV in ply_event_loop_stop_watching_fd() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1380924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1377046] Re: plymouthd crashed with SIGSEGV in ply_event_loop_stop_watching_fd()
*** This bug is a duplicate of bug 1284654 *** https://bugs.launchpad.net/bugs/1284654 ** This bug is no longer a duplicate of private bug 1051264 ** This bug has been marked a duplicate of private bug 1284654 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377046 Title: plymouthd crashed with SIGSEGV in ply_event_loop_stop_watching_fd() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1377046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060089] Re: [noble] plymouthd crashed with SIGSEGV in ply_event_loop_stop_watching_fd() from ply_kmsg_reader_stop()
I wonder if this is related to bug 1284654. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060089 Title: [noble] plymouthd crashed with SIGSEGV in ply_event_loop_stop_watching_fd() from ply_kmsg_reader_stop() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2060089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060089] [NEW] [noble] plymouthd crashed with SIGSEGV in ply_event_loop_stop_watching_fd() from ply_kmsg_reader_stop()
Public bug reported: plymouthd crashed with SIGSEGV in: ply_event_loop_stop_watching_fd () from /lib/x86_64-linux-gnu/libply.so.5 ply_kmsg_reader_stop () from /lib/x86_64-linux-gnu/libply-splash-core.so.5 https://errors.ubuntu.com/oops/23775f22-f0fd-11ee-9d81-fa163ec44ecd ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Tags: noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060089 Title: [noble] plymouthd crashed with SIGSEGV in ply_event_loop_stop_watching_fd() from ply_kmsg_reader_stop() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2060089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060086] [NEW] [noble] plymouthd crashed with SIGSEGV in ply_terminal_set_disabled_input()
Public bug reported: plymouthd crashed with SIGSEGV in: ply_terminal_set_disabled_input () from /lib/x86_64-linux-gnu/libply-splash-core.so.5 ?? () from /usr/lib/x86_64-linux-gnu/plymouth/renderers/drm.so ply_renderer_open_input_source () from /lib/x86_64-linux-gnu/libply-splash-core.so.5 ?? () from /lib/x86_64-linux-gnu/libply-splash-core.so.5 ply_keyboard_watch_for_input () from /lib/x86_64-linux-gnu/libply-splash-core.so.5 from https://errors.ubuntu.com/oops/1ae9e046-e5c2-11ee-8aa3-fa163ec8ca8c of https://errors.ubuntu.com/problem/b016ca092562d916cff710db82fbf10072530e37 ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Tags: noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060086 Title: [noble] plymouthd crashed with SIGSEGV in ply_terminal_set_disabled_input() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2060086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1597017] Re: mount rules grant excessive permissions
Hello, A gentle ping on this issue, it still shows up on jammy security report and looks like 2ubuntu2.3 here https://changelogs.ubuntu.com/changelogs/pool/main/a/apparmor/apparmor_3.0.4-2ubuntu2.3/changelog doesn't have the fix. @jjohansen can we please advise on when the fix will be backported to ubuntu 22.04? thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1597017 Title: mount rules grant excessive permissions To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1597017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059197] Re: mount.nfs: Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together
Hi Jeff, Again, I apologise for introducing this regression, but we are on our way to getting this fixed. The fixes are: commit 1e3ca7fe199531a372bb8e1c1033d8973097be50 Author: NeilBrown Date: Wed Jul 26 13:47:42 2017 -0400 Subject: mount: move handling of "-t nfs4" into nfs_nfs_version() Link: https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=1e3ca7fe199531a372bb8e1c1033d8973097be50 commit 050153ef6a86ff5ab06ef65be36336824a323779 Author: NeilBrown Date: Wed Jul 26 13:51:51 2017 -0400 Subject: mount: Fix problems with parsing minorversion= Link: https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=050153ef6a86ff5ab06ef65be36336824a323779 commit 71b807e1a69940beb31fdeb481c2e54509e8bd32 Author: Steve Dickson Date: Thu Mar 1 13:52:47 2018 -0500 Subject: mount.nfs: minorversion setting is being ignored with the -t flag Link: https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=71b807e1a69940beb31fdeb481c2e54509e8bd32 I have built these into a test package, if you are interested in taking a look. Please note this package is NOT SUPPORTED by Canonical, and is for TESTING PURPOSES ONLY. ONLY Install in a dedicated test environment. Instructions to install (On a Focal system): 1) sudo add-apt-repository ppa:mruffell/lp2059197-test 2) sudo apt update 3) sudo apt install nfs-common 4) sudo apt-cache policy nfs-common | grep Installed Installed: 1:1.3.4-2.5ubuntu3.6+lp2059197v20240403b1 If you try mount your share with the version specified, it should work. I'll write back once we have a package in -proposed with the fix. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059197 Title: mount.nfs: Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2059197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2018192] Re: Desktop Border Incorrect
this is no longer a problem... though in 23.10, my desktops will switch occasionally on its own. I'll wait for 24.04 to see if that's still a problem before reporting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2018192 Title: Desktop Border Incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/2018192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059197] Re: Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together
Attached is a debdiff for Focal which fixes this issue. ** Summary changed: - Issue with nfs4.0 mounts after upgrade to 3.6 + Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together ** Summary changed: - Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together + mount.nfs: Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together ** Description changed: - Hello, + [Impact] - On Ubuntu Server 20.04.6 LTS with the update of nfs-common package => - "nfs-common/focal-updates 1:1.3.4-2.5ubuntu3.5" to "nfs-common/focal- - updates 1:1.3.4-2.5ubuntu3.6" I started having issues mounting ntf4.0 - volumes. The NFS server supports 4.0, 4.1 and 4.2 + When specifying both '-t nfs4' and '-o vers=4.x' on the mount command + line, mount.nfs ignores any specific version set with '-o vers=4.x' or + '-o vers=4,minorversion=x', and simply attempts version negotiation, + which due to my recent changes in bug 2049262, would land on the highest + supported nfs version, likely 4.2. - The issue appears when using '-t ntfs4' and setting the version using -o - vers=. + Users who specify what version they want should get the version they ask + for, and thus, this is a regression introduced in 1:1.3.4-2.5ubuntu3.6. - When using 1:1.3.4-2.5ubuntu3.5 I am able to use '-o vers' to set the version when using -t ntfs4 eg - mount -t nfs4 -o vers=4.0 -vvv SERVER.local:/srv/data /mnt/test - mount.nfs4: trying text-based options 'vers=4.0,addr=xx.xx.xx.xx,clientaddr=xx.xx.xx.xx' + A workaround is to drop '-t nfs4' and to use mount.nfs directly instead, + i.e.: - mount -t nfs4 -o vers=4.1 -vvv SERVER.local:/srv/data /mnt/test - mount.nfs4: trying text-based options 'vers=4.1,addr=xx.xx.xx.xx,clientaddr=xx.xx.xx.xx' + $ sudo mount.nfs -o vers=4.1 -vvv jammy-nfs-server:/ /mnt - However after upgrading to 1:1.3.4-2.5ubuntu3.6 it always mounts as nfs4.2 - mount -t nfs4 -o vers=4.0 -vvv SERVER.local:/srv/data /mnt/test - mount.nfs4: trying text-based options 'vers=4.2,addr=xx.xx.xx.xx,clientaddr=xx.xx.xx.xx' + [Testcase] - mount -t nfs4 -o vers=4.1 -vvv SERVER.local:/srv/data /mnt/test - mount.nfs4: trying text-based options 'vers=4.2,addr=xx.xx.xx.xx,clientaddr=xx.xx.xx.xx' + Create two VMs, one jammy and one focal. - I would have expected the specified version in -o vers to be used when - using '-t nfs4' + The jammy VM will be the server. - When using '-t nfs' I am able to mount volumes as nfs 4.0. I understand - that 1:1.3.4-2.5ubuntu3.6 fixes version negotiation so maybe this isn't - a bug and the intent with '-t nfs4' is to always use the highest - version. If so please feel free to close the report + Server VM: + $ sudo hostnamectl set-hostname jammy-nfs-server + $ sudo apt update && sudo apt upgrade -y + $ sudo apt install nfs-kernel-server + $ sudo mkdir /export + $ sudo mkdir /export/users + $ sudo mkdir /home/users + $ sudo vi /etc/fstab # add the following line: + /home/users /export/users none bind 0 0 + $ sudo mount -a + $ sudo vi /etc/exports # add the following lines: + /export 192.168.122.0/24(rw,fsid=0,no_subtree_check,sync) + /export/users 192.168.122.0/24(rw,nohide,insecure,no_subtree_check,sync) + $ sudo systemctl restart nfs-server.service + + Focal VM: + $ sudo hostnamectl set-hostname focal-nfs-client + $ sudo apt update && sudo apt upgrade -y + $ sudo apt install nfs-common + + And then try mounting with both '-t nfs4' and '-o vers=4.1': + + $ sudo mount -t nfs4 -o vers=4.1 -vvv jammy-nfs-server:/ /mnt + mount.nfs4: timeout set for Wed Apr 3 00:51:23 2024 + mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.122.217,clientaddr=192.168.122.9' + + and then try with both '-t nfs4' and '-o vers=4,minorversion=1': + + $ sudo mount -t nfs4 -o vers=4,minorversion=1 -vvv jammy-nfs-server:/ /mnt + mount.nfs4: timeout set for Wed Apr 3 02:19:03 2024 + mount.nfs4: trying text-based options 'minorversion=1,vers=4.2,addr=192.168.122.217,clientaddr=192.168.122.9' + + In each of those mounts, it incorrectly uses protocol version 4.2, + instead of requested 4.1. + + If you install the test packages in the following ppa: + + https://launchpad.net/~mruffell/+archive/ubuntu/lp2059197-test + + then vers should always be 4.1, instead of 4.2. + + [Where problems can occur] + + It is quite clear now that changing version negotiation and parsing is + quite problematic, after the number of regressions the previous + 1:1.3.4-2.5ubuntu3.6 caused the community, and the sheer number of + commits upstream took to resolve lingering issues. + + We need to be careful, to make sure we don't introduce any further + regressions. + + This time, we are only changing how mount.nfs parses and processes + command line arguments for version specification, and not changing + version negotiation itself. This could impact NFS clients, when they go + to mount NFS filesystems. + + If a regression were to occur, then users
[Bug 2040453] Re: Gnome 45 crash on restart in X11 session [Window manager error: Another compositing manager is already running on screen 0 on display “:0”]
If it lands in 46.1 then Ubuntu 24.04 will get it after that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040453 Title: Gnome 45 crash on restart in X11 session [Window manager error: Another compositing manager is already running on screen 0 on display “:0”] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2040453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040453] Re: Gnome 45 crash on restart in X11 session [Window manager error: Another compositing manager is already running on screen 0 on display “:0”]
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3329 It seems the developer team of gnome will fix this bug in version 46.1. Any progress or plan for ubuntu? Will it be fixed in Ubuntu 24.04 LTS? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040453 Title: Gnome 45 crash on restart in X11 session [Window manager error: Another compositing manager is already running on screen 0 on display “:0”] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2040453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1989078] Re: libvirt-qemu apparmor profile doesn't allow locking of AAVMF firmware
We now have a follow-up SRU. Removing the block-proposed tags. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1989078 Title: libvirt-qemu apparmor profile doesn't allow locking of AAVMF firmware To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1989078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1989078] Re: libvirt-qemu apparmor profile doesn't allow locking of AAVMF firmware
Hello Paride, or anyone else affected, Accepted libvirt into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libvirt/6.0.0-0ubuntu8.18 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal ** Tags removed: block-proposed block-proposed-focal verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1989078 Title: libvirt-qemu apparmor profile doesn't allow locking of AAVMF firmware To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1989078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"
Hello Mauricio, or anyone else affected, Accepted libvirt into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libvirt/6.0.0-0ubuntu8.18 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libvirt (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059272 Title: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2059272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059801] Re: No PDF downloads at the official website
Thanks everybody for reporting this issue. It has now been resolved. PDF downloads are now built with GitHub Pages. ** Changed in: xubuntu-docs (Ubuntu) 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/2059801 Title: No PDF downloads at the official website To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-docs/+bug/2059801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060082] Re: Dublin timezone cause systemd cpu high
how to reduce: 1. Stop clock synchronization systemctl stop chrony 2. Set the timezone to Dublin timedatectl set-timezone Europe/Dublin 3. Change the time to waitting for Daylight saving time switch timedatectl set-time "2024-03-30 23:59:50" At 0 o'clock, the system is executing atop logrotation. # cat /etc/cron.d/atop PATH=/bin:/usr/bin:/sbin:/usr/sbin # daily restart of atop at midnight 0 0 * * * root [ -d "/run/systemd/system" ] || /usr/share/atop/atop.daily& 0 0 * * * root [ -d "/run/systemd/system" ] && systemctl restart atop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060082 Title: Dublin timezone cause systemd cpu high To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2060082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060082] [NEW] Dublin timezone cause systemd cpu high
Public bug reported: Systemd version(249) in Jammy Jellyfish is too old, When using the Dublin time zone for daylight saving time switching，the CPU usage will suddenly increase to 100% starting from 2024-03-31 00:00:00 and last for 1 hour, but return to normal at 2024-03-31 02:00:00. plz backport the bugfix to v249 or update 255 version in Jammy Jellyfish to fix it. thank you. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "systemd atop" https://bugs.launchpad.net/bugs/2060082/+attachment/5761387/+files/screenshot-20240402-142051.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060082 Title: Dublin timezone cause systemd cpu high To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2060082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059418] Re: T60 Bluetooth earbuds not being 'set up' on new machine
** Summary changed: - Bluetooth earbuds not being 'set up' on new machine + T60 Bluetooth earbuds not being 'set up' on new machine ** Changed in: bluez (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059418 Title: T60 Bluetooth earbuds not being 'set up' on new machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2059418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1990630] Re: tracker-extract-3 crashed with signal 31 in __GI_epoll_create1()
Thanks! ** Changed in: tracker-miners (Ubuntu Jammy) Assignee: (unassigned) => Talha Can Havadar (tchavadar) ** Changed in: tracker-miners (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1990630 Title: tracker-extract-3 crashed with signal 31 in __GI_epoll_create1() To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/1990630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-nvidia-tegra/5.15.0.1023.23)
All autopkgtests for the newly accepted linux-meta-nvidia-tegra (5.15.0.1023.23) for jammy have finished running. The following regressions have been reported in tests triggered by the package: systemd/249.11-0ubuntu3.12 (arm64) wireguard/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-nvidia-tegra [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2028165] Re: nvidia-dkms-* FTBS with linux 6.5
Everyone is very busy with the 24.04 release as well as other responsibilities. So don't take silence to imply anything :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2028165 Title: nvidia-dkms-* FTBS with linux 6.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059197] Re: Issue with nfs4.0 mounts after upgrade to 3.6
Hi Jeff, I believe this is a valid bug. I can reproduce it: On Focal: $ sudo mount -t nfs4 -o vers=4.1 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Wed Apr 3 00:51:23 2024 mount.nfs4: trying text-based options 'vers=4.2,addr=192.168.122.217,clientaddr=192.168.122.9' On Jammy: $ sudo mount -t nfs4 -o vers=4.1 -vvv jammy-nfs-server:/ /mnt mount.nfs4: timeout set for Wed Apr 3 00:57:08 2024 mount.nfs4: trying text-based options 'vers=4.1,addr=192.168.122.217,clientaddr=192.168.122.213' I apologise for introducing this particular regression when I changed the version negotiation. Let me try and find a fix and build a test package. In the meantime, you can use a workaround of dropping "-t nfs4" and changing "mount" to "mount.nfs", i.e.: $ sudo mount.nfs -o vers=4.1 -vvv jammy-nfs-server:/ /mnt mount.nfs: timeout set for Wed Apr 3 00:51:59 2024 mount.nfs: trying text-based options 'vers=4.1,addr=192.168.122.217,clientaddr=192.168.122.9' I will write back shortly. Thanks, Matthew ** Also affects: nfs-utils (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: nfs-utils (Ubuntu) Status: New => Fix Released ** Changed in: nfs-utils (Ubuntu Focal) Status: New => In Progress ** Changed in: nfs-utils (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: nfs-utils (Ubuntu Focal) Assignee: (unassigned) => Matthew Ruffell (mruffell) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059197 Title: Issue with nfs4.0 mounts after upgrade to 3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2059197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052929] Re: failed autopkgtests for evolver vs glibc 2.39 on amd64
This bug was fixed in the package gcc-14 - 14-20240330-1ubuntu2 --- gcc-14 (14-20240330-1ubuntu2) noble; urgency=medium * No-change rebuild for CVE-2024-3094 -- Steve Langasek Sun, 31 Mar 2024 01:02:56 + ** Changed in: gcc-14 (Ubuntu) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-3094 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052929 Title: failed autopkgtests for evolver vs glibc 2.39 on amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/2052929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059856] Re: gdb 10.0 fails to examine any global variables in D programs
** Description changed:
[ Impact ]
* GDB 10.0 introduced a regression where it cannot inspect any global
variables in any D programs compiled by any D compiler.
* LDC2 and GDC upstream stated Focal does not have such a problem and stuck
to this release for their test images.
[ Test Plan ]
Considering the following D program:
```
module t;
class uv {
int i;
}
__gshared uv i;
int main() {
i = new uv();
return 0; // #break
}
```
If you build it using `gdc -g -O0 t.d -o t` or `ldc2 -o t.o t.d -g`, run
the GDB using the following commands ...
```
b t.d:10
p t.i
```
... you will notice GDB will complain that "'t.i' has unknown type; cast
it to its declared type."
[ Where problems could occur ]
- * The fix consists of a single line change to the demangler. The worst-case
scenario would be breaking the demangling functionality of other programming
languages. However, the newer D ABI uses a symbol mangling scheme that is very
difficult to confuse with other programming languages.
- * Incorrect symbol de-mangling may also cause user confusion. However, the
patch fixed a fundamental usability issue.
+ * The fix consists of a single line change to the demangler. The worst-case
scenario would be breaking the demangling functionality of other programming
languages. However, the newer D ABI uses a symbol mangling scheme that is very
difficult to confuse with other programming languages.
+ * Incorrect symbol de-mangling may also cause user confusion. However, the
patch fixed a fundamental usability issue.
+
+ [ Other Info ]
+
+ * Initial discussion in the LDC2 bug tracker: https://github.com/ldc-
+ developers/ldc/issues/4389
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059856
Title:
gdb 10.0 fails to examine any global variables in D programs
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2059856/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059856] Re: gdb 10.0 fails to examine any global variables in D programs
** Description changed:
- Summary:
+ [ Impact ]
- * GDB 10.0 introduced a regression where it cannot inspect any global
variables in any D programs compiled by any D compiler.
- * LDC2 and GDC upstream stated Focal does not have such a problem and stuck
to this release for their test images.
+ * GDB 10.0 introduced a regression where it cannot inspect any global
variables in any D programs compiled by any D compiler.
+ * LDC2 and GDC upstream stated Focal does not have such a problem and stuck
to this release for their test images.
- Reproduce steps:
+ [ Test Plan ]
Considering the following D program:
```
module t;
class uv {
- int i;
+ int i;
}
__gshared uv i;
int main() {
- i = new uv();
- return 0; // #break
+ i = new uv();
+ return 0; // #break
}
```
If you build it using `gdc -g -O0 t.d -o t` or `ldc2 -o t.o t.d -g`, run
the GDB using the following commands ...
```
b t.d:10
p t.i
```
... you will notice GDB will complain that "'t.i' has unknown type; cast
it to its declared type."
+
+ [ Where problems could occur ]
+
+ * The fix consists of a single line change to the demangler. The worst-case
scenario would be breaking the demangling functionality of other programming
languages. However, the newer D ABI uses a symbol mangling scheme that is very
difficult to confuse with other programming languages.
+ * Incorrect symbol de-mangling may also cause user confusion. However, the
patch fixed a fundamental usability issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059856
Title:
gdb 10.0 fails to examine any global variables in D programs
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2059856/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060080] [NEW] 23.13.9-2ubuntu5 is FTBFS on armhf
Public bug reported: The armhf build fails with the following build error: ../subprojects/mocklibc-1.0/src/netgroup-debug.c: In function ‘netgroup_debug_print_entry’: ../subprojects/mocklibc-1.0/src/netgroup-debug.c:25:3: error: implicit declaration of function ‘print_indent’ [-Werror=implicit-function-declaration] 25 | print_indent(stream, indent); | ^~~~ cc1: some warnings being treated as errors See the logs here: https://launchpadlibrarian.net/722843641/buildlog_ubuntu-noble- armhf.accountsservice_23.13.9-2ubuntu5_BUILDING.txt.gz ** Affects: accountsservice (Ubuntu) Importance: Undecided Assignee: Chris Peterson (cpete) Status: In Progress ** Changed in: accountsservice (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060080 Title: 23.13.9-2ubuntu5 is FTBFS on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2060080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060073] Re: folks build test failures with glib 2.80
** Changed in: libfolks 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/2060073 Title: folks build test failures with glib 2.80 To manage notifications about this bug go to: https://bugs.launchpad.net/libfolks/+bug/2060073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059847] Re: Input lag in native terminal on Nvidia desktops with X11
I've found a workaround: I conducted a fresh installation of Ubuntu 22.04.4 and subsequently marked specific packages for holding using the following commands: $ sudo apt-mark hold gir1.2-mutter-10 $ sudo apt-mark hold libmutter-10-0 $ sudo apt-mark hold mutter-common Following this, I proceeded to update all packages. So, I'm currently utilizing version "42.9-0ubuntu5" of the mutter packages, instead of version "42.9-0ubuntu7." Now, my system is with packages: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.4 LTS Release:22.04 Codename: jammy $ dpkg -l | grep "mutter" | tr -s " " | cut -d " " -f 1-3 hi gir1.2-mutter-10:amd64 42.9-0ubuntu5 hi libmutter-10-0:amd64 42.9-0ubuntu5 hi mutter-common 42.9-0ubuntu5 $ dpkg -l | grep " nvidia-" | tr -s " " | cut -d " " -f 1-3 ii linux-modules-nvidia-535-generic-hwe-22.04 6.5.0-26.26~22.04.1 ii nvidia-compute-utils-535 535.161.07-0ubuntu0.22.04.1 ii nvidia-driver-535 535.161.07-0ubuntu0.22.04.1 ii nvidia-firmware-535-535.161.07 535.161.07-0ubuntu0.22.04.1 ii nvidia-kernel-common-535 535.161.07-0ubuntu0.22.04.1 ii nvidia-kernel-source-535 535.161.07-0ubuntu0.22.04.1 ii nvidia-prime 0.8.17.1 ii nvidia-settings 510.47.03-0ubuntu1 ii nvidia-utils-535 535.161.07-0ubuntu0.22.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag in native terminal on Nvidia desktops with X11 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2018449] Re: [SRU] `xmms2 add --playlist ... ` causes a core dump
I can confirm that the xmms2 package in mantic-proposed has fixed the bug for me. Test done: 1. Install xmms2 from mantic-proposed 2. create a playlist 3. Add few mp3 to the playlist according to the testplan 4. Switch the test playlist with the command "xmms2 playlist switch" 5. Execute "xmms2 list" to confirm that the mp3 were successfully added to the list Test result: the errors with xmms2 has been fixed. Package tested: $ apt-cache policy xmms2 xmms2: Installed: 0.8+dfsg-23ubuntu0.1 Candidate: 0.8+dfsg-23ubuntu0.1 Version table: *** 0.8+dfsg-23ubuntu0.1 100 100 http://us.archive.ubuntu.com/ubuntu mantic-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 0.8+dfsg-23build1 500 500 http://us.archive.ubuntu.com/ubuntu mantic/universe amd64 Packages ** Tags removed: verification-needed verification-needed-jammy verification-needed-mantic ** Tags added: verification-done verification-done-jammy verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2018449 Title: [SRU] `xmms2 add --playlist ... ` causes a core dump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xmms2/+bug/2018449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2018449] Re: [SRU] `xmms2 add --playlist ... ` causes a core dump
I can confirm that the xmms2 package in jammy-proposed has fixed the bug for me. Test done: 1. Install xmms2 from jammy-proposed 2. create a playlist 3. Add few mp3 to the playlist according to the testplan 4. Switch the test playlist with the command "xmms2 playlist switch" 5. Execute "xmms2 list" to confirm that the mp3 were successfully added to the list Test result: the errors with xmms2 has been fixed. Package tested: $ apt-cache policy xmms2 xmms2: Installed: 0.8+dfsg-22ubuntu0.1 Candidate: 0.8+dfsg-22ubuntu0.1 Version table: *** 0.8+dfsg-22ubuntu0.1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 0.8+dfsg-22build3 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2018449 Title: [SRU] `xmms2 add --playlist ... ` causes a core dump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xmms2/+bug/2018449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055685] Re: Cranky update-dkms-versions rollout
This bug is awaiting verification that the linux/4.15.0-224.236 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic-linux' to 'verification-done-bionic-linux'. If the problem still exists, change the tag 'verification-needed-bionic- linux' to 'verification-failed-bionic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-bionic-linux-v2 verification-needed-bionic-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055685 Title: Cranky update-dkms-versions rollout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059143] Re: Remove getabis scripts
This bug is awaiting verification that the linux/4.15.0-224.236 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic-linux' to 'verification-done-bionic-linux'. If the problem still exists, change the tag 'verification-needed-bionic- linux' to 'verification-failed-bionic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-bionic-linux-v2 verification-needed-bionic-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059143 Title: Remove getabis scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2029924] Re: [SRU] "Can't locate lcovutil.pm" after updating to 2.0-1
I can confirm that the lcov package in mantic-proposed has fixed the bug for me. Test done: 1. Install lcov on a Mantic image 2. Execute "lcov -h" and confirmed the issue is still seen 3. Add mantic-proposed to apt sources.list 4. Install lcov from mantic-proposed 5. Execute "lcov -h" again to confirm the help is displayed. 6. get test.c from the testplan 7. build it with "cc test.c -fprofile-arcs -ftest-coverage -lgcov" 8. Execute ./a.out 9. Execute "lcov --base-directory . --directory . --capture --output-file i3.info" 10. Execute "genhtml -o html/ i3.info" to generate the html files 11. Open index.html in the browser to see the record. Test result: the errors with lcov has been fixed. Package tested: $ apt-cache policy lcov lcov: Installed: 2.0-1ubuntu0.2 Candidate: 2.0-1ubuntu0.2 Version table: *** 2.0-1ubuntu0.2 100 100 http://us.archive.ubuntu.com/ubuntu mantic-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 2.0-1 500 500 http://us.archive.ubuntu.com/ubuntu mantic/universe amd64 Packages ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2029924 Title: [SRU] "Can't locate lcovutil.pm" after updating to 2.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lcov/+bug/2029924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059738] Re: Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059738 Title: Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/2059738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059973] Re: my touch pad doesn't wok at all.
** Changed in: linux-signed-hwe-6.5 (Ubuntu) Assignee: (unassigned) => Anthony Wong (anthonywong) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059973 Title: my touch pad doesn't wok at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2059973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059814] Re: Enable GDS in the 6.8 based linux-nvidia kernel
** Changed in: linux-nvidia (Ubuntu) Assignee: (unassigned) => Jose Ogando Justo (joseogando) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059814 Title: Enable GDS in the 6.8 based linux-nvidia kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2059814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059827] Re: System hung indefinitely during a Software Update prompt. The update related to audio. I had to hard restart the system.
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Anthony Wong (anthonywong) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059827 Title: System hung indefinitely during a Software Update prompt. The update related to audio. I had to hard restart the system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059951] Re: mlxbf_gige: stop interface during shutdown
** Changed in: linux-bluefield (Ubuntu) Assignee: (unassigned) => Jose Ogando Justo (joseogando) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059951 Title: mlxbf_gige: stop interface during shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2059951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059961] Re: genetlink: fix single op policy dump when do is present
** Changed in: linux-bluefield (Ubuntu) Assignee: (unassigned) => Jose Ogando Justo (joseogando) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059961 Title: genetlink: fix single op policy dump when do is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2059961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2047154] Re: [amdgpu][drm] *ERROR* flip_done timed out
** Changed in: linux-hwe-6.5 (Ubuntu) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047154 Title: [amdgpu][drm] *ERROR* flip_done timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2047154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059353] Re: kernel 6.5.0-26-generic causes 640x480 default resolution on aspeed (drm/ast) video
** Changed in: linux-signed-hwe-6.5 (Ubuntu) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059353 Title: kernel 6.5.0-26-generic causes 640x480 default resolution on aspeed (drm/ast) video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2059353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059820] Re: package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: 已安装 linux-image-6.5.0-26-generic 软件包 pre-removal 脚本 子进程返回错误状态 1
** Changed in: linux-signed-hwe-6.5 (Ubuntu) Assignee: (unassigned) => Anthony Wong (anthonywong) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059820 Title: package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: 已安装 linux-image-6.5.0-26-generic 软件包 pre-removal 脚本 子进程返回错误状态 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2059820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059712] Re: `perf report` complains about missing tips.txt file
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059712 Title: `perf report` complains about missing tips.txt file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040059] Re: [SRU] Sage crashes on start due to a missmatched dependency
I can confirm that the sagemath package in mantic-proposed has fixed the bug for me. Test done according to the testplan: $ sage ┌┐ │ SageMath version 9.5, Release Date: 2022-01-30 │ │ Using Python 3.11.6. Type "help()" for help. │ └┘ sage: 2 + 2 4 sage: factor(-2007) -1 * 3^2 * 223 sage: A = matrix(4,4, range(16)); A [ 0 1 2 3] [ 4 5 6 7] [ 8 9 10 11] [12 13 14 15] sage: factor(A.charpoly()) x^2 * (x^2 - 30*x - 80) Test result: the errors with sagemath has been fixed. Package tested: $ apt-cache policy sagemath sagemath: Installed: 9.5-6ubuntu0.1.1 Candidate: 9.5-6ubuntu0.1.1 Version table: *** 9.5-6ubuntu0.1.1 100 100 http://us.archive.ubuntu.com/ubuntu mantic-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 9.5-6 500 500 http://us.archive.ubuntu.com/ubuntu mantic/universe amd64 Packages ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040059 Title: [SRU] Sage crashes on start due to a missmatched dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sagemath/+bug/2040059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059873] Re: Thunderbird needs custom css to match Yaru colors
** Changed in: thunderbird (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059873 Title: Thunderbird needs custom css to match Yaru colors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2059873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950691] Re: Mouse's cursor size is not applied after reboot
Reading this upstream bug, it looks like it's fixed in 1.4.0, which will be available in 24.04/Noble or 22.04/Jammy with the Lubuntu Backports PPA added to it. https://github.com/lxqt/lxqt/issues/2391#issuecomment-1533247900 ** Changed in: lxqt-config (Ubuntu) Status: Confirmed => Fix Released ** Bug watch added: github.com/lxqt/lxqt/issues #2391 https://github.com/lxqt/lxqt/issues/2391 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950691 Title: Mouse's cursor size is not applied after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1950691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048517] Re: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qemu (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/2048517 Title: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2048517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059874] Re: on upgrade sshd-socket-generator conversion does not respect administrator intent
> For me the biggest problem was the socket unit beeing re-enabled when I had it disabled it but still running sshd.service (ie without socket activation) - now you're unexpectidly switched back to using socket activation - something I explicitly opted out of. Okay. We could probably adjust the check to ignore migration if the user is upgrading from kinetic or newer and has ssh.socket disabled. > I could also see this causing problems if you have the socket unit masked (dont see why you would want that however) but the the service is enabled, now you are without sshd. Actually I think the postinst would also fail in that case, as systemctl enable fails enabling masked units. This is a good point as well. ** Changed in: openssh (Ubuntu) Status: Incomplete => Confirmed ** Changed in: openssh (Ubuntu) Importance: Low => Medium ** Changed in: openssh (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059874 Title: on upgrade sshd-socket-generator conversion does not respect administrator intent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055345] Re: sigil < 2.1.0 plugin support broken by Python 3.12
Upstream released Sigil 2.1.0, carrying this patch, so it's no longer necessary if an upgrade is planned. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055345 Title: sigil < 2.1.0 plugin support broken by Python 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sigil/+bug/2055345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2018192] Re: Desktop Border Incorrect
As 23.04 is no longer a supported release of Lubuntu, is this still a problem with 23.10? ** Changed in: lxqt-config (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2018192 Title: Desktop Border Incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/2018192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044416] Re: Cannot change screenresolution with Monitor settings or xrandr
Is this still an issue? If so, I have two questions: 1. None of the listed resolutions work? 2. When you try to change the resolution in `xrandr`, what specific command do you use and what is the response? ** Changed in: lxqt-config (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044416 Title: Cannot change screenresolution with Monitor settings or xrandr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/2044416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060077] [NEW] Unable to load the feed
Public bug reported: Unable to load podcast feeds in Rythmbox. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: rhythmbox 3.4.7-2ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 16:13:03 2024 InstallationDate: Installed on 2022-04-07 (726 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.d.apport: 2024-02-22T08:20:00 ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060077 Title: Unable to load the feed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2060077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
** Changed in: procps (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/2057792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947500] Re: lxqt-config-monitor crashes in VTs
Can't reproduce in the oldest currently supported version of Lubuntu: 22.04/Jammy. ** Changed in: lxqt-config (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/1947500 Title: lxqt-config-monitor crashes in VTs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1947500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876503] Re: Keyboard input suddenly stops to work, but when i log off and relog it comes back to normal.(I cant use keyboard after the bug happens, but i can do it normaly after log out- log on)
Is this still an issue? ** Changed in: lxqt-config (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876503 Title: Keyboard input suddenly stops to work, but when i log off and relog it comes back to normal.(I cant use keyboard after the bug happens, but i can do it normaly after log out- log on) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1876503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882411] Re: lubuntu monitor settings touching screens with gap between
** Bug watch added: github.com/lxqt/lxqt-config/issues #756 https://github.com/lxqt/lxqt-config/issues/756 ** Also affects: lxqt via https://github.com/lxqt/lxqt-config/issues/756 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/1882411 Title: lubuntu monitor settings touching screens with gap between To manage notifications about this bug go to: https://bugs.launchpad.net/lxqt/+bug/1882411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054809] Re: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules
** Tags removed: verification-needed-focal-linux-aws-5.15 verification-needed-focal-linux-nvidia-tegra-5.15 verification-needed-jammy-linux-aws-fips verification-needed-jammy-linux-nvidia-tegra ** Tags added: verification-done-focal-linux-aws-5.15 verification-done-focal-linux-nvidia-tegra-5.15 verification-done-jammy-linux-aws-fips verification-done-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054809 Title: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829641] Re: brightness keys on laptop don't dim the backlight
Looking at the upstream bug, I believe this to be fixed in 1.4.0 which will be available in Noble/24.04 and is also available in Jammy/22.04 with the Lubuntu backports (https://launchpad.net/~lubuntu- dev/+archive/ubuntu/backports). If this issue persists in 1.4.0, please reopen. ** Changed in: lxqt-config (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829641 Title: brightness keys on laptop don't dim the backlight To manage notifications about this bug go to: https://bugs.launchpad.net/lxqt/+bug/1829641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857946] Re: windows maximized on one screen have a slither visible on other screen
Is this still an issue in 22.04/Jammy or beyond? ** Changed in: lxqt-config (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857946 Title: windows maximized on one screen have a slither visible on other screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1857946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835595] Re: Cannot turn off laptop LED using Monitor Settings
** Changed in: lxqt-config (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835595 Title: Cannot turn off laptop LED using Monitor Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1835595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855517] Re: xscreensaver - two displays and fliptext bottom pixel line on one display draws on wrong display
Is this still an issue in Jammy, Mantic or Noble? ** Changed in: lxqt-config (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855517 Title: xscreensaver - two displays and fliptext bottom pixel line on one display draws on wrong display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1855517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912841] Re: keyboard layout switch keys don't work correctly for the specific English/Persian combination
While still present in 22.04/Jammy, 23.10/Mantic (and beyond) is not affected. The only thing that's not known: where the fix came from. There was some suggestion that the bug existed in Qt, so that's probably where the fix is. In any case, I think that means a backport is likely out of the question. ** Changed in: lxqt-config (Ubuntu) Status: Triaged => 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/1912841 Title: keyboard layout switch keys don't work correctly for the specific English/Persian combination To manage notifications about this bug go to: https://bugs.launchpad.net/lxqt/+bug/1912841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055776] Re: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM.
I was able to reproduce the bug on Focal, and since we seem to carry the same version on Jammy/Mantic (and likely Noble), it's probable that the bug also happens in those releases. For future reference: # apt install -y libvirt-daemon-system bind9 dnsmasq Reboot, and try bringing up the "default" network on libvirt: # virsh net-start default error: Failed to start network default error: internal error: Child process (VIR_BRIDGE_NAME=virbr0 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper) unexpected exit status 2: dnsmasq: failed to create listening socket for 192.168.122.1: Address already in use -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055776 Title: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2055776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2050083] Re: generate and ship vmlinux.h to allow packages to build BPF CO-RE
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2050083 Title: generate and ship vmlinux.h to allow packages to build BPF CO-RE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2050083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060073] [NEW] folks build test failures with glib 2.80
Public bug reported: folks build tests are failing. I reported this issue upstream. It appears to be triggered by glib 2.80 and gobject-introspection 1.80. We worked around this issue for Ubuntu 24.04 LTS by ignoring build test failures because it was essential that we build folks to clear transitions. ** Affects: libfolks Importance: Unknown Status: Unknown ** Affects: folks (Ubuntu) Importance: High Status: Triaged ** Tags: ftbfs noble ** Bug watch added: gitlab.gnome.org/GNOME/folks/-/issues #140 https://gitlab.gnome.org/GNOME/folks/-/issues/140 ** Also affects: libfolks via https://gitlab.gnome.org/GNOME/folks/-/issues/140 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/2060073 Title: folks build test failures with glib 2.80 To manage notifications about this bug go to: https://bugs.launchpad.net/libfolks/+bug/2060073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060072] [NEW] Removal request to allow ruby-faraday 2.x migration
Public bug reported: ruby-faraday-middleware was marked as deprecated by ruby-faraday 2.x: https://github.com/lostisland/faraday_middleware?tab=readme-ov- file#faraday-middleware As expected, the tests do not work with the new version. We need to follow Debian and request its removal: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025092 There are some dependencies that would also require removals: $ reverse-depends -r noble src:ruby-faraday-middleware Reverse-Depends === * ruby-asana(for ruby-faraday-middleware) * ruby-behance (for ruby-faraday-middleware) * ruby-diaspora-federation (for ruby-faraday-middleware) * ruby-faraday-middleware-multi-json * ruby-gh (for ruby-faraday-middleware) * ruby-graphlient (for ruby-faraday-middleware) * ruby-puppet-forge (for ruby-faraday-middleware) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ reverse-depends -r noble src:ruby-faraday-middleware -a source Reverse-Build-Depends = * ruby-asana(for ruby-faraday-middleware) * ruby-behance (for ruby-faraday-middleware) * ruby-diaspora-federation (for ruby-faraday-middleware) * ruby-faraday-middleware-multi-json * ruby-gh (for ruby-faraday-middleware) * ruby-graphlient (for ruby-faraday-middleware) * ruby-puppet-forge (for ruby-faraday-middleware) $ reverse-depends -r noble src:ruby-asana $ reverse-depends -r noble src:ruby-asana -a source No reverse dependencies found $ reverse-depends -r noble src:ruby-diaspora-federation Reverse-Depends === * ruby-diaspora-federation-rails Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ reverse-depends -r noble src:ruby-diaspora-federation -a source Reverse-Build-Depends = * ruby-diaspora-federation-rails $ reverse-depends -r noble src:ruby-diaspora-federation-rails $ reverse-depends -r noble src:ruby-diaspora-federation-rails -a source No reverse dependencies found $ reverse-depends -r noble src:ruby-faraday-middleware-multi-json Reverse-Depends === * ruby-asana(for ruby-faraday-middleware-multi-json) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ reverse-depends -r noble src:ruby-faraday-middleware-multi-json -a source Reverse-Build-Depends = * ruby-asana(for ruby-faraday-middleware-multi-json) $ reverse-depends -r noble src:ruby-gh $ reverse-depends -r noble src:ruby-gh -a source No reverse dependencies found $ reverse-depends -r noble src:ruby-graphlient No reverse dependencies found $ reverse-depends -r noble src:ruby-graphlient -a source No reverse dependencies found $ reverse-depends -r noble src:ruby-puppet-forge Reverse-Depends === * librarian-puppet (for ruby-puppet-forge) * r10k (for ruby-puppet-forge) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ reverse-depends -r noble src:ruby-puppet-forge -a source Reverse-Build-Depends = * librarian-puppet (for ruby-puppet-forge) * r10k (for ruby-puppet-forge) $ reverse-depends -r noble src:librarian-puppet $ reverse-depends -r noble src:librarian-puppet -a source No reverse dependencies found $ reverse-depends -r noble src:r10k No reverse dependencies found $ reverse-depends -r noble src:r10k -a source No reverse dependencies found The removal of ruby-behance was already requested here: https://bugs.launchpad.net/ubuntu/+source/ruby-behance/+bug/2060069 In short, I'd like to request the removal of the following source packages and associated binaries: - ruby-faraday-middleware - ruby-asana - ruby-diaspora-federation - ruby-diaspora-federation-rails - ruby-faraday-middleware-multi-json - ruby-gh - ruby-graphlient - ruby-puppet-forge - librarian-puppet - r10k ** Affects: librarian-puppet (Ubuntu) Importance: Undecided Status: New ** Affects: r10k (Ubuntu) Importance: Undecided Status: New ** Affects: ruby-asana (Ubuntu) Importance: Undecided Status: New ** Affects: ruby-diaspora-federation (Ubuntu) Importance: Undecided Status: New ** Affects: ruby-diaspora-federation-rails (Ubuntu) Importance: Undecided Status: New ** Affects: ruby-faraday-middleware (Ubuntu) Importance: Undecided Status: New ** Affects: ruby-faraday-middleware-multi-json (Ubuntu) Importance: Undecided Status: New ** Affects: ruby-gh (Ubuntu) Importance: Undecided Status: New ** Affects: ruby-graphlient (Ubuntu) Importance: Undecided
[Bug 2058914] Re: python-pytest-flake8 FTBFS against python-flake8 7
The attachment "python-pytest-flake8_1.1.1-4ubuntu1.debdiff" 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/2058914 Title: python-pytest-flake8 FTBFS against python-flake8 7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-flake8/+bug/2058914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059874] Re: on upgrade sshd-socket-generator conversion does not respect administrator intent
I'm not that invested in the having openssh-server installed but not running use-case, but in general people do not like their local configuration beeing overridden on package upgrades in this manner. I could image people having it installed for the man-pages, or maybe using other units for it (per VRF instances or something), having the main service and socket units disabled, but I doubt that happens that much in practice. For me the biggest problem was the socket unit beeing re-enabled when I had it disabled it but still running sshd.service (ie without socket activation) - now you're unexpectidly switched back to using socket activation - something I explicitly opted out of. I could also see this causing problems if you have the socket unit masked (dont see why you would want that however) but the the service is enabled, now you are without sshd. Actually I think the postinst would also fail in that case, as systemctl enable fails enabling masked units. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059874 Title: on upgrade sshd-socket-generator conversion does not respect administrator intent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060071] [NEW] Add initial r36.3 out-of-tree module meta packages
Public bug reported: We want to enable tracks for different versions of the out-of-tree modules. For now we only have R36.3, so create the meta packages for that version. These meta packages include: * linux-nvidia-tegra-igx-r36.3-igpu: for non-realtime kernel, R36.3 OOTM, and iGPU display drivers * linux-nvidia-tegra-igx-rt-r36.3-igpu: for realtime kernel, R36.3 OOTM, and iGPU display drivers * linux-nvidia-tegra-igx-r36.3-dgpu: for non-realtime kernel, R36.3 OOTM, and dGPU display drivers ** Affects: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Importance: Undecided Assignee: Jacob Martin (jacobmartin) Status: 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/2060071 Title: Add initial r36.3 out-of-tree module meta packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx-modules-signed/+bug/2060071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059335] Re: FFe: Sync file-roller 44-2 (main) from Debian unstable (main)
Compressing a folder in nemo works now with 44-2 and it works with 43 for me also. Thank you for testing and reporting that issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059335 Title: FFe: Sync file-roller 44-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2059335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059714] Re: FFe: update numpy to 1.26.x
now in proposed ** Changed in: numpy (Ubuntu) Status: Triaged => 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/2059714 Title: FFe: update numpy to 1.26.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/numpy/+bug/2059714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060069] [NEW] Removal request to allow ruby-faraday 2.x migration
Public bug reported: ruby-behance/0.6.1-4 does not support ruby-faraday 2.x and last upstream commit in the Github repo was from 6 years ago: https://github.com/amedrz/behance Apparently, there will not be any further developement. In Debian, the Ruby team is planning to remove it from the archive: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025094 We will need to do the same to allow ruby-faraday 2.x migration. $ reverse-depends -r noble src:ruby-behance $ reverse-depends -r noble src:ruby-behance -a source No reverse dependencies found Please, remove the ruby-behance source package and its binary. ** Affects: ruby-behance (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/2060069 Title: Removal request to allow ruby-faraday 2.x migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-behance/+bug/2060069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-aws-6.5/6.5.0.1017.17~22.04.2)
All autopkgtests for the newly accepted linux-meta-aws-6.5 (6.5.0.1017.17~22.04.2) for jammy have finished running. The following regressions have been reported in tests triggered by the package: linux-aws-6.5/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-aws-6.5 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1988819] Re: When apt keeps back packages due to phased updates, it should list them separately
Not sure who all the upstream(s) involved might be, but from my personal PoV at least you can add all the options you like… the topic gets harder if we talk defaults & changing (e.g.) the lists completely (like that tabular verbose-explosion thingy from apk or whatever it was). At some point it might make sense to extended apt-patterns so that current (and future) lists can be expressed in them and then add some more options to format those lists/tables/… at which point we could have different templates and so options/choices galore. I think aptitude has formatting to some extend of its lists. One of my first apt patches that was never merged was actually about reordering/coloring the lists… that failed, so I am very positive that a much bigger yak will be shaved more easily and faster many years later. ;) Precedence of the initial ask is 'can be autoremoved' btw, which is not displayed, displays a full list, an even fuller list in version mode or displays a single line with how many packages could be autoremoved depending on config. P.S.: On a multi-arch system nearly every Depends is a choice even without or-groups: given that you e.g. pick banana:amd64 or banana:i386 for an M-A:foreign banana. And the t64 transition added a quadrillion of real vs. virtual bananas at least until everyone depends on bananat64. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1988819 Title: When apt keeps back packages due to phased updates, it should list them separately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971699] Re: disable Intel DMA remapping by default
This bug is awaiting verification that the linux-nvidia- tegra-5.15/5.15.0-1023.23~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'. If the problem still exists, change the tag 'verification-needed-focal- linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia- tegra-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 verification-needed-focal-linux-nvidia-tegra-5.15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971699 Title: disable Intel DMA remapping by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971699] Re: disable Intel DMA remapping by default
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1023.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971699 Title: disable Intel DMA remapping by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out
This bug is awaiting verification that the linux-nvidia- tegra-5.15/5.15.0-1023.23~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'. If the problem still exists, change the tag 'verification-needed-focal- linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia- tegra-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 verification-needed-focal-linux-nvidia-tegra-5.15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036239 Title: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1023.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036239 Title: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044131] Re: i915 regression introduced with 5.5 kernel
This bug is awaiting verification that the linux-nvidia- tegra-5.15/5.15.0-1023.23~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'. If the problem still exists, change the tag 'verification-needed-focal- linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia- tegra-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 verification-needed-focal-linux-nvidia-tegra-5.15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044131 Title: i915 regression introduced with 5.5 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2044131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2045561] Re: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules
This bug is awaiting verification that the linux-nvidia- tegra-5.15/5.15.0-1023.23~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'. If the problem still exists, change the tag 'verification-needed-focal- linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia- tegra-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 verification-needed-focal-linux-nvidia-tegra-5.15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2045561 Title: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044131] Re: i915 regression introduced with 5.5 kernel
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1023.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044131 Title: i915 regression introduced with 5.5 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2044131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2045561] Re: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1023.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2045561 Title: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2047634] Re: Reject connection when malformed L2CAP signal packet is received
This bug is awaiting verification that the linux-nvidia- tegra-5.15/5.15.0-1023.23~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'. If the problem still exists, change the tag 'verification-needed-focal- linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia- tegra-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047634 Title: Reject connection when malformed L2CAP signal packet is received To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2047634] Re: Reject connection when malformed L2CAP signal packet is received
This bug is awaiting verification that the linux-nvidia- tegra-5.15/5.15.0-1023.23~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'. If the problem still exists, change the tag 'verification-needed-focal- linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia- tegra-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 verification-needed-focal-linux-nvidia-tegra-5.15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047634 Title: Reject connection when malformed L2CAP signal packet is received To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2047634] Re: Reject connection when malformed L2CAP signal packet is received
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1023.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047634 Title: Reject connection when malformed L2CAP signal packet is received To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048404] Re: Don't WARN_ON_ONCE() for a broken discovery table
This bug is awaiting verification that the linux-nvidia- tegra-5.15/5.15.0-1023.23~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'. If the problem still exists, change the tag 'verification-needed-focal- linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia- tegra-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 verification-needed-focal-linux-nvidia-tegra-5.15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048404 Title: Don't WARN_ON_ONCE() for a broken discovery table To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048404] Re: Don't WARN_ON_ONCE() for a broken discovery table
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1023.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048404 Title: Don't WARN_ON_ONCE() for a broken discovery table To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049689] Re: partprobe is broken on empty loopback device
This bug is awaiting verification that the linux-nvidia- tegra-5.15/5.15.0-1023.23~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'. If the problem still exists, change the tag 'verification-needed-focal- linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia- tegra-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 verification-needed-focal-linux-nvidia-tegra-5.15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049689 Title: partprobe is broken on empty loopback device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051050] Re: Audio balancing setting doesn't work with the cirrus codec
This bug is awaiting verification that the linux-nvidia- tegra-5.15/5.15.0-1023.23~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'. If the problem still exists, change the tag 'verification-needed-focal- linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia- tegra-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 verification-needed-focal-linux-nvidia-tegra-5.15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051050 Title: Audio balancing setting doesn't work with the cirrus codec To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051050] Re: Audio balancing setting doesn't work with the cirrus codec
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1023.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051050 Title: Audio balancing setting doesn't work with the cirrus codec To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052005] Re: Validate connection interval to pass Bluetooth Test Suite
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1023.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052005 Title: Validate connection interval to pass Bluetooth Test Suite To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052005] Re: Validate connection interval to pass Bluetooth Test Suite
This bug is awaiting verification that the linux-nvidia- tegra-5.15/5.15.0-1023.23~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'. If the problem still exists, change the tag 'verification-needed-focal- linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia- tegra-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 verification-needed-focal-linux-nvidia-tegra-5.15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052005 Title: Validate connection interval to pass Bluetooth Test Suite To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
