[Bug 1877504] Re: libmysqlclient21 use of /usr/share/mysql collides with mariadb-server-core-10.3's use of the same directory
> We would - for example - in Ubuntu have a problem with an old libmysqlclient that is installed along a new mysql-8 that brings newer incompatible charsets to /usr/share/mysql. Isn't this just an assumption? AIUI, the only thing that is clear is that MariaDB doesn't understand the latest data schema for /usr/share/mysql that MySQL uses. On "old libmysqlclient", it's completely normal for /usr/share/* to update schemas in a way that older versions might not understand. What matters is that we (neither Debian nor Ubuntu) do not ship a package in a single distribution release that reads but doesn't understand it, including during an upgrade. AIUI, this is just MariaDB? If MariaDB can't understand MySQL's /usr/share/mysql/ schema, surely it should use a different directory? -- 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/1877504 Title: libmysqlclient21 use of /usr/share/mysql collides with mariadb-server- core-10.3's use of the same directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1877504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969901] Re: network-manager fails to renew ipv6 address
> The exact conditions for reproducing this bug on mixed IPv4/IPv6 networks are not known Looking at the upstream commit description, isn't it just that a DHCPv6 lease expires and the server NAKs a request for the same IP again? Or is that not sufficient to trigger the problem. In any case, I appreciate there might be difficulty in testing the fix, but what's the actual criteria you propose to use to decide when the bug is to be marked verification-done-bionic? ** Also affects: network-manager (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu Bionic) 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/1969901 Title: network-manager fails to renew ipv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
Hello Shih-Yuan, or anyone else affected, Accepted software-properties into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/software- properties/0.99.22.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Description changed: - Impact software-properties-gtk hit an exception when dealing some drivers - Test Case On a Dell XPS 13 9320 enable ppa:oem-solutions-group/intel-ipu6 and try to install libcamhal-ipu6ep0 using software-properties-gtk https://errors.ubuntu.com/problem/d3c26abd1d80970615ad06cff24972cee3001e57 should not include reports on the new version - Regression potential The change make the driver code ignore one extra type of error, it shouldn't impact on any of the already working cases. Ensure that drivers that were hitting the error correctly install now + [racb] It's possible that we accidentally catch and hide a real error + due to an unrelated TypeError exception being raised inside the try + block. + 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center software-properties-gtk 0.99.22 3) What you expected to happen No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. 4) What happened instead It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969460 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834250] Re: update-grub complains about non-existent drives (due to cardreader)
Hello Scott, or anyone else affected, Accepted lvm2 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lvm2/2.03.07-1ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: lvm2 (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834250 Title: update-grub complains about non-existent drives (due to cardreader) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1834250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976198] Please test proposed package
Hello Lin, or anyone else affected, Accepted libsdl2 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libsdl2/2.0.20+dfsg-2ubuntu1.22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976198 Title: [SRU] Possible missing dependencies of libsdl2-dev in Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsdl2/+bug/1976198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976198] Re: [SRU] Possible missing dependencies of libsdl2-dev in Jammy
In the meantime a straightforward workaround is available to users affected by this bug, which is to install the required dependencies manually. ** Changed in: libsdl2 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976198 Title: [SRU] Possible missing dependencies of libsdl2-dev in Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsdl2/+bug/1976198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976198] Re: [SRU] Possible missing dependencies of libsdl2-dev in Jammy
This looks fine and I'm accepting. I wonder though if we can stage it to bundle it with an update that directly impacts users? Otherwise every qemu user will have to download this update for no benefit to them. I don't feel too strongly about this. I'll set the tag, but if time has passed and nothing has appeared to bundle it with, or if another SRU team member thinks it needs releasing earlier, please go ahead and drop the tag. ** Tags added: block-proposed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976198 Title: [SRU] Possible missing dependencies of libsdl2-dev in Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsdl2/+bug/1976198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968228] Re: RTD collision with opcache
Hello Matt, or anyone else affected, Accepted php7.4 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/php7.4/7.4.3-4ubuntu2.11 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: php7.4 (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal ** Changed in: php7.4 (Ubuntu) Status: In Progress => Invalid ** Changed in: php7.4 (Ubuntu Focal) Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968228 Title: RTD collision with opcache To manage notifications about this bug go to: https://bugs.launchpad.net/php/+bug/1968228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973733] Proposed package upload rejected
An upload of cups to focal-proposed has been rejected from the upload queue for the following reason: "As requested in https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973733/comments/4;. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973733 Title: no change rebuild to get security update out on riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962453] Please test proposed package
Hello Utkarsh, or anyone else affected, Accepted keyutils into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/keyutils/1.6-6ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962453 Title: Apply default TTL to records obtained from getaddrinfo() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962453] Re: Apply default TTL to records obtained from getaddrinfo()
Hello Utkarsh, or anyone else affected, Accepted keyutils into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/keyutils/1.6.1-2ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: keyutils (Ubuntu Impish) Status: Incomplete => Fix Committed ** Tags added: verification-needed-impish ** Changed in: keyutils (Ubuntu Focal) Status: Incomplete => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962453 Title: Apply default TTL to records obtained from getaddrinfo() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890263] Proposed package upload rejected
An upload of php7.4 to focal-proposed has been rejected from the upload queue for the following reason: "See previous comment". ** Changed in: php7.4 (Ubuntu Focal) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890263 Title: release upgrade does not move to the new php apache mod To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-defaults/+bug/1890263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890263] Re: release upgrade does not move to the new php apache mod
I discussed this with other members of the SRU team last week. My notes: "...that would be a maintenance action being fixed in an SRU, and may pull the rug from under users’ feet by forcibly upgrading them after it has been working on Focal for years. The security implications should be dealt with separately." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890263 Title: release upgrade does not move to the new php apache mod To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-defaults/+bug/1890263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968228] Proposed package upload rejected
An upload of php7.4 to focal-proposed has been rejected from the upload queue for the following reason: "See previous comment". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968228 Title: RTD collision with opcache To manage notifications about this bug go to: https://bugs.launchpad.net/php/+bug/1968228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933363] Proposed package upload rejected
An upload of reprepro to bionic-proposed has been rejected from the upload queue for the following reason: "Includes changes not normally acceptable for an SRU with no explanation.". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933363 Title: Backport reprepro fixes to focal..hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/reprepro/+bug/1933363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802483] Please test proposed package
Hello Marco, or anyone else affected, Accepted libnotify into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libnotify/0.7.7-3ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802483 Title: Notifications emitted by a snap with local files or desktop files use wrong namespace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace
Sorry I missed your reply, but to make progress I just tweaked the version string in a new upload that I signed. It's otherwise identical. So I'll just accept that. ** Changed in: libnotify (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802483 Title: Notifications emitted by a snap with local files or desktop files use wrong namespace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936302] Please test proposed package
Hello jeremyszu, or anyone else affected, Accepted libfprint into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libfprint/1:1.90.2+tod1-0ubuntu1~20.04.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936302 Title: To support elanmoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1936302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936302] Re: To support elanmoc driver
Unsubscribed sponsors. ** Changed in: libfprint (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936302 Title: To support elanmoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1936302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936302] Re: To support elanmoc driver
Hello jeremyszu, or anyone else affected, Accepted libfprint into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libfprint/1:1.90.7+git20210222+tod1-0ubuntu4~21.10.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libfprint (Ubuntu Impish) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936302 Title: To support elanmoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1936302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace
Apart from that the Bionic upload looks fine. I note that notification- Handle-snap-applications.patch is added over the SRU for Focal, but that makes sense as that functionality is required for the other patches. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802483 Title: Notifications emitted by a snap with local files or desktop files use wrong namespace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace
+libnotify (0.7.7-3ubuntu0.20.04.1) bionic; urgency=medium Shouldn't this be ...0.18.04.1? The version number used will work, but is confusing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802483 Title: Notifications emitted by a snap with local files or desktop files use wrong namespace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972075] Re: Blank screen when viewing GL-accelerated virtio screen on 22.04
Hello Max, or anyone else affected, Accepted libvirt into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libvirt/8.0.0-1ubuntu7.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libvirt (Ubuntu Jammy) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972075 Title: Blank screen when viewing GL-accelerated virtio screen on 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1972075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954595] Please test proposed package
Hello Honza, or anyone else affected, Accepted breezy-debian into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/breezy- debian/2.8.10ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954595 Title: bzr dh-make crash - no attribute 'initialize_on_transport' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-packaging-guide/+bug/1954595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954595] Re: bzr dh-make crash - no attribute 'initialize_on_transport'
Hello Honza, or anyone else affected, Accepted breezy-debian into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/breezy- debian/2.8.32ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: breezy-debian (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal ** Changed in: breezy-debian (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954595 Title: bzr dh-make crash - no attribute 'initialize_on_transport' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-packaging-guide/+bug/1954595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973816] Re: Deja Dup's Google support will break in September 2022 for versions < 43.3
The fix for this is stuck in kinetic-proposed on a component mismatch, so I'm changing the status to Fix Committed to reflect that. If the upload is pulled from kinetic-proposed then we'll end up with a higher version in Jammy than in Kinetic so I think it's important to correctly note that it hasn't landed yet. ** Changed in: deja-dup (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973816 Title: Deja Dup's Google support will break in September 2022 for versions < 43.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1973816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973816] Please test proposed package
Hello Michael, or anyone else affected, Accepted deja-dup into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/deja-dup/42.9-1ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: deja-dup (Ubuntu) Status: Fix Released => 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/1973816 Title: Deja Dup's Google support will break in September 2022 for versions < 43.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1973816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Please test proposed package
Hello Matthew, or anyone else affected, Accepted ec2-hibinit-agent into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ec2-hibinit- agent/1.0.0-0ubuntu4~18.04.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Re: Hibernation fails when an additional swapfile is added due to priority mismatch
Unsubscribing sponsors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Please test proposed package
Hello Matthew, or anyone else affected, Accepted ec2-hibinit-agent into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ec2-hibinit-agent/1.0.0-0ubuntu9.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ec2-hibinit-agent (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Please test proposed package
Hello Matthew, or anyone else affected, Accepted ec2-hibinit-agent into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ec2-hibinit- agent/1.0.0-0ubuntu11.21.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ec2-hibinit-agent (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Re: Hibernation fails when an additional swapfile is added due to priority mismatch
Hello Matthew, or anyone else affected, Accepted ec2-hibinit-agent into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ec2-hibinit- agent/1.0.0-0ubuntu11.22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ec2-hibinit-agent (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy ** Changed in: ec2-hibinit-agent (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973296] Re: [UBUNTU 20.04] OpenCryptoki >= 3.13 with upgraded EP11 host library - Dilithium support not available
Accepted, but please adjust your Test Plan to actually test the previous missing *functionality* of opencryptoki+EP11+Dilithium from a user's perspective. This means something like "verify that a user can use their token to authenticate against X" rather than "verify that the library supports X". Just checking that it's detected and _might_ work is insufficient, IMHO. Because if it turns out that a further patch is needed to make it actually work for users, we shouldn't be pushing updates multiple times to unaffected users because we didn't test the stack all the way through. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973296 Title: [UBUNTU 20.04] OpenCryptoki >= 3.13 with upgraded EP11 host library - Dilithium support not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1973296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973296] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted opencryptoki into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/opencryptoki/3.13.0+dfsg-0ubuntu5.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973296 Title: [UBUNTU 20.04] OpenCryptoki >= 3.13 with upgraded EP11 host library - Dilithium support not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1973296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973296] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted opencryptoki into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/opencryptoki/3.17.0+dfsg+20220202.b40982e-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: opencryptoki (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973296 Title: [UBUNTU 20.04] OpenCryptoki >= 3.13 with upgraded EP11 host library - Dilithium support not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1973296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973296] Re: [UBUNTU 20.04] OpenCryptoki >= 3.13 with upgraded EP11 host library - Dilithium support not available
Hello bugproxy, or anyone else affected, Accepted opencryptoki into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/opencryptoki/3.16.0+dfsg-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: opencryptoki (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-impish ** Changed in: opencryptoki (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973296 Title: [UBUNTU 20.04] OpenCryptoki >= 3.13 with upgraded EP11 host library - Dilithium support not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1973296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973564] Please test proposed package
Hello Ted, or anyone else affected, Accepted xdg-desktop-portal-gtk into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xdg- desktop-portal-gtk/1.6.0-1ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973564 Title: File dialog doesn't return current filter in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1973564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973564] Re: File dialog doesn't return current filter in Ubuntu 20.04
Hello Ted, or anyone else affected, Accepted xdg-desktop-portal into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xdg- desktop-portal/1.6.0-1ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973564 Title: File dialog doesn't return current filter in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1973564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973229] Re: Update freerdp2 to 2.7.0
Thank you for the further details Jeremy. Seb, Jeremy and I discussed this more out of band, with me wearing my TB hat as this request matches "other cases where such upstream automatic testing is not available, exceptions must still be approved by at least one member of the Ubuntu Technical Board" according to https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases. IMHO, I think we need to work on the test plan to meet the spirit of the requirements set by the TB previously in that paragraph, so Jeremy will work on that with me and then we'll update the bug. ** Changed in: freerdp2 (Ubuntu Jammy) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973229 Title: Update freerdp2 to 2.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1973229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973229] Re: Update freerdp2 to 2.7.0
For reference, here's what I see with some of the noise removed: 1001_keep-symbol-DumpThreadHandles-if-debugging-is-disabled.patch is carried forward. The change to winpr/libwinpr/thread/thread.c is now gone. The change to winpr/include/winpr/thread.h remains. All other patches previously present are adopted in the new upstream version exactly. The new upstream version brings in the following 13 additional changes: -: - > 27: 572c63a9f Supports 10bit X11 color (BGRX32 only) -: - > 28: 62937807e Changelog -: - > 29: 0f9efe197 Fixed /gt:xxx settings -: - > 30: 0a6b999c5 Updated Changelog -: - > 31: f773d9759 Update header with missing flag -: - > 32: 66ff8cf2a Added support for AUDIO_PLAYBACK_DVC -: - > 33: 4308d8e91 fix x11 black RAIL window when connect to server 2019 -: - > 34: e8010231c Changelog -: - > 35: 70bd7f010 Update default android build config -: - > 36: 52f3e5139 Cleaned up ntlm_fetch_ntlm_v2_hash -: - > 38: c263ff19e Updated changelog -: - > 39: 32b8db302 Added missing WINPR_API -: - > 40: 40ee5d3bc Updated for 2.7.0 release Of these, the changes mentioning the changelog can be discounted from concern as they definitely don't contain any functional changes. Also the final change "Updated for 2.7.0 release" contains only the metadata change for the version number. That leaves 8 commits being brought in here. Also there is the new patchset being cherry-picked from upstream commit after they tagged 2.7.0: 0001-Refactor-thread-condition-logic.patch 0002-Do-not-mark-WinPR-implementation-of-ExitThread-as-no.patch 0003-Fixed-leak-in-TestPipeCreateNamedPipeOverlapped.patch 0004-Cleaned-up-NamedPipeOverlapped-test.patch On the packaging side, some new symbols are added against 2.7.0+dfsg1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973229 Title: Update freerdp2 to 2.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1973229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973229] Re: Update freerdp2 to 2.7.0
Oh I see them now. Sorry for the noise. I'll delete this and the last comment in a bit to try and keep the noise in the bug down. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973229 Title: Update freerdp2 to 2.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1973229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973229] Re: Update freerdp2 to 2.7.0
> The final change is backporting another patch set (from the stable branch after the 2.7.0 release). Where is this change in the upload please? I haven't managed to spot it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973229 Title: Update freerdp2 to 2.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1973229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973229] Re: Update freerdp2 to 2.7.0
** Changed in: freerdp2 (Ubuntu Jammy) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973229 Title: Update freerdp2 to 2.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1973229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973229] Re: Update freerdp2 to 2.7.0
This request doesn't seem to fit SRU policy. Could you please provide specifics that explain why users need the update beyond "bug fixes", and a plan to test that the specific issues users are experiencing are fixed? Further, I expect one bug per issue being fixed in the diff so they can be individually justified under SRU policy and verified before the SRU is released, and no other changes. To skip that, SRU policy details the conditions required at https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases. If this update will meet those conditions, please could you explain how? If you're looking for a complete exception from the normal SRU requirements, then I think you need more justification then just "few more bug fixes". For example, is the package completely broken, and if so, how? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973229 Title: Update freerdp2 to 2.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1973229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890263] Re: release upgrade does not move to the new php apache mod
Good job finding a solution that works! What's the status on Debian accepting something like this? This also seems like a pattern that would be useful elsewhere. Is it already an established pattern? I'm reluctant to take this for an SRU without having confidence that we won't end up iterating on it in our stable releases. It feels like it should be well established and socialized first to flush out any issues, and seems odd to me that I've not seen this pattern used before given its wide applicability. If it's a correct and good solution then I'd expect to be familiar with it. If it's new ground then maybe we should get general acceptance across the archive and in Debian for this pattern before SRUing it. What am I missing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890263 Title: release upgrade does not move to the new php apache mod To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-defaults/+bug/1890263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973733] Re: no change rebuild to get security update out on riscv64
Ah - is it that the same version is now built and published in Groovy and we can't safely copy the binary backwards? If so, then my second question of why this isn't going in via focal-security still stands. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973733 Title: no change rebuild to get security update out on riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Please test proposed package
Hello Nicolas, or anyone else affected, Accepted openssl into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/1.1.1-1ubuntu2.1~18.04.18 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
Thank you to all involved in the discussion and analysis for carefully considering the regression risk there. Regardless of the final decision, I think the thoughtful consideration makes this an exemplary SRU. I confirmed that the new upload is simply a straightforward review on top of the security update, so Łukasz's SRU review and decision stands and I'm accepting this into bionic-proposed. ** Changed in: openssl (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973733] Re: no change rebuild to get security update out on riscv64
I'm not sure I follow. I see a retry button for the failed riscv64 build. Can't we just hit that? If there's some reason that won't work, then why is this not going through the security sponsorship queue? If we do it as an SRU, then it'll hit focal-updates only, and focal-security will be left behind. What's the plan for that? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973733 Title: no change rebuild to get security update out on riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971932] Re: error in rsync protocol data stream
This reminds me of bug 1384503, and a search reveals some other bugs that may be related too. Perhaps it's a recurrence of the same underlying issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971932 Title: error in rsync protocol data stream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1971932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933363] Re: Backport reprepro fixes to focal..hirsute
The SRUs already landed related to minor version bumps (eg. 5.3.0-1.1 to 5.3.0-1.3~ubuntu20.04) and the entire set of changes were accounted and considered for SRU purposes by the SRU documentation provided. This doesn't apply to the Bionic Unapproved upload though, as 5.1.1-1 to 5.3.0-1.3~ubuntu18.04.1 is more of a major change and some of the changes look like they may be functional and unsuitable for SRU (eg. "drop "FILE LOCATION" headers from Contents files"). If you'd like a backport to be considered under the SRU process, please update the SRU description to provide appropriate justification so the SRU team can properly consider this. ** Changed in: reprepro (Ubuntu Bionic) 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/1933363 Title: Backport reprepro fixes to focal..hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/reprepro/+bug/1933363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970737] Re: Stalled IO Operations During MySQL Tests (with sysbench)
** Tags removed: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970737 Title: Stalled IO Operations During MySQL Tests (with sysbench) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1970737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971788] Re: Failure to enable SSL out of the box when in fips mode
** Tags removed: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971788 Title: Failure to enable SSL out of the box when in fips mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1971788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962225] Re: preinst check that kernel revision < 255 now does more harm than good
Hello Michael, or anyone else affected, Accepted glibc into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glibc/2.27-3ubuntu1.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: glibc (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962225 Title: preinst check that kernel revision < 255 now does more harm than good To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1962225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892825] Re: update-locale not perform correctly sanity checks
Hello bs, or anyone else affected, Accepted glibc into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glibc/2.27-3ubuntu1.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: glibc (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892825 Title: update-locale not perform correctly sanity checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1892825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Please test proposed package
Hello Khaled, or anyone else affected, Accepted klibc into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/klibc/2.0.4-9ubuntu2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
It's not clear to me if upstream have accepted the patch. If not,
https://lists.zytor.com/archives/klibc/2021-December/004635.html sounds
like it's a deliberate upstream design decision not to.
In Ubuntu, we might decide to maintain the patch as a delta but then
drop that delta in subsequent releases when we no longer need that
functionality. This is already the case for >18.04, and for 18.04 we're
adding the delta in an SRU.
Therefore, Won't Fix for Ubuntu for the development release I think is
appropriate. It it does get fixed upstream then our status can be
updated, but either way it's not really relevant to Ubuntu any more.
In comment 22 I asked:
> ...would it be practical and/or useful to verify that, with a timeout
of 2s, a DHCP reply sent after 1.5s works, but a DHCP reply sent after
2.5s does not?
Have you covered this in your test plan please? I don't see this
discussed anywhere.
Please could you also update the Test Plan section in the SRU
description to cover the testing you are committing to do?
Apart from that, +1, so I'll accept now to save us time. We do need to
continue discussion to resolve the Test Plan though. That needs to be
resolved to the SRU team's satisfaction before we will release the build
to the updates pocket.
** Description changed:
[Impact]
In some cases, ipconfig can take a longer time than the user-specified
timeouts, causing unexpected delays.
[Test Plan]
- Any situation where ipconfig encounters an error sending the DHCP packet, it
will automatically set a delay of 10 seconds, which could be longer than the
user-specified timeout. It can be reproduced by creating a dummy interface and
attempting to run ipconfig on it with a timeout value of less than 10:
+
+ [racb: pending agreement with the SRU team; please see comment 37]
+
+ Any situation where ipconfig encounters an error sending the DHCP
+ packet, it will automatically set a delay of 10 seconds, which could be
+ longer than the user-specified timeout. It can be reproduced by creating
+ a dummy interface and attempting to run ipconfig on it with a timeout
+ value of less than 10:
# ip link add eth1 type dummy
# date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
Thu Nov 18 04:46:13 EST 2021
IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
IP-Config: no response after 2 secs - giving up
Thu Nov 18 04:46:23 EST 2021
^ Notice above, ipconfig thinks that it waited 2 seconds, but the
timestamps show an actual delay of 10 seconds.
[Where problems could occur]
Please see reproduction steps above. We are seeing this in production too
(see comment #2).
[Other Info]
A patch to fix the issue is being proposed here. It is a safe fix - it only
checks before going into sleep that the timeout never exceeds the
user-requested value.
[Original Description]
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again later"
at time equal now + 10 seconds by setting
s->expire = now + 10;
This can happen at any time during the main event loop, which can end up
extending the user-specified timeout if "now + 10" is greater than
"start_time + user-specified-timeout".
I believe a patch like the following is needed to avoid this problem:
--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)
if (timeout > s->expire - now.tv_sec)
timeout = s->expire - now.tv_sec;
+
+ /* Compensate for already-lost time */
+ gettimeofday(, NULL);
+ if (now.tv_sec + timeout > start + loop_timeout) {
+ timeout = loop_timeout - (now.tv_sec - start);
+ printf("Lowered timeout to match user request
= (%d s) \n", timeout);
+ }
}
I believe the current behaviour is buggy. This is confirmed when the
following line is executed:
if (loop_timeout >= 0 &&
now.tv_sec - start >= loop_timeout) {
printf("IP-Config: no response after %d "
"secs - giving up\n", loop_timeout);
rc = -1;
goto bail;
}
'loop_timeout' is the user-specified time-out. With a value of 2, in
case of error, this line prints:
IP-Config: no response after 2 secs - giving up
So it thinks that it waited 2 seconds - however, in reality it had
actually waited for 10 seconds.
The suggested code-change ensures that the
[Bug 1968039] Re: DEP-8 test fails in Focal after Corosync update
I think this is blocked pending bug 1874719? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968039 Title: DEP-8 test fails in Focal after Corosync update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1968039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971565] Re: charm no longer works with latest mysql-router version
** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971565 Title: charm no longer works with latest mysql-router version To manage notifications about this bug go to: https://bugs.launchpad.net/charm-mysql-router/+bug/1971565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927100] Update Released
The verification of the Stable Release Update for gvfs has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927100 Title: Slow file dialogs, open and save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1927100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927100] Re: Slow file dialogs, open and save
Thank you for taking the time to do this! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927100 Title: Slow file dialogs, open and save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1927100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
** Changed in: xl2tpd (Ubuntu Jammy) Status: Fix Released => 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/1951832 Title: xl2tpd "Can not find tunnel" in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lto-disabled-list/+bug/1951832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
** Tags removed: verification-done verification-done-jammy ** Tags added: lto verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951832 Title: xl2tpd "Can not find tunnel" in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lto-disabled-list/+bug/1951832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971091] Re: [SRU] kstars 3.5.7 crashes with segfault on startup on 22.04 and 22.10
Hello Rik, or anyone else affected, Accepted kstars into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/kstars/5:3.5.7-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: kstars (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy ** Tags removed: verification-needed verification-needed-jammy ** Tags added: lto regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971091 Title: [SRU] kstars 3.5.7 crashes with segfault on startup on 22.04 and 22.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kstars/+bug/1971091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969125] Please test proposed package
Hello Lucas, or anyone else affected, Accepted ubuntu-advantage-tools into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/27.8~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969125 Title: [SRU] ubuntu-advantage-tools (27.7 -> 27.8) Xenial, Bionic, Focal, Impish, Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1969125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969125] Please test proposed package
Hello Lucas, or anyone else affected, Accepted ubuntu-advantage-tools into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/27.8~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-advantage-tools (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969125 Title: [SRU] ubuntu-advantage-tools (27.7 -> 27.8) Xenial, Bionic, Focal, Impish, Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1969125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969125] Please test proposed package
Hello Lucas, or anyone else affected, Accepted ubuntu-advantage-tools into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/27.8~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-advantage-tools (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969125 Title: [SRU] ubuntu-advantage-tools (27.7 -> 27.8) Xenial, Bionic, Focal, Impish, Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1969125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969125] Re: [SRU] ubuntu-advantage-tools (27.7 -> 27.8) Xenial, Bionic, Focal, Impish, Jammy
Hello Lucas, or anyone else affected, Accepted ubuntu-advantage-tools into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/27.8~21.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-advantage-tools (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed-impish ** Changed in: ubuntu-advantage-tools (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969125 Title: [SRU] ubuntu-advantage-tools (27.7 -> 27.8) Xenial, Bionic, Focal, Impish, Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1969125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
Thank you msaxl and Adrian for performing the verification! I've also verified in the build log that lto optimisation is now missing. For example: cc -DDEBUG_PPPD -DTRUST_PPPD_TO_DIE -O2 -fno-builtin -Wall -DSANITY -DLINUX -I/include/ -DIP_ALLOCATION -DUSE_KERNEL -g -O2 -ffile-prefix- map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector- strong -Wformat -Werror=format-security -DDEBUG_PPPD -DTRUST_PPPD_TO_DIE -O2 -fno-builtin -Wall -DSANITY -DLINUX -I/include/ -DIP_ALLOCATION -Wdate-time -D_FORTIFY_SOURCE=2 -c -o xl2tpd.o xl2tpd.c became cc -DDEBUG_PPPD -DTRUST_PPPD_TO_DIE -O2 -fno-builtin -Wall -DSANITY -DLINUX -I/include/ -DIP_ALLOCATION -DUSE_KERNEL -g -O2 -ffile-prefix- map=/<>=. -fstack-protector-strong -Wformat -Werror=format- security -DDEBUG_PPPD -DTRUST_PPPD_TO_DIE -O2 -fno-builtin -Wall -DSANITY -DLINUX -I/include/ -DIP_ALLOCATION -Wdate-time -D_FORTIFY_SOURCE=2 -c -o xl2tpd.o xl2tpd.c ** 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/1951832 Title: xl2tpd "Can not find tunnel" in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lto-disabled-list/+bug/1951832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
** Changed in: xl2tpd (Ubuntu Jammy) Status: Fix Released => 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/1951832 Title: xl2tpd "Can not find tunnel" in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lto-disabled-list/+bug/1951832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970896] Re: uvt-simplestreams-libvirt in ubuntu_kvm_smoke_test will eat up all disk free space on Jammy AWS baremetal
Hi Po-Hsu Lin, Sorry, there's also a decompression step. The relevant code is: https://git.launchpad.net/uvtool/tree/uvtool/libvirt/__init__.py#n45 It's possible this could be optimized if libvirt's API has had any enhancements since I wrote that code. It looks like I did it this way because I had to tell libvirt the uncompressed size before creating the image in libvirt, and decompressing into a temporary file was the easiest way of determining this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970896 Title: uvt-simplestreams-libvirt in ubuntu_kvm_smoke_test will eat up all disk free space on Jammy AWS baremetal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1970896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970896] Re: uvt-simplestreams-libvirt in ubuntu_kvm_smoke_test will eat up all disk free space on Jammy AWS baremetal
Hi, In uvtool this is by design. It has to download the entire image before it can cryptographically verify it, and only then does it start injecting the image into libvirt. It does that using libvirt's socket API. Using that mechanism, I don't think it's possible to do a filesystem-level move to economize on disk usage. I suppose it might be possible to do one of a couple of things: 1) Have some kind of "--insecure" flag and code that opportunistically skips the /tmp step in this case, streaming the download directly into libvirt. However this is more code to maintain for a very special case, and the error path cleanup at the libvirt of a failed download would also have to be checked and handled as needed. 2) Arrange to do a filesystem-level move instead of using libvirt's API. However this would break users who have more complicated setups, so there'd again have to be more code to maintain to special case the default case. Since this behaviour is by design in uvtool, it isn't a bug per se, so I'll mark it accordingly. If you want to write and merge one of the above options, please could you explain why this is important for uvtool? Requiring twice the image size to be available in disk space seems reasonable to me. ** Changed in: uvtool (Ubuntu) Status: New => Incomplete ** Changed in: uvtool (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970896 Title: uvt-simplestreams-libvirt in ubuntu_kvm_smoke_test will eat up all disk free space on Jammy AWS baremetal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1970896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
I uploaded a rebuild of xl2tpd to fix this in Kinetic, but it is still pending SRU review for Jammy (22.04). ** Changed in: xl2tpd (Ubuntu) Status: Triaged => Fix Committed ** Changed in: lto-disabled-list (Ubuntu Jammy) 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/1951832 Title: xl2tpd "Can not find tunnel" in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lto-disabled-list/+bug/1951832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
Thank you for testing the fix! I've now uploaded the fix for inclusion
in an update to 22.04. This is now awaiting SRU team review (I shouldn't
do that myself as I prepared it). Once the fix is accepted, we will ask
for testing again of the final package binary before it is published to
updates.
** Description changed:
+ [Impact]
+
+ Users cannot connect to L2TP VPNs at all, such as through network-
+ manager-l2tp-gnome.
+
+ [Development Fix]
+
+ Addition to lto-disabled-list and a rebuild of xl2tpd in Kinetic. The
+ upload to lto-disabled-list is in Unapproved, pending Kinetic opening.
+ I've added a task for lto-disabled-list to this bug, so that I'll know
+ to upload the rebuild of xl2tpd when that is built and published. Since
+ the version of the Jammy upload is 1.3.16-1ubuntu0.1, the Kinetic upload
+ will end up "lower" at 1.3.16-1build1, but that shouldn't be a problem
+ because this issue will be fixed in both packages, and then any
+ subsequent uploads to Kinetic will continue "higher" as normal.
+ Alternatively 1.3.16-1ubuntu0.1 could just be copied forward to Kinetic
+ after this SRU lands, but it would be better to avoid the delta in
+ Kinetic so that the package will autosync in the future.
+
+ [Stable Fix]
+
+ Disabling of LTO in debian/rules. This is a more minimal fix that would
+ not require coordination between two packages in a situation where
+ xl2tpd needs to be rebuilt in Jammy anyway.
+
+ [Fix method not adopted]
+
+ It would be better to fix upstream so that LTO actually works. Upstream
+ issues are https://github.com/xelerance/xl2tpd/issues/230 and
+ https://github.com/xelerance/xl2tpd/issues/232. However these aren't
+ fixed upstream and the change in the area of code suggested may not be
+ the only necessary fix, so it seems safer for both the stable and
+ development releases in Ubuntu to revert what regressed the package for
+ now, until a proper fix confirmed to cover all cases by upstream.
+
+ [Test Plan]
+
+ Requirements : An L2TP VPN server (Windows Server)
+
+ - Install Ubuntu 22.04
+ - Install network-manager-l2tp-gnome (and requirements)
+ - Configure a new L2TP VPN connection for your server
+ (in my case, not sure if this detail is required)
+ - Configure gateway address
+ - Configure password auth
+ - In the IPsec Options, enable IPsec tunnelling
+ - Configure the PSK from your server
+ - In the PPP Options, enable MSPPE, and disable MSCHAP (leaving MSCHAPv2
the only auth option)
+
+ With thanks to Adrian Wilkins, who will also do the SRU verification for
+ us, since it requires a configured Windows Server at the other end.
+
+ In addition, racb will check the build log to ensure that LTO was
+ actually disabled during the build.
+
+ [Where problems could occur]
+
+ There might be some other unreported users from whom LTO actually fixes
+ something and we will regress them by disabling it. However this bug
+ seems more important to fix since it is reported with 35 reported to be
+ affected users already.
+
+ LTO doesn't actually get disabled, and by some other non-determinism the
+ problem is accidentally fixed and regresses again later. Mitigation:
+ check the build log.
+
+ [Original Description]
+
My connection works in 20.04 and fails in 22.04. Perhaps something i've
been using is now depricated? Or perhaps jammy xl2tpd is...still
working on it?
see my attached syslog extracts at comments #6 thru #11. the er-x
extracts were simple, the ubuntu extracts were thus:
egrep -i "l2tp|swan|ipsec|charon|XFRM|layer 2|\/var/run/xl2tpd/l2tp-control c myvp7&&
while i=$(ip route) j=${i#*3.i.p.}
[[ $j = "$i" ]]
do echo -n .;sleep .3
done
i="ip route add 3.i.p.0/21 via 3.i.p.${j%% *}"
echo $i;$i
er-x /etc/ipsec.conf:
config setup
conn %default
keyexchange=ikev1
conn remote-access
authby=secret
type=transport
keyexchange=ikev1
left=2.i.p.7
leftprotoport=17/1701
right=%any
rightprotoport=17/%any
auto=add
dpddelay=15
dpdtimeout=45
dpdaction=clear
rekey=no
ikelifetime=3600
keylife=3600
er-x /etc/ipsec.secrets:
2.i.p.7 %any : PSK ...
er-x /etc/xl2tpd/xl2tpd.conf:
[global]
listen-addr = 2.i.p.7
[lns default]
ip range = 3.i.p.4-3.i.p.9
local ip = 10.255.255.0
refuse pap = yes
require authentication = yes
name = VyattaL2TPServer
ppp debug = yes
pppoptfile = /etc/ppp/options.xl2tpd
length bit = yes
er-x /etc/ppp/options.xl2tpd:
name xl2tpd
linkname l2tp
ipcp-accept-local
ipcp-accept-remote
ms-dns 8.8.8.8
ms-dns 8.8.4.4
noccp
auth
nodefaultroute
debug
proxyarp
connect-delay 5000
idle 1800
** Changed in: xl2tpd (Ubuntu Jammy)
Status: Triaged => In Progress
** Tags removed: bitesize
** Tags added: regression-release
** Description changed:
[Impact]
Users cannot connect to L2TP VPNs at all, such as through network-
manager-l2tp-gnome.
[Development
[Bug 1970740] Re: xl2tpd fails with LTO enabled
Filed upstream: https://github.com/xelerance/xl2tpd/issues/232 ** Bug watch added: github.com/xelerance/xl2tpd/issues #232 https://github.com/xelerance/xl2tpd/issues/232 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970740 Title: xl2tpd fails with LTO enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1970740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
** Also affects: lto-disabled-list (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/1951832 Title: xl2tpd "Can not find tunnel" in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lto-disabled-list/+bug/1951832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970740] [NEW] xl2tpd fails with LTO enabled
Public bug reported: See bug 1951832 for details of the failure. That bug tracks the regressed UX and will be resolved with a workaround. This bug tracks the issue that LTO cannot be enabled on this package. ** Affects: xl2tpd (Ubuntu) Importance: Undecided Status: Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970740 Title: xl2tpd fails with LTO enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1970740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
Users affected on 22.04: please test the fix from ppa:racb/fixes (https://launchpad.net/~racb/+archive/ubuntu/fixes?field.series_filter=jammy). This is the minimal change to disable LTO, and is the fix I intend to propose for 22.04 if it is reported to work. If this does work, then I'll need: 1) Reports that the package in my PPA actually fixes the problem for affected users, so that I know to proceed with this specific fix. 2) Step-by-step instructions that allow someone not familiar with the package to reproduce the issue on a fresh Ubuntu system. I appreciate that this assumes availability of a VPN endpoint somewhere else, so it won't be perfect, but as best as you can manage to explain the configuration on the Ubuntu end at least, please. 3) Further testing of the final proposed update packages for 22.04 after they're made available. If someone can commit to helping with these, please - especially step 3 - then I can proceed. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951832 Title: xl2tpd "Can not find tunnel" in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964881] Re: Logging/Log rotation does not work for catalina.out
** 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/1964881 Title: Logging/Log rotation does not work for catalina.out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat9/+bug/1964881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874719] Re: [SRU] Use the hostname as the node name instead of hardcoded 'node1'
> I'm not sure how to do that in packaging except to try to guide the user into somehow not following the broken installation flow. Maybe, *if* it's never useful to use corosync with the default shipped corosync.conf, we should just not ship it, and add a ConditionPathExists=/etc/corosync/corosync.conf to corosync.service? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874719 Title: [SRU] Use the hostname as the node name instead of hardcoded 'node1' To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1874719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874719] Re: [SRU] Use the hostname as the node name instead of hardcoded 'node1'
James said: > Setting the pacemaker distro task back to new - it seems very odd that a system designed to manage a cluster of servers would install on every node with a non-unique node id, which is a change in behaviour from older versions of the same software. In Jammy, I think this is still the case? corosync.conf still ships with a default nodeid of 1. It's just the name that's no longer supplied. My understanding of the normal use of corosync in Ubuntu is that the entire file is generally always replaced after the package is installed. I believe the hacluster charm does this too. So am I right in that the issue is that corosync started briefly before being configured by the charm, and is leaving state behind? In that case, I think the charm was possibly buggy in two ways: 1) It should use policy-rc.d to avoid corosync daemon startup before corosync.conf is written out, or maybe write it out in advance. Looks like Billy's commit fixed this in the charm already. FWIW, I find it surprising that charms don't generally always override with policy-rc.d and start services manually. 2) After rewriting corosync configuration, it should clear out corosync state files entirely before restarting the daemon. This is no longer necessary due to the other fix. Both of these apply to anything configuring corosync on Ubuntu, not just the charm. So it's not clear to me that there's a bug in the corosync packaging in Ubuntu in Focal at all. We merely ship a default cluster of size 1 that isn't very useful and needs to be replaced correctly in order to be useful. From an SRU perspective, I have further concerns for existing users. 1) It's a conffile change. Since corosync.conf is almost always modified by users, they're are going to be prompted on upgrade if interactive. This is a little alarming and not useful. Is there any actual case where existing users would realistically be using the default configuration file? Note also that since the issue is with state, changing the configuration file for existing users wouldn't avoid the issue for them anyway. 2) Changing the node name on an existing cluster seems dangerous to me. For the SRU, what problem are we actually solving here then? The charm is fixed and no longer impacted. Are we trying to avoid having dirty state when users follow the broken installation flow of starting corosync with the default configuration and then changing it? In that case, it seems to me that the proposed fix only happens to work by chance in this case. The real fix is to make sure that the state is properly cleaned. I'm not sure how to do that in packaging except to try to guide the user into somehow not following the broken installation flow. Therefore I'm soft-declining this SRU for now, but further discussion welcome if you disagree and I'll look again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874719 Title: [SRU] Use the hostname as the node name instead of hardcoded 'node1' To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1874719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970068] Re: L2TP+IPSec not working after upgrade to 22.04 LTS
*** This bug is a duplicate of bug 1951832 *** https://bugs.launchpad.net/bugs/1951832 ** This bug has been marked a duplicate of bug 1951832 xl2tpd "Can not find tunnel" in jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970068 Title: L2TP+IPSec not working after upgrade to 22.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1970068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
More info: https://wiki.ubuntu.com/ToolChain/LTO -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951832 Title: xl2tpd "Can not find tunnel" in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
Looks like this needs someone familiar with Ubuntu process to arrange either disabling link time optimisation or to use msaxl's patch in comment 30. I don't know which would be correct and would want to consult with others on the LTO thing. https://wiki.ubuntu.com/StableReleaseUpdates#Procedure documents the required process if there are any volunteers. ** Tags added: bitesize ** Also affects: xl2tpd (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Changed in: xl2tpd (Ubuntu Jammy) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951832 Title: xl2tpd "Can not find tunnel" in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799185] Re: spamd running with virtual-config-dir mkdir error
Fix available upstream so this should be trivial to cherry-pick now. It might be worth taking a briefly deeper look from a security perspective because of the force untaint. In 3.5 years nobody else reported themselves as affected though. @Giuseppe would you still benefit from this fix? If so I can flag it for someone's attention. If not, then any volunteer can drive it, but otherwise it'll be fixed in a future Ubuntu release that incorporates the next upstream release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799185 Title: spamd running with virtual-config-dir mkdir error To manage notifications about this bug go to: https://bugs.launchpad.net/spamassassin/+bug/1799185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958720] Re: python3-yaml and python3-six are not co-installable with python-is-python2 in jammy
I verified that this is fixed when upgrading from Focal to Jammy. Method: lxc launch ubuntu:focal test lxc exec test bash apt -y update && apt -y full-upgrade apt -y install python-is-python2 do-release-upgrade -d do-release-upgrade does suggest removing python-is-python2 as obsolete after the upgrade. However if you say no (the default) then the package remains. Thanks Rolf for the report and the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958720 Title: python3-yaml and python3-six are not co-installable with python-is- python2 in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyyaml/+bug/1958720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967747] Re: Lack of visual distinction between active and inactive windows
This works for me. Thanks! Now I just have to look for the button circles to tell if I'm looking at an active window or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967747 Title: Lack of visual distinction between active and inactive windows To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1967747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968919] Re: Spurious needrestart runs on do-release-upgrade
** Description changed: Expected behaviour: no unnecessary prompts during do-release-upgrade Actual behaviour: needrestart prompts during do-release-upgrade Steps to reproduce: - lxc launch ubuntu:focal reproducer + lxc launch ubuntu:impish reproducer lxc exec reproducer bash apt-get update && apt-get -y upgrade # needrestart prompts, but that's expected do-release-upgrade -d # needrestart prompts in the middle of this, and that's unexpected do-release-upgrade recommends a system reboot after the upgrade is complete. So it's unnecessary to run needrestart and prompt the user for restarts while the upgrade is running. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968919 Title: Spurious needrestart runs on do-release-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/1968919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968874] Re: Upgrades from Focal to Jammy pull in Postfix
I missed it before, but at is also pulling in default-mta through a Recommends. Again, there was a delta in Focal, but this has been lost. ** Also affects: at (Ubuntu) Importance: Undecided Status: New ** Changed in: at (Ubuntu) Status: New => In Progress ** Changed in: at (Ubuntu) Assignee: (unassigned) => Robie Basak (racb) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968874 Title: Upgrades from Focal to Jammy pull in Postfix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at/+bug/1968874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958720] Re: python3-yaml and python3-six are not co-installable with python-is-python2 in jammy
FTR, tumbleweed reviewed the change in principle for me in #ubuntu- devel. 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/1958720 Title: python3-yaml and python3-six are not co-installable with python-is- python2 in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyyaml/+bug/1958720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958720] Re: python3-yaml and python3-six are not co-installable with python-is-python2 in jammy
Uploaded fixes for pyyaml and six. Now awaiting release team approval. I'll set Fix Committed; this can always be undone if they refuse. ** Changed in: six (Ubuntu) Assignee: (unassigned) => Robie Basak (racb) ** Changed in: pyyaml (Ubuntu) Status: Incomplete => Fix Committed ** Changed in: six (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958720 Title: python3-yaml and python3-six are not co-installable with python-is- python2 in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyyaml/+bug/1958720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958720] Re: python3-yaml and python3-six are not co-installable with python-is-python2 in jammy
I did some research to ensure that removing the Breaks is safe. Some of this repeats what we covered already but I'm stating it again so my logic is self-contained here. If python-is-python2 is installed on Focal and I upgrade to Jammy, then python-is-python2 gets removed because of the Breaks. If python-is-python2 is installed on Impish and I upgrade to Jammy using do-release-upgrade, then python-is-python2 remains but the installer offers to remove it as obsolete. I can refuse, however. Therefore, by adjusting things so that in the upgrade from Focal to Jammy python-is-python2 can stay installed, I'm not changing behaviour from what the Impish to Jammy upgrade allows anyway. Note that the user will still need to state that they don't want to remove obsolete packages. This is the default if you just press Return. On Jammy, python3-yaml (src:pyyaml) Breaks python (<< 2.7.18) On Jammy, python3-six (src:six) Breaks python (<< 2.7.18) On Focal, python-is-python2 Provides python (= 2.7.17-1) On Impish, python-is-python2 Provides python (= 2.7.18-2) Nothing else on Focal nor Impish Provides python. python is not a concrete package on Focal nor Impish. On both Focal and Impish, python-is-python2 Depends on python2 but has no Depends or Recommends on any other package. Therefore the only impact of this change will be against the python-is- python2 package and I don't expect there to be unexpected interactions with any other package by removing the Breaks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958720 Title: python3-yaml and python3-six are not co-installable with python-is- python2 in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyyaml/+bug/1958720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968919] Re: Spurious needrestart runs on do-release-upgrade
In my test I think I got prompted twice (I said no to restarts as they're unnecessary as I expect to reboot when it's done). The pain of this is that release upgrades usually take a while, so every prompt may mean hours delay in the entire upgrade process since the user might not come back for a while. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968919 Title: Spurious needrestart runs on do-release-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/1968919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968919] [NEW] Spurious needrestart runs on do-release-upgrade
Public bug reported: Expected behaviour: no unnecessary prompts during do-release-upgrade Actual behaviour: needrestart prompts during do-release-upgrade Steps to reproduce: lxc launch ubuntu:focal reproducer lxc exec reproducer bash apt-get update && apt-get -y upgrade # needrestart prompts, but that's expected do-release-upgrade -d # needrestart prompts in the middle of this, and that's unexpected do-release-upgrade recommends a system reboot after the upgrade is complete. So it's unnecessary to run needrestart and prompt the user for restarts while the upgrade is running. ** Affects: needrestart (Ubuntu) Importance: Undecided Status: New ** Tags: rls-jj-incoming ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968919 Title: Spurious needrestart runs on do-release-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/1968919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968874] Re: Upgrades from Focal to Jammy pull in Postfix
Lukas FYI. ** Changed in: popularity-contest (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968874 Title: Upgrades from Focal to Jammy pull in Postfix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/popularity-contest/+bug/1968874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968874] [NEW] Upgrades from Focal to Jammy pull in Postfix
Public bug reported: Steps to reproduce: lxc launch ubuntu:focal reproducer lxc exec reproducer bash do-release-upgrade -d Expected: no Postfix debconf prompt Actual: Postfix debconf prompt This is bad because there's a debconf prompt at all, but also that users don't really know how to respond to this one because they're not the ones demanding an MTA. Why is Postfix being pulled in on this upgrade? After the upgrade, I see that the only thing that Recommends default-mta | mail-transport-agent is popularity-contest, so I think this package is the culprit. In Focal, was seeded in the standard seed which is why it was installed. However, the version in Focal does not have this Recommends. In Jammy, it is no longer seeded (https://git.launchpad.net/~ubuntu- core-dev/ubuntu- seeds/+git/platform/commit/standard?id=82c97be2eee777cb2f579474259cf86e51fe3a8f) but since it was installed previously, the upgrade causes Postfix to get installed during the upgrade process. A possible solution is to remove the Recommends in an Ubuntu delta. ** Affects: popularity-contest (Ubuntu) Importance: Undecided Status: New ** Tags: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968874 Title: Upgrades from Focal to Jammy pull in Postfix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/popularity-contest/+bug/1968874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967747] Re: Lack of visual distinction between active and inactive windows
Thanks! Is there any possibility of fixing this in Jammy? I'm aware we're past UI Freeze but I don't know how that would interact with usability fixes, exceptions, etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967747 Title: Lack of visual distinction between active and inactive windows To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1967747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899248] Re: mysql server crashes during install/update: Error: Unable to shut down server with process id X
Hello Shubham, or anyone else affected, Accepted mysql-8.0 into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mysql-8.0/8.0.28-0ubuntu0.21.10.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mysql-8.0 (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-impish ** Changed in: mysql-8.0 (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899248 Title: mysql server crashes during install/update: Error: Unable to shut down server with process id X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1899248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964969] Please test proposed package
Hello Lena, or anyone else affected, Accepted mysql-8.0 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mysql-8.0/8.0.28-0ubuntu0.20.04.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964969 Title: mysql error log always contains errors with mysqlx when installing/upgrading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1964969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964969] Re: mysql error log always contains errors with mysqlx when installing/upgrading
Hello Lena, or anyone else affected, Accepted mysql-8.0 into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mysql-8.0/8.0.28-0ubuntu0.21.10.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mysql-8.0 (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-impish ** Changed in: mysql-8.0 (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964969 Title: mysql error log always contains errors with mysqlx when installing/upgrading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1964969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
