[Bug 2063919] Update Released
The verification of the Stable Release Update for far2l 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/2063919 Title: [patch] Disable ttyxi input processing under Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/far2l/+bug/2063919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063879] Re: [SRU] EasyEffects Depends: calf-plugins should be Recommends
Hello Erich, or anyone else affected, Accepted easyeffects into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/easyeffects/7.1.6-1ubuntu0.24.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- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. 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: easyeffects (Ubuntu Noble) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063879 Title: [SRU] EasyEffects Depends: calf-plugins should be Recommends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/easyeffects/+bug/2063879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061825] Re: [SRU] ucf fails to work for local diversions on Jammy
Thank you for your reply. Unfortunately this doesn't address my concerns though. Please address paragraphs 2, 3 and 4 from my comment 7 above. Depending on your answer, it may be the case that I end up rejecting the SRU because the impact is not sufficient to justify one (see: https://wiki.ubuntu.com/StableReleaseUpdates#High-impact_bugs). Thank you for working on the Test Plan, however please expand on "B3. Confirm it still works". It's important that the steps you follow are unambiguous in case we need to follow what happened after a regression. Are you going to merely confirm that dpkg completes without errors, check that the configuration file remains modified, verify that chrony is returning NTP queries, or what? Please make sure that the cases I outlined in paragraph 6 of comment 7 are umanbiguously and fully covered. The changelog update in your debdiff is much better, thanks, but it needs re-uploading. I'll reject the existing upload. Please get all the updates I've requested above completed to the satisfaction of your sponsor, and then ask your sponsor to re-upload. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061825 Title: [SRU] ucf fails to work for local diversions on Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/2061825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063879] Re: [SRU] EasyEffects Depends: calf-plugins should be Recommends
Thank you for the discussion. My reaction was the same as Andreas', but with the alternatives having been considered, if you still want to make this change then I guess it's fine to defer to you to make the call as you're driving this and the various options all seem reasonable to me. The change in Noble Unapproved looks fine but, please could you fix Oracular now that is is open so that it is open to avoid the archive ending up in an inconsistent state wrt. versions on release upgrade? I appreciate this probably wasn't the case when you uploaded it but equally I don't want to make the archive state worse than it is by accepting it now. Once done, the Noble package version string will want adjusting to fall below the Oracular upload (see https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging) so I think a further upload to Noble will be required too, please. ** Changed in: easyeffects (Ubuntu Noble) 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/2063879 Title: [SRU] EasyEffects Depends: calf-plugins should be Recommends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/easyeffects/+bug/2063879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067319] Re: After upgrading from bionic to focal, esm-cache.service hits apparmor denials
I spoke to Andreas and Renan about this bug just now. I'm told that 32.2 in proposed passes all verification tests against the exceptional test plan except for this bug. But we also need this bug fixed and don't want to have to wait for the additional time a full test rerun would take along with a further ageing period. If we were to land exceptional SRU in proposed right now, then perform a regular SRU for a 32.3 with this bug fixed, then the second SRU would only require normal SRU verification for the particular fix being applied (test plan to include both the B->F upgrade case and the fresh installation F case, but checking apparmor behaviour only). Given that exceptional test plan verification against 32.2 is already complete and passed except for this bug, I think that not releasing 32.2 in proposed currently, replacing it with a 32.3, and then SRU-verifying only this bug is equivalent from a QA perspective and therefore acceptable and preferable in this case. We would then be able to release 32.3 to updates as normal. Plan of action: 1. Update this bug "Where problems could occur" with the specifics that Renan mentioned earlier, and link to this comment to explain what is going on from both this bug and tracking bug 2060732. 2. Complete the Test Plan for this bug to the satisfaction of one SRU team member (Andreas?) treating it as the Test Plan like one would for a regular SRU of this fix only (exercising AppArmor sufficiently for both the B->F upgrade and F fresh install cases and a smoke test to make sure the client still works if not included implicitly in exercising AppArmor is sufficient IMHO; use of automation is fine as always). 3. Complete the verification report for 32.2 in bug 2060732 as normal, except without the final change of the tags since we do not intend to release it. 4. Accept 32.3 into proposed (for all series) to address this bug 2067319. The upload should use -v to include the previous upload as well. 5. The bugs already verified (eg. tracking bug 2060732 but also any others previously verified) can be re-marked as verified with only a link to this comment as explanation (no re-verification required). 6. SRU-verify this bug 2067319 like you would a regular SRU. 7. Release when ready. I also agree that we can skip the ageing period as the only testing expected to be done is by us. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067319 Title: After upgrading from bionic to focal, esm-cache.service hits apparmor denials To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2067319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063821] Re: Ubuntu 22.04 server installer doesn't boot on Xen server as domU in PVH mode
Thank you for taking the time to report this bug and helping to make Ubuntu better. It isn't obvious to me what Ubuntu might be "doing wrong", if anything, that is causing this issue. Xen in Ubuntu is in our universe component and community-supported only. Therefore I don't expect this bug to make progress unless/until someone can volunteer an investigation and describe what exactly Ubuntu needs to change. If you could help with that, please do! ** 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/2063821 Title: Ubuntu 22.04 server installer doesn't boot on Xen server as domU in PVH mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/2063821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055728] Re: update-notifier notifies on unactionable "Pro" updates
** Description changed: - I understand that, when informing me about notifications, update- - notifier will tell me about Pro-only updates that I cannot receive - unless I subscribe to Pro. + I understand that, when informing me about updates, update-notifier will + tell me about Pro-only updates that I cannot receive unless I subscribe + to Pro. Actual behaviour: However, I am also receiving notifications that tell me about Pro-only updates when I am not subscribed to Pro and there are no other updates I can receive. Expected behaviour: if I have taken a decision not to subscribe to Pro, then while I can expect to be told about Pro updates that I can subscribe to while being told about other updates, I do not expect to receive "Pro only" notifications with no other information. Screenshot attached. See also: https://mastodon.sdf.org/@DamonWakes/111954751164015449 I suggest the following rule of thumb: we should never generate a *new* notification that displays only Pro updates unless the user has opted in to Pro. In other words, unsolicited notices about Pro can "piggy-back" on existing notifications that would have happened anyway, but must not create any new pop ups. ** Description changed: - I understand that, when informing me about updates, update-notifier will - tell me about Pro-only updates that I cannot receive unless I subscribe - to Pro. + I understand that, when informing me about available updates, update- + notifier will tell me about Pro-only updates that I cannot receive + unless I subscribe to Pro. Actual behaviour: However, I am also receiving notifications that tell me about Pro-only updates when I am not subscribed to Pro and there are no other updates I can receive. Expected behaviour: if I have taken a decision not to subscribe to Pro, then while I can expect to be told about Pro updates that I can subscribe to while being told about other updates, I do not expect to receive "Pro only" notifications with no other information. Screenshot attached. See also: https://mastodon.sdf.org/@DamonWakes/111954751164015449 I suggest the following rule of thumb: we should never generate a *new* notification that displays only Pro updates unless the user has opted in to Pro. In other words, unsolicited notices about Pro can "piggy-back" on existing notifications that would have happened anyway, but must not create any new pop ups. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055728 Title: update-notifier notifies on unactionable "Pro" updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/2055728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065863] Re: needrestart causes kernel upgrade messages in motd
Steve asked for this to be Critical and assigned to Simon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065863 Title: needrestart causes kernel upgrade messages in motd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2065863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065863] [NEW] needrestart causes kernel upgrade messages in motd
Public bug reported:
On Noble, I see this in my motd:
*** System restart required ***
Pending kernel upgrade!
Running kernel version:
6.8.0-22-generic
Diagnostics:
The currently running kernel version is not the expected kernel version
6.8.0-31-generic.
I found this code in needrestart:
/usr/sbin/needrestart: 'The currently
running kernel version is {kversion} which is not the expected kernel
version {eversion}.',
I'm told that it is incorrect for needrestart to be injecting this into
motd. Steve points out that needrestart isn't installed on desktop and
the behaviour shouldn't be different here, thinks that this shouldn't be
injected into motd, and asked for a bug report for this.
needrestart 3.6-7ubuntu4
** Affects: needrestart (Ubuntu)
Importance: Critical
Assignee: Simon Chopin (schopin)
Status: New
** Changed in: needrestart (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
** Changed in: needrestart (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065863
Title:
needrestart causes kernel upgrade messages in motd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2065863/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055728] Re: update-notifier notifies on unactionable "Pro" updates
This doesn't seem like a duplicate to me? ** This bug is no longer a duplicate of bug 2051115 ubuntu pro integration interferes with dist-upgrade prompting -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055728 Title: update-notifier notifies on unactionable "Pro" updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/2055728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059756] Re: [SRU] adsys 0.14.1
OK, thanks. I guess we can review the Jammy upload for now then on the assumption that the Mantic upload won't have substantial changes until it arrives in the queue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059756 Title: [SRU] adsys 0.14.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061324] Re: Error when re-building package from source
This should be Fix Released for the development release, right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061324 Title: Error when re-building package from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061825] Re: [SRU] ucf fails to work for local diversions on Jammy
> * run update-maintainer script FWIW, it's not necessary to mention this directly. It is correct to do it, but convention is to skip mentioning it in the changelog because otherwise we'd have to unnecessarily mention it on nearly every Ubuntu upload. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061825 Title: [SRU] ucf fails to work for local diversions on Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/2061825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061825] Re: [SRU] ucf fails to work for local diversions on Jammy
I wondered if ucf is expected to handle dpkg-divert -ed files in the first place, since that seemed odd to me. It does seem like that's a feature the code was intended to support, although it's unclear to me if it ever worked, and it's not really documented anywhere I can find except that is implied by the manpage. So it seems like it's debatable as to whether this is a bugfix or a request to add a feature. Looking at your description of "Impact", please could you expand on what you're trying to achieve? Why are you using dpkg-divert to divert configuration files installed by ucf? Did this method work in a previous release? Why aren't you writing chrony.conf and then using UCF_FORCE_CONFFOLD=1 instead, or just overwriting chrony.conf after installation, given that ucf is intended to gracefully handle local configuration file changes? I ask because this seems like a risky change to make. ucf is widely used, we don't have the means to test a broad set of uses, it ships with no automated tests, and this particular "fix" was uploaded in a Debian NMU that has yet to be acknowledged by the maintainer. I'd like to understand the use case and why it is essential to fix this in order to weigh up the risk please. If we do decide to go ahead, then there are a few things that need fixing, please. The Test Plan must include the common case - that ucf continues to work as expected when there is no diversion. Since there are no automated tests whatsoever, please include exercise of the common cases that ucf handles (installation, upgrade when packaging changes the configuration file, with and without local user modification, package removal/purge, etc). Please fix the changelog description to explain what the actual user story is that is being fixed, so that users can easily see if the fix is relevant to them or not. For example: "Fix handling of configuration files diverted with dpkg-divert (LP: #...)". Feel free to mention other things like the syntax error if you wish, but just saying that you're fixing a syntax error doesn't really convey anything useful to most readers. ** Changed in: ucf (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/2061825 Title: [SRU] ucf fails to work for local diversions on Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/2061825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064467] Re: Merge ssh-import-id from Debian unstable for oracular
Debian is behind and the server team is upstream, so there is no work to do on this package. There is a delta introduced in Ubuntu, but no need to merge it upstream right now as there wouldn't be any user-facing benefit to that. We can catch up when there is user-facing benefit work to do. ** Changed in: ssh-import-id (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064467 Title: Merge ssh-import-id from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ssh-import-id/+bug/2064467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064428] Re: Merge mosh from Debian unstable for oracular
There is currently no newer Debian version. ** Changed in: mosh (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064428 Title: Merge mosh from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/2064428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059756] Re: [SRU] adsys 0.14.1
Currently the version of adsys in Mantic is 0.13.1ubuntu0.1, which is lower than the version in Jammy Unapproved. What's your plan for Mantic and/or users upgrading to Mantic please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059756 Title: [SRU] adsys 0.14.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949314] Please test proposed package
Hello Leonardo, or anyone else affected, Accepted intel-gpu-tools into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/intel-gpu- tools/1.26-2ubuntu0.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/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
Hello Leonardo, or anyone else affected, Accepted intel-gpu-tools into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/intel-gpu- tools/1.27.1-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- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. 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: intel-gpu-tools (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-mantic ** Changed in: intel-gpu-tools (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/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061324] Re: Error when re-building package from source
Hello Hector, or anyone else affected, Accepted intel-gpu-tools into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/intel-gpu- tools/1.26-2ubuntu0.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: intel-gpu-tools (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/2061324 Title: Error when re-building package from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1979963] Re: Upgrade fwupd to 1.8.3 in jammy to support HP Thunderbolt Dock G4
I'm concerned that my questions at https://lists.ubuntu.com/archives/ubuntu-release/2024-March/005937.html have not been fully answered. Please could you participate in that discussion? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1979963 Title: Upgrade fwupd to 1.8.3 in jammy to support HP Thunderbolt Dock G4 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1979963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855189] Update Released
The verification of the Stable Release Update for usbguard 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/1855189 Title: usbguard stops responding when recvmsg receives ENOBUFS To manage notifications about this bug go to: https://bugs.launchpad.net/usbguard/+bug/1855189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855189] Re: usbguard stops responding when recvmsg receives ENOBUFS
Thank you for the detailed explanation of your testing! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855189 Title: usbguard stops responding when recvmsg receives ENOBUFS To manage notifications about this bug go to: https://bugs.launchpad.net/usbguard/+bug/1855189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040059] Update Released
The verification of the Stable Release Update for sagemath 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/2040059 Title: [SRU] Sage crashes on start due to a missmatched dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sagemath/+bug/2040059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058687] Update Released
The verification of the Stable Release Update for libreoffice 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/2058687 Title: [SRU] libreoffice 7.6.6 for mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2058687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064349] Re: ubuntu-kernel-accessories does not get installed on upgrade
~ubuntu-release: could we treat this as a blocker for enabling upgrades, please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064349 Title: ubuntu-kernel-accessories does not get installed on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2064349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064349] [NEW] ubuntu-kernel-accessories does not get installed on upgrade
Public bug reported: Upgrading from Jammy to Noble, we need the kernel metapackage to switch from the Jammy HWE one to linux-generic or similar. linux-generic Recommends ubuntu-kernel-accessories. It should get pulled in on upgrade. It's important to ensure that this works so it is the same as in a fresh installation, but I cannot test it because upgrades are currently disabled. This may not be an issue. If it works as expected when upgrades are enabled then this bug should probably be Invalid. But if it doesn't, then we'll have some set of broken users for whom it'll be difficult to solve the problem later, so I thought that filing a bug might help with ensuring this is checked before upgrades are enabled. I don't know if ubuntu-release-upgrader is an appropriate place to put this bug task. If something else is appropriate instead, please could you advise? ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Verify that ubuntu-kernel-accessories gets installed on upgrade + ubuntu-kernel-accessories does not get installed on upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064349 Title: ubuntu-kernel-accessories does not get installed on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2064349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056485] Re: Behaviour of socat in Ubuntu 20.04 unexpected
I've removed this from the queue as requested. Thank you for all your work on this! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056485 Title: Behaviour of socat in Ubuntu 20.04 unexpected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1989078] Re: libvirt-qemu apparmor profile doesn't allow locking of AAVMF firmware
Hello Paride, or anyone else affected, Accepted libvirt into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libvirt/6.0.0-0ubuntu8.20 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1989078 Title: libvirt-qemu apparmor profile doesn't allow locking of AAVMF firmware To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1989078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"
Hello Mauricio, or anyone else affected, Accepted libvirt into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libvirt/6.0.0-0ubuntu8.20 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-failed-focal ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059272 Title: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2059272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"
Mauricio identified that there are many symbols added in libvirt-daemon- driver-qemu.so, due to the inclusion of the RPC archives, associated with gcc/ld export-dynamic in the build (which includes all symbols, not just actually used). On consultation with both Mauricio and Sergio, we concluded that this is OK, and not worth the effort and risk of further changes to suppress them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059272 Title: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2059272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062269] Re: incorrect parsing of long command lines
** Merge proposal linked: https://code.launchpad.net/~racb/ubuntu/+source/unhide/+git/unhide/+merge/464618 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062269 Title: incorrect parsing of long command lines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unhide/+bug/2062269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053146] Update Released
The verification of the Stable Release Update for openssh 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/2053146 Title: openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is slightly wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2053146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053146] Re: openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is slightly wrong
It's not clear to me if a simple "ssh -Snone localhost" is covered by the autopkgtests, so I did that manually, testing without -proposed first, and ensuring to run "sudo systemctl restart ssh" after upgrading to -proposed to ensure that I'm definitely hitting the daemon from -proposed. Success on: 1:8.9p1-3ubuntu0.7 on Jammy and 1:9.3p1-1ubuntu3.3 on Mantic. My commands were: lxc launch ubuntu:jammy foo lxc exec foo bash login -f ubuntu ssh-keygen # and set no passphrase cd .ssh cat id_rsa.pub >> authorized_keys ssh -Snone localhost exit sudo add-apt-repository -p proposed apt install -t jammy-proposed openssh-server sudo systemctl restart ssh ssh -Snone localhost exit apt policy openssh-server (and the equivalent for Mantic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053146 Title: openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is slightly wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2053146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747499] Re: 98-reboot-required and Interaction with livepatch
** Tags added: reboot-required -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747499 Title: 98-reboot-required and Interaction with livepatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1747499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1998947] Re: restore reboot notification so that users are notified after unattended-upgrades
** Tags added: reboot-required -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1998947 Title: restore reboot notification so that users are notified after unattended-upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1998947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036213] Re: Duplicate reboot prompt is displayed
** Tags added: reboot-required -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036213 Title: Duplicate reboot prompt is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/2036213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2017401] Re: Unexpected / unwanted unattended-upgrades behaviour after kernel upgrade when Livepatch enabled
** Tags added: reboot-required -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2017401 Title: Unexpected / unwanted unattended-upgrades behaviour after kernel upgrade when Livepatch enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2017401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056485] Re: Behaviour of socat in Ubuntu 20.04 unexpected
> would like this avenue to be investigated To be clear, I mean the general avenue of workarounds in mkvterm, not necessarily my specific idea. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056485 Title: Behaviour of socat in Ubuntu 20.04 unexpected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056485] Re: Behaviour of socat in Ubuntu 20.04 unexpected
I consulted with other SRU team members today. We agree that the bug is valid and that the current behaviour is wrong. However, if we were to change behaviour, the concern is that existing users might be regressed in a way that will be difficult for them to track down. The trade-off we must make is between this, what a fix/workaround for such regressed users would look like and the (very valid) issue with mkvterm in Focal, and what a fix/workaround for mkvterm would look like. I assume that the fix itself for regressed users would be to adjust the call to socat so that it works correctly, which should be straightforward once an affected user identifies the call to socat as the cause of a regression and assuming that the user is in a position to change the socat call. We'd like to hear more about the opportunity to work around the issue in mkvterm. For example, am I right in understanding that the issue is that when specifying "socat $spec_a,extra-options $spec_b", extra-options in $spec_a are (incorrectly) _copied_ forward to $spec_b? Does this happen the other way round? Would a workaround be to use "socat $spec_b $spec_a,extra-options" instead, or would this not work? If it would work, then how difficult would it be to work around the issue in this way in mkvterm or by adding a wrapper around it? The SRU team would like this avenue to be investigated before making a decision please. > The updated debdiff is attached. Did you forget to attach this? The latest upload in the queue still has changes to Makefile.in which I think are unnecessary? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056485 Title: Behaviour of socat in Ubuntu 20.04 unexpected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039206] Re: open-vm-tools "hwclock" needed for VM guest customization not available
> still if adding hwclock command back has no conflict, it will be great helpful for customers. Unfortunately hwclock is in universe so we cannot easily ship it automatically any more. We'd have to promote it back to main first. So it isn't so easy. If you wish to undertake "Guest Customization" reliably then you must interact correctly with the interfaces provided by the guest OS. These will of course change from release to release of the guest OS, so in general it is always necessary to adapt interactions as required by new guest OS releases. Therefore your customers should not expect any new guest OS release to function correctly with your Guest Customization feature prior to receiving such an update from you. Unfortunately it is not practical for us to provide backwards compatibility such as this in the general case. We might be able to make an exception but in this particular case this also seems impractical. It sounds like this problem will go away as soon as you release your fixed vSphere update? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039206 Title: open-vm-tools "hwclock" needed for VM guest customization not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/2039206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039206] Re: open-vm-tools "hwclock" needed for VM guest customization not available
Here's some more background: https://lists.freedesktop.org/archives/systemd- devel/2011-May/002526.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039206 Title: open-vm-tools "hwclock" needed for VM guest customization not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/2039206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039206] Re: open-vm-tools "hwclock" needed for VM guest customization not available
The reason hwclock isn't shipped any more is that Ubuntu now uses systemd's functionality to perform the same task instead. To configure RTC translation between UTC and local time, the primary supported method is now "sudo timedatectl set-local-rtc 0" or "sudo timedatectl set- local-rtc 1". See timedatectl(1) for details (including why '1' is unreliable). Use of hwclock should be considered a deprecated method on newer releases of Ubuntu, although I'm not aware of any plans to remove it completely and it looks like the new method is currently entirely compatible with the old one. This isn't Ubuntu-specific - I imagine that this is the case for all platforms that are exclusively based on systemd. Given that open-vm-tools itself does not contain the call to hwclock either, I'm not sure that we can consider this to be an actionable bug against Ubuntu itself. Is it possible for VMware guest customization to use the new recommended method on newer Ubuntu releases instead? Alternatively, I suggest that if you're sending commands to run via open-vm-tools, that you precede that with commands to ensure that the packages those commands depend on are installed first. ** Changed in: open-vm-tools (Ubuntu Mantic) Status: Confirmed => Invalid ** Changed in: open-vm-tools (Ubuntu Noble) 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/2039206 Title: open-vm-tools "hwclock" needed for VM guest customization not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/2039206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855189] Please test proposed package
Hello Jamie, or anyone else affected, Accepted usbguard into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/usbguard/0.7.6+ds-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/1855189 Title: usbguard stops responding when recvmsg receives ENOBUFS To manage notifications about this bug go to: https://bugs.launchpad.net/usbguard/+bug/1855189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855189] Re: usbguard stops responding when recvmsg receives ENOBUFS
Accepting, but in the Test Plan, please could you elaborate on how long you need to typically wait to see the reproducer, so that a third party will be able to verify if they are not affected? Eg. 1 minute, 1 hour, 1 day or 1 week? Then, during SRU verification, if we wait (say) double that time, then we can have some documented confidence that the bug is fixed. Thanks! ** Changed in: usbguard (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/1855189 Title: usbguard stops responding when recvmsg receives ENOBUFS To manage notifications about this bug go to: https://bugs.launchpad.net/usbguard/+bug/1855189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876597] Re: [SRU] package pure-ftpd-common 1.0.49-4 failed to install/upgrade: unable to open '/usr/share/doc/pure-ftpd-common/README.Authentication-Modules.gz.dpkg-new': No such file or directo
Hello Roland, or anyone else affected, Accepted pure-ftpd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pure- ftpd/1.0.49-4ubuntu0.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: pure-ftpd (Ubuntu Focal) Status: Confirmed => 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/1876597 Title: [SRU] package pure-ftpd-common 1.0.49-4 failed to install/upgrade: unable to open '/usr/share/doc/pure-ftpd-common/README.Authentication- Modules.gz.dpkg-new': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pure-ftpd/+bug/1876597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056361] Re: [SRU] python3-qrencode fails with SystemError about PY_SSIZE_T_CLEAN macro
Hello Arrigo, or anyone else affected, Accepted python-qrencode into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python- qrencode/1.2-5ubuntu0.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: python-qrencode (Ubuntu Jammy) Status: Confirmed => 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/2056361 Title: [SRU] python3-qrencode fails with SystemError about PY_SSIZE_T_CLEAN macro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-qrencode/+bug/2056361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048906] Re: [SRU] ngspice-36 crashes in various ways
Hello Denys, or anyone else affected,
Accepted ngspice into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ngspice/36+ds-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.
** Description changed:
[ Impact ]
ngspice will sometimes crash on some trivial circuits and will result in
Segmentation fault.
Though upstream mentioned these types of circuits causing the segfault as
"strange input".
[ Test Plan ]
* create a test file named "test.netlist" with the following content:
.title KiCad schematic
.save all
.probe alli
.end
* execute "ngspice" command
* run this command: "source test.netlist" on the ngspice prompt.
With the fixed package it will print:
Circuit: KiCad schematic
[ Where problems could occur ]
It is an upstream patch which only adds an check for a pointer before
dereferencing it and there is a little chance of any regression because
of this patch.
+
+ [racb] The modprobenames function will now do nothing under some
+ circumstances. This seems OK and is the intention of this change, but if
+ there's a regression then it is likely to be because of a consequence of
+ this. It always needs to dereference a pointer, and a null pointer
+ deference is always bad, so in the worst case it seems like it would be
+ that the bug isn't really fixed, eg. some kind of silent failure or
+ logic error.
[ Other Info ]
The patch in the debdiff looks quite big due to the indentation changes
but the real change is only:
@@ -1130,6 +1130,7 @@ static char* get_terminal_number(char* e
Called from inp.c*/
void modprobenames(INPtables* tab) {
GENinstance* GENinst;
+if (tab->defVmod) {
for (GENinst = tab->defVmod->GENinstances; GENinst; GENinst =
GENinst->GENnextInstance) {
char* name = GENinst->GENname;
/* Do not inlude the x in the new name, XU1 -> U1 */
@@ -1159,4 +1160,5 @@ void modprobenames(INPtables* tab) {
}
}
}
+}
}
[ Original Bug Description ]
$ lsb_release -rd
Description: Ubuntu 22.04.3 LTS
Release: 22.04
ngspice version: 36+ds-1
The following happens:
=
ngspice is used by KiCad to simulate circuits.
I have noticed that ngspice tends to crash or fail on relatively simple
circuits.
Taking KiCad out of equation I can see that even trivialities lead to
crashes.
For example, create a text file "test.netlist" with the following
content:
--- CUT ---
.title KiCad schematic
.save all
.probe alli
.end
--- CUT ---
Then start ngspice command line tool and run this command: "source
test.netlist".
The results would be this:
--- CUT ---
No compatibility mode selected!
Circuit: KiCad schematic
Segmentation fault (core dumped)
--- CUT ---
Other than segmentation faults, sometimes ngspice attempts to allocate a
negative amount of memory (which also results in crashes).
The following is expected:
=
I expect that ngspice would not crash and would instead either do what it is
asked to do or report errors.
Suggested change:
=
Update ngspice from version 3.6 to version 4.2: I have built v4.2 myself and
checked - it appears to work or report genuine errors in all cases where the
old ngspice simply crashes with no apparent reason.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ngspice 36+ds-1
ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-35-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Wed Jan 10 14:32:41 2024
InstallationDate:
[Bug 2056485] Re: Behaviour of socat in Ubuntu 20.04 unexpected
Interleaving Frank's and jldolan's comments here: > I just assumed socat was not a very popular package. My experience is the opposite! I understand it to be used in all kinds of corners - particularly in user scripts that don't appear in the archive. > I've learned (and I generally agree with that) that it is better to stick to entire upstream commits/patches (if possible) for the reason of future maintainability. This is true for development branch tips, but not for the maintenance of stable releases. "Future maintainability" is minimal for socat in Focal, for example: it hasn't had an update since before Focal's release in 2020, and is likely to only need the odd security update in the future. SRU policy says this: > ...the requirements for stable updates are not necessarily the same as those in the development release. When preparing future releases, one of our goals is to construct the most elegant and maintainable system possible, and this often involves fundamental improvements to the system's architecture, rearranging packages to avoid bundled copies of other software so that we only have to maintain it in one place, and so on. However, once we have completed a release, the priority is normally to minimise risk caused by changes not explicitly required to fix qualifying bugs, and this tends to be well-correlated with minimising the size of those changes. As such, the same bug may need to be fixed in different ways in stable and development releases. Therefore, I do not expect to see a change to Makefile.am in this case where changing the build system isn't necessary to fix the bug. If we decide to go ahead with the SRU (see below), then I'd like the upload replaced with a minimal one, please. Improvements to test suites are generally fine though, as they pose little risk to production users and we can benefit from such improvements during SRU verification. As long as we aren't making the tests less useful :) > I think it's close to a philosophical question what is best to do in case > "users of 20.04 relying on the current behaviour". > I personally believe that since the behavior is wrong, that it needs to be > corrected. I agree that it's a difficult question. Like you, I generally lean towards fixing bugs over changing behaviour: if the bug is obviously the wrong behaviour, then I figure that it's perhaps a regression for existing users that would be acceptable. So I would agree were this an issue in Jammy. But Focal is four years old now. At this point I think there are far more users relying on existing behaviour than new deployments relying on correct behaviour. This is what gives me concern. > Please notice that the behavior is correct in all releases newer than focal - means if not fixing this now with an upgrade, things will break at least after a dist-upgrade. This is fine - users expect behaviour changes over a release upgrade far more than they expect behaviour changes during the lifetime of a release. Considering just this point, the former is actually preferable. > Let me check with the Novalink team to see if this is an acceptable workaround for them. Thanks - I think this should at least be considered first given the above concern. If you conclude that it's not possible then I can consult with the SRU team to make a final decision. One possibility for example is to set an environment variable like LP2056485_SOCAT_BEHAVIOUR and have this socat SRU only activate if that is set. mkvterm could either set that, or you could arrange a wrapper. Then we wouldn't have to worry about changed behaviour for other users. I don't know if this is overkill though - I'd want to consult with other SRU team members before going ahead with it. ** Changed in: socat (Ubuntu Focal) 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/2056485 Title: Behaviour of socat in Ubuntu 20.04 unexpected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059857] Re: logcheck report flooded with cron session lines
Ah sorry, I think I know what this is. Let me look again. ** Changed in: logcheck (Ubuntu) Status: Incomplete => New ** Changed in: logcheck (Ubuntu) Assignee: (unassigned) => Robie Basak (racb) ** 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/2059857 Title: logcheck report flooded with cron session lines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logcheck/+bug/2059857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059857] Re: logcheck report flooded with cron session lines
Thank you for reporting this bug and helping to make Ubuntu better.
As far as I can tell, the line you've provided should be matched by the
following line, from /etc/logcheck/ignore.d.paranoid/cron:
^(\w{3} [ :0-9]{11}|[0-9T:.+-]{32}) [._[:alnum:]-]+ CRON\[[0-9]+\]:
pam_[[:alnum:]]+\(cron:session\): session (opened|closed) for user
[[:alnum:]-]+(\(uid=[[:digit:]]+\))?( by \(uid=[0-9]+\))?$
For my locale I used this as test log file input:
Apr 05 14:57:01 logcheck CRON[6191]: pam_unix(cron:session): session
opened for user root(uid=0) by (uid=0)
I created this by creating a cronjob to run every minute. After the log
line appeared, I also tried "sudo -u logcheck logcheck -o -t" and the
line was *not* reported (matching expected behaviour).
Additionally, logcheck-test output is as follows:
# logcheck-test -q -l ~/test.log -r /etc/logcheck/ignore.d.paranoid/cron &&
echo match
Apr 05 14:57:01 logcheck CRON[6191]: pam_unix(cron:session): session opened for
user root(uid=0) by (uid=0)
match
So it looks like that line is matching as expected.
logcheck(8) says:
> The ignore rules work in additive manner. "paranoid" rules are also
included at level "server". "workstation" level includes both "paranoid"
and "server" rules.
Therefore, if it matches paranoid rules, it should be sufficient for all
settings. I see from your report that you have extensive logcheck
configuration customisations. Is this interfering with this expectation
somehow?
It might be that ignore.d.server/logcheck could be improved with the
newer PAM patterns, but to justify making a specific change in Ubuntu
directly I need a specific failure case that I can reproduce please.
Otherwise, code quality improvements should probably be sent as merge
requests directly to https://salsa.debian.org/debian/logcheck instead.
Since I cannot reproduce the behaviour you're experiencing, I'm marking
the bug as Incomplete for Ubuntu. If this turns out to be a local
configuration issue, please set the status as Invalid. If you can
provide steps to reproduce or have a correction to make to my analysis,
please do that in a comment and then change the status back to New.
Thanks!
** Changed in: logcheck (Ubuntu)
Status: Triaged => Incomplete
** Changed in: logcheck (Ubuntu)
Assignee: Robie Basak (racb) => (unassigned)
** Tags removed: server-todo
** Tags removed: bitesize
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059857
Title:
logcheck report flooded with cron session lines
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logcheck/+bug/2059857/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1988366] Re: python-rtslib-fb needs to handle new attribute cpus_allowed_list
SRU review > +-version_attributes = set(["lio_version", "version"]) > +-discovery_auth_attributes = set(["discovery_auth"]) These might be accessed by an API caller somewhere, and so would represent a regression. I spent some time digging around and didn't find a direct example, so I was going to leave it, but then I came across in rtslib/tcm.py: > from .fabric import target_names_excludes target_names_excludes is being maintained so I think this is OK. However, I think it demonstrates that "stuff" does make use of these names arbitrarily and so we probably shouldn't be dropping items from the module namespace if we don't have to. Would there be a problem with just dropping the dropping of these two lines, to reduce the risk that we'll break something somewhere, including something external to the archive that we cannot find, by unnecessarily dropping these? It should be trivial to do and could save users quite a bit of pain if they are impacted, even if unlikely. Or, put another way, if we were writing this directly for Jammy, we certainly wouldn't be doing the refactoring that is being done here because it is riskier, so it seems to me that we shouldn't, and the change I suggest should be trivially safe. So I think we should do that. Apart from this, +1 from an SRU perspective. If you disagree let's discuss, so I'll leave this in the queue for now. If you agree, please upload an adjustment. ** Also affects: python-rtslib-fb (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: python-rtslib-fb (Ubuntu Jammy) 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/1988366 Title: python-rtslib-fb needs to handle new attribute cpus_allowed_list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-rtslib-fb/+bug/1988366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059857] Re: logcheck report flooded with cron session lines
** Changed in: logcheck (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/2059857 Title: logcheck report flooded with cron session lines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logcheck/+bug/2059857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055776] Re: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM.
** 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/2055776 Title: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2055776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1988942] Re: Failed to set image property. Invalid input for field/attribute simplestreams_metadata. Value: ... is too long (HTTP 400)
@dgadomski looks like you signed the uploads. Please could you take a look and re-upload with the correct versions? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1988942 Title: Failed to set image property. Invalid input for field/attribute simplestreams_metadata. Value: ... is too long (HTTP 400) To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1988942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056485] Re: Behaviour of socat in Ubuntu 20.04 unexpected
SRU review Please could you explain why "minor-corrections-in-makefile-and-test- sh.patch" is required - in particular the change to Makefile.in, but also the test change? If only parts are required, can the patch be made more minimal? > [ Where problems could occur ] I accept that this is a bug and the fix is correct. However, I'm concerned about how the proposed change in behaviour might affect users of 20.04 relying on the current behaviour, even if it is incorrect. If a user already has scripting relying on this behaviour, it'll break. Notably, this is being proposed for 20.04 rather than the current LTS. We're four years from release now; I'd expect few new deployments on 20.04 at this point. Given its age and the existence of a newer LTS, users also expect behaviour to be more stable with fewer exceptions at this point in the 20.04 release lifecycle. Perhaps this is what you meant by "If the changed condition of IF was done wrong" but it's not clear to me if this risk has been considered in depth. For example, can you work around this problem in mkvterm instead, just for 20.04, so that the impact to users can be fixed without risking breaking existing users of socat who might be relying on the problem behaviour? If not, can we arrange for some interaction between mkvterm and socat to switch behaviour only if specifically requested? ** Changed in: socat (Ubuntu Focal) 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/2056485 Title: Behaviour of socat in Ubuntu 20.04 unexpected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052813] Re: [MIR] bpfcc
> [Rationale] > - The package bpfcc is required in Ubuntu main as a runtime dependency of > bpftrace. Correction: this is true, but we'd also like bpfcc-tools in its own right since these tools are recommended by experts for direct use. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052813 Title: [MIR] bpfcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bpfcc/+bug/2052813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052813] Re: [MIR] bpfcc
The main user story being implemented here is the one specified by Brendan Gregg in his literature, including his book "Systems Performance, 2nd Edition". In that book he specifies "Linux crisis tool packages" [Table 4.1], which specifies bpfcc-tools and a bunch of binaries provided by that. Looking at the difference between libbpf-tools and bpfcc-tools, the former is only a subset and doesn't include all the tools specified in the book. For example, the book covers trace and argdist in section 15.1.6. These have -bpfcc versions provided by bpfcc-tools, but I don't see any equivalents in libbpf-tools. The intention is that we install by default what the book covers. Therefore, I'd like to request (at least initially) that we have bpfcc- tools in main. If that's not possible then libbpf-tools will be better than nothing, but will add to the caveats in this entire effort. Please could you consider the MIR request to be for the bpfcc-tools binary package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052813 Title: [MIR] bpfcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bpfcc/+bug/2052813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055432] Re: [needs-packaging] Metapackage for performance engineering tooling
This is in the Noble release pocket now. ** Changed in: ubuntu Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055432 Title: [needs-packaging] Metapackage for performance engineering tooling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2055432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051288] Re: byobu should revert to dmidecode if bogomips in /proc/cpuinfo are set to zero
** Tags added: needs-upstream-report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051288 Title: byobu should revert to dmidecode if bogomips in /proc/cpuinfo are set to zero To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/2051288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 878333] Re: ifconfig not showing virtual ip addresses
This sounds like exactly the behaviour that I explained in 2013 here: https://askubuntu.com/a/332421/7808 ifconfig still exists but is deprecated and no longer shipped by default. Users should use its replacement "ip" instead. However it is true that ifconfig does not display the additional aliases set by ifupdown, so the bug remains valid. But since ifconfig is deprecated we don't expect this to ever be addressed, so I'm setting the bug status to Won't Fix. ** Changed in: net-tools (Ubuntu) Status: Expired => 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/878333 Title: ifconfig not showing virtual ip addresses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/878333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059859] Re: pam_env(sshd:session): deprecated reading of user environment enabled
** Changed in: openssh (Ubuntu) Status: New => Triaged ** Changed in: openssh (Ubuntu) Importance: Undecided => Medium ** 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/2059859 Title: pam_env(sshd:session): deprecated reading of user environment enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059857] Re: logcheck report flooded with cron session lines
** Changed in: logcheck (Ubuntu) Status: New => Triaged ** Changed in: logcheck (Ubuntu) Importance: Undecided => Medium ** Tags added: server-todo ** Tags added: bitesize -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059857 Title: logcheck report flooded with cron session lines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logcheck/+bug/2059857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892673] Re: Segfault on launching yforth
** Also affects: yforth (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: yforth (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: yforth (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: yforth (Ubuntu Noble) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892673 Title: Segfault on launching yforth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yforth/+bug/1892673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936449] Re: numptyphysics segfault on startup on XUb 21.04
** Also affects: numptyphysics (Ubuntu Focal) 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/1936449 Title: numptyphysics segfault on startup on XUb 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/numptyphysics/+bug/1936449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054621] Re: Fix PHP crashes due to accessing dangling pointers
What's the status of this bug in Mantic and Noble please? Were 8.2 and 8.3 ever affected, and if so, in which versions were they fixed? I couldn't figure this out within a few minutes - sorry! > [ Test Plan ] > Run the upstream tests included within this fix. To do so, an upstream development/testing PHP extension for zend introspection is required. Please could you provide the steps to follow to run the upstream tests included in this fix? This should be in enough detail that a developer who is not familiar with this package should be able to follow it. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054621 Title: Fix PHP crashes due to accessing dangling pointers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php8.1/+bug/2054621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056442] Re: Podman (crun) regression in Ubuntu 22.04: OCI runtime error: chmod `run/shm`: Operation not supported
> [Test plan] > Needs to be finalized... Is this finalized yet please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056442 Title: Podman (crun) regression in Ubuntu 22.04: OCI runtime error: chmod `run/shm`: Operation not supported To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2056442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058080] Re: Sync python-qrencode 1.2-7 (universe) from Debian unstable (main)
This bug was fixed in the package python-qrencode - 1.2-7 Sponsored for Sudip Mukherjee (sudipmuk) --- python-qrencode (1.2-7) unstable; urgency=medium * QA upload. * fix crash in Python 3.10 (Closes: #1032287) - redo the fix from 1.2-5.1 which was lost with the update to 1.2-6. * Add autopkgtest. -- Sudip Mukherjee Wed, 13 Mar 2024 10:31:23 + ** Changed in: python-qrencode (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058080 Title: Sync python-qrencode 1.2-7 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-qrencode/+bug/2058080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058136] Re: Sync udisks2 2.10.1-6 (main) from Debian unstable (main)
Thank you for working on this! > Can I suggest ubuntu adds the debian delta as well as the ubuntu delta patch as part of this sync & merge Sorry, I don't follow. It looks like lp-2037569-skip- bd_part_get_disk_spec.patch is part of the Ubuntu delta uploaded in ubuntu1. A sync would drop this, but you tested a build that still includes it? If so, why are you requesting a sync? 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/2058136 Title: Sync udisks2 2.10.1-6 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/2058136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056101] Re: [noble] Quod Libet doesn't start: ModuleNotFoundError: No module named 'senf'
Thank you for the fix! I haven't reviewed this in detail, but normally I'd expect there to be a commit or bug report upstream but I cannot find one. Is this fixed upstream yet please, and if not, have you sent it there for review? Looks like that would be here: https://github.com/quodlibet/quodlibet. We can take the patch into Ubuntu without upstream, but it would be preferable to ensure it will be fixed upstream so that we don't need to maintain the patch forever or worry about the package in Ubuntu getting neglected due to the delta. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056101 Title: [noble] Quod Libet doesn't start: ModuleNotFoundError: No module named 'senf' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quodlibet/+bug/2056101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056565] Re: [FFe] [needs-packaging] ubuntu-kernel-accessories seed and metapackage
Uploaded. ** Changed in: ubuntu Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056565 Title: [FFe] [needs-packaging] ubuntu-kernel-accessories seed and metapackage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2056565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056549] Re: Problems with nfs-common after upgrade to 3.6
It sounds like this is/was a valid regression report. It's something that was considered: > e.g. 4.2 may be selected instead of 4.0 used previously. This could have an impact on workloads if there are any regressions in switching to 4.2 from 4.0 etc. ...but on balance we chose to proceed anyway. That's not necessarily a wrong decision - we have to choose between fixing a valid bug and risking regressing some users - but it's still a regression from the perspective of this class of users. Therefore, I think regression-update is correct, and I'd like to leave that tag there for future analysis please. And I think the bug is valid, albeit "Won't Fix" since at least for now we think that the original fix is preferable even if some users are regressed (without applying a workaround) from the protocol upgrade. ** Tags added: regression-update ** Changed in: nfs-utils (Ubuntu Focal) Status: Invalid => 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/2056549 Title: Problems with nfs-common after upgrade to 3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2056549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking
Hello Kai-Heng, or anyone else affected, Accepted mutter into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu7 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. ** Tags removed: verification-done verification-failed-jammy ** 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/2051074 Title: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
Hello Daniel, or anyone else affected, Accepted mutter into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu7 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. ** Tags removed: verification-failed-jammy ** 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/2054510 Title: Incomplete screen redraws in virtual machines running Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055530] Re: Mutter (sometimes) fails to build with [fatal error: meta/meta-enum-types.h: No such file or directory]
Hello Daniel, or anyone else affected, Accepted mutter into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu7 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: mutter (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/2055530 Title: Mutter (sometimes) fails to build with [fatal error: meta/meta-enum- types.h: No such file or directory] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2055530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055519] Re: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1)
Hello Daniel, or anyone else affected, Accepted mutter into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu7 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: mutter (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/2055519 Title: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2055519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056565] Re: [FFe] [needs-packaging] ubuntu-kernel-accessories seed and metapackage
@p-pisati FYI. As soon as this lands and the new binary package is created, we'll be ready to add this Recommends to src:linux-meta* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056565 Title: [FFe] [needs-packaging] ubuntu-kernel-accessories seed and metapackage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2056565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056565] Re: [FFe] [needs-packaging] ubuntu-kernel-accessories seed and metapackage
** Merge proposal linked: https://code.launchpad.net/~racb/ubuntu/+source/ubuntu-meta/+git/ubuntu-meta/+merge/462062 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056565 Title: [FFe] [needs-packaging] ubuntu-kernel-accessories seed and metapackage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2056565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055432] Re: [needs-packaging] Metapackage for performance engineering tooling
This is awaiting AA accept from the Noble NEW queue. ** Description changed: + Specification: https://discourse.ubuntu.com/t/spec-include-performance- + tooling-in-ubuntu/43134 + As we raise the bar for performance management and optimisation we will publish a metapackage to make it easy for Ubuntu users to install a standard set of tools ready for use in case of a production engineering incident. We shall add a new metapackage to universe called performance-tools. Description: utilities for debugging performance and reliability issues - This metapackage installs utilities for inspecting and debugging systems that are - experiencing performance and/or reliability issues. - - Included are more traditional performance analysis and inspection tools, along with - dynamic tracing and instrumentation tools which make use of the eBPF subsystem. + This metapackage installs utilities for inspecting and debugging systems that are + experiencing performance and/or reliability issues. - On Ubuntu, some of these packages are installed by default already, but are - also included here to assist with deployments that do not use the defaults. + Included are more traditional performance analysis and inspection tools, along with + dynamic tracing and instrumentation tools which make use of the eBPF subsystem. + + On Ubuntu, some of these packages are installed by default already, but are + also included here to assist with deployments that do not use the defaults. This metapackage shall depend on the following packages: procps sysstat iproute2 numactl bpfcc-tools bpftrace perf-tools-unstable trace-cmd nicstat ethtool tiptop sysprof -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055432 Title: [needs-packaging] Metapackage for performance engineering tooling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2055432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056565] [NEW] [FFe] [needs-packaging] ubuntu-kernel-accessories seed and metapackage
Public bug reported: Specification: https://discourse.ubuntu.com/t/spec-kernel-accessories- seed-and-metapackage/43133 Pending MIRs: bpfcc is LP: #2052813; bpftrace is LP: #2052809. This missed feature freeze because it turns out that the seed change cannot take effect in ubuntu-meta until the MIRs are complete (I'm told that ubuntu-meta regeneration is ignoring these packages because they're in universe). I think it is preferable to push this change into Noble sooner rather than later, so that the image size implications can be felt in practice. If a revert or changes are then deemed required, we will have the opportunity to make those changes. Therefore, I'd like to deliberately create a component mismatch to enable this. For ubuntu-meta, I will create the metapackage as a manually-managed binary package for now, and switch over to the usual automatic generation when bpfcc and bpftrace move to main. After the ubuntu-meta change lands, linux-meta* will Recommend ubuntu- kernel-accessories, which will cause bpftrace and bpfcc to be pulled into the relevant images as desired. If the MIRs end up being rejected, a revert of these changes will be straightforward. Release team: please could you provide an FFe ack for the ubuntu-meta change as well as the linux-meta* change? ** Affects: ubuntu Importance: Undecided Assignee: Robie Basak (racb) Status: In Progress ** Tags: needs-packaging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056565 Title: [FFe] [needs-packaging] ubuntu-kernel-accessories seed and metapackage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2056565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056467] Re: No IPv6 Repositories in AWS
This is a bug specific to the default repositories configured on/by AWS cloud images, so the cloud-images project is probably a more suitable bug target. ** Package changed: ubuntu => cloud-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056467 Title: No IPv6 Repositories in AWS To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2056467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2019997] Please test proposed package
Hello Jeremy, 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/31.2~16.04 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/2019997 Title: pro livepatch status incorrect when run as normal user To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-livepatch-client/+bug/2019997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2019997] Please test proposed package
Hello Jeremy, 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/31.2~18.04 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/2019997 Title: pro livepatch status incorrect when run as normal user To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-livepatch-client/+bug/2019997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2019997] Please test proposed package
Hello Jeremy, 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/31.2~20.04 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/2019997 Title: pro livepatch status incorrect when run as normal user To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-livepatch-client/+bug/2019997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2019997] Please test proposed package
Hello Jeremy, or anyone else affected, Accepted ubuntu-advantage-tools into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/31.2~22.04 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/2019997 Title: pro livepatch status incorrect when run as normal user To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-livepatch-client/+bug/2019997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2019997] Please test proposed package
Hello Jeremy, or anyone else affected, Accepted ubuntu-advantage-tools into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/31.2~23.10 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- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. 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/2019997 Title: pro livepatch status incorrect when run as normal user To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-livepatch-client/+bug/2019997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2021988] Please test proposed package
Hello John, 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/31.2~16.04 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/2021988 Title: package ubuntu-advantage-tools 27.14.4 failed to install/upgrade: le sous-processus paquet ubuntu-advantage-tools script pre-removal installé a renvoyé un état de sortie d'erreur 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2021988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2021988] Please test proposed package
Hello John, 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/31.2~18.04 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/2021988 Title: package ubuntu-advantage-tools 27.14.4 failed to install/upgrade: le sous-processus paquet ubuntu-advantage-tools script pre-removal installé a renvoyé un état de sortie d'erreur 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2021988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2021988] Please test proposed package
Hello John, 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/31.2~20.04 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/2021988 Title: package ubuntu-advantage-tools 27.14.4 failed to install/upgrade: le sous-processus paquet ubuntu-advantage-tools script pre-removal installé a renvoyé un état de sortie d'erreur 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2021988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2021988] Please test proposed package
Hello John, or anyone else affected, Accepted ubuntu-advantage-tools into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/31.2~22.04 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/2021988 Title: package ubuntu-advantage-tools 27.14.4 failed to install/upgrade: le sous-processus paquet ubuntu-advantage-tools script pre-removal installé a renvoyé un état de sortie d'erreur 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2021988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2021988] Please test proposed package
Hello John, or anyone else affected, Accepted ubuntu-advantage-tools into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/31.2~23.10 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- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. 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/2021988 Title: package ubuntu-advantage-tools 27.14.4 failed to install/upgrade: le sous-processus paquet ubuntu-advantage-tools script pre-removal installé a renvoyé un état de sortie d'erreur 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2021988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043836] Please test proposed package
Hello errors.ubuntu.com, 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/31.2~18.04 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/2043836 Title: /usr/bin/ubuntu- advantage:UnboundLocalError:wrapper:main:action_security_status:security_status_dict:get_installed_packages_by_origin:__enter__:get_apt_pkg_cache:get_last_known_candidate:get_pkg_candidate_version:__enter__:get_apt_pkg_cache:/usr/bin/ubuntu- advantage@33:wrapper:_warn_about_new_version:check_for_new_version:get_last_known_candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2043836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043836] Please test proposed package
Hello errors.ubuntu.com, 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/31.2~16.04 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/2043836 Title: /usr/bin/ubuntu- advantage:UnboundLocalError:wrapper:main:action_security_status:security_status_dict:get_installed_packages_by_origin:__enter__:get_apt_pkg_cache:get_last_known_candidate:get_pkg_candidate_version:__enter__:get_apt_pkg_cache:/usr/bin/ubuntu- advantage@33:wrapper:_warn_about_new_version:check_for_new_version:get_last_known_candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2043836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043836] Please test proposed package
Hello errors.ubuntu.com, or anyone else affected, Accepted ubuntu-advantage-tools into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/31.2~22.04 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/2043836 Title: /usr/bin/ubuntu- advantage:UnboundLocalError:wrapper:main:action_security_status:security_status_dict:get_installed_packages_by_origin:__enter__:get_apt_pkg_cache:get_last_known_candidate:get_pkg_candidate_version:__enter__:get_apt_pkg_cache:/usr/bin/ubuntu- advantage@33:wrapper:_warn_about_new_version:check_for_new_version:get_last_known_candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2043836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043836] Please test proposed package
Hello errors.ubuntu.com, 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/31.2~20.04 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/2043836 Title: /usr/bin/ubuntu- advantage:UnboundLocalError:wrapper:main:action_security_status:security_status_dict:get_installed_packages_by_origin:__enter__:get_apt_pkg_cache:get_last_known_candidate:get_pkg_candidate_version:__enter__:get_apt_pkg_cache:/usr/bin/ubuntu- advantage@33:wrapper:_warn_about_new_version:check_for_new_version:get_last_known_candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2043836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043836] Please test proposed package
Hello errors.ubuntu.com, or anyone else affected, Accepted ubuntu-advantage-tools into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/31.2~23.10 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- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. 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/2043836 Title: /usr/bin/ubuntu- advantage:UnboundLocalError:wrapper:main:action_security_status:security_status_dict:get_installed_packages_by_origin:__enter__:get_apt_pkg_cache:get_last_known_candidate:get_pkg_candidate_version:__enter__:get_apt_pkg_cache:/usr/bin/ubuntu- advantage@33:wrapper:_warn_about_new_version:check_for_new_version:get_last_known_candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2043836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048921] Please test proposed package
Hello Grant, 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/31.2~20.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-failed-bionic ** 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/2048921 Title: [SRU] ubuntu-advantage-tools (30 -> 31) Xenial, Bionic, Focal, Jammy, Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2048921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048921] Please test proposed package
Hello Grant, 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/31.2~16.04 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/2048921 Title: [SRU] ubuntu-advantage-tools (30 -> 31) Xenial, Bionic, Focal, Jammy, Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2048921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048921] Please test proposed package
Hello Grant, 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/31.2~18.04 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. ** Tags removed: verification-failed-xenial ** 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/2048921 Title: [SRU] ubuntu-advantage-tools (30 -> 31) Xenial, Bionic, Focal, Jammy, Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2048921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048921] Re: [SRU] ubuntu-advantage-tools (30 -> 31) Xenial, Bionic, Focal, Jammy, Mantic
Hello Grant, or anyone else affected, Accepted ubuntu-advantage-tools into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/31.2~23.10 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- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-failed verification-failed-mantic ** Tags added: verification-needed verification-needed-mantic ** Tags removed: verification-failed-jammy ** 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/2048921 Title: [SRU] ubuntu-advantage-tools (30 -> 31) Xenial, Bionic, Focal, Jammy, Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2048921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
