[Bug 2061373] Re: [Lenovo Ubuntu 24.04 Bug] Print grub message before the uefi POST screen disappears in Ubuntu24.04 Beta
The message in question is from "EFI stub", which is part of the kernel, not grub. The reference grub patch is for an unrelated issue. ** Changed in: grub2 (Ubuntu) Status: New => Invalid ** Changed in: grub2 (Ubuntu Noble) 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/2061373 Title: [Lenovo Ubuntu 24.04 Bug] Print grub message before the uefi POST screen disappears in Ubuntu24.04 Beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2061373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071885] Re: System takes 5 Minutes (300 Seconds) to Boot - Regression of previous BUG ?
** Tags removed: 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/2071885 Title: System takes 5 Minutes (300 Seconds) to Boot - Regression of previous BUG ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2071885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072322] Re: Unable to validate the rsa generated ssh keys though it is in openSSH fomat
> I am trying to build my own image > using 0001-com-ubuntu-server-jammy > (20_04-lts) image using ARM template > but, it is failing to validate SSH > keys generated though it is in > openSSH format and have required > permissions. None of this appears to have to do with software on Ubuntu, or the software we use to produce Ubuntu images. ** Changed in: ubuntu-cdimage Status: New => Invalid ** Changed in: 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/2072322 Title: Unable to validate the rsa generated ssh keys though it is in openSSH fomat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/2072322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065180] Re: performance regression in dracut-install 060
** Tags removed: fountations-todo ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065180 Title: performance regression in dracut-install 060 To manage notifications about this bug go to: https://bugs.launchpad.net/dracut/+bug/2065180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2012371] Re: [FFe] ubuntu-proxy-manager and adsys
Hello Gabriel, or anyone else affected, Accepted adsys into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.14.1~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. ** Changed in: adsys (Ubuntu Jammy) Status: Incomplete => 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/2012371 Title: [FFe] ubuntu-proxy-manager and adsys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2012371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2020682] Re: Release adsys 0.12.0
Hello Denison, or anyone else affected, Accepted adsys into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.14.1~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. ** Changed in: adsys (Ubuntu Jammy) Status: Incomplete => 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/2020682 Title: Release adsys 0.12.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2020682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2037270] Re: No PAM module is shipped in mantic
Hello Didier, or anyone else affected, Accepted adsys into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.14.1~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. ** Changed in: adsys (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2037270 Title: No PAM module is shipped in mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2037270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2024377] Re: Adsys can't fetch GPOs
Hello Juarez, or anyone else affected, Accepted adsys into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.14.1~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. ** Changed in: adsys (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2024377 Title: Adsys can't fetch GPOs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2024377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044112] Re: Add dependency on nfs-common
Hello Gabriel, or anyone else affected, Accepted adsys into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.14.1~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. ** Changed in: adsys (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044112 Title: Add dependency on nfs-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2044112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2037271] Re: No pot file extraction when using multiple lines
Hello Didier, or anyone else affected, Accepted adsys into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.14.1~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. ** Changed in: adsys (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2037271 Title: No pot file extraction when using multiple lines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2037271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049061] Re: adsysctl update with a domain user fails if KRB5CCNAME is not set
Hello Fabio, or anyone else affected, Accepted adsys into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.14.1~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. ** Changed in: adsys (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049061 Title: adsysctl update with a domain user fails if KRB5CCNAME is not set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2049061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051363] Re: Cannot perform certificate auto-enroll without NDES installed
Hello Gabriel, or anyone else affected, Accepted adsys into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.14.1~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. ** Changed in: adsys (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051363 Title: Cannot perform certificate auto-enroll without NDES installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2051363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054445] Re: Regresion in sssd backend configuration
Hello Gabriel, or anyone else affected, Accepted adsys into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.14.1~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. ** Changed in: adsys (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054445 Title: Regresion in sssd backend configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2054445/+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
Hello Jean-Baptiste, or anyone else affected, Accepted adsys into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.14.1~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. ** Changed in: adsys (Ubuntu Jammy) Status: Incomplete => 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/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 2069712] Re: wrong key mapping when two languages are installed
For the desktop, console-setup only handles the declaration of the keyboard mappings; the actual toggling between keymaps is handled up the stack in the X or Wayland stack. Are you using X or Wayland here? ** Package changed: console-setup (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (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/2069712 Title: wrong key mapping when two languages are installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2069712/+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
> First, I note that since this is a new upstream version, there are a number > of bugs referenced in the > changelog that are not going to go through SRU verification. Per > https://wiki.ubuntu.com/StableReleaseUpdates#Bug_references_in_changelogs, > please update the > descriptions of these bugs to indicate this explicitly, so it is clear as > part of the SRU review > process that these are net SRU bugs that are missing the SRU bug template. > The bugs referenced in the .changes are: > LP: #2012371 LP: #2020682 LP: #2024377 LP: #2037270 LP: #2037271 LP: #2044112 > LP: #2049061 LP: #2051363 LP: #2054445 This hasn't been done yet, can you please take care of it? -- 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 2070441] [NEW] inaccurate battery status reporting
Public bug reported:
My laptop is plugged into main power most of the time, but as I'm
currently travelling, it's connected a lot more intermittently right
now. So I don't know when this problem started. But I noticed my
desktop indicator was reporting 9% charge and that the battery was not
being charged. Disconnecting and reconnecting the power did not change
this. Suspending and resuming did not change this. But after
rebooting, the desktop was CORRECTLY showing that the battery was at
100% capacity.
The problem seems to be wrong values being reported in /sys from the
kernel:
$ cat /sys/class/power_supply/BAT0/charge_{full,full_design,now}
17030
32872
6533
$
The charge_now value is, TTBOMK, correct. But the charge_full value is
NOT and appears to change over time?
So now my laptop which has been plugged in over night is reported to be
at 38% battery.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-35-generic 6.8.0-35.35+1
ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4
Uname: Linux 6.8.0-35-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:vorlon 9164 F pipewire
/dev/snd/controlC0: vorlon 9168 F wireplumber
/dev/snd/controlC1: vorlon 9168 F wireplumber
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 26 08:57:50 2024
InstallationDate: Installed on 2019-12-23 (1646 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 20QVCTO1WW
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_di672m@/vmlinuz-6.8.0-35-generic
root=ZFS=rpool/ROOT/ubuntu_di672m ro quiet splash intel_iommu=off vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-6.8.0-35-generic N/A
linux-backports-modules-6.8.0-35-generic N/A
linux-firmware20240318.git3b128b60-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2024-05-22 (34 days ago)
dmi.bios.date: 04/28/2021
dmi.bios.release: 1.39
dmi.bios.vendor: LENOVO
dmi.bios.version: N2OET52W (1.39 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QVCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.22
dmi.modalias:
dmi:bvnLENOVO:bvrN2OET52W(1.39):bd04/28/2021:br1.39:efr1.22:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd:
dmi.product.family: ThinkPad X1 Extreme 2nd
dmi.product.name: 20QVCTO1WW
dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
dmi.product.version: ThinkPad X1 Extreme 2nd
dmi.sys.vendor: LENOVO
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2024-05-24T01:12:43.275502
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070441
Title:
inaccurate battery status reporting
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2070441/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069860] Re: [needs-packaging] cmocka-extensions
independent of anything else, the package uploaded to the NEW queue in oracular does not have a compliant Ubuntu version number: 0.50.0-7 was never a Debian package version, as cmocka-extensions has never been in Debian (and is not in the NEW queue currently). Please reupload with a correct version number (-0ubuntu1). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069860 Title: [needs-packaging] cmocka-extensions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2069860/+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
I've completed the review of the rest of the adsys delta. This looks
good to me; my only observation is that as part of the change of i18n
handling libraries, there are two regressions in the localizability of
strings:
internal/adsysservice/service.go: updateFmt := "%s" + gotext.Get(", updated on
") + "%s"
internal/cmdhandler/suggest.go: requireMsg := "%s " + gotext.Get("requires a
valid subcommand")
Both of these introduce assumptions about the word order of the
sentences which were not present before, making the new version less
translatable than the previous version.
However, I will not block the SRU on this because I see that the only
language adsys is currently translated to is French, which is not
affected. Still, it is bad form to use concatenation of translated
strings like this, which you appear to know because both of these are
marked with 'fixme's in the code.
For the other issues with the packaging:
> - debian/prerm: thank you for catching this, I don't know how it slipped
> through, I guess it was all the false encouragement given by packages in the
> wild that employ the same (broken) prerm workflow. I've opened a PR to revert
> this upstream https://github.com/ubuntu/adsys/pull/1026 -- I don't think it
> adds much value to have this working (and it was not explicitly documented in
> the changelog either, so I'm happy with removing the broken code, as it never
> worked)
Yes, please revert this, thanks.
> - krb5/winbind as an alternative to sssd: this was explicitly requested by
> paying customers with specific requirements related to cross-domain forest
> setups which could not be satisfied by sssd directly -- it's documented
> (albeit
> in a terse manner, only mentioning winbind) in the 0.10.0 changelog
Ok, understood (and accepted for SRU).
> - addition of Depends: apparmor: opted for this because the apparmor policy
> manager subprocesses "apparmor_parser" (ref:
> https://github.com/ubuntu/adsys/blob/b20890f78bd55d5b5c90d77af61d17eb31f40b77/internal/policies/apparmor/apparmor.go#L82)
> -- happy to drop it if you think it's the best practice
Since you are invoking programs from this package directly, it's fine to
leave this as-is.
> - additional of dependency on nfs-common: opted for a "Depends" here because
> adsys could apply a nfs mount policy which would fail hard if nfs-common were
> not installed -- I would've gone for "Recommends" in case of a soft warning
Ok, please leave this as-is.
--
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 2070151] Re: package linux-image-6.8.0-35-lowlatency 6.8.0-35.35.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
To be honest, I was surprised it got as far as it did, once I stopped to think. I suppose I'm used to the tools having some guardrails to keep me from casually asking for the impossible. Clean up was fairly straightforward, though, just removing the various lowlatency packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070151 Title: package linux-image-6.8.0-35-lowlatency 6.8.0-35.35.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2070151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070151] [NEW] package linux-image-6.8.0-35-lowlatency 6.8.0-35.35.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: Crash while using ubuntustudio-installer on rpi5 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-35-lowlatency 6.8.0-35.35.1 ProcVersionSignature: Ubuntu 6.8.0-1005.5-raspi 6.8.4 Uname: Linux 6.8.0-1005-raspi aarch64 ApportVersion: 2.28.1-0ubuntu3 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Sun Jun 23 15:30:54 2024 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: initramfs-tools Title: package linux-image-6.8.0-35-lowlatency 6.8.0-35.35.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to noble on 2024-06-17 (6 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070151 Title: package linux-image-6.8.0-35-lowlatency 6.8.0-35.35.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2070151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066262] Re: [MIR] libdex
** Tags added: sec-4617 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066262 Title: [MIR] libdex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdex/+bug/2066262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061373] Re: [Lenovo Ubuntu 24.04 Bug] Print grub message before the uefi POST screen disappears in Ubuntu24.04 Beta
** Package changed: grub (Ubuntu) => grub2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061373 Title: [Lenovo Ubuntu 24.04 Bug] Print grub message before the uefi POST screen disappears in Ubuntu24.04 Beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2061373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057716] Re: SRU of ubuntu-dev-tools 0.201ubuntu2
autopkgtests passed for jammy and mantic. ** Tags removed: verification-needed verification-needed-jammy verification-needed-mantic ** Tags added: verification-done-jammy verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057716 Title: SRU of ubuntu-dev-tools 0.201ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/2057716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061079] Re: GTK-ngl (new default backend) rendering issues with the nvidia 470 driver
Does not work on: Graphics: NVIDIA GeForce GT 710 Graphics 1: NVIDIA GeForce GT 710 Posted on 'Ask Ubuntu': After upgrading to 24.04 label from buttons on the settings menu (wifi, wired, etc) disappeared Fresh install yesterday. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061079 Title: GTK-ngl (new default backend) rendering issues with the nvidia 470 driver To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066931] Re: gdm login screen in noble does not display on wayland
Attached the kernel logs (journalctl -b0 -k --until 'May 22 16:31:05', which is when my user login under X began), plus logs for the gdm service as well as the gdm session (which seems to be where most of the actual log activity happens). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066931 Title: gdm login screen in noble does not display on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2066931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066931] Re: gdm login screen in noble does not display on wayland
** Attachment added: "journal-for-gdm-session.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2066931/+attachment/5788985/+files/journal-for-gdm-session.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066931 Title: gdm login screen in noble does not display on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2066931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066931] Re: gdm login screen in noble does not display on wayland
** Attachment added: "journal-for-gdm.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2066931/+attachment/5788984/+files/journal-for-gdm.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066931 Title: gdm login screen in noble does not display on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2066931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066931] Re: gdm login screen in noble does not display on wayland
** Attachment added: "journal-for-kernel.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2066931/+attachment/5788983/+files/journal-for-kernel.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066931 Title: gdm login screen in noble does not display on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2066931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066931] Re: gdm login screen in noble does not display on wayland
sorry, missed your question before, apparently my launchpad mail delivery is unreliable. are you looking for the kernel logs, gdm service, both, something else? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066931 Title: gdm login screen in noble does not display on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2066931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069041] Re: Changing Port in sshd_config and restarting ssh.service without effect
** Tags added: rls-nn-incoming rls-oo-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069041 Title: Changing Port in sshd_config and restarting ssh.service without effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2069041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068834] Re: package plymouth 24.004.60-1ubuntu7 failed to install/upgrade: installed plymouth package post-installation script subprocess returned error exit status 1
** Package changed: plymouth (Ubuntu) => flash-kernel (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068834 Title: package plymouth 24.004.60-1ubuntu7 failed to install/upgrade: installed plymouth package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2068834/+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
I have begun reviewing the adsys upload in the jammy unapproved queue. The review is not yet complete, but I am sending my partial review notes for the desktop team to respond to. First, I note that since this is a new upstream version, there are a number of bugs referenced in the changelog that are not going to go through SRU verification. Per https://wiki.ubuntu.com/StableReleaseUpdates#Bug_references_in_changelogs, please update the descriptions of these bugs to indicate this explicitly, so it is clear as part of the SRU review process that these are net SRU bugs that are missing the SRU bug template. The bugs referenced in the .changes are: LP: #2012371 LP: #2020682 LP: #2024377 LP: #2037270 LP: #2037271 LP: #2044112 LP: #2049061 LP: #2051363 LP: #2054445 Then, I have reviewed the changes to the Debian packaging in this package. I have prioritized this initially because as a rule, exceptions for new upstream versions of software do not extend to packaging changes since those pertain to distro integration and not upstream code. My observations: - debian/prerm: this change is simply incorrect and clearly untested, because dpkg NEVER calls a prerm script with an argument of 'purge'; 'purge' is only ever given as an argument to a postrm script. This change to the prerm should be reverted, in devel and in the SRU in the queue; and brought back only after there is a verified implementation with a test case. - apport hook changes: no runtime impact. accepted. - addition of a new empty /var/lib/adsys dir: accepted. - installation of additional adsys python module: accepted. - lintian overrides change: no runtime impact. accepted. - build dep on golang-1.22-go: golang-go in jammy is 1.18. accepted. - added build-deps: accepted. - krb5/winbind as an alternative to sssd: why? not discussed in the changelog and the integration of krb5+winbind directly, vs sssd, is strictly inferior. - addition of Depends: apparmor - unusual; packages which integrate with apparmor do not in general depend on it. Basically irrelevant anyway since snapd does depend on apparmor and is mandatory. But I think this should be dropped in devel. - additional of dependency on nfs-common: since nfs mounts are not used by default, and are overall uncommon in AD environments, I believe this better fits the policy definition of a Recommends rather than a Depends. However, adsys is opt-in and in either case will pull in nfs-common by default so I will not block on this. I will follow up with any review comments on the upstream changes incrementally. ** Changed in: adsys (Ubuntu Jammy) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/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 2066995] Re: apport-gtk keeps prompting to report crashes in a loop
> It seems to boil down to a race condition between the apport postinst > and the whoopsie postinst, the latter correctly chmoding /var/crash > to 3777 *if it creates it*. My read of the postinst is that it correctly chmod's /var/crash regardless of whether it did the creating: mkdir -p -m 3777 /var/crash chmod g+s /var/crash chgrp whoopsie /var/crash I've confirmed that 'mkdir -p -m' doesn't change the mode of an existing directory. And /var/crash has been on my system since 2019 when this system was installed, so it's not new here? Running `dpkg-reconfigure whoopsie` (i.e., triggering a rerun of the postinst) is sufficient to fix the directory permissions. But it must have been something else besides the apport postinst that dropped the g+s bit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066995 Title: apport-gtk keeps prompting to report crashes in a loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2066995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066995] Re: apport-gtk keeps prompting to report crashes in a loop
$ journalctl --no-pager -lu apport-autoreport.service -- No entries -- $ FTR: │ ├─app-gnome-update\x2dnotifier-14736.scope │ │ ├─ 14736 /usr/bin/update-notifier │ │ ├─1602383 /usr/lib/update-notifier/livepatch-notification │ │ ├─2268421 /usr/bin/python3 /usr/share/apport/apport-gtk │ │ ├─2268570 /usr/bin/python3 /usr/share/apport/apport-gtk │ │ └─2268868 /usr/bin/python3 /usr/share/apport/apport-gtk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066995 Title: apport-gtk keeps prompting to report crashes in a loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2066995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066995] Re: apport-gtk keeps prompting to report crashes in a loop
$ ls -ld /var/crash/ drwxrwxrwt 2 root whoopsie 3 Jun 7 15:16 /var/crash/ $ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066995 Title: apport-gtk keeps prompting to report crashes in a loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2066995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068762] [NEW] diffstat assert failure: *** buffer overflow detected ***: terminated
Public bug reported: $ debdiff adsys*dsc | diffstat gpgv: Signature made Thu Jun 6 05:46:03 2024 PDT gpgv:using DSA key DD00EF8F4D23C30D78EC990998B24A9CE4AC208E gpgv: Can't check signature: No public key dpkg-source: warning: cannot verify inline signature for /tmp/adsys_0.14.1~22.04.dsc: no acceptable signature found gpgv: Signature made Tue Jul 4 10:39:13 2023 PDT gpgv:using RSA key E2A94CC41C753DEC7874962EC537E004805EE657 gpgv: Can't check signature: No public key dpkg-source: warning: cannot verify inline signature for /tmp/adsys_0.9.2~22.04.2.dsc: no acceptable signature found *** buffer overflow detected ***: terminated Aborted (core dumped) $ ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: diffstat 1.66-1build1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_6_8_0_31_31_generic_104 zfs ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 AssertionMessage: *** buffer overflow detected ***: terminated CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jun 7 12:29:49 2024 Dependencies: gcc-14-base 14-20240412-0ubuntu1 libc6 2.39-0ubuntu8.2 libgcc-s1 14-20240412-0ubuntu1 libidn2-0 2.3.7-2build1 libunistring5 1.1-2build1 ExecutablePath: /usr/bin/diffstat InstallationDate: Installed on 2019-12-23 (1628 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) JournalErrors: Jun 07 12:29:42 hostname sudo[2235834]: pam_krb5(sudo:setcred): (user username) credential reinitialization in a setuid context ignored ProcCmdline: diffstat RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SignalName: SIGABRT SourcePackage: diffstat StacktraceTop: __libc_message_impl (fmt=fmt@entry=0x7776e5ec5765 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:132 __GI___fortify_fail (msg=msg@entry=0x7776e5ec574c "buffer overflow detected") at ./debug/fortify_fail.c:24 __GI___chk_fail () at ./debug/chk_fail.c:28 __mbsrtowcs_chk (dst=, src=, len=, ps=, dstlen=) at ./debug/mbsrtowcs_chk.c:27 ?? () Title: diffstat assert failure: *** buffer overflow detected ***: terminated UpgradeStatus: Upgraded to noble on 2024-05-22 (16 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sbuild src sudo modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2024-05-23T16:12:43.275502 separator: ** Affects: diffstat (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace noble ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068762 Title: diffstat assert failure: *** buffer overflow detected ***: terminated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/diffstat/+bug/2068762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install
Hello Dave, or anyone else affected, Accepted webkit2gtk into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/webkit2gtk/2.44.2-0ubuntu0.24.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- 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. ** 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/2037015 Title: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062146] Re: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile
Hello Daniel, or anyone else affected, Accepted webkit2gtk into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/webkit2gtk/2.44.2-0ubuntu0.24.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- 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. ** 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/2062146 Title: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2062146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043084] Please test proposed package
Hello Chengen, or anyone else affected, Accepted grub2-signed into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grub2-signed/1.187.8~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043084 Title: GRUB menu loading failure via HTTP Boot on BlueField To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/2043084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043084] Re: GRUB menu loading failure via HTTP Boot on BlueField
Hello Chengen, or anyone else affected, Accepted grub2-unsigned into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grub2-unsigned/2.06-2ubuntu14.5 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: grub2-unsigned (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal ** Changed in: grub2-signed (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043084 Title: GRUB menu loading failure via HTTP Boot on BlueField To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/2043084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043084] Re: GRUB menu loading failure via HTTP Boot on BlueField
Hello Chengen, or anyone else affected, Accepted grub2-unsigned into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grub2-unsigned/2.06-2ubuntu14.5 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: grub2-unsigned (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy ** Also affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Changed in: grub2-signed (Ubuntu) Status: New => Fix Released ** Changed in: grub2-signed (Ubuntu Noble) Status: New => Fix Released ** Changed in: grub2-signed (Ubuntu Mantic) Status: New => Invalid ** Changed in: grub2-signed (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043084 Title: GRUB menu loading failure via HTTP Boot on BlueField To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/2043084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043084] Please test proposed package
Hello Chengen, or anyone else affected, Accepted grub2-signed into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/grub2-signed/1.187.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- 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/2043084 Title: GRUB menu loading failure via HTTP Boot on BlueField To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/2043084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043084] Re: GRUB menu loading failure via HTTP Boot on BlueField
** Description changed:
[Impact]
The GRUB menu fails to load via HTTP boot but functions properly with PXE
boot, displaying the error message:
error: Fail to send a request! status=0x8002.
The error code 0x8002 corresponds to GRUB_EFI_INVALID_PARAMETER.
Notably, this issue is unreproducible in QEMU but surfaces on BlueField.
[Fix]
Bisecting Oracle's patches, we confirmed with the customer that the issue was
resolved with the following commit:
-
https://github.com/rhboot/grub2/commit/205b7b44bb2a7911f1e8c1ce22d66c111a4b429e
+
https://github.com/rhboot/grub2/commit/205b7b44bb2a7911f1e8c1ce22d66c111a4b429e
[Test Plan]
We've requested the customer to test the patch on BlueField.
- Our test plan will focus on checking for any regressions after applying this
patch.
+ Our test plan will focus on checking for any regressions after applying this
patch and will include testing on machines in the Canonical hyperscale lab.
1. Run a DHCP server on the host and configure /etc/dhcp/dhcpd.conf with the
provided content.
...
host http_boot {
- option host-name "http_boot";
- hardware ethernet XX:XX:XX:XX:XX:XX;
- fixed-address 192.168.122.10;
- class "HTTPClient" {
- match if substring (option vendor-class-identifier, 0, 10) = "HTTPClient";
- option vendor-class-identifier "HTTPClient";
- filename <-efi's path->;
- }
+ option host-name "http_boot";
+ hardware ethernet XX:XX:XX:XX:XX:XX;
+ fixed-address 192.168.122.10;
+ class "HTTPClient" {
+ match if substring (option vendor-class-identifier, 0, 10) = "HTTPClient";
+ option vendor-class-identifier "HTTPClient";
+ filename <-efi's path->;
+ }
}
...
2. Start a UEFI VM and use "virsh console" for access.
3. Execute "systemctl reboot --firmware-setup" in the console to enter the
UEFI interface.
4. Test the successful loading of the GRUB menu by selecting "Boot Manager"
-> "UEFI HTTPv4."
[Where problems could occur]
The patch only updates a member variable type to comply with UEFI 2.9,
preserving the original behavior.
In QEMU, using EFI v2.70 from EDK II, we can still access the GRUB menu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2043084
Title:
GRUB menu loading failure via HTTP Boot on BlueField
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2043084/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063203] Re: Build ubuntu-core-desktop images
Because this is an entirely new image type that we are not currently
building, the risk of regression for this image type in particular is
effectively nil; and there are other changes included in this SRU that
are time-sensitive; so regardless of what the bug description says, I am
not going to hold up the SRU for this.
- LB_UBUNTU_IMAGE_CHANNEL="${LB_UBUNTU_IMAGE_CHANNEL:-candidate}"
+ LB_UBUNTU_IMAGE_CHANNEL="${LB_UBUNTU_IMAGE_CHANNEL:-stable}"
Well that is a change that is entirely appropriate, and entirely
undocumented in the changelog!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063203
Title:
Build ubuntu-core-desktop images
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2063203/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064280] Re: Hyperv desktop images no longer building in Noble
Hello Philip, or anyone else affected, Accepted livecd-rootfs into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd- rootfs/24.04.71 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: livecd-rootfs (Ubuntu Noble) Status: New => 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/2064280 Title: Hyperv desktop images no longer building in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2064280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063203] Re: Build ubuntu-core-desktop images
Hello Łukasz, or anyone else affected, Accepted livecd-rootfs into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd- rootfs/24.04.71 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: livecd-rootfs (Ubuntu Noble) Status: Incomplete => 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/2063203 Title: Build ubuntu-core-desktop images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2063203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066905] Re: LXD snap no longer seeded in any images so does not need special handling in unminimize logic
Hello Philip, or anyone else affected, Accepted livecd-rootfs into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd- rootfs/24.04.71 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: livecd-rootfs (Ubuntu Noble) Status: New => 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/2066905 Title: LXD snap no longer seeded in any images so does not need special handling in unminimize logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2066905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063362] Please test proposed package
Hello John, or anyone else affected, Accepted involflt into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/involflt/0.1.0-0ubuntu6~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063362 Title: Backport for 22.04, 20.04, and 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/involflt/+bug/2063362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063362] Re: Backport for 22.04, 20.04, and 18.04
- Added a copyright entry, src/md5.c is public domain. It is not. As https://www.debian.org/doc/packaging-manuals/copyright- format/1.0/ says: Widespread misunderstanding about copyright in general, and the public domain in particular, results in the common assertion that a work is in the public domain when this is partly or wholly untrue for that work. The Wikipedia article on public domain is a useful reference for this subject. There is no provision under US copyright law for a copyright holder to grant a work to the public domain. Legally a work only enters the public domain only when copyright term lapses, or if it is a government work to which no copyright is attached. What you can say here is that: - the copyright holder is waiving all of their rights under copyright - the work can be treated AS IF it is in the public domain because that is the copyright holder's intent but the copyright still EXISTS and the debian copyright format still expects you to document this, including the use of the Copyright: field - which, because it is missing here, means the file does not parse correctly according to the standard. Furthermore, changing debian/copyright in an SRU upload whose changelog says that it is a backport, without also changing it in the devel series, is a bad call. ** Changed in: involflt (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063362 Title: Backport for 22.04, 20.04, and 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/involflt/+bug/2063362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063362] Re: Backport for 22.04, 20.04, and 18.04
Hello John, or anyone else affected, Accepted involflt into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/involflt/0.1.0-0ubuntu6~22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: involflt (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/2063362 Title: Backport for 22.04, 20.04, and 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/involflt/+bug/2063362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2037137] Re: Enable NX support for ARM VMs
Desktop TPM FDE and edk2 intersect where it comes to testing the implementation in VMs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2037137 Title: Enable NX support for ARM VMs To manage notifications about this bug go to: https://bugs.launchpad.net/shim/+bug/2037137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059978] Re: linux-aws-5.15 ADT test MISS because it's unable to find package
Since the tgt source package builds no architecture: all packages, and there are no armhf packages published, I think there is a bug in whatever is trying to trigger this test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059978 Title: linux-aws-5.15 ADT test MISS because it's unable to find package To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2059978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059978] Re: linux-aws-5.15 ADT test MISS because it's unable to find package
Per https://launchpad.net/ubuntu/noble/armhf/tgt the binaries were removed because they depend on another package (ceph) that is not portable to armhf. So a no-change rebuild is not appropriate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059978 Title: linux-aws-5.15 ADT test MISS because it's unable to find package To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2059978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066995] Re: apport-gtk keeps prompting to report crashes in a loop
> Steve, do you still have the crash file on your system? No, but I have no trouble generating more of them on demand. > If so, could you give us its mod and owner? -rw-r- 1 vorlon vorlon 41580 Jun 3 17:51 /var/crash/_usr_bin_grep- merges.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066995 Title: apport-gtk keeps prompting to report crashes in a loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2066995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067814] Re: não entra no app e não consegue instalar nada / does not enter the app and cannot install anything
Nota-se que vc instalou o Ubuntu 20.04 LTS, uma versão de fa 4 anos. É recomendável que instale a versão atual (i.e. o Ubuntu 24.04 LTS). Além disso, não vejo aqui nada que descreva um falho no software de Ubuntu. Se vc precisa de suporte técnico, https://ubuntu.com/support#community tem uma lista de recursos. ** Changed in: ubuntu Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067814 Title: não entra no app e não consegue instalar nada / does not enter the app and cannot install anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2067814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install
** Changed in: webkit2gtk (Ubuntu Noble) Milestone: None => ubuntu-24.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2037015 Title: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install
My understanding is that while this bug manifests as graphical corruption in the common case, when running on a RPi booted from an SSD the memory map is permuted in such a way that it instead results in a crash. Therefore raising the severity of the bug accordingly, in line with duplicate LP: #2064208. ** Changed in: webkit2gtk (Ubuntu Noble) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2037015 Title: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064208] Re: Installer crashes when booting from USB on Raspberry Pi
*** This bug is a duplicate of bug 2037015 *** https://bugs.launchpad.net/bugs/2037015 My understanding is that it was determined this has the same root cause as LP: #2037015. Marking it as a duplicate. ** This bug has been marked a duplicate of bug 2037015 Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064208 Title: Installer crashes when booting from USB on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2064208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062176] Re: Cannot launch armhf containers on arm64 host under noble
I initially reassigned this from lxd to glibc on the basis that glibc is responsible for deciding whether to use the 64-bit vs 32-bit time_t variants for all the syscalls it wraps, and give preference to the 64-bit variants; HOWEVER, Note: glibc provides no wrapper for futex(), necessitating the use of syscall(2). futex(2). Confirmed that there are no 'futex' symbols in glibc. So this is not a bug in glibc, and there is insufficient information here or in the linked github issue to say where the problem lies. The test case given in the github issue is invalid, because it builds without the default noble compiler flags of -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 so tells us nothing about what code is actually being run as part of noble that depends on the old syscall. Someone will need to strace this to find the guilty binary. ** Package changed: glibc (Ubuntu) => lxd (Ubuntu) ** Changed in: lxd (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062176 Title: Cannot launch armhf containers on arm64 host under noble To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/2062176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062176] Re: Cannot launch armhf containers on arm64 host under noble
** Package changed: lxd (Ubuntu) => glibc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062176 Title: Cannot launch armhf containers on arm64 host under noble To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/2062176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064123] Re: dpkg: dependency problems prevent configuration of plymouth-theme-ubuntutext
** Changed in: plymouth (Ubuntu) Status: Fix Committed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064123 Title: dpkg: dependency problems prevent configuration of plymouth-theme- ubuntutext To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2064123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059156] Re: proposed-migration for m2crypto 0.40.1-2build1
Note for the record that this is now regressed in baseline (in the release pocket) and therefore does not block migrations, which is why the hint was dropped as no longer required. Fixing the tests so that they pass is of course ideal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059156 Title: proposed-migration for m2crypto 0.40.1-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/m2crypto/+bug/2059156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2029089] Update Released
The verification of the Stable Release Update for distro-info 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/2029089 Title: [SRU] Please backport UbuntuDistroInfo().get_all(result="object") to Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distro-info/+bug/2029089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067662] Re: Cannot install software-properties-common=0.96.20.13 on Ubuntu 16.04 anymore
This was a result of an unfortunate out-of-order release of SRUs to xenial-updates. distro-info 0.14ubuntu0.3 was present in xenial- proposed waiting for release, but there was nothing in our process which ensured they would be released in order. As distro-info has also passed its SRU verification, I have released it now. You should see software-properties-common installable within a few hours as this propagates to mirrors. ** Changed in: software-properties (Ubuntu) Status: Incomplete => 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/2067662 Title: Cannot install software-properties-common=0.96.20.13 on Ubuntu 16.04 anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2067662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2055806] Re: sshd.service ssh.socket systemd-tmpfiles-setup:Before= - Missing privilege separation directory: /run/sshd
On Mon, Jun 03, 2024 at 02:22:48AM -, JakFrost wrote: > After the fix, there is still a problem happening but I don't know if > it's SystemD related or due to some of my Units that I created for a few > services and auto-mount points. > I did an upgrade from Ubuntu 23.10 to 24.04 also and updated all > packages. > Now the problem shows up like this, with SystemD deleting the ssh.socket > start job! WTF! > 2024-06-02T03:14:29.787646-05:00 htpc kernel: systemd[1]: > sockets.target: Found ordering cycle on ssh.socket/start Further to Nick's comment: there are no (known, widely seen) ordering cycles in the Ubuntu-provided systemd units for ssh. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055806 Title: sshd.service ssh.socket systemd-tmpfiles-setup:Before= - Missing privilege separation directory: /run/sshd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2055806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063041] Re: crashes immediately on pressing a key with python3.12 (Ubuntu Noble 24.04)
Ubuntu 24.04 internet upgrade from 23.10 Onboard worked prior to the upgrade. Afterward the keyboard would display but instantly vanish when any key was pressed, followed by a request to submit a report, which I did. It fails in every attempt to use the keyboard. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063041 Title: crashes immediately on pressing a key with python3.12 (Ubuntu Noble 24.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/2063041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
** Changed in: aptdaemon Assignee: Yam budhathoki (yam-8138) => (unassigned) ** Changed in: aptdaemon (Ubuntu) Assignee: Yam budhathoki (yam-8138) => (unassigned) ** Changed in: debconf (Ubuntu) Assignee: Yam budhathoki (yam-8138) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/aptdaemon/+bug/349469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058051] Re: [SRU] Backport 0.107.1-3 to Ubuntu 23.10
+ * debian/netplan.io.preinst: +- This preinst script is intended to cleanup the .pyc files from + share/netplan/netplan. This directory is supposed to be removed after + the upgrade from netplan.io 0.106.1 to 0.107, as the Python code + was moved to it's own python3-netplan package, but it's left behind + due to Python cached files. This warrants a separate test case. Also, I have a system here which is upgraded to noble and I have an orphaned /usr/share/netplan/netplan/cli/commands/ directory. So it appears this is not fixed in noble; it should be fixed in noble before/at the same time as fixing in mantic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058051 Title: [SRU] Backport 0.107.1-3 to Ubuntu 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2058051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058051] Re: [SRU] Backport 0.107.1-3 to Ubuntu 23.10
> The changes below though will cause backwards compatibility issues if the > user upgrades to the new version of netplan.io, starts to use the new > features and > then decides to downgrade for some reason: That's not a backwards-compatibility issue, please omit this in the future. ** Description changed: Stable Release Update for netplan.io 0.107.1-3 to Mantic. This version has many bug fixes and new features we want to make available to users of Ubuntu 23.10. netplan.io has an SRU exception for backporting new versions with new features https://wiki.ubuntu.com/NetplanUpdates Another SRU, for Jammy, was prepared in a separate LP bug: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2058031. As the package is slightly different (due to backwards compatibility patches) and on Mantic we have the integration with Network Manager (which can cause different problems and requires more tests) I thought it would be more appropriate to work on the Mantic SRU in a different LP bug. [Impact] This release contains both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: - - In terms of new features there were not big changes. - The changes below though will cause backwards compatibility issues if the - user upgrades to the new version of netplan.io, starts to use the new features and - then decides to downgrade for some reason: * wifi: add support for WPA3-Enterprise https://github.com/canonical/netplan/pull/402 https://bugs.launchpad.net/netplan/+bug/2029876 * wifi: make it possible to have a psk and an eap password simultaneously https://github.com/canonical/netplan/pull/416 * parse: allow COMMON_LINK_HANDLERS for VRFs https://github.com/canonical/netplan/pull/401 The change below generates a different backend configuration for wpa-supplicant. Although is will not cause major backwards compatibility problems: * wifi: support WPA2 and WPA3 Personal simultaneously https://github.com/canonical/netplan/pull/404 In addition to all the changes from netplan.io 0.107.1-3, a couple of bug fixes were imported from netplan.io 1.0-1: * debian/patches/lp2041727: Check if ovsdb-server.service is active before displaying warning https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2041727 https://github.com/canonical/netplan/pull/421 This fixes an annoying warning message that many users were seeing when they call "netplan apply". * d/p/0004-tests-assert-generated-.service-files-in-assert_srio.patch, d/p/0005-tests-sriov-test-if-the-generated-netplan-rebind-ser.patch, d/p/0006-sriov-don-t-generate-duplicate-entries-in-the-rebind.patch: Don't generate duplicate entries in the netplan-sriov-rebind.service https://github.com/canonical/netplan/pull/437 This fixes a duplication problem where "netplan rebind" could process the same SR-IOV interface multiple times. See the changelog entry below for a full list of changes and bugs. [Test Plan] The following development and SRU process was followed: https://wiki.ubuntu.com/NetplanUpdates Netplan contains an extensive integration test suite that is ran using the SRU package for each releases. This test suite's results are available here: http://autopkgtest.ubuntu.com/packages/n/netplan.io A successful run is required before the proposed netplan package can be let into -updates. The netplan team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Netplan team members will not mark ‘verification-done’ until this has happened. Testing netplan upgrade 1) Launch a Mantic LXD VM lxc launch ubuntu:mantic mantic-vm --vm lxc shell mantic-vm 2) Check Netplan works netplan get netplan apply 3) Install Network Manager so we can test the netplan-everywhere integration apt update apt install network-manager 4) Change the default renderer to NetworkManager in /etc/netplan/50-cloud-init.yaml network: renderer: NetworkManager version: 2 ethernets: enp5s0: dhcp4: true 5) Apply the configuration netplan apply nmcli con show 6) Add a new connection with nmcli nmcli con add type dummy ifname dummy0 7) Check that a new 'dummy-device' is present in Netplan netplan get 8) Add the PPA with the new package add-apt-repository ppa:danilogondolfo/netplan-sru apt update ; apt -y upgrade 9) Restart Network Manager so it will load the new libnetplan systemctl restart NetworkManager 10) Add a new interface using nmcli nmcli con add type dummy ifname dummy1 11) Check it will show up in the Netplan configuration netplan get 12) Delete both of the new connections nmcli con del dummy-dummy0 nmcli con del dummy-dummy1 13)
[Bug 2061954] Re: filezilla crashed with SIGABRT in start_thread()
Hello Phil, or anyone else affected, Accepted libfilezilla into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libfilezilla/0.46.0-3.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- 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: libfilezilla (Ubuntu Noble) Status: New => 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/2061954 Title: filezilla crashed with SIGABRT in start_thread() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfilezilla/+bug/2061954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
The bug task for bubblewrap was marked 'wontfix' on the basis that John said it will not get an unconfined profile. But this is wrong; that is saying only that a particular solution is rejected, not that we will not be making changes to this package. bubblewrap is part of the desktop and having it not work is a significant release regression, to the point where people are now proposing SRUs to work around this breakage by bypassing the security benefits of bubblewrap's sandboxing (LP: #2065708). This needs to be addressed. ** Changed in: bubblewrap (Ubuntu) Importance: Undecided => Critical ** Changed in: bubblewrap (Ubuntu) Status: Won't Fix => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065708] Re: Add Picture button in Background does not allow you to select wallpaper
The proposed solution here deals with bubblewrap being broken by apparmor in noble by altogether eliminating the intended security benefits of the bubblewrap sandboxing of the thumbnailer. I do not think this is an appropriate resolution of this issue. We need to fix bubblewrap to work with current apparmor, not downgrade the security of the desktop in noble. I have reopened the bubblewrap task on LP: #2046844 and escalated to the AppArmor team. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065708 Title: Add Picture button in Background does not allow you to select wallpaper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-control-center/+bug/2065708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063200] Re: useradd --extrausers --groups tries to lock /etc/group
Hello Valentin, or anyone else affected, Accepted shadow into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/shadow/1:4.13+dfsg1-4ubuntu3.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. ** Description changed: [ Impact ] On Ubuntu Core 24 calling the command line useradd --extrausers --groups somegroup somenewuser ... fails with: useradd: cannot lock /etc/group; try again later. It worked on 22.04. /etc is not writable. It also fails if somegroup is a group in extrausers. [ Test Plan ] Part of the upload is adding an autopkgtest script testing useradd and usermod in the extrausers+readonly-etc case. In addition, the following commands should be run as root in a fresh container: ``` # Install prerequisites apt install libnss-extrausers - vim /etc/nsswitch.conf # enable extrausers in group, passwd, shadow and gshadow + sed -i -r -e'/^(passwd|group|shadow|gshadow)/ s/$/ extrausers/' /etc/nsswitch.conf # enable extrausers in group, passwd, shadow and gshadow # Sanity checks of "normal" path groupadd etcgroup useradd --groups etcgroup etcuser id etcuser | grep etcgroup groupadd etcgroup2 usermod --groups etcgroup2 etcuser id etcuser | grep etcgroup2 useradd --groups nullgroup etcuser || echo Successfully rejected invalid group ls /var/lib/extrausers/ # should be empty # Sanity checks of "extrausers" path in rw context groupadd --extrausers extragroup useradd --extrausers --groups extragroup extrauser # currently fails id extrauser | grep extragroup useradd --extrausers extrauser2 id extrauser2 usermod --extrausers --groups extragroup extrauser2 id extrauser2 | grep extragroup # Sanity checks of "extrausers" path in ro context mv /etc /etc-rw mkdir /etc mount -o bind,ro /etc-rw /etc groupadd --extrausers extragroup2 useradd --extrausers --groups etcgroup extrauser3 id extrauser4 | grep etcgroup usermod --extrausers --groups extragroup2 extrauser3 id extrauser4 | grep extragroup2 ``` - Furthermore, validation from the Ubuntu Core team that this actually fixes their use case is required. [ Where problems could occur ] Regression potential is in the group validation stage of the `usermod` and `useradd` tools. Besides the usual risks related to C code, the various failure scenarios that come to mind are: * try to add the user to an non-existing local group, which would fail further - down with a different error message + down with a different error message * actually fail to identify a valid local group * Fail to either add the user to the system, or the user to the group * Update the wrong file (/var/lib/extrausers/* vs /etc/*) ** Changed in: shadow (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/2063200 Title: useradd --extrausers --groups tries to lock /etc/group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
+ * New patches: +- d/p/0002-collect-refactor-_format_version.patch +- d/p/0003-pacemaker-Use-pep440-formatted-version-on-comparison.patch +- d/p/0004-cirrus-Run-tests-on-latest-daily-builds-for-ubuntu.patch +- d/p/0005-processor-handle-msr-module-loading-via-predicate.patch Why, when this is an upstream release for which Canonical is the upstream, are there local Debian patches included here? + * d/control: +- Add 'python3-packaging' as part of the runtime depends. +- Add 'python3-packaging' as part of the build depends. +- Add 'python3-yaml' as part of the build depends. When making such packaging changes in an SRU, it should be documented in the changelog why they are necessary and justified. I can infer a reason for the python3-packaging addition from the debdiff, but shouldn't have to: the rationale should be documented so that there is no misunderstanding. And it is not at all obvious from the debdiff why python3-yaml is added to the build-dependencies: it was already listed in setup.py before as a requirement but apparently didn't cause a build failure. So explanation is needed here. +- Add 'X-Python3-Version: >= 3.6' to ensure we use the python + revision that is supported. (LP #2038648) Well this is pointless, since python3 is >= 3.6 in all releases after bionic and we don't do SRUs for bionic anymore. +- Add 'python3-boto3' to Suggests This is also pretty pointless as nothing installs package Suggests: by default and users almost never look at this. ** Changed in: sosreport (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/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065867] Re: mgr: failed dependency - no module named distutils
The proposed test case here involves a snap, not the deb which is being SRUed. The test plan needs to provide a way for testing the .deb from the noble-proposed pocket. ** Changed in: ceph (Ubuntu Oracular) Status: Triaged => Fix Committed ** Changed in: ceph (Ubuntu Noble) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065867 Title: mgr: failed dependency - no module named distutils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/2065867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064717] Re: ceph-volume needs "packaging" and "ceph" modules
** Changed in: ceph (Ubuntu Oracular) 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/2064717 Title: ceph-volume needs "packaging" and "ceph" modules To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceph-osd/+bug/2064717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063456] Re: package cephadm: dependency "cephadmlib" missing
** Changed in: ceph (Ubuntu Oracular) 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/2063456 Title: package cephadm: dependency "cephadmlib" missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/2063456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060882] Re: [SRU] usrpctl fails to run
Hello Sudip, or anyone else affected, Accepted uhd into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/uhd/4.4.0.0+ds1-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- 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: uhd (Ubuntu Mantic) Status: New => Fix Committed ** Tags added: verification-needed-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060882 Title: [SRU] usrpctl fails to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uhd/+bug/2060882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921914] Proposed package upload rejected
An upload of quickml to mantic-proposed has been rejected from the upload queue for the following reason: "includes changes rejected by Debian maintainer". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921914 Title: [SRU] package quickml 0.7-5.1 failed to install/upgrade: installed quickml package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quickml/+bug/1921914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921914] Proposed package upload rejected
An upload of quickml to focal-proposed has been rejected from the upload queue for the following reason: "includes changes rejected by Debian maintainer". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921914 Title: [SRU] package quickml 0.7-5.1 failed to install/upgrade: installed quickml package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quickml/+bug/1921914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921914] Proposed package upload rejected
An upload of quickml to jammy-proposed has been rejected from the upload queue for the following reason: "includes changes rejected by Debian maintainer". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921914 Title: [SRU] package quickml 0.7-5.1 failed to install/upgrade: installed quickml package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quickml/+bug/1921914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921914] Proposed package upload rejected
An upload of quickml to noble-proposed has been rejected from the upload queue for the following reason: "includes changes rejected by Debian maintainer". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921914 Title: [SRU] package quickml 0.7-5.1 failed to install/upgrade: installed quickml package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quickml/+bug/1921914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921914] Re: [SRU] package quickml 0.7-5.1 failed to install/upgrade: installed quickml package post-installation script subprocess returned error exit status 1
So effectively: - the quickml package has been unusable out of the box for at least 4 years due to a missing dependency - a bug was filed 3 years ago, but no one cared enough about the impact to escalate it before now - the package also (apparently) depends on the existence of /etc/mailname at runtime; but rather than populating it with correct contents (an actual mailname), you are making it an empty file, which is incorrect and could interfere with the proper functioning of other packages which may be installed later and expect to prompt the user for the value to populate the file with if it does not exist - the Debian maintainer has rejected the latter change. I do not think this upload is suitable for SRU. Rejecting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921914 Title: [SRU] package quickml 0.7-5.1 failed to install/upgrade: installed quickml package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quickml/+bug/1921914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060882] Re: [SRU] usrpctl fails to run
Hello Sudip, or anyone else affected, Accepted uhd into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/uhd/4.6.0.0+ds1-5.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: uhd (Ubuntu Noble) Status: New => 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/2060882 Title: [SRU] usrpctl fails to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uhd/+bug/2060882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2015017] Please test proposed package
Hello David, or anyone else affected, Accepted graphviz into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/graphviz/2.42.2-6ubuntu0.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/2015017 Title: [SRU] scaling is wrong in SVG output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/2015017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2015017] Re: [SRU] scaling is wrong in SVG output
Hello David, or anyone else affected, Accepted graphviz into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/graphviz/2.42.2-9ubuntu0.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: graphviz (Ubuntu Noble) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-noble ** Changed in: graphviz (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: verification-needed-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2015017 Title: [SRU] scaling is wrong in SVG output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/2015017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2015017] Please test proposed package
Hello David, or anyone else affected, Accepted graphviz into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/graphviz/2.42.2-7ubuntu0.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: graphviz (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/2015017 Title: [SRU] scaling is wrong in SVG output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/2015017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063895] Re: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png
Hello Aaron, or anyone else affected, Accepted edubuntu-artwork into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/edubuntu- artwork/24.04.26.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: edubuntu-artwork (Ubuntu Noble) Status: In Progress => Fix Committed ** Tags removed: verification-done verification-done-noble ** 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/2063895 Title: Multiple plymouth themes display wrong keyboard layout for decryption due to outdated keymap-render.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-artwork/+bug/2063895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067013] Re: package libpam-modules 1.3.1-5ubuntu4.7 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2
Your dpkg log shows the following prompt: Configuring libpam-modules you are using pam_tally or pam_tally2 in your configuration The pam_tally and pam_tally2 modules have been removed from PAM. You are using one of these modules in your PAM configuration in /etc/pam.d. You must remove the uses of these modules before PAM can be upgraded; including these modules in your PAM configuration after the upgrade will stop users from being able to log into the system. Consider the pam_faillock module as a replacement for pam_tally. This is not a bug. The pam package is saving you from making it impossible to log into your system after upgrade. If you were using the supported `do-release-upgrade` tool for upgrading between releases, this would have notified you at the beginning of the upgrade and not resulted in a package upgrade failure. ** Changed in: pam (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/2067013 Title: package libpam-modules 1.3.1-5ubuntu4.7 failed to install/upgrade: new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2067013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066995] Re: apport-gtk keeps prompting to report crashes in a loop
> Can you provide the journal log from during that time frame? For what service? For whoopsie, I see: May 23 13:58:13 homer systemd[1]: Started whoopsie.service - crash report submission. May 23 13:58:13 homer whoopsie[147832]: [13:58:13] Using lock path: /var/lock/whoopsie/lock May 23 13:58:13 homer systemd[1]: whoopsie.service: Deactivated successfully. May 23 13:58:13 homer systemd[1]: Started whoopsie.service - crash report submission. May 23 13:58:13 homer whoopsie[147855]: [13:58:13] Using lock path: /var/lock/whoopsie/lock May 23 13:58:13 homer systemd[1]: whoopsie.service: Deactivated successfully. May 23 13:58:20 homer systemd[1]: Started whoopsie.service - crash report submission. May 23 13:58:20 homer whoopsie[148149]: [13:58:20] Using lock path: /var/lock/whoopsie/lock May 23 13:58:20 homer systemd[1]: whoopsie.service: Deactivated successfully. May 23 13:58:44 homer systemd[1]: Started whoopsie.service - crash report submission. May 23 13:58:44 homer whoopsie[148216]: [13:58:44] Using lock path: /var/lock/whoopsie/lock May 23 13:58:44 homer systemd[1]: whoopsie.service: Deactivated successfully. May 23 13:58:48 homer systemd[1]: Started whoopsie.service - crash report submission. May 23 13:58:48 homer whoopsie[148496]: [13:58:48] Using lock path: /var/lock/whoopsie/lock May 23 13:58:48 homer systemd[1]: whoopsie.service: Deactivated successfully. May 23 13:59:11 homer systemd[1]: Started whoopsie.service - crash report submission. May 23 13:59:11 homer whoopsie[148522]: [13:59:11] Using lock path: /var/lock/whoopsie/lock May 23 13:59:11 homer whoopsie[148522]: [13:59:11] Parsing /var/crash/_usr_bin_python-argcomplete-check-easy-install-script.1000.crash. May 23 13:59:11 homer whoopsie[148522]: [13:59:11] Unable to parse report (/var/crash/_usr_bin_python-argcomplete-check-easy-install-script.1000.crash): /var/crash/_usr_bin_python-argcomplete-check-easy-install-script.1000.crash could not be opened. May 23 13:59:11 homer systemd[1]: whoopsie.service: Deactivated successfully. May 23 13:59:25 homer systemd[1]: Started whoopsie.service - crash report submission. May 23 13:59:25 homer whoopsie[148594]: [13:59:25] Using lock path: /var/lock/whoopsie/lock May 23 13:59:25 homer whoopsie[148594]: [13:59:25] Parsing /var/crash/_usr_bin_python-argcomplete-check-easy-install-script.1000.crash. May 23 13:59:25 homer whoopsie[148594]: [13:59:25] Unable to parse report (/var/crash/_usr_bin_python-argcomplete-check-easy-install-script.1000.crash): /var/crash/_usr_bin_python-argcomplete-check-easy-install-script.1000.crash could not be opened. May 23 13:59:25 homer systemd[1]: whoopsie.service: Deactivated successfully. May 23 13:59:25 homer systemd[1]: Started whoopsie.service - crash report submission. May 23 13:59:25 homer whoopsie[148608]: [13:59:25] Using lock path: /var/lock/whoopsie/lock May 23 13:59:25 homer systemd[1]: whoopsie.service: Deactivated successfully. May 23 13:59:29 homer systemd[1]: Started whoopsie.service - crash report submission. May 23 13:59:29 homer whoopsie[148618]: [13:59:29] Using lock path: /var/lock/whoopsie/lock May 23 13:59:29 homer systemd[1]: whoopsie.service: Deactivated successfully. May 23 14:01:44 homer systemd[1]: Started whoopsie.service - crash report submission. May 23 14:01:44 homer whoopsie[148787]: [14:01:44] Using lock path: /var/lock/whoopsie/lock May 23 14:01:44 homer systemd[1]: whoopsie.service: Deactivated successfully. May 23 14:01:44 homer systemd[1]: Started whoopsie.service - crash report submission. May 23 14:01:44 homer whoopsie[148813]: [14:01:44] Using lock path: /var/lock/whoopsie/lock May 23 14:01:44 homer systemd[1]: whoopsie.service: Deactivated successfully. May 23 14:04:44 homer systemd[1]: Started whoopsie.service - crash report submission. [...] > Did that application crash multiple times? No. It was a SINGLE crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066995 Title: apport-gtk keeps prompting to report crashes in a loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2066995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066995] Re: apport-gtk keeps prompting to report crashes in a loop
> Did you remove the content there? I did not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066995 Title: apport-gtk keeps prompting to report crashes in a loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2066995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067088] [NEW] gourmand generates SQL that is invalid for postgresql gourmand crashed with (Background on this error at in do_execute(): https://sqlalche.me/e/14/f405)
Public bug reported: Running gourmand with a --database-url pointing to my postgres database fails immediately with the following backtrace. It is generating SQL that may be valid for sqlite but is not valid for postgresql. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gourmand 1.1.0+really1.1.0~rc3-3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 24 08:48:52 2024 ExecutablePath: /usr/bin/gourmand InstallationDate: Installed on 2019-12-23 (1614 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterpreterPath: /usr/bin/python3.12 JournalErrors: May 24 08:48:55 hostname NetworkManager[2893]: [1716565735.9215] device (veth01294ac0): Activation: failed for connection 'Auto Ethernet' PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/gourmand --database-url=postgresql://borges/recipes Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonArgs: ['/usr/bin/gourmand', '--database-url=postgresql://borges/recipes'] PythonDetails: N/A SourcePackage: gourmand Title: gourmand crashed with (Background on this error at in do_execute(): https://sqlalche.me/e/14/f405) UpgradeStatus: Upgraded to noble on 2024-05-22 (2 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sbuild src sudo modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2024-05-23T16:12:43.275502 ** Affects: gourmand (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash noble third-party-packages ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067088 Title: gourmand generates SQL that is invalid for postgresql gourmand crashed with (Background on this error at in do_execute(): https://sqlalche.me/e/14/f405) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gourmand/+bug/2067088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066997] Re: gourmand crashed with ImportError in /usr/lib/python3/dist-packages/extruct/xmldom.py: cannot import name '_ElementStringResult' from 'lxml.etree' (/usr/lib/python3/dist-packages/lxm
** Description changed: - [ Impact ] The extruct package is a python module that cannot be used in noble because it is incompatible with the lxml module that is shipped in noble. [ Test plan ] 1. bad: $ python3 -c 'import extruct' Traceback (most recent call last): - File "", line 1, in - File "/usr/lib/python3/dist-packages/extruct/__init__.py", line 1, in - from ._extruct import SYNTAXES, extract - File "/usr/lib/python3/dist-packages/extruct/_extruct.py", line 9, in - from extruct.dublincore import DublinCoreExtractor - File "/usr/lib/python3/dist-packages/extruct/dublincore.py", line 6, in - from extruct.utils import parse_html - File "/usr/lib/python3/dist-packages/extruct/utils.py", line 5, in - from extruct.xmldom import XmlDomHTMLParser - File "/usr/lib/python3/dist-packages/extruct/xmldom.py", line 9, in - from lxml.etree import ( + File "", line 1, in + File "/usr/lib/python3/dist-packages/extruct/__init__.py", line 1, in + from ._extruct import SYNTAXES, extract + File "/usr/lib/python3/dist-packages/extruct/_extruct.py", line 9, in + from extruct.dublincore import DublinCoreExtractor + File "/usr/lib/python3/dist-packages/extruct/dublincore.py", line 6, in + from extruct.utils import parse_html + File "/usr/lib/python3/dist-packages/extruct/utils.py", line 5, in + from extruct.xmldom import XmlDomHTMLParser + File "/usr/lib/python3/dist-packages/extruct/xmldom.py", line 9, in + from lxml.etree import ( ImportError: cannot import name '_ElementStringResult' from 'lxml.etree' (/usr/lib/python3/dist-packages/lxml/etree.cpython-312-x86_64-linux-gnu.so). Did you mean: '_ElementUnicodeResult'? $ 2. good: $ python3 -c 'import extruct' $ [ Where problems could occur ] The package as shipped is completely unusable so runtime regressions are not possible. The Debian fix for this includes introducing an additional dependency, so new install-time failures are possible but unlikely. No analysis has been done to check for this. - [Original description] + [ Original description ] Well, for the fourth Ubuntu release running, gourmand is completely unusable. Downgrading again to my local copy of gourmand 1.1.0+really1.0.0-3. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gourmand 1.1.0+really1.1.0~rc3-3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 23 16:13:30 2024 ExecutablePath: /usr/bin/gourmand InstallationDate: Installed on 2019-12-23 (1613 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterpreterPath: /usr/bin/python3.12 JournalErrors: -- No entries -- PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/gourmand --database-url=postgresql://borges/recipes Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonArgs: ['/usr/bin/gourmand', '--database-url=postgresql://borges/recipes'] PythonDetails: N/A SourcePackage: gourmand Title: gourmand crashed with ImportError in /usr/lib/python3/dist-packages/extruct/xmldom.py: cannot import name '_ElementStringResult' from 'lxml.etree' (/usr/lib/python3/dist-packages/lxml/etree.cpython-312-x86_64-linux-gnu.so) UpgradeStatus: Upgraded to noble on 2024-05-22 (1 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sbuild src sudo modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2024-05-23T16:12:43.275502 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066997 Title: gourmand crashed with ImportError in /usr/lib/python3/dist- packages/extruct/xmldom.py: cannot import name '_ElementStringResult' from 'lxml.etree' (/usr/lib/python3/dist- packages/lxml/etree.cpython-312-x86_64-linux-gnu.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/extruct/+bug/2066997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066997] Re: gourmand crashed with ImportError in /usr/lib/python3/dist-packages/extruct/xmldom.py: cannot import name '_ElementStringResult' from 'lxml.etree' (/usr/lib/python3/dist-packages/lxm
** Description changed: - Well, for the fourth Ubuntu release running, gourmand is completely - unusable. + + [ Impact ] + The extruct package is a python module that cannot be used in noble because it is incompatible with the lxml module that is shipped in noble. + + [ Test plan ] + 1. bad: + $ python3 -c 'import extruct' + Traceback (most recent call last): + File "", line 1, in + File "/usr/lib/python3/dist-packages/extruct/__init__.py", line 1, in + from ._extruct import SYNTAXES, extract + File "/usr/lib/python3/dist-packages/extruct/_extruct.py", line 9, in + from extruct.dublincore import DublinCoreExtractor + File "/usr/lib/python3/dist-packages/extruct/dublincore.py", line 6, in + from extruct.utils import parse_html + File "/usr/lib/python3/dist-packages/extruct/utils.py", line 5, in + from extruct.xmldom import XmlDomHTMLParser + File "/usr/lib/python3/dist-packages/extruct/xmldom.py", line 9, in + from lxml.etree import ( + ImportError: cannot import name '_ElementStringResult' from 'lxml.etree' (/usr/lib/python3/dist-packages/lxml/etree.cpython-312-x86_64-linux-gnu.so). Did you mean: '_ElementUnicodeResult'? + $ + + 2. good: + $ python3 -c 'import extruct' + $ + + [ Where problems could occur ] + The package as shipped is completely unusable so runtime regressions are not possible. + + The Debian fix for this includes introducing an additional dependency, + so new install-time failures are possible but unlikely. No analysis has + been done to check for this. + + [Original description] + Well, for the fourth Ubuntu release running, gourmand is completely unusable. Downgrading again to my local copy of gourmand 1.1.0+really1.0.0-3. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gourmand 1.1.0+really1.1.0~rc3-3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 23 16:13:30 2024 ExecutablePath: /usr/bin/gourmand InstallationDate: Installed on 2019-12-23 (1613 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterpreterPath: /usr/bin/python3.12 JournalErrors: -- No entries -- PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/gourmand --database-url=postgresql://borges/recipes Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonArgs: ['/usr/bin/gourmand', '--database-url=postgresql://borges/recipes'] PythonDetails: N/A SourcePackage: gourmand Title: gourmand crashed with ImportError in /usr/lib/python3/dist-packages/extruct/xmldom.py: cannot import name '_ElementStringResult' from 'lxml.etree' (/usr/lib/python3/dist-packages/lxml/etree.cpython-312-x86_64-linux-gnu.so) UpgradeStatus: Upgraded to noble on 2024-05-22 (1 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sbuild src sudo modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2024-05-23T16:12:43.275502 ** Changed in: extruct (Ubuntu Noble) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066997 Title: gourmand crashed with ImportError in /usr/lib/python3/dist- packages/extruct/xmldom.py: cannot import name '_ElementStringResult' from 'lxml.etree' (/usr/lib/python3/dist- packages/lxml/etree.cpython-312-x86_64-linux-gnu.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/extruct/+bug/2066997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066997] Re: gourmand crashed with ImportError in /usr/lib/python3/dist-packages/extruct/xmldom.py: cannot import name '_ElementStringResult' from 'lxml.etree' (/usr/lib/python3/dist-packages/lxm
Probably fixed by: extruct (0.16.0-4) unstable; urgency=medium * Add upstream patch to add support for python3 lxml >= 5.2.0 and python3-lxml-html-clean to Depends. -- Christian Marillat Fri, 19 Apr 2024 11:44:13 +0200 ** Information type changed from Private to Public ** Changed in: extruct (Ubuntu) Status: New => Fix Released ** Also affects: gourmand (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: extruct (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: extruct (Ubuntu Noble) 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/2066997 Title: gourmand crashed with ImportError in /usr/lib/python3/dist- packages/extruct/xmldom.py: cannot import name '_ElementStringResult' from 'lxml.etree' (/usr/lib/python3/dist- packages/lxml/etree.cpython-312-x86_64-linux-gnu.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/extruct/+bug/2066997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066995] [NEW] apport-gtk keeps prompting to report crashes in a loop
Public bug reported: /var/crash has the following contents: -rw-r- 1 vorlon vorlon 107490 May 23 16:05 _usr_bin_gourmand.1000.crash -rw-rw-r-- 1 vorlon vorlon0 May 23 16:06 _usr_bin_gourmand.1000.upload -rw--- 1 whoopsie whoopsie 5 May 23 16:07 _usr_bin_gourmand.1000.uploaded -rw-r- 1 vorlon vorlon23647 May 23 13:57 _usr_bin_python-argcomplete-check-easy-install-script.1000.crash -rw-rw-r-- 1 vorlon vorlon0 May 23 13:59 _usr_bin_python-argcomplete-check-easy-install-script.1000.upload -rw--- 1 whoopsie whoopsie 5 May 23 13:59 _usr_bin_python-argcomplete-check-easy-install-script.1000.uploaded As seen, the .upload / .uploaded files were created within 2 minutes of each of the crashes. But after submitting the crash report for /usr/bin/python-argcomplete- check-easy-install-script, I left my desktop for a while. I came back to find at least TWENTY dialogs prompting me to submit the same crash report. The only way to stop the system from creating more prompts is to remove these files from disk. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apport 2.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportLog: ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 23 16:06:43 2024 InstallationDate: Installed on 2019-12-23 (1613 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to noble on 2024-05-22 (1 days ago) ** Affects: apport (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-bug noble ** Changed in: apport (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066995 Title: apport-gtk keeps prompting to report crashes in a loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2066995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066931] [NEW] gdm login screen in noble does not display on wayland
Public bug reported: after upgrade from mantic to noble, my laptop booted to the firmware splash screen with Ubuntu logo, plus a mouse cursor. The gdm login screen did not appear. Switching to disable wayland (as in the attached modified config file) fixed this so that the login screen appears. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gdm3 46.0-2ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 23 08:06:45 2024 InstallationDate: Installed on 2019-12-23 (1613 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gdm3 UpgradeStatus: Upgraded to noble on 2024-05-22 (1 days ago) mtime.conffile..etc.gdm3.custom.conf: 2024-05-22T16:33:18.326823 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066931 Title: gdm login screen in noble does not display on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2066931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066503] [NEW] held packages cause release upgrade to be skipped silently
Public bug reported: I have a held package on my system (because the newer upstream version available in newer Ubuntu releases is unusably broken). As a result, update-manager presents me the option to upgrade: The software on this computer is up to date. However, Ubuntu 24.04 LTS is now available (you have 23.10). If I choose to 'upgrade', the dialog disappears, and nothing else happens. If I run update-manager from a terminal, I see the following output: Checking for a new Ubuntu release Please install all available updates for your release before upgrading. But update-manager is a graphical application. This information should be shown in the GUI, not on the terminal which is normally not visible to the user. ** Affects: update-manager (Ubuntu) Importance: Medium Status: Triaged ** Changed in: update-manager (Ubuntu) Status: New => Triaged ** Changed in: update-manager (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066503 Title: held packages cause release upgrade to be skipped silently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2066503/+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
Simon, I don't know if this is a regression in noble, but for sure it shouldn't be needrestart telling us about kernel updates - we already have update-notifier for this which, crucially, is livepatch aware. -- 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
