[Bug 2064450] Re: Merge qemu from Debian unstable for oracular
** Changed in: qemu (Ubuntu) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064450 Title: Merge qemu from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2064450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064469] Re: Merge sssd from Debian unstable for oracular
** Changed in: sssd (Ubuntu) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064469 Title: Merge sssd from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2064469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064434] Re: Merge openldap from Debian unstable for oracular
** Changed in: openldap (Ubuntu) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064434 Title: Merge openldap from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2064434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064457] Re: Merge rsync from Debian unstable for oracular
** Changed in: rsync (Ubuntu) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064457 Title: Merge rsync from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2064457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064096] Re: rsyslog service timeout on noble numbat
Andreas and I spent some time this afternoon investigating this issue. Here are our findings. First, we noticed that the paths being reported by apparmor on dmesg appear to be relative to /run. This is just an impression, though: I believe that, for some reason, apparmor/systemd/something-else is actually seeing the paths as "/systemd/notify" instead of "/run/systemd/notify". Therefore, we decided to try to list those paths inside the apparmor profile, like: /systemd/journal/dev-log rwkl, /systemd/notify rwkl, Note that we're using "rwkl" just because we don't want to deal with limiting the scope of each access. After adding these paths to /etc/apparmor.d/usr.sbin.rsyslogd and reloading the profile, the service can finally be (re)started. This indicates that there's a discrepancy between the paths seeing by apparmor/systemd/Linux and those seeing by the userspace application. With that in mind, our next idea was to try to use "systemd-run" to mimic what's happening with rsyslogd. This could help us determine which component is problematic, but unfortunately we were unable to make the failure happen. We tried many combinations of commands; some of them are listed below: # Try to "ls" the notify socket using different paths systemd-run -p AppArmorProfile=rsyslogd ls /run/systemd/notify systemd-run -p AppArmorProfile=rsyslogd ls /systemd/notify # Likewise, but running the command using the syslog user systemd-run --uid 102 -p AppArmorProfile=rsyslogd ls /run/systemd/notify systemd-run --uid 102 -p AppArmorProfile=rsyslogd ls /systemd/notify Strangely, "ls" was able to properly list the contents of /run/systemd/notify on both cases (which it shouldn't, because the apparmor profile doesn't allow it). It also reported that "/systemd/notify", which is correct but unexpected (because we thought that systemd might be the problematic component which doesn't use "/run" in the paths). We also double checked and confirmed that the processes started by "systemd-run" have "systemd" as their parent, so in theory we should have seen the same problem here. There is also the fact that these file accesses are being denied even when the apparmor profile is running in complain mode. AFAIU, this shouldn't happen. Unless apparmor is affecting the path resolution that happens when the service tries to connect to the socket, effectively mangling the final path... but that would be very weird, I believe. Either way, it is unclear: 1) Why we're seeing these "partial" paths in the logs. 2) Why these accesses are being denied even when the apparmor profile is in complain mode. 3) Why "systemd-run" can't seem to reproduce the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: rsyslog service timeout on noble numbat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2064096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061740] Re: update to apache2_2.4.52-1ubuntu4.9_amd64 causes website to respond with 301 redirect to itself
Thank you for taking the time to file a bug report. I installed the latest version of apache2 (Jammy) here and could not reproduce the issue. Could you please provide a minimal reproducer so that we can determine if this is indeed a problem with the package? If you could, please provide the configuration files for apache2 that you are using (make sure to remove any confidential/personal information from them). Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'. However, if you believe that this is really a bug in Ubuntu, then we would be grateful if you would provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: apache2 (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/2061740 Title: update to apache2_2.4.52-1ubuntu4.9_amd64 causes website to respond with 301 redirect to itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/2061740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062013] [NEW] RM: telegraf from Noble; no longer maintained in Ubuntu
Public bug reported: Hi, Telegraf was added in Ubuntu back in 2020 as part of the LMA (Logging, Monitoring and Alert) effort, but priorities have changed since then and the package is no longer maintained in the distribution. Telegraf is also one of those "hard" packages to maintain because it requires bundling of everything it depends on, which makes things very difficult for the Security team, for example. The package does not have any reverse dependencies. ** Affects: telegraf (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/2062013 Title: RM: telegraf from Noble; no longer maintained in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telegraf/+bug/2062013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061911] Re: check if new addresses for b.root-servers.net is needed
Doesn't https://bugs.launchpad.net/ubuntu/+source/dns-root- data/+bug/2045297 already address this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061911 Title: check if new addresses for b.root-servers.net is needed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/2061911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"
Hi Mauricio, Thanks for the detailed explanations, as usual. I took some time here to read your patch. It took me down the rabbit hole and I did some archaeology to find out what these "inhibit*" pointers are about. It was fun; I learned that they were introduced back in 2012 as a means to allow drivers to signal libvirt when to inhibit shutdown because there are still VMs around. But I digress. I liked your approach here and indeed, it seems simpler than the other one (although the initial approach was also simple to grasp and elegant; too bad it didn't work for all cases). My only comment/question here would be this: the changes to qemuProcessReconnect mention that they're being done in order to prevent the XML "corruption" when there's a shutdown detected during initialization, but (and I may be wrong here) it seems to me that this new code path could be reached even after the initialization, couldn't it? Either way, this is not really important and doesn't affect the patch (aside from the possible amends to the comments being added), and it's OK if you don't know the answer, too. My other source of "concern" here was the reference handling for the new pointer, but I couldn't find any potential problems with what you did. Worst case scenario (i.e., if we fail to consider a code path), we will have a "memory leak" during shutdown, which is not the end of the world. The lock/unlock dance is also simple and trivially verifiable. Otherwise, the patch LGTM and I'm satisfied with the testing you did. Feel free to go ahead and upload it. Thanks again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059272 Title: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2059272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2014964] Re: kea does not manage exported shared library symbols visibility
Still no further activity on the upstream bug, apparently. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2014964 Title: kea does not manage exported shared library symbols visibility To manage notifications about this bug go to: https://bugs.launchpad.net/kea/+bug/2014964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945774] Re: openssl: breaks ssl-cert installation: 8022CB35777F0000:error:1200007A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom
This is not a bug in ssl-cert. It's a bug in libapache2-mod-auth- mellon, more specifically in the way it configures openssl to generate its certificate. From /usr/sbin/mellon_create_metadata: cat >"$TEMPLATEFILE" < Triaged ** Changed in: ssl-cert (Ubuntu Jammy) Status: Confirmed => Fix Released ** Changed in: hplip (Ubuntu Jammy) 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/1945774 Title: openssl: breaks ssl-cert installation: 8022CB35777F:error:127A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom To manage notifications about this bug go to: https://bugs.launchpad.net/mod-auth-mellon/+bug/1945774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945774] Re: openssl: breaks ssl-cert installation: 8022CB35777F0000:error:1200007A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom
Upstream fix: https://github.com/latchset/mod_auth_mellon/commit/c6102de6ff651bf763400cb59202d9abe384f615 ** Bug watch added: github.com/latchset/mod_auth_mellon/issues #105 https://github.com/latchset/mod_auth_mellon/issues/105 ** Also affects: mod-auth-mellon via https://github.com/latchset/mod_auth_mellon/issues/105 Importance: Unknown Status: Unknown ** Tags added: bitesize -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945774 Title: openssl: breaks ssl-cert installation: 8022CB35777F:error:127A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom To manage notifications about this bug go to: https://bugs.launchpad.net/mod-auth-mellon/+bug/1945774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040470] Re: Upstream microrelease of squid 5.9
** Changed in: squid (Ubuntu Jammy) Status: Triaged => 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/2040470 Title: Upstream microrelease of squid 5.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/2040470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors
Performing the verification on Jammy. First, verifying that we can reproduce the problem. # apt policy qemu-system-x86 qemu-system-x86: Installed: 1:6.2+dfsg-2ubuntu6.18 Candidate: 1:6.2+dfsg-2ubuntu6.18 Version table: *** 1:6.2+dfsg-2ubuntu6.18 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:6.2+dfsg-2ubuntu6.16 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 1:6.2+dfsg-2ubuntu6 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages # qemu-system-x86_64 -M pc-q35-jammy,accel=kvm,kernel-irqchip=split -device intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm -net none -m 4096M -nographic -kernel /boot/vmlinuz -initrd /boot/initrd.img -chardev stdio,mux=on,id=char0 -mon chardev=char0,mode=readline -serial chardev:char0 -append "console=ttyS0" qemu-system-x86_64: Invalid SMP CPUs 300. The max CPUs supported by machine 'pc-q35-jammy' is 288 Now, updating the package and verifying that the version from -proposed fixes the issue: # apt policy qemu-system-x86 qemu-system-x86: Installed: 1:6.2+dfsg-2ubuntu6.19 Candidate: 1:6.2+dfsg-2ubuntu6.19 Version table: *** 1:6.2+dfsg-2ubuntu6.19 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:6.2+dfsg-2ubuntu6.18 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 1:6.2+dfsg-2ubuntu6.16 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 1:6.2+dfsg-2ubuntu6 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages # qemu-system-x86_64 -M pc-q35-jammy-maxcpus,accel=kvm,kernel-irqchip=split -device intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm -net none -m 4096M -nographic -kernel /boot/vmlinuz -initrd /boot/initrd.img -chardev stdio,mux=on,id=char0 -mon chardev=char0,mode=readline -serial chardev:char0 -append "console=ttyS0" ... This concludes the verification on Jammy. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2012763 Title: qemu-system-amd64 max cpus is too low for latest processors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2012763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058023] Re: New versions of amavis with security fixes
Hello Dominic, Thanks for reporting a bug. Noble is currently in Feature Freeze, which means that only bug fixes can be uploaded to the archive. Based on the release notes for version 2.13.1 of amavisd, there is at least one new feature being introduced in this release, which makes it unsuitable to be backported right now. The good news is that amavisd-new is officially supported by Canonical and therefore the Security team will be able to upload any security fixes that come out. The same applies for the versions in Jammy and Mantic, by the way. I will make sure to bring this bug to their attention just in case. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2058023 Title: New versions of amavis with security fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/2058023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060752] Re: package samba-common 2:4.15.13+dfsg-0ubuntu1.6 failed to install/upgrade: el subproceso instalado paquete samba-common script post-installation devolvió el código de salida de error
Thank you for taking the time to file a bug report. This sounds like a local configuration problem. If you believe this is a bug in the package, could you please provide more technical details about what is happening? Log files from Samba, for example, would help with the diagnostic. I see that you also posted a DpkgTerminalLog.txt file, which contains the following message: root@alpfa-HP:/# apt-get install samba E: No se pudo obtener un bloqueo /var/lib/dpkg/lock-frontend. Lo mantiene el proceso 4954 (dpkg) N: Tenga en cuenta que eliminar el archivo de bloqueo no es una solución y puede dañar su sistema. E: No se pudo obtener el bloqueo de la interfaz dpkg (/var/lib/dpkg/lock-frontend). ¿Hay otro proceso utilizándolo? root@alpfa-HP:/# exit exit dpkg: error al procesar el paquete samba-common (--configure): el subproceso instalado paquete samba-common script post-installation devolvió el código de salida de error 1 Configurando libwbclient0:amd64 (2:4.15.13+dfsg-0ubuntu1.6) ... This indicates that there is a bigger problem at play here; maybe some leftover lockfile from an unsuccessful apt-get invocation? Either way, it doesn't seem to be related to Samba itself. Since there is not enough information in your report to begin triage or to differentiate between a local configuration problem and a bug in Ubuntu, I am marking this bug as "Incomplete". We would be grateful if you would: provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: samba (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/2060752 Title: package samba-common 2:4.15.13+dfsg-0ubuntu1.6 failed to install/upgrade: el subproceso instalado paquete samba-common script post-installation devolvió el código de salida de error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/2060752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060826] Re: hxtools ftbfs in Noble
libhx doesn't FTBFS on Noble. Closing this as Invalid. ** Changed in: libhx (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/2060826 Title: hxtools ftbfs in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhx/+bug/2060826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061005] Re: Merge qemu from Debian unstable for noble
** Merge proposal linked: https://code.launchpad.net/~sergiodj/ubuntu/+source/qemu/+git/qemu/+merge/464242 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061005 Title: Merge qemu from Debian unstable for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2061005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061005] Re: Merge qemu from Debian unstable for noble
I will use this bug to track the merge of 8.2.2. QEMU 8.2.3 will be released after the planned Final Freeze, so it may not be possible to merge it after all. ** Changed in: qemu (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061005 Title: Merge qemu from Debian unstable for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2061005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048517] Re: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU
Hello Giuseppe, Thank you. I went ahead and backported the necessary patches. In total, I had to backport the following upstream commits: fb00aa61267c8b9c57a2d1a1fa1e336d02e3bcd1 d7c72735f618a7ee27ee109d8b1468193734606a cca0a000d06f897411a8af4402e5d0522bbe450b I uploaded a version of QEMU with the patches to: https://launchpad.net/~sergiodj/+archive/ubuntu/qemu/+packages The version is 1:4.2-3ubuntu6.29~ppa1. Could you take it for a spin, please? I'm interested in seeing the results of the scenarios suggested by Jan (namely, migrating VMs between hosts that have differing states for XSAVES). Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048517 Title: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2048517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061005] [NEW] Merge qemu from Debian unstable for noble
Public bug reported: QEMU 8.2.3 will be released on 2024-04-22. I will merge it into Noble. ** Affects: qemu (Ubuntu) Importance: High Assignee: Sergio Durigan Junior (sergiodj) Status: New ** Tags: needs-merge upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061005 Title: Merge qemu from Debian unstable for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2061005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040470] Re: Upstream microrelease of squid 5.9
** Description changed: This bug tracks the following MRE updates for the Squid package: Jammy (22.04): 5.9 This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates. [Upstream changes] http://www.squid-cache.org/Versions/v5/ChangeLog.html (Jammy: 5.7..5.9) The two releases that we are MRE'ing here (5.8 and 5.9) do not contain major/noticeable changes per se. There are quite a few bugfixes, some of them generic enough to benefit Ubuntu users, others specifically aimed at problems we don't experience (like LLVM-build fixes). A few noteworthy bugfixes have been added to the d/changelog entry. [Test Plan] The proposed changes were applied in the following PPA: https://launchpad.net/~sergiodj/+archive/ubuntu/squid/+packages Build logs can be found for the builds in the PPA linked above. Here are the amd64 one: - https://launchpadlibrarian.net/722976147/buildlog_ubuntu-jammy- - amd64.squid_5.9-0ubuntu0.22.04.1~ppa1_BUILDING.txt.gz + https://launchpadlibrarian.net/724125399/buildlog_ubuntu-jammy- + amd64.squid_5.9-0ubuntu0.22.04.1~ppa3_BUILDING.txt.gz All tests are passing during build time, as shown in the build log (builds would fail otherwise, see LP: #2004050). TODO: add results of local autopkgtest run against all the new Squid versions being uploaded here [Regression Potential] Upstream tests are always executed during build-time. Failures would prevent builds from succeeding. Squid does not have many reverse dependencies. However, any upgrade is a risk to introduce breakage to other packages. Whenever a regression occurs in autopkgtests, we will investigate and provide fixes. TODO: consider any other regression potential specific to the version being updated and list them here if any. [Other Info] No CVEs are being addressed this time. Therefore, this should go through the updates pockets. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040470 Title: Upstream microrelease of squid 5.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/2040470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936449] Re: [SRU] numptyphysics segfault on startup on XUb 21.04
Thanks for the fix. Uploaded to Focal. ** Changed in: numptyphysics (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: numptyphysics (Ubuntu Focal) Assignee: (unassigned) => Sudip Mukherjee (sudipmuk) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936449 Title: [SRU] numptyphysics segfault on startup on XUb 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/numptyphysics/+bug/1936449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892558] Re: [SRU] binhex always segfaults
Thank you for the patch. Uploaded to Focal. ** Changed in: macutils (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: macutils (Ubuntu Focal) Assignee: (unassigned) => Sudip Mukherjee (sudipmuk) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892558 Title: [SRU] binhex always segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/macutils/+bug/1892558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040470] Re: Upstream microrelease of squid 5.9
** Description changed: This bug tracks the following MRE updates for the Squid package: Jammy (22.04): 5.9 This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates. [Upstream changes] http://www.squid-cache.org/Versions/v5/ChangeLog.html (Jammy: 5.7..5.9) - TODO: List the major changes introduced in this release + The two releases that we are MRE'ing here (5.8 and 5.9) do not contain + major/noticeable changes per se. There are quite a few bugfixes, some + of them generic enough to benefit Ubuntu users, others specifically + aimed at problems we don't experience (like LLVM-build fixes). A few + noteworthy bugfixes have been added to the d/changelog entry. [Test Plan] The proposed changes were applied in the following PPA: https://launchpad.net/~sergiodj/+archive/ubuntu/squid/+packages Build logs can be found for the builds in the PPA linked above. Here are the amd64 one: https://launchpadlibrarian.net/722976147/buildlog_ubuntu-jammy- amd64.squid_5.9-0ubuntu0.22.04.1~ppa1_BUILDING.txt.gz All tests are passing during build time, as shown in the build log (builds would fail otherwise, see LP: #2004050). TODO: add results of local autopkgtest run against all the new Squid versions being uploaded here [Regression Potential] Upstream tests are always executed during build-time. Failures would prevent builds from succeeding. Squid does not have many reverse dependencies. However, any upgrade is a risk to introduce breakage to other packages. Whenever a regression occurs in autopkgtests, we will investigate and provide fixes. TODO: consider any other regression potential specific to the version being updated and list them here if any. [Other Info] No CVEs are being addressed this time. Therefore, this should go through the updates pockets. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040470 Title: Upstream microrelease of squid 5.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/2040470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040470] Re: Upstream microrelease of squid 5.9
** Description changed: This bug tracks the following MRE updates for the Squid package: Jammy (22.04): 5.9 This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates. [Upstream changes] http://www.squid-cache.org/Versions/v5/ChangeLog.html (Jammy: 5.7..5.9) TODO: List the major changes introduced in this release [Test Plan] - TODO: link the build log containing all tests being executed + The proposed changes were applied in the following PPA: + https://launchpad.net/~sergiodj/+archive/ubuntu/squid/+packages - TODO: All tests are passing during build time, as shown in the build log + Build logs can be found for the builds in the PPA linked above. Here are + the amd64 one: + + https://launchpadlibrarian.net/722976147/buildlog_ubuntu-jammy- + amd64.squid_5.9-0ubuntu0.22.04.1~ppa1_BUILDING.txt.gz + + All tests are passing during build time, as shown in the build log (builds would fail otherwise, see LP: #2004050). TODO: add results of local autopkgtest run against all the new Squid versions being uploaded here [Regression Potential] Upstream tests are always executed during build-time. Failures would prevent builds from succeeding. Squid does not have many reverse dependencies. However, any upgrade is a risk to introduce breakage to other packages. Whenever a regression occurs in autopkgtests, we will investigate and provide fixes. TODO: consider any other regression potential specific to the version being updated and list them here if any. [Other Info] - TODO-A: No CVEs are being addressed this time. Therefore, this should go - through the updates pockets. - - TODO-B: CVEs TBD are being addressed by these updates. Therefore, this - update should go through the security pocket. - - TODO: list previous MREs for this package, if any. + No CVEs are being addressed this time. Therefore, this should go through + the updates pockets. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040470 Title: Upstream microrelease of squid 5.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/2040470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040470] Re: Upstream microrelease of squid 5.9
** Merge proposal linked: https://code.launchpad.net/~sergiodj/ubuntu/+source/squid/+git/squid/+merge/464045 ** Changed in: squid (Ubuntu Jammy) 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/2040470 Title: Upstream microrelease of squid 5.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/2040470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040470] Re: Upstream microrelease of squid 5.9
Ah, got it. I've added "of squid" in the title now, should read better on Pinot. Thanks! ** Summary changed: - Upstream microrelease 5.9 + Upstream microrelease of squid 5.9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040470 Title: Upstream microrelease of squid 5.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/2040470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048517] Re: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU
** Changed in: qemu (Ubuntu) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) ** Tags added: server-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048517 Title: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2048517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040470] Re: Upstream microrelease 5.9
Hi Bryce, I'm following the same title pattern as established by Athos, which I think is better in this case. Just leaving the explanation here :-). ** Summary changed: - Upstream microrelease of squid 5.9 for noble + Upstream microrelease 5.9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040470 Title: Upstream microrelease 5.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/2040470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055776] Re: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM.
I talked to Marc to understand whether the security team had any plans
to "fix" this problem, and he raised a valid point: from his perspective
(and the Security team's as well, I gather), this is not a bug because
we have two services trying to listen on the same port. The "fix" here
is to adjust the local configuration, as mentioned in the comments
above.
I'm reverting this bug's state to Invalid, then.
** Changed in: dnsmasq (Ubuntu)
Assignee: Sergio Durigan Junior (sergiodj) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055776
Title:
After updating ubuntu, the network to which the subnet address is
assigned does not become active in KVM.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2055776/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048517] Re: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU
Hello Jan, Thank you for reporting this bug, and for providing a good initial analysis of the problem. Would you have access to a host with an EPYC-Rome CPU where you can run some tests? This is something that needs to be done in order to proceed here, especially if we indeed decide to SRU this change into Focal. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048517 Title: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2048517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2058576] Re: FTBFS: armhf: build-time test failures
On Wednesday, April 03 2024, Andreas Hasenack wrote: > It is enabled: > > Types: deb > URIs: http://ports.ubuntu.com/ubuntu-ports > Suites: noble noble-updates noble-backports noble-proposed > Components: main universe restricted multiverse > Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg > > > Or is there some other trick specific to the state noble is in now? Not that I know of. I only commented because you didn't mention noble-updates on your first message and I thought it was worth bringing it up. -- Sergio GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058576 Title: FTBFS: armhf: build-time test failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2058576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2058576] Re: FTBFS: armhf: build-time test failures
On Wednesday, April 03 2024, Andreas Hasenack wrote: > This is very hard to troubleshoot at the moment, because I just can't > get the build-dependencies installed, either with noble or noble- > proposed: I think you need to enable noble-updates. -- Sergio GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058576 Title: FTBFS: armhf: build-time test failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2058576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040470] Re: MRE updates of squid for noble
** Also affects: squid (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: squid (Ubuntu Noble) ** Changed in: squid (Ubuntu Jammy) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) ** Tags added: server-todo ** Description changed: - Backport squid as MRE to noble once the update for noble has been - completed. + This bug tracks the following MRE updates for the Squid package: - + [Release codename] ([Release version]): Squid [Squid version] + [...] - [Impact] - TBD + This update includes bugfixes following the SRU policy exception defined + at https://wiki.ubuntu.com/SquidUpdates. - [Major Changes] - TBD + [Upstream changes] + + TODO: Add a link to the upstream changelog + + TODO: List the major changes introduced in this release [Test Plan] - TBD + + TODO: link the build log containing all tests being executed + + TODO: All tests are passing during build time, as shown in the build log + (builds would fail otherwise, see LP: #2004050). + + TODO: add results of local autopkgtest run against all the new Squid + versions being uploaded here [Regression Potential] - Upstream has an extensive build and integration test suite. So regressions would likely arise from a change in interaction with Ubuntu-specific integrations, such as in relation to the versions of dependencies available and other packaging-specific matters. - + + Upstream tests are always executed during build-time. Failures would + prevent builds from succeeding. + + Squid does not have many reverse dependencies. However, any upgrade is a + risk to introduce breakage to other packages. Whenever a regression + occurs in autopkgtests, we will investigate and provide fixes. + + TODO: consider any other regression potential specific to the version + being updated and list them here if any. + + [Other Info] + + TODO-A: No CVEs are being addressed this time. Therefore, this should go + through the updates pockets. + + TODO-B: CVEs TBD are being addressed by these updates. Therefore, this + update should go through the security pocket. + + TODO: list previous MREs for this package, if any. ** Summary changed: - MRE updates of squid for noble + Upstream microrelease 5.9 ** Description changed: This bug tracks the following MRE updates for the Squid package: - [Release codename] ([Release version]): Squid [Squid version] - [...] + Jammy (22.04): 5.9 This update includes bugfixes following the SRU policy exception defined at https://wiki.ubuntu.com/SquidUpdates. [Upstream changes] - TODO: Add a link to the upstream changelog + http://www.squid-cache.org/Versions/v5/ChangeLog.html + (Jammy: 5.7..5.9) TODO: List the major changes introduced in this release [Test Plan] TODO: link the build log containing all tests being executed TODO: All tests are passing during build time, as shown in the build log (builds would fail otherwise, see LP: #2004050). TODO: add results of local autopkgtest run against all the new Squid versions being uploaded here [Regression Potential] Upstream tests are always executed during build-time. Failures would prevent builds from succeeding. Squid does not have many reverse dependencies. However, any upgrade is a risk to introduce breakage to other packages. Whenever a regression occurs in autopkgtests, we will investigate and provide fixes. TODO: consider any other regression potential specific to the version being updated and list them here if any. [Other Info] TODO-A: No CVEs are being addressed this time. Therefore, this should go through the updates pockets. TODO-B: CVEs TBD are being addressed by these updates. Therefore, this update should go through the security pocket. TODO: list previous MREs for this package, if any. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040470 Title: Upstream microrelease 5.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/2040470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060016] Re: package mysql-server-8.0 8.0.36-0ubuntu0.22.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 2019003 *** https://bugs.launchpad.net/bugs/2019003 Thank you for reporting a bug. This is a duplicate of bug #2019003, so I marked it as such. Please take a look at that other bug, there may be a workaround available for this case. Thanks. ** This bug has been marked a duplicate of bug 2019003 package mysql-server-8.0 8.0.33-0ubuntu0.22.04.1 failed to install/upgrade: Can't start server: Bind on TCP/IP port: Address already in use -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060016 Title: package mysql-server-8.0 8.0.36-0ubuntu0.22.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/2060016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055776] Re: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM.
I was able to reproduce the bug on Focal, and since we seem to carry the same version on Jammy/Mantic (and likely Noble), it's probable that the bug also happens in those releases. For future reference: # apt install -y libvirt-daemon-system bind9 dnsmasq Reboot, and try bringing up the "default" network on libvirt: # virsh net-start default error: Failed to start network default error: internal error: Child process (VIR_BRIDGE_NAME=virbr0 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper) unexpected exit status 2: dnsmasq: failed to create listening socket for 192.168.122.1: Address already in use -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055776 Title: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2055776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"
Mauricio asked me to review the debdiff for Focal as well. This debdiff is different because he had to implement some code to synchronize the destruction of the worker threads with the free'ing of the thread pool. I looked at the new code, analyzed it as best as I could, asked a few questions to Mauricio regarding the new environment variable being created, and finally got convinced that everything seems OK. The implementation is sound and the concept is simple: qemuStateCleanupWait acts similarly to a thread barrier and makes sure that all threads previously created by qemuProcessReconnect are able to finish before qemuStateCleanup can proceed. In a nutshell: LGTM, +1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059272 Title: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2059272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055151] Re: kea-ctrl-agent segfault in ppc64el dep8 test
After some more debugging/testing, it seems like the problem is indeed caused by compiler optimization. More specifically, LTO. Disabling it seems to have done the trick, and I can't reproduce the segmentation fault anymore. Basically: ifeq ($(DEB_HOST_ARCH),ppc64el) export DEB_BUILD_MAINT_OPTIONS += optimize=-lto endif on d/rules. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055151 Title: kea-ctrl-agent segfault in ppc64el dep8 test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-kea/+bug/2055151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051754] Re: Live migration fails (missing vmx features)
** Changed in: libvirt (Ubuntu) Status: Triaged => 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/2051754 Title: Live migration fails (missing vmx features) To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/2051754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors
Thank you, Andreas. I will wait for bug #2046439 to clear -proposed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2012763 Title: qemu-system-amd64 max cpus is too low for latest processors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2012763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors
Performing the verification on Mantic. First, verifying that we can reproduce the problem. # apt policy qemu-system-x86 qemu-system-x86: Installed: 1:8.0.4+dfsg-1ubuntu3.23.10.3 Candidate: 1:8.0.4+dfsg-1ubuntu3.23.10.3 Version table: *** 1:8.0.4+dfsg-1ubuntu3.23.10.3 500 500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:8.0.4+dfsg-1ubuntu3.23.10.2 500 500 http://security.ubuntu.com/ubuntu mantic-security/main amd64 Packages 1:8.0.4+dfsg-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages # qemu-system-x86_64 -M pc-q35-jammy,accel=kvm,kernel-irqchip=split -device intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm -net none -m 4096M -nographic -kernel /boot/vmlinuz -initrd /boot/initrd.img -chardev stdio,mux=on,id=char0 -mon chardev=char0,mode=readline -serial chardev:char0 -append "console=ttyS0" qemu-system-x86_64: Invalid SMP CPUs 300. The max CPUs supported by machine 'pc-q35-jammy' is 288 # qemu-system-x86_64 -M pc-q35-mantic,accel=kvm,kernel-irqchip=split -device intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm -net none -m 4096M -nographic -kernel /boot/vmlinuz -initrd /boot/initrd.img -chardev stdio,mux=on,id=char0 -mon chardev=char0,mode=readline -serial chardev:char0 -append "console=ttyS0" qemu-system-x86_64: Invalid SMP CPUs 300. The max CPUs supported by machine 'pc-q35-mantic' is 288 Now, updating the package and verifying that the version from -proposed fixes the issue: # apt policy qemu-system-x86 qemu-system-x86: Installed: 1:8.0.4+dfsg-1ubuntu3.23.10.5 Candidate: 1:8.0.4+dfsg-1ubuntu3.23.10.5 Version table: *** 1:8.0.4+dfsg-1ubuntu3.23.10.5 100 100 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:8.0.4+dfsg-1ubuntu3.23.10.3 500 500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages 1:8.0.4+dfsg-1ubuntu3.23.10.2 500 500 http://security.ubuntu.com/ubuntu mantic-security/main amd64 Packages 1:8.0.4+dfsg-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages # qemu-system-x86_64 -M pc-q35-jammy-maxcpus,accel=kvm,kernel-irqchip=split -device intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm -net none -m 4096M -nographic -kern el /boot/vmlinuz -initrd /boot/initrd.img -chardev stdio,mux=on,id=char0 -mon chardev=char0,mode=readline -serial chardev:char0 -append "console=ttyS0" qemu-system-x86_64: warning: Number of SMP cpus requested (300) exceeds the recommended cpus supported by KVM (12) qemu-system-x86_64: warning: Number of hotpluggable cpus requested (300) exceeds the recommended cpus supported by KVM (12) ... # qemu-system-x86_64 -M pc-q35-mantic-maxcpus,accel=kvm,kernel-irqchip=split -device intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm -net none -m 4096M -nographic -kern el /boot/vmlinuz -initrd /boot/initrd.img -chardev stdio,mux=on,id=char0 -mon chardev=char0,mode=readline -serial chardev:char0 -append "console=ttyS0" qemu-system-x86_64: warning: Number of SMP cpus requested (300) exceeds the recommended cpus supported by KVM (12) qemu-system-x86_64: warning: Number of hotpluggable cpus requested (300) exceeds the recommended cpus supported by KVM (12) ... This concludes the verification on Mantic. ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2012763 Title: qemu-system-amd64 max cpus is too low for latest processors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2012763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"
OK, I tested the fixed package from your PPA and verified that it indeed solves the issue. Just to reiterate, then: LGTM, +1! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059272 Title: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2059272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"
Hah, I didn't see your comment before I posted mine. Mid air conflict! Anyway, thanks for providing the PPA. I'll take it for a spin :-). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059272 Title: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2059272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"
Mauricio, Wow! Such an awesome reproducer. Very detailed and easy to follow. Thanks for providing it. I was able to verify the problem here, and looked at the upstream patch[1] that fixes it. The rationale makes sense to me, although that cleanup function is pretty involved and it's hard to say if there can be any fallout from moving the worker thread pool freeing action earlier. I looked at the upstream repository and could not find any amends/fixes to the commit in question. It's present in Mantic and Noble, which is a good sign. Do you have a PPA build that I can try with the reproducer to check the fix, please? Otherwise, this LGTM and I'm +1 on proceeding with the SRU. Thanks! [1]: For reference: https://gitlab.com/libvirt/libvirt/-/commit/152770333449cd3b78b4f5a9f1148fc1f482d842 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059272 Title: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2059272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors
Fixed package uploaded to Mantic: qemu_8.0.4+dfsg-1ubuntu3.23.10.5_source.changes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2012763 Title: qemu-system-amd64 max cpus is too low for latest processors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2012763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors
Performing the verification on Mantic. First, reproduce the problem. # apt policy qemu-system-x86 qemu-system-x86: Installed: 1:8.0.4+dfsg-1ubuntu3.23.10.3 Candidate: 1:8.0.4+dfsg-1ubuntu3.23.10.3 Version table: *** 1:8.0.4+dfsg-1ubuntu3.23.10.3 500 500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:8.0.4+dfsg-1ubuntu3.23.10.2 500 500 http://security.ubuntu.com/ubuntu mantic-security/main amd64 Packages 1:8.0.4+dfsg-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages # qemu-system-x86_64 -M pc-q35-jammy,accel=kvm,kernel-irqchip=split -device intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm -net none -m 4096M -nographic -kernel /boot/vmlinuz -initrd /boot/initrd.img -chardev stdio,mux=on,id=char0 -mon chardev=char0,mode=readline -serial chardev:char0 -append "console=ttyS0" qemu-system-x86_64: Invalid SMP CPUs 300. The max CPUs supported by machine 'pc-q35-jammy' is 288 # qemu-system-x86_64 -M pc-q35-mantic,accel=kvm,kernel-irqchip=split -device intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm -net none -m 4096M -nographic -kernel /boot/vmlinuz -initrd /boot/initrd.img -chardev stdio,mux=on,id=char0 -mon chardev=char0,mode=readline -serial chardev:char0 -append "console=ttyS0" qemu-system-x86_64: Invalid SMP CPUs 300. The max CPUs supported by machine 'pc-q35-mantic' is 288 Now, verifying that the package from mantic-proposed fixes the issue: # apt policy qemu-system-x86 qemu-system-x86: Installed: 1:8.0.4+dfsg-1ubuntu3.23.10.4 Candidate: 1:8.0.4+dfsg-1ubuntu3.23.10.4 Version table: *** 1:8.0.4+dfsg-1ubuntu3.23.10.4 100 100 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:8.0.4+dfsg-1ubuntu3.23.10.3 500 500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages 1:8.0.4+dfsg-1ubuntu3.23.10.2 500 500 http://security.ubuntu.com/ubuntu mantic-security/main amd64 Packages 1:8.0.4+dfsg-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages # qemu-system-x86_64 -M pc-q35-jammy-maxcpus,accel=kvm,kernel-irqchip=split -device intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm -net none -m 4096M -nographic -kernel /boot/vmlinuz -initrd /boot/initrd.img -chardev stdio,mux=on,id=char0 -mon chardev=char0,mode=readline -serial chardev:char0 -append "console=ttyS0" < all worked as expected > # qemu-system-x86_64 -M pc-q35-mantic-maxcpus,accel=kvm,kernel-irqchip=split -device intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm -net none -m 4096M -nographic -kernel /boot/vmlinuz -initrd /boot/initrd.img -chardev stdio,mux=on,id=char0 -mon chardev=char0,mode=readline -serial chardev:char0 -append "console=ttyS0" qemu-system-x86_64: Invalid SMP CPUs 300. The max CPUs supported by machine 'pc-q35-mantic-maxcpus' is 288 As can be seen above, there is a problem with the new pc-q35-mantic- maxcpus machine type. As such, I am tagging this bug as verification- mantic-failed and will upload a fix for the issue. ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-failed-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2012763 Title: qemu-system-amd64 max cpus is too low for latest processors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2012763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors
** Changed in: qemu (Ubuntu Jammy) Status: New => In Progress ** Changed in: qemu (Ubuntu Mantic) Status: Confirmed => In Progress ** Changed in: qemu (Ubuntu Noble) Status: Confirmed => 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/2012763 Title: qemu-system-amd64 max cpus is too low for latest processors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2012763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2058576] [NEW] FTBFS: armhf: build-time test failures
On Wednesday, March 20 2024, Andreas Hasenack wrote: > Public bug reported: > > sssd is currently failing to build on armhf due to build-time test > failures[1]¨: Without having checked anything: is this not related to the time_t transition? The build was passing before. I'll check more tomorrow. -- Sergio GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058576 Title: FTBFS: armhf: build-time test failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2058576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors
** Tags added: server-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2012763 Title: qemu-system-amd64 max cpus is too low for latest processors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2012763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors
Hi Jeff, Thanks for the offer. Actually there is! - If you could test Noble and double/triple check that we don't need to do anything else there in order to support maxcpus, that'd be great. Just use the "ubuntu" machine type and check if QEMU starts correct with more than 288 vCPUs. - Once the Jammy/Mantic SRUs are accepted, we will need to perform a verification for both uploads. I can do it my side, but it would be very helpful if you could also verify the uploads on your side. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2012763 Title: qemu-system-amd64 max cpus is too low for latest processors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2012763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors
** Description changed:
[ Impact ]
- QEMU users on Ubuntu Jammy who try to spawn a VM with more than 288
- vCPUs will not be able to do so, because the machine types available
+ QEMU users on Ubuntu Jammy/Mantic who try to spawn a VM with more than
+ 288 vCPUs will not be able to do so, because the machine types available
don't support such scenario. The following error will happen:
qemu-system-x86_64: Invalid SMP CPUs 300. The max CPUs supported by
machine 'pc-q35-jammy' is 288
[ Test Plan ]
Ideally, the test should be performed in a machine with more than 288
physical CPUs available. However, due to the difficulty in finding such
systems, it is possible to emulate the usage of more than 288 vCPUs.
- On a Jammy machine, you can do:
+ On a Jammy/Mantic machine, making sure to adjust the machine type
+ accordingly, you can do:
$ sudo qemu-system-x86_64 -M pc-q35-jammy,accel=kvm,kernel-irqchip=split
-device intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm
-net none -m 4096M -nographic -kernel /boot/vmlinuz -initrd
/boot/initrd.img -chardev stdio,mux=on,id=char0 -mon
chardev=char0,mode=readline -serial chardev:char0 -append
"console=ttyS0"
You will notice that the command will fail, as expected.
- The proposed fix is to create a new machine type on Jammy, in order to
- minimize the possibility of regressions in deployments using the
- existing machine types. This new type is named pc-{q35,i440fx}-jammy-
- maxcpus. When doing the test, make sure to provide this new machine
- type (as part of the "-M" argument).
+ The proposed fix is to create a new machine type on Jammy/Mantic, in
+ order to minimize the possibility of regressions in deployments using
+ the existing machine types. This new type is named
+ pc-{q35,i440fx}-{jammy,mantic}-maxcpus. When doing the test, make sure
+ to provide this new machine type (as part of the "-M" argument).
[ Where problems could occur ]
As explained above, a new machine type was created in order to minimize
the possibility of regressions. As such, the existing
- "pc-{q35,i440fx}-jammy" machine types should continue to work as before,
- without any change.
+ "pc-{q35,i440fx}-{jammy,mantic}" machine types should continue to work
+ as before, without any change.
[ Original Description ]
During testing of an AMD Genoa CPU, it was discovered that qemu-system-
amd64 doesn't support enough cpus.
The specific error the tester received was:
qemu-system-x86_64: Invalid SMP CPUs 384. The max supported by machine
'pc-q35-7.1' is 288
Looking at the sournce that seems to be an easy fix at first glance:
https://github.com/qemu/qemu/blob/master/hw/i386/pc_q35.c
372machine_class_allow_dynamic_sysbus_dev(m, TYPE_VMBUS_BRIDGE);
373m->max_cpus = 288;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2012763
Title:
qemu-system-amd64 max cpus is too low for latest processors
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2012763/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors
** Description changed:
+ [ Impact ]
+
+ QEMU users on Ubuntu Jammy who try to spawn a VM with more than 288
+ vCPUs will not be able to do so, because the machine types available
+ don't support such scenario. The following error will happen:
+
+ qemu-system-x86_64: Invalid SMP CPUs 300. The max CPUs supported by
+ machine 'pc-q35-jammy' is 288
+
+ [ Test Plan ]
+
+ Ideally, the test should be performed in a machine with more than 288
+ physical CPUs available. However, due to the difficulty in finding such
+ systems, it is possible to emulate the usage of more than 288 vCPUs.
+
+ On a Jammy machine, you can do:
+
+ $ sudo qemu-system-x86_64 -M pc-q35-jammy,accel=kvm,kernel-irqchip=split
+ -device intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm
+ -net none -m 4096M -nographic -kernel /boot/vmlinuz -initrd
+ /boot/initrd.img -chardev stdio,mux=on,id=char0 -mon
+ chardev=char0,mode=readline -serial chardev:char0 -append
+ "console=ttyS0"
+
+ You will notice that the command will fail, as expected.
+
+ The proposed fix is to create a new machine type on Jammy, in order to
+ minimize the possibility of regressions in deployments using the
+ existing machine types. This new type is named pc-{q35,i440fx}-jammy-
+ maxcpus. When doing the test, make sure to provide this new machine
+ type (as part of the "-M" argument).
+
+ [ Where problems could occur ]
+
+ As explained above, a new machine type was created in order to minimize
+ the possibility of regressions. As such, the existing
+ "pc-{q35,i440fx}-jammy" machine types should continue to work as before,
+ without any change.
+
+ [ Original Description ]
+
During testing of an AMD Genoa CPU, it was discovered that qemu-system-
amd64 doesn't support enough cpus.
The specific error the tester received was:
qemu-system-x86_64: Invalid SMP CPUs 384. The max supported by machine
'pc-q35-7.1' is 288
Looking at the sournce that seems to be an easy fix at first glance:
https://github.com/qemu/qemu/blob/master/hw/i386/pc_q35.c
372machine_class_allow_dynamic_sysbus_dev(m, TYPE_VMBUS_BRIDGE);
373m->max_cpus = 288;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2012763
Title:
qemu-system-amd64 max cpus is too low for latest processors
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2012763/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058278] Re: [Backport] libvirt-daemon-system won't install on Focal
Thanks, Guilherme. I found: https://salsa.debian.org/utopia- team/polkit/-/commit/81c21cdadbe0a98ca016738b8c2cc7d4f225f067 and then: https://salsa.debian.org/libvirt- team/libvirt/-/commit/b9b2923abfae8ec80507bc267767db4b51fb4021 which explain why we're depending on polkitd. So yeah, I believe Guilherme's suggestion might be enough to fix this issue on Focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058278 Title: [Backport] libvirt-daemon-system won't install on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2058278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058278] Re: [Backport] libvirt-daemon-system won't install on Focal
Kudos to gpiccoli for finding the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058278 Title: [Backport] libvirt-daemon-system won't install on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2058278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058278] [NEW] [Backport] libvirt-daemon-system won't install on Focal
Public bug reported: When installing libvirt-daemon-system (from https://launchpad.net/~canonical-server/+archive/ubuntu/server- backports) on a Focal system, one will see the following error: # apt install libvirt-daemon-system Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libvirt-daemon-system : Depends: polkitd but it is not installable Depends: polkitd-pkla but it is not installable Recommends: dnsmasq-base Recommends: mdevctl but it is not going to be installed E: Unable to correct problems, you have held broken packages. As discussed with Bryce, I believe polkit should be backported to Focal as well. ** Affects: libvirt (Ubuntu) Importance: Undecided Assignee: Bryce Harrington (bryce) Status: Triaged ** Changed in: libvirt (Ubuntu) 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/2058278 Title: [Backport] libvirt-daemon-system won't install on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2058278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056479] Re: Error qemu-system-x86_64: -accel kvm: failed to initialize kvm: Permission denied
Hello and thanks for reporting a bug. You shouldn't need to manually chown /dev/kvm. On a fresh Ubuntu Jammy install, I see: # ls -la /dev/kvm crw-rw 1 root kvm 10, 232 Mar 7 19:41 /dev/kvm After installing qemu and virt-manager, I still see the proper permissions/ownership, as expected. Therefore, it looks to me like this could be a local configuration issue. Could you please provide more details about what actions you performed before seeing the error? Also, note that if you're trying to execute qemu using a regular user then you will need to add this user to the kvm group. Marking the bug as Incomplete for now until we get more details about it. Thanks. ** Changed in: virt-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/2056479 Title: Error qemu-system-x86_64: -accel kvm: failed to initialize kvm: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/2056479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056065] Re: cloud images slow to boot under kvm
Hi Ross,
Thanks for the feedback. It's a strange situation, indeed. And I have
to say that I cannot reproduce the issue here even after forcing qemu to
use pc-i440fx-{mantic,jammy}, which is what happens when you don't
specify type=q35. The VM boots without issues. Of course, the first
time it boots it takes longer than usual because of the snap seed
population and other first-boot tasks that are executed, but otherwise
everything else happens as expected.
I am going to keep this bug as Incomplete for now because we're unable
to reproduce the issue on our end. Please let us know if you have more
information that could help us trigger the problem.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056065
Title:
cloud images slow to boot under kvm
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2056065/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056152] Re: errors when starting thunderbird, directly after boot. error message: package dnsmasq 2.90-0ubuntu0.22.04.1 failed to install/upgrade: end of file on stdin at conffile prompt
Thank you for taking the time to file a bug report. From DpkgTerminalLog.txt, we see the following message: *** dnsmasq.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package dnsmasq (--configure): end of file on stdin at conffile prompt This indicates that there was no reply to the question posed by dpkg (debconf). The upgrade process had to ask the question because there is some local modification on your /etc/dnsmasq.conf, and it could not figure out how to merge your modifications with the new configuration file provided by the package. As such, it expects you to answer how the conflict should be resolved. Since the answer provided was an EOF, it errored out. In other words, you have to be able to properly answer dpkg's question in order to proceed with the upgrade. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'. However, if you believe that this is really a bug in Ubuntu, then we would be grateful if you would provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: dnsmasq (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/2056152 Title: errors when starting thunderbird, directly after boot. error message: package dnsmasq 2.90-0ubuntu0.22.04.1 failed to install/upgrade: end of file on stdin at conffile prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2056152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1999190] Re: missing lines in apparmor config for sssd
** Merge proposal unlinked: https://code.launchpad.net/~sergiodj/ubuntu/+source/sssd/+git/sssd/+merge/461744 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1999190 Title: missing lines in apparmor config for sssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1999190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055405] Re: python3-samba syntaxwarnings while upgrading
Thank you for the bug report. These are coming from test cases, so while it is indeed a good thing to fix, it's not something urgent. May I suggest that you raise this issue on Debian, please? If it's fixed there, then it will automatically get picked up by Ubuntu the next time we merge the package. For now, I am marking this as Triaged but setting a Low priority to it. Thanks. ** Changed in: samba (Ubuntu) Status: New => Triaged ** Changed in: samba (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055405 Title: python3-samba syntaxwarnings while upgrading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/2055405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040459] Re: MRE updates of bind9 for noble
FTR: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/2055436 could/should probably be fixed as part of the upcoming MRE. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040459 Title: MRE updates of bind9 for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/2040459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055436] Re: Package recommends nonexistent "bind-doc" package
I am marking this bug as triaged but setting its importance to Low. It should be fixed whenever we make a new bind9 upload on Jammy (likely an MRE). I left a comment on the MRE bug #2040459. ** Changed in: bind9 (Ubuntu) Status: New => Triaged ** Changed in: bind9 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055436 Title: Package recommends nonexistent "bind-doc" package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/2055436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054470] Re: NBD Client Fails to Parse /etc/nbdtab Correctly on Ubuntu 22.04 and 20.04
Performing the verification on Jammy. First, checking that the issue can be triggered: # apt policy nbd-client nbd-client: Installed: 1:3.23-3ubuntu1 Candidate: 1:3.23-3ubuntu1 Version table: *** 1:3.23-3ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status nbd-server: Installed: 1:3.23-3ubuntu1 Candidate: 1:3.23-3ubuntu1 Version table: *** 1:3.23-3ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status # nbd-client nbd0 parse error parsing /etc/nbdtab: syntax errorERROR: no valid configuration for specified device found Now, verifying that the package from -proposed fixes the bug: # apt policy nbd-client nbd-server nbd-client: Installed: 1:3.23-3ubuntu1.22.04.1 Candidate: 1:3.23-3ubuntu1.22.04.1 Version table: *** 1:3.23-3ubuntu1.22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 1:3.23-3ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages nbd-server: Installed: 1:3.23-3ubuntu1.22.04.1 Candidate: 1:3.23-3ubuntu1.22.04.1 Version table: *** 1:3.23-3ubuntu1.22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:3.23-3ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages # nbd-client nbd0 Negotiation: ..size = 1048576MB Connected /dev/nbd0 This concludes the verification on Jammy. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054470 Title: NBD Client Fails to Parse /etc/nbdtab Correctly on Ubuntu 22.04 and 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/nbd/+bug/2054470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2055126] Re: Unable to bring up a guest using 24.04(Noble Numbat) ISO
On Thursday, February 29 2024, Frank Heimes wrote: > This bug could be related LP#2055294 ... Heh, I had *just* mentioned this bug to Patrícia as a likely cause of this issue and then got your comment, Frank. Anyway, I'll redownload the daily image and give it another spin. -- Sergio GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055126 Title: Unable to bring up a guest using 24.04(Noble Numbat) ISO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2055126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055357] Re: Sync etcd 3.4.30-1 (universe) from Debian unstable (main)
This bug was fixed in the package etcd - 3.4.30-1 Sponsored for Shengjing Zhu (zhsj) --- etcd (3.4.30-1) unstable; urgency=medium * Team upload * New upstream version 3.4.30 + CVE-2021-28235 (fixed in 3.4.25): Clearing password after authenticating the user. + CVE-2023-32082 (fixed in 3.4.26): LeaseTimeToLive API may return keys to clients which have no read permission on the keys -- Shengjing Zhu Wed, 28 Feb 2024 17:43:49 +0800 etcd (3.4.23-6) unstable; urgency=medium * Team upload * Add a patch to skip flaky test that failed on 3/10 buildds -- Mathias Gibbens Sat, 17 Feb 2024 00:31:39 + etcd (3.4.23-5) unstable; urgency=medium * Team upload * d/control: - Replace transitional golang-goprotobuf-dev package - Allow golang-github-golang-protobuf-1-5-dev as optional Depends * Add a patch to skip tests that fail in some environments -- Mathias Gibbens Fri, 16 Feb 2024 22:07:53 + ** Changed in: etcd (Ubuntu) Status: New => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-28235 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-32082 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055357 Title: Sync etcd 3.4.30-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etcd/+bug/2055357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055126] Re: Unable to bring up a guest using 24.04(Noble Numbat) ISO
Thanks for providing further details on how to reproduce the issue. Unfortunately, I haven't been able to trigger the problem here. I'm using an LPAR, so it's a nested VM scenario (which is what gather you're also using, but please let me know otherwise), and I can't get the installation to finish because subiquity (our installer) crashes. This is certainly a problem, but it seem unrelated to QEMU/virt-install and not the same issue that you're experiencing. Are you using a baremetal machine perhaps? Also, allow me to reiterate what Frank said above. Our Ubuntu Cloud images are generated for KVM and recommended in this case. Having said that, could you please provide more details on the problem you're having. Are you able to access any logs at all? Do you see error/warning messages? I'm going to mark this bug as Incomplete for now in order to reflect the fact that we're waiting on more information. Thanks! ** Changed in: virtinst (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/2055126 Title: Unable to bring up a guest using 24.04(Noble Numbat) ISO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2055126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054632] Re: ninja command failing for upstream libvirt compilation
** Changed in: libvirt (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/2054632 Title: ninja command failing for upstream libvirt compilation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2054632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2051965] Re: QEmu with TCG acceleration (without KVM) causes kernel panics with guest kernels >=6.3
On Tuesday, February 27 2024, Matthieu Baerts wrote: > Hi Sergio, Andreas, Hey Matthieu, > Thank you for the new version! > > I also confirm that with the new version from mantic-proposed... > > # apt-cache policy qemu-system-x86 > qemu-system-x86: > Installed: 1:8.0.4+dfsg-1ubuntu3.23.10.3 > Candidate: 1:8.0.4+dfsg-1ubuntu3.23.10.3 > Version table: > *** 1:8.0.4+dfsg-1ubuntu3.23.10.3 100 > 100 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 > Packages > 100 /var/lib/dpkg/status > 1:8.0.4+dfsg-1ubuntu3.23.10.2 500 > 500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 > Packages > 500 http://security.ubuntu.com/ubuntu mantic-security/main amd64 > Packages > 1:8.0.4+dfsg-1ubuntu3 500 > 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages > > > ...I didn't have any panic after 30 minutes of tests with the new version, > while it took me 30 seconds to get the panic with the previous one. That's great, thanks for confirming that the fix indeed works. The package should be released to mantic-release in the next few days. Cheers, -- Sergio GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051965 Title: QEmu with TCG acceleration (without KVM) causes kernel panics with guest kernels >=6.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2051965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051965] Re: QEmu with TCG acceleration (without KVM) causes kernel panics with guest kernels >=6.3
Performing the verification for Mantic. Verifying that we're using the QEMU package from mantic-proposed: $ apt policy qemu-system-x86 qemu-system-x86: Installed: 1:8.0.4+dfsg-1ubuntu3.23.10.3 Candidate: 1:8.0.4+dfsg-1ubuntu3.23.10.3 Version table: *** 1:8.0.4+dfsg-1ubuntu3.23.10.3 100 100 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:8.0.4+dfsg-1ubuntu3.23.10.2 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu mantic-security/main amd64 Packages 1:8.0.4+dfsg-1ubuntu3 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu mantic/main amd64 Packages Running the tests in a loop and verifying that the guest Linux kernel doesn't panic: $ sudo INPUT_BUILD_SKIP_PACKETDRILL=1 INPUT_BUILD_SKIP_PERF=1 INPUT_NO_BLOCK=1 $HOME/repr/entrypoint.sh auto-normal ... == Summary == fatal: No names found, cannot describe anything. Ref: Mode: normal Extra kconfig: / All tests: ok 1 test: selftest_mptcp_connect KVM Validation: Success! ✅ This concludes the verification for Mantic. ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051965 Title: QEmu with TCG acceleration (without KVM) causes kernel panics with guest kernels >=6.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2051965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054632] Re: ninja command failing for upstream libvirt compilation
Hello, As Frank mentioned, it would be really useful if we could actually reproduce this problem with our package. Also, I'm curious about something. If you are building libvirt directly from upstream sources, would it really make a difference if our package had the patch after all? Thank you in advance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054632 Title: ninja command failing for upstream libvirt compilation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2054632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors
Hi there, I just wanted to give a quick update. I still have to perform a "real world" test using the server with more than 300 CPUs, but meanwhile I was able to test the Jammy QEMU from my PPA using a 12-core machine and it seems like we won't need to backport any patches there either. Here's the command line I used: $ sudo qemu-system-x86_64 -M pc-q35-jammy-maxcpus,accel=kvm,kernel- irqchip=split -device intel-iommu,intremap=on -smp cpus=300,maxcpus=300 -enable-kvm -net none -m 4096M -nographic -kernel /boot/vmlinuz -initrd /boot/initrd.img -chardev stdio,mux=on,id=char0 -mon chardev=char0,mode=readline -serial chardev:char0 -append "console=ttyS0" Upon booting and getting dropped into the initramfs shell, I did a "cat /proc/cpuinfo" and verified that the 300 vCPUs were correctly listed there. So yeah, good news :-). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2012763 Title: qemu-system-amd64 max cpus is too low for latest processors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2012763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055003] Re: Qemu cmdline core dumped with more(8193 or more) cpus
** Changed in: qemu (Ubuntu Noble) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) ** Tags added: server-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055003 Title: Qemu cmdline core dumped with more(8193 or more) cpus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2055003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2045063] Re: Demote glusterfs for noble
** Merge proposal unlinked: https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/461236 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2045063 Title: Demote glusterfs for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/2045063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1999190] Re: missing lines in apparmor config for sssd
** Merge proposal unlinked: https://code.launchpad.net/~sergiodj/ubuntu/+source/sssd/+git/sssd/+merge/461283 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1999190 Title: missing lines in apparmor config for sssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1999190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055074] Re: Merge sssd from Debian unstable for noble
** Merge proposal linked: https://code.launchpad.net/~sergiodj/ubuntu/+source/sssd/+git/sssd/+merge/461283 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055074 Title: Merge sssd from Debian unstable for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2055074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055074] [NEW] Merge sssd from Debian unstable for noble
Public bug reported: Merge sssd 2.9.4-1 from Debian unstable. ** Affects: sssd (Ubuntu) Importance: High Assignee: Sergio Durigan Junior (sergiodj) Status: In Progress ** Tags: needs-merge upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055074 Title: Merge sssd from Debian unstable for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2055074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 720638] Re: snmpd crashes with segfault (libnetsnmpmibs.so.15.1.2)
Thank you for the update. Would you be able to provide a coredump, a backtrace and/or a reproducer? I did some research and found upstream's https://github.com/net-snmp/net-snmp/issues/107 which seems to be related, but the patch that fixes their issue doesn't make sense on Jammy's net-snmp, so I'm thinking that there might be more to this bug than meets the eye. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/720638 Title: snmpd crashes with segfault (libnetsnmpmibs.so.15.1.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/720638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1997220] Re: CVE-2022-42898
** Changed in: samba (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: samba (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1997220 Title: CVE-2022-42898 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1997220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2007272] Re: I have ubuntu 22.04 on my system and have the following vulnerability : CVE-2022-42898. On which release/path of Ubuntu can I expect them to be fixed ?
Thank you for taking the time to report a bug. The CVE mentioned affects only 32-bit systems. Are you running a samba 32-bit binary? Are you on amd64? If yes to both question, then this is an unsupported scenario. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2007272 Title: I have ubuntu 22.04 on my system and have the following vulnerability : CVE-2022-42898. On which release/path of Ubuntu can I expect them to be fixed ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2007272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971295] Re: Merge net-snmp from Debian unstable for kinetic
** Changed in: net-snmp (Ubuntu) Status: New => In Progress ** Changed in: net-snmp (Ubuntu) Milestone: ubuntu-22.07 => ubuntu-22.06 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971295 Title: Merge net-snmp from Debian unstable for kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1971295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932552] Re: php-symfony-dependency-injection not working with php 8
Utkarsh mentioned in #ubuntu-server that he is still planning to work 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/1932552 Title: php-symfony-dependency-injection not working with php 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/symfony/+bug/1932552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975766] Re: Backport postgresql as MRE for bionic, focal, jammy (August)
** Changed in: postgresql-10 (Ubuntu) Status: Invalid => New ** Changed in: postgresql-12 (Ubuntu) Status: Invalid => New ** Changed in: postgresql-14 (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975766 Title: Backport postgresql as MRE for bionic, focal, jammy (August) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-10/+bug/1975766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977627] Re: New upstream microrelease 2.5.12
** Changed in: openldap (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977627 Title: New upstream microrelease 2.5.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1977627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974214] Re: Segfaults on verify callout, in _gnutls_trust_list_get_issuer
** Description changed: [ Impact ] When the user sends a message to someone, if the server responsible for receiving this message defers it, and if there are other possible servers (i.e., other servers listed as secondary MX) to try, exim4 will segfault while trying to connect to the second server. [ Test Plan ] The test case for this bug is a bit involved. It makes use of the upstream reporter's mail server, which has been configured to defer emails when they come through the primary MX, but accept when they come through the secondary MX. This means that you will need access to port 25 (unfortunately canonistack seems to block it). $ lxc launch ubuntu-daily:jammy exim4-bug1974214 $ lxc shell exim4-bug1974214 # apt update && apt full-upgrade # apt install -y exim4 # dpkg-reconfigure exim4-config ... In the "Mail Server configuration" screen, select "internet site; mail is sent and received directly using SMTP". Leave everything else untouched. # cat > /etc/netplan/99-disable-ipv6.yaml << _EOF_ network: ethernets: eth0: link-local: [ ipv4 ] _EOF_ # netplan apply # reboot $ lxc shell exim4-bug1974214 # cat > 1.msg << _EOF_ Subject: test this is a test _EOF_ # exim4 -odq -f defe...@example.com geda...@gedalya.net < 1.msg # exim4 -bp 0m 321 1nxC3o-Ax-AS geda...@gedalya.net ... You will have to grab the message ID, which is 1nxC3o-Ax-AS in this case. You have to use this ID in the following command. # exim4 -d+all -q 1nxC3o-Ax-AS 2>&1 | tee /tmp/exim.debug ... # grep SEGV /tmp/exim.debug You should be able to see exim4 signalling the segmentation fault that occurred while attempting to connect to the second server. [ Where problems could occur ] The patches, albeit well contained and relatively simple, touch code that deals with TLS and security. There is always the risk of introducing an unwanted vulnerability or normal regression here. If that happens, the very first thing we need to do is revert the patches and work with upstream to develop a fix. + + In the unlikely case that we encounter regressions, they are probably + going to affect TLS connections when sending/receiving messages. Email + servers nowadays generally offer encrypted connections (via TLS or + STARTTLS), and some still offer plaintext as well. If there is a + problem with TLS and exim4 is configured to fallback to plaintext, + things will still work assuming that the other end also talks plaintext. + Otherwise, we might see reports of undelivered emails. + + Finally, the fix is composed of two patches. The first one prevents + exim4 from discarding the cached credentials when the transport + connection with the primary MX closes, and the second resets headers + before trying to connect to the secondary MX. [ Original Description ] We are experiencing segfaults in exim since upgrading from impish (4.94.2-7ubuntu2 with libgnutls30 3.7.1-5ubuntu1) to jammy (4.95-4ubuntu2 with libgnutls30 3.7.3-4ubuntu1), in _gnutls_trust_list_get_issuer, seemingly in the sender/recipient verify callout during message submission. Typically the initial attempt to submit a message crashes an exim child thread, but the same message is accepted when the sender retries. gdb backtrace: Thread 2.1 "exim4" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fe2f844d080 (LWP 29278)] 0x7fe2f8f3eb2b in _gnutls_trust_list_get_issuer (flags=, issuer=, cert=, list=) at x509/../../../lib/x509/verify-high.c:1026 1026x509/../../../lib/x509/verify-high.c: No such file or directory. (gdb) bt #0 0x7fe2f8f3eb2b in _gnutls_trust_list_get_issuer (flags=, issuer=, cert=, list=) at x509/../../../lib/x509/verify-high.c:1026 #1 gnutls_x509_trust_list_get_issuer (list=list@entry=0x55ef6bd9c260, cert=0x55ef6bd9be20, issuer=issuer@entry=0x7ffc82dba510, flags=flags@entry=16) at x509/../../../lib/x509/verify-high.c:1129 #2 0x7fe2f8f3f679 in gnutls_x509_trust_list_verify_crt2 (list=0x55ef6bd9c260, cert_list=0x7ffc82dba5c0, cert_list_size=, data=, elements=, flags=33554432, voutput=0x7ffc82dba888, func=0x0) at x509/../../../lib/x509/verify-high.c:1522 #3 0x7fe2f8ed7516 in _gnutls_x509_cert_verify_peers (status=0x7ffc82dba888, elements=0, data=0x0, session=0x55ef6c0c1150) at ../../lib/cert-session.c:597 #4 gnutls_certificate_verify_peers (session=0x55ef6c0c1150, data=data@entry=0x0, elements=elements@entry=0, status=status@entry=0x7ffc82dba888) at ../../lib/cert-session.c:776 #5 0x7fe2f8ed8000 in gnutls_certificate_verify_peers2 (session=, status=status@entry=0x7ffc82dba888) at ../../lib/cert-session.c:653 #6 0x55ef6b7698ef in verify_certificate (state=, errstr=0x7ffc82dbaa20) at
[Bug 1977627] [NEW] New upstream microrelease 2.5.12
Public bug reported:
[ Impact ]
* MRE for the latest stable OpenLDAP 2.5.x release, 2.5.12.
This update includes bugfixes only following the SRU policy exception
defined at https://wiki.ubuntu.com/StableReleaseUpdates/OpenLDAPUpdates.
[ Major Changes ]
* See the list of bugs fixed in this release here:
https://lists.openldap.org/hyperkitty/list/openldap-
annou...@openldap.org/thread/LSEQKADYZFFMZJGPEVBRR3OVOY4IOGRA/
[ Test Plan ]
* Upstream gitlab pipeline results:
https://git.openldap.org/openldap/openldap/-/pipelines/4298
* Upstream "call for testing":
https://lists.openldap.org/hyperkitty/list/openldap-
techni...@openldap.org/thread/5ZJEOQSVFQBG5TRLAAF6S5M3VRJH5IAV/
* As described in the MRE wiki page for OpenLDAP, the test plan is to
build the package in bileto and make sure that (1) all build-time tests
pass and (2) all autopkgtest runs (from reverse dependencies) also pass.
[ Where problems could occur ]
* Upstream tests are always executed during build-time. There are many
reverse dependencies whose dep8 tests depend on OpenLDAP so the coverage
is good. Nevertheless, there is always a risk for something to break
since we are dealing with a microrelease upgrade. Whenever a test
failure is detected, we will be on top of it and make sure it doesn't
affect existing users.
[ Other Info ]
* This is a reoccurring MRE. See below for previous MRE's links.
* CVEs fixed by this release:
- CVE-2022-29155, which has already been addressed in Jammy
Current versions in supported releases that got updates:
openldap | 2.5.11+dfsg-1~exp1ubuntu3.1 | jammy-updates | source
Special cases:
- None.
Standing MRE - Consider last updates as template:
- None so far.
As usual we test and prep from the PPA and then push through
SRU/Security as applicable.
** Affects: openldap (Ubuntu)
Importance: High
Status: Invalid
** Affects: openldap (Ubuntu Jammy)
Importance: High
Assignee: Sergio Durigan Junior (sergiodj)
Status: Confirmed
** Tags: needs-mre-backport server-todo
** Also affects: openldap (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: openldap (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: openldap (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: openldap (Ubuntu Jammy)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Changed in: openldap (Ubuntu)
Assignee: Sergio Durigan Junior (sergiodj) => (unassigned)
** Changed in: openldap (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/1977627
Title:
New upstream microrelease 2.5.12
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1977627/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974214] Re: Segfaults on verify callout, in _gnutls_trust_list_get_issuer
** Description changed: [ Impact ] When the user sends a message to someone, if the server responsible for receiving this message defers it, and if there are other possible servers (i.e., other servers listed as secondary MX) to try, exim4 will segfault while trying to connect to the second server. - [ Test Case ] + [ Test Plan ] The test case for this bug is a bit involved. It makes use of the upstream reporter's mail server, which has been configured to defer emails when they come through the primary MX, but accept when they come through the secondary MX. This means that you will need access to port 25 (unfortunately canonistack seems to block it). $ lxc launch ubuntu-daily:jammy exim4-bug1974214 $ lxc shell exim4-bug1974214 # apt update && apt full-upgrade # apt install -y exim4 # dpkg-reconfigure exim4-config ... In the "Mail Server configuration" screen, select "internet site; mail is sent and received directly using SMTP". Leave everything else untouched. # cat > /etc/netplan/99-disable-ipv6.yaml << _EOF_ network: - ethernets: - eth0: - link-local: [ ipv4 ] + ethernets: + eth0: + link-local: [ ipv4 ] _EOF_ # netplan apply # reboot $ lxc shell exim4-bug1974214 # cat > 1.msg << _EOF_ Subject: test this is a test _EOF_ # exim4 -odq -f defe...@example.com geda...@gedalya.net < 1.msg # exim4 -bp - 0m 321 1nxC3o-Ax-AS - geda...@gedalya.net + 0m 321 1nxC3o-Ax-AS + geda...@gedalya.net ... You will have to grab the message ID, which is 1nxC3o-Ax-AS in this case. You have to use this ID in the following command. # exim4 -d+all -q 1nxC3o-Ax-AS 2>&1 | tee /tmp/exim.debug ... # grep SEGV /tmp/exim.debug You should be able to see exim4 signalling the segmentation fault that occurred while attempting to connect to the second server. [ Where problems could occur ] The patches, albeit well contained and relatively simple, touch code that deals with TLS and security. There is always the risk of introducing an unwanted vulnerability or normal regression here. If that happens, the very first thing we need to do is revert the patches and work with upstream to develop a fix. [ Original Description ] We are experiencing segfaults in exim since upgrading from impish (4.94.2-7ubuntu2 with libgnutls30 3.7.1-5ubuntu1) to jammy (4.95-4ubuntu2 with libgnutls30 3.7.3-4ubuntu1), in _gnutls_trust_list_get_issuer, seemingly in the sender/recipient verify callout during message submission. Typically the initial attempt to submit a message crashes an exim child thread, but the same message is accepted when the sender retries. gdb backtrace: Thread 2.1 "exim4" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fe2f844d080 (LWP 29278)] 0x7fe2f8f3eb2b in _gnutls_trust_list_get_issuer (flags=, issuer=, cert=, list=) at x509/../../../lib/x509/verify-high.c:1026 1026x509/../../../lib/x509/verify-high.c: No such file or directory. (gdb) bt #0 0x7fe2f8f3eb2b in _gnutls_trust_list_get_issuer (flags=, issuer=, cert=, list=) at x509/../../../lib/x509/verify-high.c:1026 #1 gnutls_x509_trust_list_get_issuer (list=list@entry=0x55ef6bd9c260, cert=0x55ef6bd9be20, issuer=issuer@entry=0x7ffc82dba510, flags=flags@entry=16) at x509/../../../lib/x509/verify-high.c:1129 #2 0x7fe2f8f3f679 in gnutls_x509_trust_list_verify_crt2 (list=0x55ef6bd9c260, cert_list=0x7ffc82dba5c0, cert_list_size=, data=, elements=, flags=33554432, voutput=0x7ffc82dba888, func=0x0) at x509/../../../lib/x509/verify-high.c:1522 #3 0x7fe2f8ed7516 in _gnutls_x509_cert_verify_peers (status=0x7ffc82dba888, elements=0, data=0x0, session=0x55ef6c0c1150) at ../../lib/cert-session.c:597 #4 gnutls_certificate_verify_peers (session=0x55ef6c0c1150, data=data@entry=0x0, elements=elements@entry=0, status=status@entry=0x7ffc82dba888) at ../../lib/cert-session.c:776 #5 0x7fe2f8ed8000 in gnutls_certificate_verify_peers2 (session=, status=status@entry=0x7ffc82dba888) at ../../lib/cert-session.c:653 #6 0x55ef6b7698ef in verify_certificate (state=, errstr=0x7ffc82dbaa20) at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/tls-gnu.c:2519 #7 0x55ef6b7a5d7b in tls_client_start.constprop.0 (cctx=cctx@entry=0x55ef6be0e688, conn_args=conn_args@entry=0x55ef6bdfe5f8, tlsp=0x55ef6b7f59c0 , errstr=errstr@entry=0x7ffc82dbaa20, cookie=) at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/tls-gnu.c:3593 #8 0x55ef6b78b0ef in smtp_setup_conn (sx=0x55ef6bdfe5e8, suppress_tls=) at transports/smtp.c:2673 #9 0x55ef6b776350 in do_callout (pm_mailfrom=, se_mailfrom=, options=, callout_connect=, callout_overall=, callout=, tf=0x7ffc82dbbc10, host_list=, addr=0x7ffc82dbbdd0) at
[Bug 1971295] Re: Merge net-snmp from Debian unstable for kinetic
Thanks, Bryce. I'll address this one next week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971295 Title: Merge net-snmp from Debian unstable for kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1971295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974214] Re: Segfaults on verify callout, in _gnutls_trust_list_get_issuer
** Tags added: server-todo ** Changed in: exim4 (Ubuntu Jammy) Status: Triaged => In Progress ** Changed in: exim4 (Ubuntu Kinetic) Status: Triaged => In Progress ** Bug watch added: Debian Bug tracker #1004740 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004740 ** Also affects: exim4 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004740 Importance: Unknown Status: Unknown ** Also affects: exim via http://bugs.exim.org/show_bug.cgi?id=2886 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/1974214 Title: Segfaults on verify callout, in _gnutls_trust_list_get_issuer To manage notifications about this bug go to: https://bugs.launchpad.net/exim/+bug/1974214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974214] Re: Segfaults on verify callout, in _gnutls_trust_list_get_issuer
** Description changed: + [ Impact ] + + When the user sends a message to someone, if the server responsible for + receiving this message defers it, and if there are other possible + servers (i.e., other servers listed as secondary MX) to try, exim4 will + segfault while trying to connect to the second server. + + [ Test Case ] + + The test case for this bug is a bit involved. It makes use of the + upstream reporter's mail server, which has been configured to defer + emails when they come through the primary MX, but accept when they come + through the secondary MX. This means that you will need access to port + 25 (unfortunately canonistack seems to block it). + + $ lxc launch ubuntu-daily:jammy exim4-bug1974214 + $ lxc shell exim4-bug1974214 + # apt update && apt full-upgrade + # apt install -y exim4 + # dpkg-reconfigure exim4-config + ... In the "Mail Server configuration" screen, select "internet site; mail is sent and received directly using SMTP". Leave everything else untouched. + # cat > /etc/netplan/99-disable-ipv6.yaml << _EOF_ + network: + ethernets: + eth0: + link-local: [ ipv4 ] + _EOF_ + # netplan apply + # reboot + $ lxc shell exim4-bug1974214 + # cat > 1.msg << _EOF_ + Subject: test + + this is a test + _EOF_ + # exim4 -odq -f defe...@example.com geda...@gedalya.net < 1.msg + # exim4 -bp + 0m 321 1nxC3o-Ax-AS + geda...@gedalya.net + + ... You will have to grab the message ID, which is 1nxC3o-Ax-AS in + this case. You have to use this ID in the following command. + + # exim4 -d+all -q 1nxC3o-Ax-AS 2>&1 | tee /tmp/exim.debug + ... + # grep SEGV /tmp/exim.debug + + You should be able to see exim4 signalling the segmentation fault that + occurred while attempting to connect to the second server. + + [ Where problems could occur ] + + The patches, albeit well contained and relatively simple, touch code + that deals with TLS and security. There is always the risk of + introducing an unwanted vulnerability or normal regression here. If + that happens, the very first thing we need to do is revert the patches + and work with upstream to develop a fix. + + [ Original Description ] + We are experiencing segfaults in exim since upgrading from impish (4.94.2-7ubuntu2 with libgnutls30 3.7.1-5ubuntu1) to jammy (4.95-4ubuntu2 with libgnutls30 3.7.3-4ubuntu1), in _gnutls_trust_list_get_issuer, seemingly in the sender/recipient verify callout during message submission. Typically the initial attempt to submit a message crashes an exim child thread, but the same message is accepted when the sender retries. gdb backtrace: Thread 2.1 "exim4" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fe2f844d080 (LWP 29278)] 0x7fe2f8f3eb2b in _gnutls_trust_list_get_issuer (flags=, issuer=, cert=, list=) at x509/../../../lib/x509/verify-high.c:1026 1026x509/../../../lib/x509/verify-high.c: No such file or directory. (gdb) bt #0 0x7fe2f8f3eb2b in _gnutls_trust_list_get_issuer (flags=, issuer=, cert=, list=) at x509/../../../lib/x509/verify-high.c:1026 #1 gnutls_x509_trust_list_get_issuer (list=list@entry=0x55ef6bd9c260, cert=0x55ef6bd9be20, issuer=issuer@entry=0x7ffc82dba510, flags=flags@entry=16) at x509/../../../lib/x509/verify-high.c:1129 #2 0x7fe2f8f3f679 in gnutls_x509_trust_list_verify_crt2 (list=0x55ef6bd9c260, cert_list=0x7ffc82dba5c0, cert_list_size=, data=, elements=, flags=33554432, voutput=0x7ffc82dba888, func=0x0) at x509/../../../lib/x509/verify-high.c:1522 #3 0x7fe2f8ed7516 in _gnutls_x509_cert_verify_peers (status=0x7ffc82dba888, elements=0, data=0x0, session=0x55ef6c0c1150) at ../../lib/cert-session.c:597 #4 gnutls_certificate_verify_peers (session=0x55ef6c0c1150, data=data@entry=0x0, elements=elements@entry=0, status=status@entry=0x7ffc82dba888) at ../../lib/cert-session.c:776 #5 0x7fe2f8ed8000 in gnutls_certificate_verify_peers2 (session=, status=status@entry=0x7ffc82dba888) at ../../lib/cert-session.c:653 #6 0x55ef6b7698ef in verify_certificate (state=, errstr=0x7ffc82dbaa20) at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/tls-gnu.c:2519 #7 0x55ef6b7a5d7b in tls_client_start.constprop.0 (cctx=cctx@entry=0x55ef6be0e688, conn_args=conn_args@entry=0x55ef6bdfe5f8, tlsp=0x55ef6b7f59c0 , errstr=errstr@entry=0x7ffc82dbaa20, cookie=) at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/tls-gnu.c:3593 #8 0x55ef6b78b0ef in smtp_setup_conn (sx=0x55ef6bdfe5e8, suppress_tls=) at transports/smtp.c:2673 #9 0x55ef6b776350 in do_callout (pm_mailfrom=, se_mailfrom=, options=, callout_connect=, callout_overall=, callout=, tf=0x7ffc82dbbc10, host_list=, addr=0x7ffc82dbbdd0) at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/verify.c:677 #10 verify_address (vaddr=, fp=, options=,
Re: [Bug 1975766] Re: Backport postgresql as MRE for bionic, focal, jammy (August)
On Friday, June 03 2022, Athos Ribeiro wrote: > Then, in August, we are using this bug instead of filing the usual template > as the in in > https://bugs.launchpad.net/ubuntu/+source/postgresql-14/+bug/1973627 > right? Sounds good to me. We can edit this bug's description when we start working on the MRE. -- Sergio GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975766 Title: Backport postgresql as MRE for bionic, focal, jammy (August) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-10/+bug/1975766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975766] Re: Backport postgresql as MRE for bionic, focal, impish, jammy (August)
** No longer affects: postgresql-10 (Ubuntu Focal) ** No longer affects: postgresql-10 (Ubuntu Impish) ** No longer affects: postgresql-10 (Ubuntu Jammy) ** No longer affects: postgresql-12 (Ubuntu Bionic) ** No longer affects: postgresql-12 (Ubuntu Impish) ** No longer affects: postgresql-12 (Ubuntu Jammy) ** Summary changed: - Backport postgresql as MRE for bionic, focal, impish, jammy (August) + Backport postgresql as MRE for bionic, focal, jammy (August) ** Description changed: - Backport postgresql as MRE for bionic, focal, impish, jammy + Backport postgresql as MRE for bionic, focal, jammy ** No longer affects: postgresql-13 (Ubuntu) ** No longer affects: postgresql-13 (Ubuntu Bionic) ** No longer affects: postgresql-13 (Ubuntu Focal) ** No longer affects: postgresql-13 (Ubuntu Impish) ** No longer affects: postgresql-13 (Ubuntu Jammy) ** Also affects: postgresql-14 (Ubuntu) Importance: Undecided Status: New ** Also affects: postgresql-10 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: postgresql-12 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: postgresql-14 (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: postgresql-12 (Ubuntu Jammy) ** No longer affects: postgresql-10 (Ubuntu Jammy) ** Changed in: postgresql-10 (Ubuntu) Status: New => Invalid ** Changed in: postgresql-12 (Ubuntu) Status: New => Invalid ** Changed in: postgresql-14 (Ubuntu) Status: New => Invalid ** Changed in: postgresql-14 (Ubuntu) Milestone: None => ubuntu-22.08 ** Changed in: postgresql-14 (Ubuntu Jammy) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) ** Changed in: postgresql-10 (Ubuntu Bionic) Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro) ** Changed in: postgresql-12 (Ubuntu Focal) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975766 Title: Backport postgresql as MRE for bionic, focal, jammy (August) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-10/+bug/1975766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912256] Re: Missing channel binding prevents authentication to ActiveDirectory
Thank you, Christian. As discussed with Andreas, I've added a cyrus-sasl2 task to this bug and assigned him to it. This bug is probably going to involve modifications on cyrus-sasl2 only; after channel binding has been implemented there, we should be able to enable it in openldap by just rebuilding the package. Either way, I'm leaving the openldap task open and assigned to myself just in case. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912256 Title: Missing channel binding prevents authentication to ActiveDirectory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1912256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912256] Re: Missing channel binding prevents authentication to ActiveDirectory
** Also affects: cyrus-sasl2 (Ubuntu) Importance: Undecided Status: New ** Changed in: cyrus-sasl2 (Ubuntu) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) ** Changed in: cyrus-sasl2 (Ubuntu) Assignee: Sergio Durigan Junior (sergiodj) => Andreas Hasenack (ahasenack) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912256 Title: Missing channel binding prevents authentication to ActiveDirectory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1912256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974214] Re: Segfaults on verify callout, in _gnutls_trust_list_get_issuer
Thank you for testing the package from the PPA and providing feedback, Malcom and Raf. I took some time today to try and come up with a reproducer for the bug, since this is one of the requirements for a successful SRU to Jammy. So far I haven't had any success, but I'll try to continue working on this tomorrow. I found some possible reproducer in the upstream bug but none of them worked OOTB for me. Meanwhile, if any of you already have a simple reproducer that'd be great. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974214 Title: Segfaults on verify callout, in _gnutls_trust_list_get_issuer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1974214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971298] Re: Merge nmap from Debian unstable for kinetic
Nothing to merge from Debian yet. I'm moving this to July. ** Changed in: nmap (Ubuntu) Milestone: ubuntu-22.05 => ubuntu-22.07 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971298 Title: Merge nmap from Debian unstable for kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nmap/+bug/1971298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969629] Re: Apache 2.4.x: mod_http2 sends empty response after MaxRequestsPerChild
Verification for Impish.
First, verifying that the bug is reproducible:
# apt policy apache2
apache2:
Installed: 2.4.48-3.1ubuntu3.3
Candidate: 2.4.48-3.1ubuntu3.3
Version table:
*** 2.4.48-3.1ubuntu3.3 500
500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu impish-security/main amd64
Packages
100 /var/lib/dpkg/status
2.4.48-3.1ubuntu3 500
500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages
# while true; do if [[ $(curl -o /dev/null -s -k --http2 http://localhost/ -w
'%{size_download}') == 0 ]]; then echo "BUG DETECTED"; break; fi; done
BUG DETECTED
Now, installing the package from -proposed and verifying that it fixes
the bug:
# apt policy apache2
apache2:
Installed: 2.4.48-3.1ubuntu3.4
Candidate: 2.4.48-3.1ubuntu3.4
Version table:
*** 2.4.48-3.1ubuntu3.4 500
500 http://archive.ubuntu.com/ubuntu impish-proposed/main amd64 Packages
100 /var/lib/dpkg/status
2.4.48-3.1ubuntu3.3 500
500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu impish-security/main amd64
Packages
2.4.48-3.1ubuntu3 500
500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages
# while true; do if [[ $(curl -o /dev/null -s -k --http2 http://localhost/ -w
'%{size_download}') == 0 ]]; then echo "BUG DETECTED"; break; fi; done
^C
#
As can be seen, the loop did not return right away and instead had to be
manually stopped.
This concludes the verification for Impish.
** Tags removed: server-todo verification-needed verification-needed-bionic
verification-needed-focal verification-needed-impish
** Tags added: verification-done-bionic verification-done-focal
verification-done-impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969629
Title:
Apache 2.4.x: mod_http2 sends empty response after MaxRequestsPerChild
To manage notifications about this bug go to:
https://bugs.launchpad.net/apache2/+bug/1969629/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969629] Re: Apache 2.4.x: mod_http2 sends empty response after MaxRequestsPerChild
Verification for Focal.
First, verifying that the bug is reproducible:
# apt policy apache2
apache2:
Installed: 2.4.41-4ubuntu3.10
Candidate: 2.4.41-4ubuntu3.10
Version table:
*** 2.4.41-4ubuntu3.10 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
100 /var/lib/dpkg/status
2.4.41-4ubuntu3 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
# while true; do if [[ $(curl -o /dev/null -s -k --http2 http://localhost/ -w
'%{size_download}') == 0 ]]; then echo "BUG DETECTED"; break; fi; done
BUG DETECTED
Now, installing the package from -proposed and verifying that it fixes
the bug:
# apt policy apache2
apache2:
Installed: 2.4.41-4ubuntu3.11
Candidate: 2.4.41-4ubuntu3.11
Version table:
*** 2.4.41-4ubuntu3.11 500
500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
100 /var/lib/dpkg/status
2.4.41-4ubuntu3.10 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
2.4.41-4ubuntu3 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
# while true; do if [[ $(curl -o /dev/null -s -k --http2 http://localhost/ -w
'%{size_download}') == 0 ]]; then echo "BUG DETECTED"; break; fi; done
^C
#
As can be seen, the loop did not return right away and instead had to be
manually stopped.
This concludes the verification for Focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969629
Title:
Apache 2.4.x: mod_http2 sends empty response after MaxRequestsPerChild
To manage notifications about this bug go to:
https://bugs.launchpad.net/apache2/+bug/1969629/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969629] Re: Apache 2.4.x: mod_http2 sends empty response after MaxRequestsPerChild
Sorry about the delay. Here's the verification for Bionic:
First, verifying that the bug is reproducible:
# apt policy apache2
apache2:
Installed: 2.4.29-1ubuntu4.22
Candidate: 2.4.29-1ubuntu4.22
Version table:
*** 2.4.29-1ubuntu4.22 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
100 /var/lib/dpkg/status
2.4.29-1ubuntu4 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
# while true; do if [[ $(curl -o /dev/null -s -k --http2 http://localhost/ -w
'%{size_download}') == 0 ]]; then echo "BUG DETECTED"; break; fi; done
BUG DETECTED
Now, installing the package from -proposed and verifying that it fixes
the bug:
# apt policy apache2
apache2:
Installed: 2.4.29-1ubuntu4.23
Candidate: 2.4.29-1ubuntu4.23
Version table:
*** 2.4.29-1ubuntu4.23 500
500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages
100 /var/lib/dpkg/status
2.4.29-1ubuntu4.22 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
2.4.29-1ubuntu4 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
# while true; do if [[ $(curl -o /dev/null -s -k --http2 http://localhost/ -w
'%{size_download}') == 0 ]]; then echo "BUG DETECTED"; break; fi; done
^C
#
As can be seen, the loop did not return right away and instead had to be
manually stopped.
This concludes the verification for Bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969629
Title:
Apache 2.4.x: mod_http2 sends empty response after MaxRequestsPerChild
To manage notifications about this bug go to:
https://bugs.launchpad.net/apache2/+bug/1969629/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973107] Re: Failure to link a PIE binary on ppc64el (FTBFS)
I had to revert the patch in Kinetic because it was causing golang-1.18.2 to fail to compile itself on ppc64el. After some more investigation and help from upstream, I finally have the couple of patches needed to be backported in order to fix this bug fully. That's why I'm setting this bug as In Progress again. ** Changed in: golang-1.18 (Ubuntu Kinetic) Status: Fix Released => 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/1973107 Title: Failure to link a PIE binary on ppc64el (FTBFS) To manage notifications about this bug go to: https://bugs.launchpad.net/golang/+bug/1973107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
