[Bug 148875] Re: Full keymap for Genius TwinTouch
** Bug watch added: gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues #61 https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/61 ** Changed in: xkeyboard-config Importance: Medium => Unknown ** Changed in: xkeyboard-config Remote watch: freedesktop.org Bugzilla #18837 => gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues #61 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/148875 Title: Full keymap for Genius TwinTouch To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/148875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067383] Comment bridged from LTC Bugzilla
--- Comment From sthou...@in.ibm.com 2024-06-18 02:54 EDT--- distro, any update on this bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067383 Title: [Ubuntu 24.04] hotplug of 68 or more cpus is making the guest shutoff! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2067383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 148875] Re: Full keymap for Genius TwinTouch
** Changed in: xkeyboard-config Status: Unknown => 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/148875 Title: Full keymap for Genius TwinTouch To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/148875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064163] Re: mlxbf-gige: Vitesse PHY stuck in a bad state during reboot test
Re-add verification-done-jammy-linux-bluefield tag (it was removed by ubuntu-kernel-bot after incorrect removal of kernel-spammed-jammy-linux- bluefield-v2 tag). ** Tags removed: verification-needed-jammy-linux-bluefield ** Tags added: verification-done-jammy-linux-bluefield -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064163 Title: mlxbf-gige: Vitesse PHY stuck in a bad state during reboot test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2064163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069582] Re: backport-iwlwifi-dkms FTBS with linux 6.8 in jammy
** Patch added: "jammy-backport-iwlwifi.debdiff" https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/2069582/+attachment/5790444/+files/jammy-backport-iwlwifi.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069582 Title: backport-iwlwifi-dkms FTBS with linux 6.8 in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/2069582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059756] Re: [SRU] adsys 0.14.1
This bug was fixed in the package golang-1.22 - 1.22.2-2~22.04
---
golang-1.22 (1.22.2-2~22.04) jammy; urgency=medium
* Backport golang 1.22 to jammy (LP: #2059756)
* Build with Go 1.20
- d/control{,.in}: use golang-1.20-go in Build-Depends
- d/rules: use /usr/lib/go-1.20/bin/go to set GOROOT_BOOTSTRAP path
-- Gabriel Nagy Mon, 22 Apr 2024 14:49:00
+0300
** Changed in: golang-1.22 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** Changed in: golang-1.22 (Ubuntu Mantic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059756
Title:
[SRU] adsys 0.14.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059756] Re: [SRU] adsys 0.14.1
This bug was fixed in the package golang-1.22 - 1.22.2-2~23.10
---
golang-1.22 (1.22.2-2~23.10) mantic; urgency=medium
* Backport to Mantic (LP: #2059756)
* Build with Go 1.20
+ d/control{,.in}: use golang-1.20-go in Build-Depends
+ d/rules: use /usr/lib/go-1.20/bin/go to set GOROOT_BOOTSTRAP path
-- Gabriel Nagy Tue, 30 Apr 2024 15:39:36
+0300
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059756
Title:
[SRU] adsys 0.14.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059756] Re: [SRU] adsys 0.14.1
(out of band) Additionally, Utkarsh has validated that the golang-1.22 packages in jammy-proposed correctly build docker.io, and golang-1.22 from mantic has correctly built the adsys in mantic. As golang-1.22 a new package in Jammy and Mantic and hence low regression risk, and in the absence of any other test plan for the golang-1.22 packages (:P), I'm releasing golang-1.22 for jammy and mantic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059756 Title: [SRU] adsys 0.14.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059756] Update Released
The verification of the Stable Release Update for golang-1.22 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059756 Title: [SRU] adsys 0.14.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069686] [NEW] package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1
Public bug reported: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tex-common 6.13 ProcVersionSignature: Ubuntu 5.15.0-107.117~20.04.1-generic 5.15.149 Uname: Linux 5.15.0-107-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_15_0_107_117_generic_104 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 18 17:12:35 2024 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-12-09 (1286 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: tex-common Title: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2024-02-18 (120 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069686 Title: package tex-common 6.13 failed to install/upgrade: installed tex- common package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/2069686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069582] Re: backport-iwlwifi-dkms FTBS with linux 6.8 in jammy
Test build with GA kernel 5.15: Building initial module for 5.15.0-115-generic ... iwlwifi-compat.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-115-generic/updates/dkms/ iwlwifi.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-115-generic/updates/dkms/ iwlxvt.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-115-generic/updates/dkms/ iwlmvm.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-115-generic/updates/dkms/ mac80211.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-115-generic/updates/dkms/ cfg80211.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.0-115-generic/updates/dkms/ Test build with new 6.8 hwe kernel: Building initial module for 6.8.0-35-lowlatency ... iwlwifi-compat.ko: Running module version sanity check. Module has been obsoleted due to being included in kernel 6.7.0. We will avoid installing for future kernels above 6.7.0. You may override by specifying --force. iwlwifi.ko: Running module version sanity check. Module has been obsoleted due to being included in kernel 6.7.0. We will avoid installing for future kernels above 6.7.0. You may override by specifying --force. iwlxvt.ko: Running module version sanity check. Module has been obsoleted due to being included in kernel 6.7.0. We will avoid installing for future kernels above 6.7.0. You may override by specifying --force. iwlmvm.ko: Running module version sanity check. Module has been obsoleted due to being included in kernel 6.7.0. We will avoid installing for future kernels above 6.7.0. You may override by specifying --force. mac80211.ko: Running module version sanity check. Module has been obsoleted due to being included in kernel 6.7.0. We will avoid installing for future kernels above 6.7.0. You may override by specifying --force. cfg80211.ko: Running module version sanity check. Module has been obsoleted due to being included in kernel 6.7.0. We will avoid installing for future kernels above 6.7.0. You may override by specifying --force. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069582 Title: backport-iwlwifi-dkms FTBS with linux 6.8 in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/2069582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069687] [NEW] dahdi-dkms FTBS with the new 6.8 hwe kernel in jammy
Public bug reported: [Impact] /var/lib/dkms/dahdi/2.11.1~dfsg-1ubuntu12~22.04.3/build/drivers/dahdi/xpp/card_global.c:301:9: error: implicit declaration of function ‘strlcpy’; did you mean ‘strscpy’? [-Werror=implicit-function-declaration] 301 | strlcpy(buf, cmdline, MAX_PROC_WRITE); /* Save a copy */ | ^~~ | strscpy [Test case] $ sudo apt install dahdi-dkms [Fix] Backport the patch from Noble to properly support the new 6.8 kernel ABI. [Regression potential] DAHDI is an interface for telephony devices, we may experience regressions in systems relying on this interface/module, especially with the new 6.8 kernel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dahdi-dkms 1:2.11.1~dfsg-1ubuntu12~22.04.3 ProcVersionSignature: User Name 6.8.0-35.35.1~22.04.1-lowlatency 6.8.4 Uname: Linux 6.8.0-35-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/vdb) Date: Tue Jun 18 07:16:01 2024 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: dahdi-linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dahdi-linux (Ubuntu) Importance: Undecided Status: New ** Affects: dahdi-linux (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images ** Also affects: dahdi-linux (Ubuntu Jammy) 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/2069687 Title: dahdi-dkms FTBS with the new 6.8 hwe kernel in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/2069687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069686] Re: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069686 Title: package tex-common 6.13 failed to install/upgrade: installed tex- common package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/2069686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059756] Re: [SRU] adsys 0.14.1
Thank you, Chris. I can confirm that Jammy Go 1.22 works nicely so far - $ lxc launch ubuntu-daily:jammy docker-io --vm Creating docker-io Starting docker-io $ lxc shell docker-io root@docker-io:~# apt update root@docker-io:~# ls docker-doc_24.0.7-0ubuntu4~22.04.1_all.deb docker.io_24.0.7-0ubuntu4~22.04.1_amd64.deb snap root@docker-io:~# apt install ./*.deb Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'docker-doc' instead of './docker-doc_24.0.7-0ubuntu4~22.04.1_all.deb' Note, selecting 'docker.io' instead of './docker.io_24.0.7-0ubuntu4~22.04.1_amd64.deb' The following additional packages will be installed: bridge-utils containerd dns-root-data dnsmasq-base pigz runc ubuntu-fan Suggested packages: ifupdown aufs-tools cgroupfs-mount | cgroup-lite debootstrap docker-buildx docker-compose-v2 rinse zfs-fuse | zfsutils The following NEW packages will be installed: bridge-utils containerd dns-root-data dnsmasq-base docker-doc docker.io pigz runc ubuntu-fan 0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded. Need to get 46.7 MB/78.2 MB of archives. After this operation, 288 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 /root/docker-doc_24.0.7-0ubuntu4~22.04.1_all.deb docker-doc all 24.0.7-0ubuntu4~22.04.1 [2325 kB] Get:2 /root/docker.io_24.0.7-0ubuntu4~22.04.1_amd64.deb docker.io amd64 24.0.7-0ubuntu4~22.04.1 [29.1 MB] Get:3 http://archive.ubuntu.com/ubuntu jammy/universe amd64 pigz amd64 2.6-1 [63.6 kB] Get:4 http://archive.ubuntu.com/ubuntu jammy/main amd64 bridge-utils amd64 1.7-1ubuntu3 [34.4 kB] Get:5 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 runc amd64 1.1.12-0ubuntu2~22.04.1 [8405 kB] Get:6 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 containerd amd64 1.7.12-0ubuntu2~22.04.1 [37.8 MB] Get:7 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 dns-root-data all 2023112702~ubuntu0.22.04.1 [5136 B] Get:8 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 dnsmasq-base amd64 2.90-0ubuntu0.22.04.1 [374 kB] Get:9 http://archive.ubuntu.com/ubuntu jammy/universe amd64 ubuntu-fan all 0.12.16 [35.2 kB] Fetched 46.7 MB in 11s (4128 kB/s) Preconfiguring packages ... Selecting previously unselected package pigz. (Reading database ... 56810 files and directories currently installed.) Preparing to unpack .../0-pigz_2.6-1_amd64.deb ... Unpacking pigz (2.6-1) ... Selecting previously unselected package bridge-utils. Preparing to unpack .../1-bridge-utils_1.7-1ubuntu3_amd64.deb ... Unpacking bridge-utils (1.7-1ubuntu3) ... Selecting previously unselected package runc. Preparing to unpack .../2-runc_1.1.12-0ubuntu2~22.04.1_amd64.deb ... Unpacking runc (1.1.12-0ubuntu2~22.04.1) ... Selecting previously unselected package containerd. Preparing to unpack .../3-containerd_1.7.12-0ubuntu2~22.04.1_amd64.deb ... Unpacking containerd (1.7.12-0ubuntu2~22.04.1) ... Selecting previously unselected package dns-root-data. Preparing to unpack .../4-dns-root-data_2023112702~ubuntu0.22.04.1_all.deb ... Unpacking dns-root-data (2023112702~ubuntu0.22.04.1) ... Selecting previously unselected package dnsmasq-base. Preparing to unpack .../5-dnsmasq-base_2.90-0ubuntu0.22.04.1_amd64.deb ... Unpacking dnsmasq-base (2.90-0ubuntu0.22.04.1) ... Selecting previously unselected package docker-doc. Preparing to unpack .../6-docker-doc_24.0.7-0ubuntu4~22.04.1_all.deb ... Unpacking docker-doc (24.0.7-0ubuntu4~22.04.1) ... Selecting previously unselected package docker.io. Preparing to unpack .../7-docker.io_24.0.7-0ubuntu4~22.04.1_amd64.deb ... Unpacking docker.io (24.0.7-0ubuntu4~22.04.1) ... Selecting previously unselected package ubuntu-fan. Preparing to unpack .../8-ubuntu-fan_0.12.16_all.deb ... Unpacking ubuntu-fan (0.12.16) ... Setting up dnsmasq-base (2.90-0ubuntu0.22.04.1) ... Setting up runc (1.1.12-0ubuntu2~22.04.1) ... Setting up dns-root-data (2023112702~ubuntu0.22.04.1) ... Setting up bridge-utils (1.7-1ubuntu3) ... Setting up pigz (2.6-1) ... Setting up docker-doc (24.0.7-0ubuntu4~22.04.1) ... Setting up containerd (1.7.12-0ubuntu2~22.04.1) ... Created symlink /etc/systemd/system/multi-user.target.wants/containerd.service → /lib/systemd/system/containerd.servi ce. Setting up ubuntu-fan (0.12.16) ... Created symlink /etc/systemd/system/multi-user.target.wants/ubuntu-fan.service → /lib/systemd/system/ubuntu-fan.servi ce. Setting up docker.io (24.0.7-0ubuntu4~22.04.1) ... Adding group `docker' (GID 121) ... Done. Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /lib/systemd/system/docker.service. Created symlink /etc/systemd/system/sockets.target.wants/docker.socket → /lib/systemd/system/docker.socket. Processing triggers for dbus (1.12.20-2ubuntu4.1) ... Processing triggers for man-db (2.10.2-1) ... Scanning processes..
[Bug 2069687] Re: dahdi-dkms FTBS with the new 6.8 hwe kernel in jammy
** Patch added: "jammy-dahdi-dkms.debdiff" https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/2069687/+attachment/5790455/+files/jammy-dahdi-dkms.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069687 Title: dahdi-dkms FTBS with the new 6.8 hwe kernel in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/2069687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067125] Re: CVE-2024-21096 et al affects MariaDB in Ubuntu
** Changed in: mariadb (Ubuntu Mantic) Assignee: (unassigned) => Eduardo Barretto (ebarretto) ** Changed in: mariadb (Ubuntu Noble) Assignee: (unassigned) => Eduardo Barretto (ebarretto) ** Changed in: mariadb-10.6 (Ubuntu Jammy) Assignee: (unassigned) => Eduardo Barretto (ebarretto) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067125 Title: CVE-2024-21096 et al affects MariaDB in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb/+bug/2067125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 148875] Re: Full keymap for Genius TwinTouch
You did not reply to the need to format the patch in the required format in 2009. Marking as incomplete. ** Changed in: xkeyboard-config (Ubuntu) Status: Triaged => Incomplete ** Changed in: xkeyboard-config Importance: Unknown => Undecided ** Changed in: xkeyboard-config Status: Fix Released => New ** Changed in: xkeyboard-config Remote watch: gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues #61 => None ** Changed in: xkeyboard-config 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/148875 Title: Full keymap for Genius TwinTouch To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/148875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067383] Re: [Ubuntu 24.04] hotplug of 68 or more cpus is making the guest shutoff!
Hello, as far as I can see (and I just double checked at github.com/qemu) the patch set PATCH v2 - "target/ppc: vcpu hotplug failure handling fixes" (4 parts) is still not upstream accepted - not in 9.0.1 (latest) nor in master (commit list). (But please, correct me if I'm wrong, in case the commit names have changes or other reasons that may have prevented me from finding them upstream.) Please note that we need the patches to be upstream accepted before we can pick (and 'SRU') them. (A ping here in case they got accepted would be helpful too.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067383 Title: [Ubuntu 24.04] hotplug of 68 or more cpus is making the guest shutoff! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2067383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069687] Re: dahdi-dkms FTBS with the new 6.8 hwe kernel in jammy
Test build with the new 6.8 hwe kernel: Building initial module for 6.8.0-35-lowlatency ... EFI variables are not supported on this system /sys/firmware/efi/efivars not found, aborting. Done. dahdi_dummy.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ dahdi_dynamic_eth.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ dahdi_dynamic.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ dahdi_dynamic_loc.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ dahdi_echocan_jpah.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ dahdi_echocan_kb1.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ dahdi_echocan_mg2.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ dahdi_echocan_sec2.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ dahdi_echocan_sec.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ dahdi.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ dahdi_transcode.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ pciradio.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ tor2.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ wcb4xxp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ wcfxo.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ wct1xxp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ wct4xxp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ wctc4xxp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ wctdm.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ wctdm24xxp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ wcte11xp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ wcte12xp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ xpd_fxo.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.8.0-35-lowlatency/updates/dkms/ xpd_fxs.ko: Running module version sanity check. - Original module - No original module ex
[Bug 2054799] Re: [SRU] Issue with Project administration at Cloud Admin level
I successfully reproduced the problem in a 2023.2 test env created by sunbeam - https://postimg.cc/Tph65M29 and also sucessfully verified the fix as well - https://i.imgur.com/KkLqexo ** Tags removed: verification-needed-mantic ** Tags added: 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/2054799 Title: [SRU] Issue with Project administration at Cloud Admin level To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2054799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067125] Re: CVE-2024-21096 et al affects MariaDB in Ubuntu
Hi Otto, I've uploaded yesterday the 3 updates to our security-proposed ppa: https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+packages?field.name_filter=mariadb&field.status_filter=published&field.series_filter= I will take a look at the autopkgtests we have in that ppa and, if everything is looking good, I will publish it either later today or earlier tomorrow. One note though, on your comment you said the branches ubuntu-2* (e.g. ubuntu-22.04) but the correct branches are the ones you sent before, ubuntu/2* (e.g. ubuntu/22.04-jammy). Perhaps to avoid confusion in the future, would it be better to consolidate the branches? Thanks again for preparing those and I will let you know when it is released or in case of issues. ** Changed in: mariadb (Ubuntu Mantic) Status: New => Fix Committed ** Changed in: mariadb (Ubuntu Noble) Status: New => Fix Committed ** Changed in: mariadb-10.6 (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067125 Title: CVE-2024-21096 et al affects MariaDB in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb/+bug/2067125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1271238] Re: Typo in comment
Not found on Noble. ** Changed in: xkeyboard-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/1271238 Title: Typo in comment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1271238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 792434] Re: Multimedia key for stop not working correctly
Hey dfoerster, You filed this bug report against oneiric, but I see it's still open and doesn't appear to have much activity recently. So, now that noble is released, this may be a good point for you to upgrade and re-test if this issue is still present there. If it's solved in the new release and you think it's worth backporting the fix, please indicate that. Or if having the fix in the new release is good enough, feel free to close out the bug (or let us know and we'll close it.) If it's not solved, leave the bug report open. I can't promise we'll get to it (we get way more bugs filed than we can usually get to), but your testing and feedback can help out if and when we do. ** Changed in: xkeyboard-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/792434 Title: Multimedia key for stop not working correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/792434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776280] Re: Russian phonetic layout could be improved
Please check this still happens on a currently supported Ubuntu release. ** Changed in: xkeyboard-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/776280 Title: Russian phonetic layout could be improved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/776280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1561618] Re: package xkb-data 2.10.1-1ubuntu1 [modified: usr/share/X11/xkb/symbols/gr] failed to install/upgrade: impossible de créer un lien symbolique de secours de « ./usr/share/X11/xkb/symbol
Please check this still happens on a supported Ubuntu release. ** Changed in: xkeyboard-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/1561618 Title: package xkb-data 2.10.1-1ubuntu1 [modified: usr/share/X11/xkb/symbols/gr] failed to install/upgrade: impossible de créer un lien symbolique de secours de « ./usr/share/X11/xkb/symbols/gr » avant d'installer une nouvelle version: Lien croisé de périphéque invalide To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1561618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995622] Re: Unable to select Xorg supported Japanese keyboard Sanwa
Please check this still happens on a supported Ubuntu release. ** Changed in: gnome-control-center (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/995622 Title: Unable to select Xorg supported Japanese keyboard Sanwa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/995622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 652447] Re: After come back to screesaver the window manager freezes sometime
Please check this still happens on a supported Ubuntu release with supported NVIDIA drivers. ** Changed in: nvidia-graphics-drivers-180 (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/652447 Title: After come back to screesaver the window manager freezes sometime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/652447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64678] Re: apt-get dist-upgrade fails from Dapper to Edgy (different from #57121)
Please check this still happens on a supported Ubuntu release. ** Changed in: xkb-data-legacy (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/64678 Title: apt-get dist-upgrade fails from Dapper to Edgy (different from #57121) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkb-data-legacy/+bug/64678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069694] [NEW] "Flip event timeout on head 1" shutdown hang
Public bug reported: Ubuntu 24.04 LTS with 2 monitor setup, NVIDIA 4070TI graphics card using the 550 driver and Wayland. Shutting down after the end of a session the machine hung reporting a 'Flip event timeout on head 1' Let me know what additional logs would be useful for debugging this as I appreciate it's not very detailed. Photo of monitor screen attached. ** Affects: nvidia-graphics-drivers-550 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "PXL_20240614_182059150.jpg" https://bugs.launchpad.net/bugs/2069694/+attachment/5790456/+files/PXL_20240614_182059150.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069694 Title: "Flip event timeout on head 1" shutdown hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2069694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290002] Re: Volume wheel (Dell keyboard) not adjusting Ubuntu volume properly after update
Please check this still happens on a supported Ubuntu release. ** Changed in: xkeyboard-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/1290002 Title: Volume wheel (Dell keyboard) not adjusting Ubuntu volume properly after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1290002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248351] Re: Common "Dutch US international" not available
Please check this still happens on a supported Ubuntu release. ** Changed in: xkeyboard-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/1248351 Title: Common "Dutch US international" not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1248351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069695] [NEW] [SRU] OpenStack 2024.1 point release updates
Public bug reported: [Impact] This release sports mostly bug-fixes and we would like to make sure all of our users have access to these improvements. The update contains the following package updates: * heat - 22.0.1 * manila - 18.0.1 * nova - 29.0.1 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. ** Affects: cloud-archive Importance: Undecided Status: New ** Affects: cloud-archive/caracal Importance: Undecided Status: New ** Affects: heat (Ubuntu) Importance: Undecided Status: New ** Affects: manila (Ubuntu) Importance: Undecided Status: New ** Affects: nova (Ubuntu) Importance: Undecided Status: New ** Affects: heat (Ubuntu Noble) Importance: Undecided Status: New ** Affects: manila (Ubuntu Noble) Importance: Undecided Status: New ** Affects: nova (Ubuntu Noble) Importance: Undecided Status: New ** Affects: heat (Ubuntu Oracular) Importance: Undecided Status: New ** Affects: manila (Ubuntu Oracular) Importance: Undecided Status: New ** Affects: nova (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: cloud-archive/caracal Importance: Undecided Status: New ** Also affects: heat (Ubuntu) Importance: Undecided Status: New ** Also affects: manila (Ubuntu) Importance: Undecided Status: New ** Also affects: nova (Ubuntu) Importance: Undecided Status: New ** Also affects: nova (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: heat (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: manila (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: nova (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: heat (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: manila (Ubuntu Oracular) Importance: Undecided Status: New ** Description changed: - Point release updates for OpenStack Caracal. + [Impact] + This release sports mostly bug-fixes and we would like to make sure all of our users have access to these improvements. - heat - 22.0.1 - manila - 18.0.1 - nova - 29.0.1 + The update contains the following package updates: + + * heat - 22.0.1 + * manila - 18.0.1 + * nova - 29.0.1 + + [Test Case] + The following SRU process was followed: + https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates + + In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the + proposed packages can be let into -updates. + + The OpenStack team will be in charge of attaching the output summary of + the executed tests. The OpenStack team members will not mark + ‘verification-done’ until this has happened. + + [Regression Potential] + In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069695 Title: [SRU] OpenStack 2024.1 point release updates To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2069695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069695] Re: [SRU] OpenStack 2024.1 point release updates
Note this is blocked as we can't currently deploy on Noble pending completion of charm enablement work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069695 Title: [SRU] OpenStack 2024.1 point release updates To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2069695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 802589] Re: KEY_CYCLEWINDOWS invalidly mapped to XF86RotateWindows
Please check this still happens on a supported Ubuntu release. ** Changed in: xkeyboard-config (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/802589 Title: KEY_CYCLEWINDOWS invalidly mapped to XF86RotateWindows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/802589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879558] Re: grub-efi-amd64 postinst fails to install GRUB if previous GRUB install is not detected
> You can just run grub-install once by hand, and it will all update correctly afterwards. The package already has a good debconf-driven install process for GRUB ---requiring the user to do it manually not only discards the benefit of that, it's a delicate and error-prone operation that most users are not accustomed to doing (hence wrapping it in debconf). The core of the problem is the chicken-and-egg scenario of requiring GRUB to be installed in order to install GRUB. I just want to do e.g. "dpkg-reconfigure grub-efi-amd64" on a newborn system, and have the instalL_devices question come up. Right now, in order to get that, I have to fool the postinst script by running "touch /boot/grub/x86_64-efi/core.efi" beforehand. That's not a reasonable UI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879558 Title: grub-efi-amd64 postinst fails to install GRUB if previous GRUB install is not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1879558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1271238] Re: Typo in comment
I think you can mark this "Fix released", since the problem has been fixed since I reported it over ten years ago. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271238 Title: Typo in comment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1271238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990138] Re: package xkb-data 2.5-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
Please check this still happens on a supported Ubuntu release. ** Changed in: update-manager (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/990138 Title: package xkb-data 2.5-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/990138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 327963] Re: Error activating XKB configuration with MacBook keyboard model
** Bug watch added: gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues #112 https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues/112 ** Changed in: xkeyboard-config Importance: Medium => Unknown ** Changed in: xkeyboard-config Remote watch: freedesktop.org Bugzilla #24486 => gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues #112 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/327963 Title: Error activating XKB configuration with MacBook keyboard model To manage notifications about this bug go to: https://bugs.launchpad.net/mactel-support/+bug/327963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879466] Re: Purging grub-pc package deletes /etc/default/grub file owned by grub-efi-amd64
See https://salsa.debian.org/grub-team/grub/-/merge_requests/62 But ideally we should just move /etc/default/grub to grub-common -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879466 Title: Purging grub-pc package deletes /etc/default/grub file owned by grub- efi-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1879466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1524556] Re: Can't rebuild package / unrepresentable changes
You can re-build the current GRUB2 package multiple times. Re- bootstrapping does change tarball files indeed, but there is not much we can do about that. ** Changed in: grub2 (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1524556 Title: Can't rebuild package / unrepresentable changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1524556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1544809] Re: kernel security update fails if a 2nd Ubuntu on same machine
Two GRUBs taking control "back-and-forth" is unfortunately expected, and there isn't much that can be done with this with the current ESP layout. ** Changed in: grub2 (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1544809 Title: kernel security update fails if a 2nd Ubuntu on same machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1544809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570249] Re: Braswell + UBUNTU 15.10 legacy mode , grub2 graphics interface picture color distorted
The legacy VGA BIOS on your machine doesn't seem to support the same colour depth as UEFI GOP does. There isn't anything GRUB2 can do about this, and the menu is still displayed "correctly" with just less colour depth. As BIOS support is getting worse and worse on new machines, it is recommended to use UEFI boot instead of CSM. ** Changed in: grub2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570249 Title: Braswell + UBUNTU 15.10 legacy mode , grub2 graphics interface picture color distorted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1570249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712808] Re: udev interface fails in privileged containers
@jugmac00 this got resolved along the way - that same recipe is here now, and passing. https://launchpad.net/~mir-team/+snap/miriway-beta So not a Launchpad issue any more. ** Changed in: launchpad Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712808 Title: udev interface fails in privileged containers To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1712808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553687] Re: Lenovo Y700-17ISK Boot Error: Failure writing sector 0x21c8800 to 'hd0'
This seems like the BIOS failing to write to disk when trying to write the environment block and not an actual bug in GRUB2. Perhaps trying UEFI mode might help on newer machines. ** Changed in: grub2 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553687 Title: Lenovo Y700-17ISK Boot Error: Failure writing sector 0x21c8800 to 'hd0' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1553687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558926] Re: Executing "update-grub" on the console with LANG=de_DE.UTF-8 shows a malformed character
It seems to be caused by your terminal not being able to display the multibyte character "…", and not a bug in GRUB2. ** Changed in: grub2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558926 Title: Executing "update-grub" on the console with LANG=de_DE.UTF-8 shows a malformed character To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1558926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879466] Re: Purging grub-pc package deletes /etc/default/grub file owned by grub-efi-amd64
Looks like a reasonable solution. But why not just move the file instead, if that's the end goal? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879466 Title: Purging grub-pc package deletes /etc/default/grub file owned by grub- efi-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1879466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1568128] Re: GRUB fails to chainload another EFI loader when Secure Boot is active
Chainloading signed (both db and Mok) EFI loaders works fine with the current shim+GRUB+peimage combination. ** Changed in: grub2 (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/1568128 Title: GRUB fails to chainload another EFI loader when Secure Boot is active To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1568128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567534] Re: Placing grub.cfg in /boot/efi causes avoidable problems on EFI-based systems
** Changed in: grub2 (Ubuntu) Status: Confirmed => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567534 Title: Placing grub.cfg in /boot/efi causes avoidable problems on EFI-based systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1567534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 327963] Re: Error activating XKB configuration with MacBook keyboard model
** Changed in: xkeyboard-config 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/327963 Title: Error activating XKB configuration with MacBook keyboard model To manage notifications about this bug go to: https://bugs.launchpad.net/mactel-support/+bug/327963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559921] Re: package grub-pc 2.02~beta2-9ubuntu1.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Ubuntu "Precise Pangolin" is no longer supported, and Ubuntu "Trusty Tahr" only receives ESM fixes for security problems. ** Changed in: grub2 (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559921 Title: package grub-pc 2.02~beta2-9ubuntu1.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1559921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562537] Re: Ubiquity installs to 4Kn disk in BIOS mode, but installation won't boot
> Booting from 4Kn drives is and will NEVER be supported by BIOS (AKA legacy BIOS AKA LEGACY). The ONLY solution for 4Kn AF drives is to boot via UEFI. I think this is going to be the case for us too. Please use UEFI to boot 4Kn drives (512e ones still work fine on BIOS) ** Changed in: grub2 (Ubuntu) Status: New => Won't Fix ** Changed in: ubiquity (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1562537 Title: Ubiquity installs to 4Kn disk in BIOS mode, but installation won't boot To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1562537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575588] Re: package memtest86+ 5.01-3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1. Installation was made in process update of dis
Hmm this seems related to GRUB trying to find something on a NFS (or other network mounted) disk. However Ubuntu 16.04 is in ESM support only, please report a new bug if you are still experiencing similar issues on modern Ubuntu ** Changed in: grub2 (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575588 Title: package memtest86+ 5.01-3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1. Installation was made in process update of diskless station from 15.10 to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1575588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571355] Re: package grub-efi-amd64 2.02~beta2-9ubuntu1.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 64
Ubuntu 14.04 is in ESM support only, please report a new bug if you are still experiencing similar issues on modern Ubuntu ** Changed in: grub2 (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571355 Title: package grub-efi-amd64 2.02~beta2-9ubuntu1.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1571355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569567] Re: Running update-grub does not update /boot/grub/grub.cfg with GRUB_CMDLINE_LINUX_DEFAULT from /etc/default/grub
Curtin overriding /etc/default/grub via /etc/default/grub.d might not be desirable, but it is certainly not a but in grub2. ** Changed in: grub2 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569567 Title: Running update-grub does not update /boot/grub/grub.cfg with GRUB_CMDLINE_LINUX_DEFAULT from /etc/default/grub To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1569567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1596238] Re: NTFS Module not signed
NTFS is signed in the current grub2, although it is debatable whether or not it should be. ** Changed in: grub2 (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/1596238 Title: NTFS Module not signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1596238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1583691] Re: grub-probe: When a device has been specified WITHOUT option '-d', grub-probe should display an additional user-friendly advice message
While I do agree that this error message is indeed unfriendly, we ideally shouldn't expose the end user to grub-probe output anyways, and I don't feel we should carry a downstream patch for this. You are free to report this upstream and/or contribute a patch upstream that changes the error message. ** Changed in: grub2 (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583691 Title: grub-probe: When a device has been specified WITHOUT option '-d', grub-probe should display an additional user-friendly advice message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1583691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069041] Re: Changing Port in sshd_config and restarting ssh.service without effect
I'm currently trying out the Ubuntu 24.04 version and encountered an issue where modifying the SSH port didn't take effect. Fortunately, I came across this help and followed your suggestions to attempt the modifications. The port modification is now working as expected. sudo vim /etc/ssh/sshd_config sudo systemctl daemon-reload sudo systemctl restart ssh.socket -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069041 Title: Changing Port in sshd_config and restarting ssh.service without effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2069041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068843] Re: Android phone "Unable to connect" to rhythmbox daap
I have discovered that my Android phone can access rhythmbox 3.4.6 via daap. Working daap from rhythmbox 3.4.6 ** Attachment added: "good_rb_3.4.6_debug.log" https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2068843/+attachment/5790465/+files/good_rb_3.4.6_debug.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068843 Title: Android phone "Unable to connect" to rhythmbox daap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2068843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068843] Re: Android phone "Unable to connect" to rhythmbox daap
Not working daap from rhythmbox 3.4.7 ** Attachment added: "bad_rb_3.4.7_debug.log" https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2068843/+attachment/5790466/+files/bad_rb_3.4.7_debug.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068843 Title: Android phone "Unable to connect" to rhythmbox daap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2068843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069695] Re: [SRU] OpenStack 2024.1 point release updates
** Tags added: open-2213 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069695 Title: [SRU] OpenStack 2024.1 point release updates To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2069695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069565] Re: gnome-shell crashed with SIGSEGV in meta_drm_buffer_get_width() from meta_onscreen_native_flip_crtc() from try_post_latest_swap() from meta_onscreen_native_swap_buffers_with_damage()
A bunch of ways it can happen according to the crash reports: --- kernel: INFO: task kworker/u65:1:1093 blocked for more than 491 seconds. kernel: Tainted: G W 6.8.0-35-generic #35-Ubuntu kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. gnome-shell[2744]: Failed to blit shared framebuffer: EGL failed to allocate resources for the requested operation. gnome-shell[2744]: Failed to blit shared framebuffer: EGL failed to allocate resources for the requested operation. --- gnome-shell[2856]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Argumento inválido --- (nvidia kernel crash) kernel: ---[ end trace ]--- gnome-shell[2603]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument --- gnome-shell[1862]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Das Argument ist ungültig --- 1. nouveau kernel crash 2. multiple binaries crash --- gnome-shell[2313]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument --- (nvidia kernel crash) kernel: ---[ end trace ]--- gnome-shell[5704]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB failed: Invalid argument --- gnome-shell[2939]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Argumento inválido --- gnome-shell[3678]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument --- gnome-shell[2396]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Invalid argument --- gnome-shell[3925]: Realizing HW cursor failed: Failed to allocate gbm_bo: Invalid argument gnome-shell[3925]: Failed to set hardware cursor (Failed to allocate gbm_bo: Invalid argument), using OpenGL from now on gnome-shell[3925]: drmModeRmFB: Invalid argument gnome-shell[3925]: Failed to blit shared framebuffer: EGL failed to allocate resources for the requested operation. --- gnome-shell[2800]: meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers failed: Argumento inválido --- nouveau kernel crash --- nouveau kernel crash --- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069565 Title: gnome-shell crashed with SIGSEGV in meta_drm_buffer_get_width() from meta_onscreen_native_flip_crtc() from try_post_latest_swap() from meta_onscreen_native_swap_buffers_with_damage() from cogl_onscreen_swap_buffers_with_damage() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2069565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064211] Re: /usr/bin/update-manager:AttributeError::available:start_available:refresh_cache:_get_ua_security_status
** Merge proposal linked: https://code.launchpad.net/~nteodosio/update-manager/+git/update-manager/+merge/467674 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064211 Title: /usr/bin/update- manager:AttributeError::available:start_available:refresh_cache:_get_ua_security_status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2064211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069702] [NEW] [SRU] OpenStack 2023.2 stable point releases
Public bug reported: [Impact] This release sports mostly bug-fixes and we would like to make sure all of our users have access to these improvements. The update contains the following package updates: * cinder 23.1.0 * ironic 23.0.1 * magnum 17.0.2 * manila 17.2.0 * nova 28.1.0 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. ** Affects: cloud-archive Importance: Undecided Status: Invalid ** Affects: cloud-archive/bobcat Importance: Undecided Status: New ** Affects: cinder (Ubuntu) Importance: Undecided Status: Invalid ** Affects: ironic (Ubuntu) Importance: Undecided Status: Invalid ** Affects: magnum (Ubuntu) Importance: Undecided Status: Invalid ** Affects: manila (Ubuntu) Importance: Undecided Status: Invalid ** Affects: nova (Ubuntu) Importance: Undecided Status: Invalid ** Affects: cinder (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: ironic (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: magnum (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: manila (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: nova (Ubuntu Mantic) Importance: Undecided Status: New ** Tags: open-2214 ** Description changed: [Impact] This release sports mostly bug-fixes and we would like to make sure all of our users have access to these improvements. The update contains the following package updates: - * + * cinder 23.1.0 + * ironic 23.0.1 + * magnum 17.0.2 + * manila 17.2.0 + * nova 28.1.0 + [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. ** Also affects: nova (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: nova (Ubuntu) Status: New => Invalid ** Also affects: cinder (Ubuntu) Importance: Undecided Status: New ** Changed in: cinder (Ubuntu) Status: New => Invalid ** Also affects: ironic (Ubuntu) Importance: Undecided Status: New ** Changed in: ironic (Ubuntu) Status: New => Invalid ** Also affects: manila (Ubuntu) Importance: Undecided Status: New ** Changed in: manila (Ubuntu) Status: New => Invalid ** Also affects: magnum (Ubuntu) Importance: Undecided Status: New ** Changed in: magnum (Ubuntu) Status: New => Invalid ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/bobcat Importance: Undecided Status: New ** Changed in: cloud-archive Status: New => Invalid ** Tags added: open-2214 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069702 Title: [SRU] OpenStack 2023.2 stable point releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2069702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049192] Re: Audio problem on zoom + kubuntu 23.10
Just one more comment: if I connect to my Jabra via bluetooth, then everything works fine (audio profile is "Headset Head Unit"). Connected via usb I have audio problems (profile is "analog stereo input + mono output"). Not sure how to debug further. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049192 Title: Audio problem on zoom + kubuntu 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2049192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069559] Re: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_paint_box() from st_theme_node_transition_get_paint_box()
** Bug watch added: github.com/micheleg/dash-to-dock/issues #2179 https://github.com/micheleg/dash-to-dock/issues/2179 ** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/2179 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/2069559 Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_paint_box() from st_theme_node_transition_get_paint_box() from st_widget_get_paint_volume() To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/2069559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063869] Re: Missing default cursor
** Also affects: dmz-cursor-theme (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: dmz-cursor-theme (Ubuntu Oracular) Importance: Undecided Status: Won't Fix ** Also affects: mutter (Ubuntu Oracular) Importance: Medium Assignee: Daniel van Vugt (vanvugt) Status: Fix Committed ** Changed in: mutter (Ubuntu Noble) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Noble) Status: New => Triaged ** No longer affects: dmz-cursor-theme (Ubuntu Oracular) ** No longer affects: dmz-cursor-theme (Ubuntu Noble) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063869 Title: Missing default cursor To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2063869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062377] Re: Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected
** Also affects: mutter (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Oracular) Importance: Medium Assignee: Daniel van Vugt (vanvugt) Status: Fix Committed ** Changed in: mutter (Ubuntu Noble) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Noble) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062377 Title: Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2062377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
Thanks Joris, that worked for me to. Best, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967707] Re: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached"
** Changed in: mutter (Ubuntu) Milestone: None => ubuntu-24.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967707 Title: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679429] Re: UEFI tftp configuration lookup
** Changed in: grub2 (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679429 Title: UEFI tftp configuration lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1679429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745740] Re: [Xenial] Update to kernel 4.4.0-112-generic make the system failed to boot with enabled BIOS SecureBoot mode
All kernels boot fine under SB on modern Ubuntu. I don't think major changes will be made to Xenial at this point. ** Changed in: grub2 (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Won't Fix ** Changed in: grub2 (Ubuntu Xenial) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745740 Title: [Xenial] Update to kernel 4.4.0-112-generic make the system failed to boot with enabled BIOS SecureBoot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1745740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069709] [NEW] Seahorse silently fails to sync PGP keys
Public bug reported:
In order to add OpenPGP keys to launchpad, the website guides you
through synchronizing your key with the Ubuntu key server first by using
Seahorse ("Passwords and Keys").
You can manually trigger a sync from the hamburger menu > Sync and
publish keys > Sync.
However in my Ubuntu 24.04 fresh install this step silently fails.
The journal shows: `gpg-agent[191732]: can't connect to the daemon
/usr/lib/gnupg/scdaemon: IPC connect call failed`
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: seahorse 43.0-3build2
Uname: Linux 6.9.3-060903-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 18 10:58:01 2024
InstallationDate: Installed on 2024-06-16 (2 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
SourcePackage: seahorse
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: seahorse (Ubuntu)
Importance: Undecided
Assignee: Alessandro Astone (aleasto)
Status: Triaged
** Tags: amd64 apport-bug noble wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069709
Title:
Seahorse silently fails to sync PGP keys
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/2069709/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069709] Re: Seahorse silently fails to sync PGP keys
Installing the scdaemon package solves the issue. scdaemon seems to be a mandatory dependency of gpg-agent, it should be added to the dependency chain ** Changed in: seahorse (Ubuntu) Status: New => Triaged ** Changed in: seahorse (Ubuntu) Assignee: (unassigned) => Alessandro Astone (aleasto) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069709 Title: Seahorse silently fails to sync PGP keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/2069709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924261] Re: Krusader: missing icons
Almost a year later - same issue. Would be nice to fix this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924261 Title: Krusader: missing icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krusader/+bug/1924261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069710] [NEW] ddcci-dkms FTBS with linux hwe 6.8 on jammy
Public bug reported: [Impact] /var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.c:1677:9: error: implicit declaration of function ‘strlcpy’; did you mean ‘strscpy’? [-Werror=implicit-function-declaration] 1677 | strlcpy(info->type, (outer_addr == DDCCI_DEFAULT_DEVICE_ADDR) ? "ddcci" : "ddcci-dependent", I2C_NAME_SIZE); | ^~~ | strscpy /var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.c: At top level: /var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.c:1835:27: error: ‘I2C_CLASS_DDC’ undeclared here (not in a function); did you mean ‘I2C_CLASS_SPD’? 1835 | .class = I2C_CLASS_DDC, | ^ | I2C_CLASS_SPD cc1: some warnings being treated as errors [Test case] $ sudo apt install ddcci-dkms [Fix] Backport from Noble the required changes to properly support the new 6.8 kernel ABI. [Regression potential] DDC/CI is a driver for compatible monitors and their integration into the backlight system class. We may experience graphical regressions in systems that are using this particular driver. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ddcci-dkms 0.4.1-3ubuntu3 ProcVersionSignature: User Name 6.8.0-35.35.1~22.04.1-lowlatency 6.8.4 Uname: Linux 6.8.0-35-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/vdb) Date: Tue Jun 18 09:22:45 2024 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ddcci-driver-linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ddcci-driver-linux (Ubuntu) Importance: Undecided Status: New ** Affects: ddcci-driver-linux (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images ** Also affects: ddcci-driver-linux (Ubuntu Jammy) 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/2069710 Title: ddcci-dkms FTBS with linux hwe 6.8 on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddcci-driver-linux/+bug/2069710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069599] Re: ELF package metadata uses osVersion value that might change
From the responses on the systemd-devel list my take is: Do not set osVersion. The osVersion does not reflect the version of the Ubuntu release that package is shipped by, because it can be part of multiple releases without rebuild. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069599 Title: ELF package metadata uses osVersion value that might change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2069599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069712] [NEW] wrong key mapping when two languages are installed
Public bug reported: OS: ubuntu 22.04, with both Hebrew and English installed. Currently English is selected. In Pycharm editor: When pressing "CTRL /", the "/" key is interpreted as it was in Hebrew: "." I opened a bug in Jetbrain and we followed it until deciding it is an OS bug. see the report at https://youtrack.jetbrains.com/issue/IJPL-155829#focus=Comments-27-9905012.0-0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: keyboard-configuration 1.205ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-35.35~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 18 12:29:28 2024 InstallationDate: Installed on 2024-04-01 (78 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069712 Title: wrong key mapping when two languages are installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2069712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069559] Re: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_paint_box() from st_theme_node_transition_get_paint_box()
** Changed in: dash-to-dock Status: Unknown => 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/2069559 Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_paint_box() from st_theme_node_transition_get_paint_box() from st_widget_get_paint_volume() To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/2069559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056578] Re: [SRU - Noble] Tor Browser - keyboard not functioning
I did set up two (clean installation, fully updated) 24.04 VMs: one with noble-proposed disabled and the other one with noble-proposed enabled. Installed latest torbrowser-launcher on both of them. - On the VM without noble-proposed enabled and using torbrowser-launcher version 0.3.7-1build2, the keyboard input in Tor Browser does not work. - On the VM with noble-proposed enabled and using torbrowser-launcher version 0.3.7-1ubuntu1, the keyboard input in Tor Browser *works fine*. In other words, the 0.3.7-1ubuntu1 build fixes the issue. Thanks! ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056578 Title: [SRU - Noble] Tor Browser - keyboard not functioning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/2056578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052575] Re: [SRU] Update firmware to support autofocus
I have confirmed with the uploaders that the package has been verified. Releasing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052575 Title: [SRU] Update firmware to support autofocus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-xilinx-ap1302/+bug/2052575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052575] Re: [SRU] Update firmware to support autofocus
This bug was fixed in the package linux-firmware-xilinx-ap1302 - 1:2.0-0ubuntu1~23.10.1 --- linux-firmware-xilinx-ap1302 (1:2.0-0ubuntu1~23.10.1) mantic; urgency=medium * Backport 1:2.0-0ubuntu1 to mantic (tag v2.0) (LP: #2052575) -- Pallav Joshi Tue, 09 Apr 2024 14:58:58 -0700 ** Changed in: linux-firmware-xilinx-ap1302 (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052575 Title: [SRU] Update firmware to support autofocus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-xilinx-ap1302/+bug/2052575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052575] Re: [SRU] Update firmware to support autofocus
This bug was fixed in the package linux-firmware-xilinx-ap1302 - 1:2.0-0ubuntu1~22.04.1 --- linux-firmware-xilinx-ap1302 (1:2.0-0ubuntu1~22.04.1) jammy; urgency=medium * Backport 1:2.0-0ubuntu1 to jammy (tag v2.0) (LP: #2052575) -- Pallav Joshi Thu, 07 Mar 2024 13:46:23 -0800 ** Changed in: linux-firmware-xilinx-ap1302 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052575 Title: [SRU] Update firmware to support autofocus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-xilinx-ap1302/+bug/2052575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052575] Update Released
The verification of the Stable Release Update for linux-firmware-xilinx- ap1302 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052575 Title: [SRU] Update firmware to support autofocus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-xilinx-ap1302/+bug/2052575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067125] Re: CVE-2024-21096 et al affects MariaDB in Ubuntu
Updated branch links to have correct (new) naming scheme. Thanks Dave for triggering autopkgtests. Back in January 2024 I was still able to do it myself (https://bugs.launchpad.net/ubuntu/+source/mariadb/+bug/2045452/comments/18), I wonder what changed. I now checked https://autopkgtest.ubuntu.com/results/autopkgtest-mantic- mysql-ubuntu- mariadb-10.11/mantic/amd64/m/mariadb/20240617_174047_0dd5c@/log.gz that autopkgtest passed: 1478s configuration-tracing PASS 1478s smokePASS 1478s upstream PASS This is a surprising large amount of work to do a simple security upload, I need to think ways of automating it. It would be by far easiest if Salsa-CI supported Ubuntu (https://salsa.debian.org/salsa-ci- team/pipeline/-/issues/327). ** Bug watch added: salsa.debian.org/salsa-ci-team/pipeline/-/issues #327 https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/327 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067125 Title: CVE-2024-21096 et al affects MariaDB in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb/+bug/2067125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065848] Re: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount.
Hi Mitchell, if you are not using the "nfs_shared_infodir" parameter, removing the init script is sufficent. However, if the parameter is used an a custom place is provided do_unbind will make an uncecked umount of /var/lib/nfs. Any issues there will not return an error. This is independent of the EXEC_Mode. So you have this potential issue even with systemd and a removed /etc/init.d/nfs-kernel-server script. Best wishes Jacob -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065848 Title: An ocf:heartbeat:nfsserver resource's stop operation succeeded despite the /var/lib/nfs filesystem failing to unmount. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/2065848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069714] [NEW] therion: 6.2.1-1build1 FTBFS (vtk9 9.3?)
Public bug reported: The therion package fails to builds. It might be related to vtk9 9.3 since it started with this transition but the issue is a missing font file (logo10 at 600dpi) for latex which is not completely consistent with that. Since this file is required only if other font files are not found, we can add a depends on texlive-fonts-recommended and skip the issue. ** Affects: therion (Ubuntu) Importance: High Assignee: Adrien Nader (adrien) Status: 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/2069714 Title: therion: 6.2.1-1build1 FTBFS (vtk9 9.3?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/therion/+bug/2069714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874272] Re: Stage "searching for obsolete software" takes a very long time (30 minutes)
I am also seeing this on two separate systems, while upgrading from 22.04 to 24.04. On the first system, with less packages installed the process took about 2 hours. On the second system, based on the current progress I estimate that it will take around 14 hours. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874272 Title: Stage "searching for obsolete software" takes a very long time (30 minutes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1874272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068058] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (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/2068058 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2068058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069715] [NEW] DRBG initialization failed on some AMD EPYC series CPU and lead to kernel panic
Public bug reported: BugLink: https://bugs.launchpad.net/bugs/2069715 [Impact] Install Focal with FIPS enabled on AMD EPYC 7262 8-Core Processor, kernel panic happens during boot: [3.430477] ima: Allocated hash algorithm: sha1 [3.433358] ima: No architecture policies found [3.435785] evm: Initialising EVM extended attributes: [3.438271] evm: security.selinux [3.440265] evm: security.SMACK64 [3.442532] evm: security.SMACK64EXEC [3.444753] evm: security.SMACK64TRANSMUTE [3.446900] evm: security.SMACK64MMAP [3.448912] evm: security.apparmor [3.452277] evm: security.ima [3.455549] evm: security.capability [3.457537] evm: HMAC attrs: 0x1 [3.461049] PM: Magic number: 12:438:677 [3.463502] rtc_cmos 00:03: setting system clock to 2024-06-18T09:40:59 UTC (1718703659) [3.467750] Kernel panic - not syncing: random: Failed to reset DRBG (drbg_nopr_ctr_aes256): -2 [3.471060] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.4.0-1100-fips #110-Ubuntu [3.474288] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009)/LXD, BIOS 0.0.0 02/06/2015 [3.478191] Call Trace: [3.480175] dump_stack+0x6d/0x8b [3.482652] panic+0x114/0x2f6 [3.490069] fips_drbg_init+0xa7/0xbd [3.492169] ? chr_dev_init+0x148/0x148 [3.494330] do_one_initcall+0x4a/0x200 [3.496396] kernel_init_freeable+0x1e6/0x289 [3.498967] ? rest_init+0xb0/0xb0 [3.500965] kernel_init+0xe/0x110 [3.502983] ret_from_fork+0x35/0x40 [3.505305] Kernel Offset: 0x35c0 from 0x8100 (relocation range: 0x8000-0xbfff) [3.509544] ACPI MEMORY or I/O RESET_REG. It fails to initialize DRBG, this issue doesn't happen on Intel CPU, only on some AMD EPYC series CPU. Also Jammy with FIPS enabled doesn't have this issue. [Fix] It's been fixed by this upstream commit: commit 552d03a223eda3df84526ab2c1f4d82e15eaee7a Author: Stephan Mller Date: Sun Nov 21 15:14:20 2021 +0100 crypto: jitter - consider 32 LSB for APT The APT compares the current time stamp with a pre-set value. The current code only considered the 4 LSB only. Yet, after reviews by mathematicians of the user space Jitter RNG version >= 3.1.0, it was concluded that the APT can be calculated on the 32 LSB of the time delta. Thi change is applied to the kernel. This fixes a bug where an AMD EPYC fails this test as its RDTSC value contains zeros in the LSB. The most appropriate fix would have been to apply a GCD calculation and divide the time stamp by the GCD. Yet, this is a significant code change that will be considered for a future update. Note, tests showed that constantly the GCD always was 32 on these systems, i.e. the 5 LSB were always zero (thus failing the APT since it only considered the 4 LSB for its calculation). Signed-off-by: Stephan Mueller Signed-off-by: Herbert Xu [Testcase] On AMD EPYC 7262 8-Core Processor, create a VM and enable FIPS can also reproduce the issue. I've backport the upstream commit to Focal FIPS kernel (5.4.0-1100.110-fips), the DRBG init failed message is gone: [3.267954] rtc_cmos 00:03: setting system clock to 2024-06-18T06:58:53 UTC (1718693933) [3.275683] random: random: DRBG (drbg_nopr_ctr_aes256) initialized! [3.279309] md: Waiting for all devices to be available before autodetect [Where problems could occur] This commit considers AMD EPYC CPU's RDTSC contains zero in LSB, this won't affect other cases. [Other Info] Users also reported the issue here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045322 https://askubuntu.com/questions/1509977/fips-kernel-panics-with-failed-to-reset-drbg-during-boot ** Affects: linux (Ubuntu) Importance: Undecided Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: gerald.yang (gerald-yang-tw) Status: In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu) Status: New => In Progress ** Description changed: + BugLink: https://bugs.launchpad.net/bugs/2069715 + [Impact] Install Focal with FIPS enabled on AMD EPYC 7262 8-Core Processor, kernel panic happens during boot: [3.430477] ima: Allocated hash algorithm: sha1 [3.433358] ima: No architecture policies found [3.435785] evm: Initialising EVM extended attributes: [3.438271] evm: security.selinux [3.440265] evm: security.SMACK64 [3.442532] evm: security.SMACK64EXEC [3.444753] evm: security.SMACK64TRANSMUTE [3.446900] evm: security.SMACK64MMAP [3.448912] evm: security.apparmor [3.452277] evm: security.ima [3.455549] evm: security.capability [3.457537] evm: HMAC attrs: 0x1 [3.461049] PM: Magic number: 12:438:677 [3.463502] rtc_cmos 00:03: setting system clock to 2024
[Bug 2069717] [NEW] Upgrading from Ubuntu 23.10 to 24.04 fails on DisplayLink Module / evdi
Public bug reported: During upgrade using `sudo do-realease-upgrade` Upgrade failed and system became unbootable. Booting into recovery mode discovered that kernel make fails (linux- image-6.8.0-35-generic) for module evdi which is the Dell DisplayLink Driver Solution: 1) Boot into recovery mode 2) Follow these instructions to remove module evdi https://askubuntu.com/questions/1467898/dkms-errors-when-updating-upgrading-ubuntu/1468704#1468704 3) dpkg --configure -a 4) sudo apt update && sudo apt upgrade The system then recovered although the DisplayLink driver was no longer present As the Dell XPS range are officially covered laptops (not sure if by Dell or Ubuntu) I thought this may be useful to resolve Further suggestion: removing the evdi module automatically during upgrade would at least ensure this issue does not stop the upgrade completing. DisplayLink can be reinstalled by those who need it ** Affects: 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/2069717 Title: Upgrading from Ubuntu 23.10 to 24.04 fails on DisplayLink Module / evdi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2069717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069709] Re: Seahorse silently fails to sync PGP keys
Do you have some custom config maybe in ~/.gnupg? Does it behave differently with a new user account on the same machine. scdaemon is used for smartcard authentification, it shouldn't be needed in a standard setup Note that scdaemon is in universe so we would need to get it promoted to main first if we wanted to add a depends or recommends (which would be easy enough since it's only a binary, the source it's built from is gnupg2 which is already in main) $ rmadison -s oracular scdaemon scdaemon | 2.4.4-2ubuntu17 | oracular/universe | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x extra reference to the MIR process on https://github.com/canonical/ubuntu-mir -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069709 Title: Seahorse silently fails to sync PGP keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/2069709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043820] Re: Unable to contact snap store on Xubuntu from Jammy to Noble
Hi Gabriel, Thanks for your proposed solution. While this may be fine for end users to do so, let me highlight some things people should know if they read this: * This is a manual solution that could be applied to a system, but please take good care in checking that removing `firefox` doesn't remove your whole desktop, since some metapackages like `ubuntu-desktop` seems to depend on it. More generally, this solution is more a hack that might work for some people, but you better know what you're doing. * Adding the Mozilla third-party repository may also be fine, but is not officially supported. This will install Firefox as a native package, while the official supported way on Ubuntu is with the snap. That mostly means that this is way less tested, and you might have other unknown issues there. You also need to evaluate the trust you put into that third party repo. * This bug was opened because our automated testing is broken, so the root-cause needs to be fixed anyway. This is not really an end-user support thread. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043820 Title: Unable to contact snap store on Xubuntu from Jammy to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2043820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069720] [NEW] Summary: "Unexpected behavior when renaming items on the desktop"
Public bug reported: Steps to reproduce: Right-click on an item on the desktop and select "Rename". After renaming, click the left or right mouse button. Notice that clicking left performs an "Enter" action, and clicking right moves the cursor left or right. Expected behavior: Clicking left or right should not perform "Enter" or move the cursor. Actual behavior: Clicking left performs "Enter", and clicking right moves the cursor. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5.1 ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4 Uname: Linux 6.8.0-35-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 18 15:46:10 2024 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-06-07 (11 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069720 Title: Summary: "Unexpected behavior when renaming items on the desktop" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2069720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069304] Re: Autopkgtests failing due to new git 2.45
** Changed in: git (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/2069304 Title: Autopkgtests failing due to new git 2.45 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git/+bug/2069304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069293] Re: Autopkgtests failing due to new git 2.45
** Changed in: git (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/2069293 Title: Autopkgtests failing due to new git 2.45 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git/+bug/2069293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069714] Re: therion: 6.2.1-1build1 FTBFS (vtk9 9.3?)
** Bug watch added: Debian Bug tracker #1072828 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072828 ** Also affects: texlive-bin (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072828 Importance: Unknown Status: Unknown ** Summary changed: - therion: 6.2.1-1build1 FTBFS (vtk9 9.3?) + therion: 6.2.1-1build1 FTBFS with texlive-binaries 2024.20240313.70630+ds-2 ** Description changed: - The therion package fails to builds. It might be related to vtk9 9.3 - since it started with this transition but the issue is a missing font - file (logo10 at 600dpi) for latex which is not completely consistent - with that. Since this file is required only if other font files are not - found, we can add a depends on texlive-fonts-recommended and skip the - issue. + The therion package fails to builds. mktexpk seems to not work and is + required sincea font file for latex (logo10 at 600dpi) is missing. Since + this file is required only if other font files are not found, we can add + a depends on texlive-fonts-recommended and skip the issue it seems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069714 Title: therion: 6.2.1-1build1 FTBFS with texlive-binaries 2024.20240313.70630+ds-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/therion/+bug/2069714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069721] [NEW] New files or directories not visible until refreshing Ubuntu 24.04 LTS
Public bug reported: Copy and paste it anywhere on the system. Notice that the new item does not appear until you press the F5 button. Expected behavior: The new file or directory should appear immediately after creation or pasting. Actual behavior: The new file or directory only appears after pressing F5 to refresh the view. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4 Uname: Linux 6.8.0-35-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 18 15:53:47 2024 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'" b'org.gnome.nautilus.preferences' b'fts-enabled' b'false' b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(360, 380)' b'org.gnome.nautilus.window-state' b'maximized' b'true' SourcePackage: nautilus UpgradeStatus: Upgraded to noble on 2024-06-07 (11 days ago) usr_lib_nautilus: file-roller 44.1-1 nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069721 Title: New files or directories not visible until refreshing Ubuntu 24.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2069721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069714] Re: therion: 6.2.1-1build1 FTBFS with texlive-binaries 2024.20240313.70630+ds-2
** Merge proposal linked: https://code.launchpad.net/~adrien/ubuntu/+source/therion/+git/therion/+merge/467694 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069714 Title: therion: 6.2.1-1build1 FTBFS with texlive-binaries 2024.20240313.70630+ds-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/therion/+bug/2069714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067429] Re: Address out-of-bounds issue when using TPM SPI interface
This bug is awaiting verification that the linux- nvidia-6.8/6.8.0-1008.8~22.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-jammy-linux- nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067429 Title: Address out-of-bounds issue when using TPM SPI interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2067429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067106] Re: Blacklist coresight_etm4x
This bug is awaiting verification that the linux- nvidia-6.8/6.8.0-1008.8~22.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-jammy-linux- nvidia-6.8' to 'verification-done-jammy-linux-nvidia-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- nvidia-6.8' to 'verification-failed-jammy-linux-nvidia-6.8'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-6.8-v2 verification-needed-jammy-linux-nvidia-6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067106 Title: Blacklist coresight_etm4x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2067106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
