[Bug 1907713] Re: aufs support is deprecated and should be handled on upgrade
Attached is a debdiff to add a preinst file to docker.io that will stop it from upgrading if containers are using aufs. ** Patch added: "lp1907713.debdiff" https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1907713/+attachment/5466341/+files/lp1907713.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907713 Title: aufs support is deprecated and should be handled on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1907713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902025] Re: hwe kernel not scoped under "Ubuntu Base"
The verification passed for focal. The attached image shows linux kernel packages not grouped under Ubuntu base with version 1:20.04.10.5, and the packages correctly grouped with version 1:20.04.10.6. The section highlighted in green shows that the kernel packages are not grouped under "Unused kernel updates to be removed" and that the check boxes are functional. This demonstrates that the regression in LP: #1912718 is not present in version 1:20.04.10.6. ** Attachment added: "Focal Verification" https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1902025/+attachment/5466670/+files/lp1902025_verification_focal.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902025 Title: hwe kernel not scoped under "Ubuntu Base" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1902025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902025] Re: hwe kernel not scoped under "Ubuntu Base"
The verification passed for groovy. The attached image shows linux kernel packages not grouped under Ubuntu base with version 1:20.10.4, and the packages correctly grouped with version 1:20.10.5. ** Attachment added: "Groovy Verification" https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1902025/+attachment/5466671/+files/lp1902025_verification_groovy.png ** Tags removed: verification-needed verification-needed-focal verification-needed-groovy ** Tags added: verification-done verification-done-focal verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902025 Title: hwe kernel not scoped under "Ubuntu Base" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1902025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907713] Re: aufs support is deprecated and should be handled on upgrade
https://github.com/tianon/debian-docker/pull/4 This PR removes the check for the snap aufs dir. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907713 Title: aufs support is deprecated and should be handled on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1907713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907713] Re: aufs support is deprecated and should be handled on upgrade
Per Tianon's suggestion, I have created a NEWS file for aufs-tools to warn users of the deprecation of AUFS. ** Patch added: "aufs-tools NEWS debdiff" https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1907713/+attachment/5466772/+files/news.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907713 Title: aufs support is deprecated and should be handled on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1907713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901043] Re: No sound in ubiquity-dm with nomodeset
The verification passed for focal. The following steps were taken for verification: 1)boot to safe graphics mode a) observe that no startup sound is played b) `watch -n 1 'systemctl status sound.target'` 1) wait for sound.target to become active 2) observe that no startup sound is played after sound.target becomes active 2) download source for ubiquity version 20.04.15.11 a) copy the changed files gtk_ui.py and misc.py to a flash drive 3) reboot to safe graphics mode a) add `break=init` to the kernel command line b) in the initramfs, copy gtk_ui.py and misc.py from the flash drive to the root/ file system c) exit initramfs and allow boot to continue d) once the boot process has finished, observe that no startup sound is immediately played e) `cat /proc/cmdline` to ensure that `nomodeset` is on the kernel command line f) `watch -n 1 'systemctl status sound.target'` 1) the startup sound is played when sound.target becomes active. Success! ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901043 Title: No sound in ubiquity-dm with nomodeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1901043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907713] Re: aufs support is deprecated and should be handled on upgrade
** Changed in: ubuntu-release-upgrader (Ubuntu Hirsute) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907713 Title: aufs support is deprecated and should be handled on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1907713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913476] Re: /usr/bin/update-manager:TypeError:/usr/bin/update-manager@118:start_update:start_available:refresh_cache:update:_make_groups:__contains__
The verification passed for focal. The attached image shows the latest version has staged many packages for upgrade without crashing. ** Attachment added: "Focal Verification" https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1913476/+attachment/5471580/+files/lp1902025_verification_focal.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913476 Title: /usr/bin/update-manager:TypeError:/usr/bin/update- manager@118:start_update:start_available:refresh_cache:update:_make_groups:__contains__ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1913476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913476] Re: /usr/bin/update-manager:TypeError:/usr/bin/update-manager@118:start_update:start_available:refresh_cache:update:_make_groups:__contains__
The verification passed for Groovy. The attached image shows update- manager has staged many packages for upgrade without crashing. ** Attachment added: "Groovy Verification" https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1913476/+attachment/5471581/+files/lp1902025_verification_groovy.png ** Changed in: update-manager (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-focal verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913476 Title: /usr/bin/update-manager:TypeError:/usr/bin/update- manager@118:start_update:start_available:refresh_cache:update:_make_groups:__contains__ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1913476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912718] Re: update-manager: clicks do not toggle checkboxes for "Remove old kernels"
The verification passed for focal. The portion of the image highlighted in green shows that the check boxes are working for kernel packages staged for autoremoval. ** Attachment added: "Focal Verification" https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1912718/+attachment/5471582/+files/lp1902025_verification_focal.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912718 Title: update-manager: clicks do not toggle checkboxes for "Remove old kernels" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1912718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912718] Re: update-manager: clicks do not toggle checkboxes for "Remove old kernels"
The verification passed for groovy. The attached image shows that the check boxes are working for kernel packages staged for autoremoval. ** Attachment added: "Groovy Verification" https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1912718/+attachment/5471583/+files/lp1912718_groovy.png ** Tags removed: verification-needed verification-needed-focal verification-needed-groovy ** Tags added: verification-done verification-done-focal verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912718 Title: update-manager: clicks do not toggle checkboxes for "Remove old kernels" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1912718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913476] Re: /usr/bin/update-manager:TypeError:/usr/bin/update-manager@118:start_update:start_available:refresh_cache:update:_make_groups:__contains__
** Changed in: update-manager (Ubuntu) Assignee: (unassigned) => William Wilson (jawn-smith) ** Changed in: update-manager (Ubuntu Focal) Assignee: (unassigned) => William Wilson (jawn-smith) ** Changed in: update-manager (Ubuntu Groovy) Assignee: (unassigned) => William Wilson (jawn-smith) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913476 Title: /usr/bin/update-manager:TypeError:/usr/bin/update- manager@118:start_update:start_available:refresh_cache:update:_make_groups:__contains__ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1913476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912718] Re: update-manager: clicks do not toggle checkboxes for "Remove old kernels"
** Changed in: update-manager (Ubuntu Focal) Assignee: (unassigned) => William Wilson (jawn-smith) ** Changed in: update-manager (Ubuntu Groovy) Assignee: (unassigned) => William Wilson (jawn-smith) ** Changed in: update-manager (Ubuntu Hirsute) Assignee: (unassigned) => William Wilson (jawn-smith) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912718 Title: update-manager: clicks do not toggle checkboxes for "Remove old kernels" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1912718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571506] Re: update-initramfs should include firmware from /lib/firmware/updates
** Changed in: initramfs-tools (Ubuntu Focal) Assignee: (unassigned) => William Wilson (jawn-smith) ** Changed in: initramfs-tools (Ubuntu Groovy) Assignee: (unassigned) => William Wilson (jawn-smith) ** Changed in: initramfs-tools (Ubuntu Hirsute) Assignee: Dave Jones (waveform) => William Wilson (jawn-smith) ** Changed in: initramfs-tools (Ubuntu Groovy) Status: New => Fix Released ** Changed in: initramfs-tools (Ubuntu Hirsute) Status: Triaged => Fix Released ** Changed in: initramfs-tools (Ubuntu Focal) 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/1571506 Title: update-initramfs should include firmware from /lib/firmware/updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1571506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928966] [NEW] Please merge procps 2:3.3.17-5 (main) from Debian unstable
Public bug reported: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. ** Affects: procps (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928966 Title: Please merge procps 2:3.3.17-5 (main) from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1928966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912371] Re: [MIR] flashrom + libftdi
This debdiff corrects the accidentally left in debug statement and adds `optimize=-lto` to DEB_BUILD_MAINT_OPTIONS. Tests are succeeding again. ** Patch added: "lp1912371_v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+attachment/5498808/+files/lp1912371_v2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912371 Title: [MIR] flashrom + libftdi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921915] Re: Bluetooth controller not detected on CM4
** Changed in: pi-bluetooth (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921915 Title: Bluetooth controller not detected on CM4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pi-bluetooth/+bug/1921915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925971] Re: SRU bluetooth fixes and CVEs to focal and groovy
** Changed in: linux-firmware-raspi2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925971 Title: SRU bluetooth fixes and CVEs to focal and groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1925971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929110] [NEW] Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit
Public bug reported: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. ** Affects: sudo (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929110 Title: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1929110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910965] Re: riscv: backport support for SiFive Unmatched
** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => William Wilson (jawn-smith) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910965 Title: riscv: backport support for SiFive Unmatched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929110] Re: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit
** Patch added: "Diff from 1.9.5p2-2ubuntu3" https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1929110/+attachment/5499102/+files/sudo-ubuntu-ubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929110 Title: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1929110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929110] Re: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit
** Patch added: "Diff from Debian" https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1929110/+attachment/5499101/+files/sudo-debian-ubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929110 Title: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1929110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929229] [NEW] Please merge gnutls28 3.7.1-4 (main) from Debian unstable
Public bug reported: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. ** Affects: gnutls28 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929229 Title: Please merge gnutls28 3.7.1-4 (main) from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1929229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929229] Re: Please merge gnutls28 3.7.1-4 (main) from Debian unstable
** Changed in: gnutls28 (Ubuntu) Status: New => Confirmed ** Changed in: gnutls28 (Ubuntu) Assignee: (unassigned) => William Wilson (jawn-smith) ** Patch added: "Diff from Debian" https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1929229/+attachment/5499282/+files/gnutls28-debian-ubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929229 Title: Please merge gnutls28 3.7.1-4 (main) from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1929229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929229] Re: Please merge gnutls28 3.7.1-4 (main) from Debian unstable
** Patch added: "Diff from 3.7.1-3ubuntu1" https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1929229/+attachment/5499283/+files/gnutls28-debian-ubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929229 Title: Please merge gnutls28 3.7.1-4 (main) from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1929229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929229] Re: Please merge gnutls28 3.7.1-4 (main) from Debian unstable
** Patch added: "Diff from 3.7.1-3ubuntu1" https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1929229/+attachment/5499284/+files/gnutls28-ubuntu-ubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929229 Title: Please merge gnutls28 3.7.1-4 (main) from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1929229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929110] Re: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit
** Changed in: sudo (Ubuntu) Status: New => Confirmed ** Changed in: sudo (Ubuntu) Assignee: (unassigned) => William Wilson (jawn-smith) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929110 Title: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1929110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910965] Re: riscv: backport support for SiFive Unmatched
** Changed in: linux (Ubuntu Focal) Assignee: William Wilson (jawn-smith) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910965 Title: riscv: backport support for SiFive Unmatched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929110] Re: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit
This corrected patch accounts for the apport-hooks now being present in Debian. ** Patch added: "Diff from Debian" https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1929110/+attachment/5500040/+files/sudo-debian-ubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929110 Title: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1929110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929110] Re: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit
This corrected patch accounts for the apport-hooks now being present in Debian. ** Patch added: "Diff from 1.9.5p2-2ubuntu3" https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1929110/+attachment/5500041/+files/sudo-ubuntu-ubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929110 Title: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1929110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928966] Re: Please merge procps 2:3.3.17-5 (main) from Debian unstable
This diff from Debian merges in the new Debian version while keeping some diffs that we have carried for many versions. There is a new diff, which is an autopkgtest for the stack limit issue that was seen in bug 1874824. This test has been submitted to Debian under bug 988792. Justification of dropped patch: There was a patch called pmap_test that disabled one of the tests in the test suite. It appears to have been around since version 3.3.8, but the reason why is not specified in the changelog. Since Debian has this test enabled, I tested the package with the test enabled. There were no issues, so I have decided to drop the patch. ** Patch added: "Diff from Debian" https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1928966/+attachment/5500321/+files/procps-debian-ubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928966 Title: Please merge procps 2:3.3.17-5 (main) from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1928966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928966] Re: Please merge procps 2:3.3.17-5 (main) from Debian unstable
This diff from the previous Ubuntu version of the package is very large. That is mostly due to the new language packs and autoconf files present in the new Debian version of the package. This diff also addresses bug 1903351 by correcting the patches we carry for ignore_erofs and ignore_eaccess ** Patch added: "Diff from 3.3.16-5ubuntu3" https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1928966/+attachment/5500322/+files/procps-ubuntu-ubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928966 Title: Please merge procps 2:3.3.17-5 (main) from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1928966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928966] Re: Please merge procps 2:3.3.17-5 (main) from Debian unstable
This diff from Debian merges in the new Debian version while keeping some diffs that we have carried for many versions. ** Patch removed: "Diff from Debian" https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1928966/+attachment/5500321/+files/procps-debian-ubuntu.debdiff ** Patch removed: "Diff from 3.3.16-5ubuntu3" https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1928966/+attachment/5500322/+files/procps-ubuntu-ubuntu.debdiff ** Patch added: "Diff from Debian" https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1928966/+attachment/5500329/+files/procps-debian-ubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928966 Title: Please merge procps 2:3.3.17-5 (main) from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1928966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928966] Re: Please merge procps 2:3.3.17-5 (main) from Debian unstable
This diff from the previous Ubuntu version of the package is very large. That is mostly due to the new language packs and autoconf files present in the new Debian version of the package. This diff also addresses bug 1903351 by correcting the patches we carry for ignore_erofs and ignore_eaccess ** Patch added: "Diff from 3.3.16-5ubuntu3" https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1928966/+attachment/5500331/+files/procps-ubuntu-ubuntu.debdiff ** Description changed: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. + + + Justification of new diff: + - There is a new diff, which is an autopkgtest for the stack limit issue + that was seen in bug 1874824. This test has been submitted to + Debian so the patch can be dropped if they accept it. + + Justification of dropped patches + - missing_potfiles_in: Debian has now added this code in POTFILES.in + so the patch is no longer needed + - pmap_test: This patch disables some tests that are not causing + any problems. These tests are run in Debian so should be run + in Ubuntu as well + - top_config_file_bwcompat: Debian has applied this code upstream so + the patch is no longer needed + - tar-version: Debian has applied this code upstream so the patch is + no longer needed + - stack_limit: Debian has applied this code upstream so the patch is + no longer needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928966 Title: Please merge procps 2:3.3.17-5 (main) from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1928966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928966] Re: Please merge procps 2:3.3.17-5 (main) from Debian unstable
This diff from the previous Ubuntu version of the package is very large. That is mostly due to the new language packs and autoconf files present in the new Debian version of the package. This diff also addresses bug 1903351 by correcting the patches we carry for ignore_erofs and ignore_eaccess ** Patch added: "Diff from 3.3.16-5ubuntu3" https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1928966/+attachment/5500330/+files/procps-ubuntu-ubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928966 Title: Please merge procps 2:3.3.17-5 (main) from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1928966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903351] Re: ignore_eacces and ignore_erofs patches don't work properly
The attached patch cleans up the switch statement to not replicate the xwarn. ** Patch added: "lp1903351_cleanup.debdiff" https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1903351/+attachment/5501733/+files/lp1903351_cleanup.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903351 Title: ignore_eacces and ignore_erofs patches don't work properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1903351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912371] Re: [MIR] flashrom + libftdi
The attached patch cleans up the lintian warnings and errors in flashrom. ** Patch added: "Lintian Cleanup" https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+attachment/5502234/+files/lp1912371_lintian_cleanup.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912371 Title: [MIR] flashrom + libftdi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912371] Re: [MIR] flashrom + libftdi
Yes, they were included in the package twice. Once in debian/flashrom.udev and once in util/z60_flashrom.rules. The debian/flashrom.udev was causing a lintian warning, so I removed that and added a section to meson.build that installs z60_flashrom.rules to the correct location in a way that doesn't cause a lintian warning. However, it seems that change to meson.build did not get included in that last patch somehow. I will investigate and add another patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912371 Title: [MIR] flashrom + libftdi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912371] Re: [MIR] flashrom + libftdi
That should fix the udev rules issue. ** Patch added: "Lintian Cleanup with udev fix" https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+attachment/5502490/+files/lp1912371_lintian_cleanup.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912371 Title: [MIR] flashrom + libftdi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927078] Re: Don't allow useradd to use fully numeric names
** Changed in: shadow (Ubuntu Impish) Assignee: (unassigned) => William Wilson (jawn-smith) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927078] Re: Don't allow useradd to use fully numeric names
This fix for impish uses sbeattie's suggestion of simply disallowing a numeric character at the beginning of the username. It also includes a test case. ** Patch added: "lp1927078.debdiff" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+attachment/5505076/+files/lp1927078.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923659] Re: Builds are failing due to harmless warnings
*** This bug is a duplicate of bug 1932076 *** https://bugs.launchpad.net/bugs/1932076 ** Description changed: The builds have some tests that are failing due to harmless warnings. - The warning "no name" for a missing key is valid behavior, so we will - add it to the regex for acceptable crypt-gnupg warnings. + The warning "no name" for a missing key is caused by an internet + failure, so we will add it to the regex for acceptable crypt-gnupg + warnings. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923659 Title: Builds are failing due to harmless warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/request-tracker5/+bug/1923659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927078] Re: Don't allow useradd to use fully numeric names
@Seth that very incorrect comment is actually part of block of upstream code that is commented out. It doesn't apply to the more relaxed Debian username scheme. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927078] Re: Don't allow useradd to use fully numeric names
Attached is a patch that disallows fully numeric usernames while still allowing usernames such as 91jawn-smith. ** Patch added: "Disallow Fully Numeric Patch" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+attachment/5505363/+files/lp1927078_fully_numeric.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927078] Re: Don't allow useradd to use fully numeric names
I'd be happy to make that change and add the test cases, but I'm still not sure which patch we landed on. I'm rather indifferent so I will leave the discussion to others before adding those test cases to whichever method we decide. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933353] [NEW] Tests fail with go 1.16 due to changed error message in text/template
Public bug reported: As of golang 1.16, the error message that is checked by one of the tests in this package has changed slightly. The test should be updated to check for this new error message. ** Affects: golang-github-nicksnyder-go-i18n (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933353 Title: Tests fail with go 1.16 due to changed error message in text/template To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-nicksnyder-go-i18n/+bug/1933353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933353] Re: Tests fail with go 1.16 due to changed error message in text/template
I created this against the incorrect package. Apparently there's a v2 version of this package and that is the correct one to file the bug against. ** Changed in: golang-github-nicksnyder-go-i18n (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/1933353 Title: Tests fail with go 1.16 due to changed error message in text/template To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-nicksnyder-go-i18n/+bug/1933353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930928] Re: autopkgtest failure - dh-golang / symlink / copy
** Bug watch added: Debian Bug tracker #989477 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989477 ** Also affects: golang-yaml.v2 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989477 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930928 Title: autopkgtest failure - dh-golang / symlink / copy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-yaml.v2/+bug/1930928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930776] Re: failing test with golang 1.16
This patch resolves the broken tests by checking if the string "unclosed action" is present in the error message rather than looking for the whole message. This allows it to work on all versions of go. It has been forwarded upstream: https://github.com/nicksnyder/go- i18n/pull/260 It has been forwarded to Debian: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=990236 ** Bug watch added: Debian Bug tracker #990236 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990236 ** Patch added: "lp1930776.debdiff" https://bugs.launchpad.net/ubuntu/+source/golang-github-nicksnyder-go-i18n.v2/+bug/1930776/+attachment/5506503/+files/lp1930776.debdiff ** Also affects: golang-github-nicksnyder-go-i18n.v2 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990236 Importance: Unknown Status: Unknown ** Changed in: golang-github-nicksnyder-go-i18n.v2 (Ubuntu) Assignee: (unassigned) => William Wilson (jawn-smith) ** Changed in: golang-github-nicksnyder-go-i18n.v2 (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930776 Title: failing test with golang 1.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-nicksnyder-go-i18n.v2/+bug/1930776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930772] Re: currently FTBFS due to TestTLSConfig
** Changed in: golang-github-prometheus-common (Ubuntu) Assignee: (unassigned) => William Wilson (jawn-smith) ** Changed in: golang-github-prometheus-common (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930772 Title: currently FTBFS due to TestTLSConfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-prometheus-common/+bug/1930772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930772] Re: currently FTBFS due to TestTLSConfig
This patch cherry picks a minor upstream change to enable building with golang 1.16. ** Patch added: "lp1930772.debdiff" https://bugs.launchpad.net/ubuntu/+source/golang-github-prometheus-common/+bug/1930772/+attachment/5506526/+files/lp1930772.debdiff ** Changed in: golang-github-prometheus-common (Ubuntu) Status: In Progress => Fix Committed ** Bug watch added: Debian Bug tracker #990241 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990241 ** Also affects: golang-github-prometheus-common (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990241 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930772 Title: currently FTBFS due to TestTLSConfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-prometheus-common/+bug/1930772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923684] Re: Parallel builds for monero are running out of memory
** Changed in: monero (Ubuntu) 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/1923684 Title: Parallel builds for monero are running out of memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monero/+bug/1923684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931955] Re: 1.14+ds-1 is FTBFS on arm64, riscv64, s390x
** Changed in: micropython (Ubuntu) Assignee: (unassigned) => William Wilson (jawn-smith) ** Changed in: micropython (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931955 Title: 1.14+ds-1 is FTBFS on arm64, riscv64, s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/micropython/+bug/1931955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931955] Re: 1.14+ds-1 is FTBFS on arm64, riscv64, s390x
This patch pulls in the upstream change. ** Patch added: "lp1931955.debdiff" https://bugs.launchpad.net/ubuntu/+source/micropython/+bug/1931955/+attachment/5506549/+files/lp1931955.debdiff ** Bug watch added: Debian Bug tracker #988267 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988267 ** Also affects: micropython (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988267 Importance: Unknown Status: Unknown ** Changed in: micropython (Ubuntu) Status: In Progress => 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/1931955 Title: 1.14+ds-1 is FTBFS on arm64, riscv64, s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/micropython/+bug/1931955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534346] Re: FTBFS with golang-go 1.6
** Changed in: golang-github-aws-aws-sdk-go (Ubuntu) Assignee: (unassigned) => William Wilson (jawn-smith) ** Changed in: golang-github-aws-aws-sdk-go (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534346 Title: FTBFS with golang-go 1.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/consul-migrate/+bug/1534346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933678] [NEW] FTBFS with go 1.16
Public bug reported: There is already an upstream change to address this. ** Affects: golang-github-aws-aws-sdk-go (Ubuntu) Importance: Undecided Assignee: William Wilson (jawn-smith) Status: In Progress ** Changed in: golang-github-aws-aws-sdk-go (Ubuntu) Assignee: (unassigned) => William Wilson (jawn-smith) ** Changed in: golang-github-aws-aws-sdk-go (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933678 Title: FTBFS with go 1.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-aws-aws-sdk-go/+bug/1933678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534346] Re: FTBFS with golang-go 1.6
** Changed in: golang-github-aws-aws-sdk-go (Ubuntu) Assignee: William Wilson (jawn-smith) => (unassigned) ** Changed in: golang-github-aws-aws-sdk-go (Ubuntu) Status: In Progress => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534346 Title: FTBFS with golang-go 1.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/consul-migrate/+bug/1534346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930776] Re: failing test with golang 1.16
The upstream PR has been merged. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930776 Title: failing test with golang 1.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-nicksnyder-go-i18n.v2/+bug/1930776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933678] Re: FTBFS with go 1.16
This patch pulls in a small upstream change needed to build with go 1.16 ** Patch added: "lp1933678.debdiff" https://bugs.launchpad.net/ubuntu/+source/golang-github-aws-aws-sdk-go/+bug/1933678/+attachment/5507112/+files/lp1933678.debdiff ** Changed in: golang-github-aws-aws-sdk-go (Ubuntu) Status: In Progress => 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/1933678 Title: FTBFS with go 1.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-aws-aws-sdk-go/+bug/1933678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912371] Re: [MIR] flashrom + libftdi
This patch enables fwupd to build with the flashrom plugin enabled on Ubuntu. ** Patch added: "lp1912371_fwupd_build_with_flashrom.debdiff" https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+attachment/5507958/+files/lp1912371_fwupd_build_with_flashrom.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912371 Title: [MIR] flashrom + libftdi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934011] [NEW] SRU u-boot-menu to focal to enable HiFive Unmatched booting
Public bug reported: In order to boot focal on the HiFive Unmatched, changes from hirsute are needed. ** Affects: u-boot-menu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934011 Title: SRU u-boot-menu to focal to enable HiFive Unmatched booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot-menu/+bug/1934011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923162] Re: riscv64 images fail to boot in qemu
This patch backports the changes from hirsute in u-boot-menu to focal. ** Changed in: u-boot-menu (Ubuntu Focal) Status: Invalid => In Progress ** Changed in: u-boot-menu (Ubuntu Focal) Assignee: (unassigned) => William Wilson (jawn-smith) ** Patch added: "lp1923162_focal_u-boot-menu.debdiff" https://bugs.launchpad.net/ubuntu/focal/+source/u-boot-menu/+bug/1923162/+attachment/5507959/+files/lp1923162_focal_u-boot-menu.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923162 Title: riscv64 images fail to boot in qemu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923162] Re: riscv64 images fail to boot in qemu
** Changed in: u-boot-menu (Ubuntu Focal) Status: In Progress => 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/1923162 Title: riscv64 images fail to boot in qemu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934387] [NEW] Kernel panic booting on Unmatched with kernel 5.8
Public bug reported: This doesn't happen every time a boot is attempted, but very frequently. Log below: [ 15.024548] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969' [ 15.038870] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19' [ 15.048759] zswap: loaded using pool lzo/zbud [ 15.053091] Key type ._fscrypt registered [ 15.056452] Key type .fscrypt registered [ 15.060276] GPT:Primary header thinks Alt. header is not at the end of the disk. [ 15.060376] Key type fscrypt-provisioning registered [ 15.067784] GPT:7340031 != 62333951 [ 15.067790] GPT:Alternate GPT header not at the end of the disk. [ 15.082195] GPT:7340031 != 62333951 [ 15.085655] GPT: Use GNU Parted to correct GPT errors. [ 15.089268] Key type encrypted registered [ 15.090848] mmcblk0: p1 p12 p13 p14 p15 [ 15.094794] AppArmor: AppArmor sha1 policy hashing enabled [ 15.104197] ima: No TPM chip found, activating TPM-bypass! [ 15.109690] ima: Allocated hash algorithm: sha1 [ 15.114191] ima: No architecture policies found [ 15.118816] evm: Initialising EVM extended attributes: [ 15.123787] evm: security.selinux [ 15.127086] evm: security.SMACK64 [ 15.130380] evm: security.SMACK64EXEC [ 15.134030] evm: security.SMACK64TRANSMUTE [ 15.138108] evm: security.SMACK64MMAP [ 15.141755] evm: security.apparmor [ 15.145142] evm: security.ima [ 15.148081] evm: security.capability [ 15.151656] evm: HMAC attrs: 0x1 [ 18.062579] Freeing unused kernel memory: 308K [ 18.071639] [ cut here ] [ 18.075533] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 18.084242] WARNING: CPU: 2 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 18.092116] Modules linked in: [ 18.095142] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.103320] epc: ffe00020891a ra : ffe00020891a sp : ffe1f5bebb30 [ 18.110425] gp : ffe0013206b8 tp : ffe1f5be6780 t0 : ffe001336fa0 [ 18.117650] t1 : ffe001336f38 t2 : 0001fecd4000 s0 : ffe1f5bebb80 [ 18.124859] s1 : ffe1f5bebe10 a0 : 0053 a1 : 00020020 [ 18.132067] a2 : ffe1f5beb870 a3 : a4 : ffe0012200a0 [ 18.139277] a5 : ffe0012200a0 a6 : 00c6 a7 : ffe0006ebfee [ 18.146485] s2 : ffdff8001000 s3 : s4 : 0004 [ 18.153698] s5 : s6 : s7 : ffe1f5bebd20 [ 18.160917] s8 : ffdff8001000 s9 : ffe001322148 s10: ffdff8002000 [ 18.168116] s11: ffe000c16e20 t3 : 0003cca8 t4 : 0003cca8 [ 18.175323] t5 : t6 : ffe001331462 [ 18.180605] status: 00020120 badaddr: ffe1f5bebb30 cause: 0003 [ 18.188525] ---[ end trace ecc2ef275d977b46 ]--- [ 18.193629] Checked W+X mappings: failed, 513 W+X pages found [ 18.198865] Run /init as init process Loading, please wait... Starting version 245.4-4ubuntu3.7 [ 18.683096] Unable to handle kernel paging request at virtual address 005f8141b42c [ 18.690315] Oops [#1] [ 18.692526] Modules linked in: phylink i2c_ocores(+) [ 18.697489] CPU: 0 PID: 147 Comm: systemd-udevd Tainted: GW 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.707566] epc: ffdf8141b42c ra : ffe000266012 sp : ffe1f4b3bd20 [ 18.714668] gp : ffe0013206b8 tp : ffe1f46f t0 : 0040 [ 18.721931] t1 : t2 : 000a s0 : ffe1f4b3bda0 [ 18.729123] s1 : a0 : 0003 a1 : ffe1f4a39018 [ 18.736314] a2 : 0001 a3 : a4 : ffdf8141b42c [ 18.739498] macb 1009.ethernet: Registered clk switch 'sifive-gemgxl-mgmt' [ 18.743528] a5 : 0003 a6 : ffe1f5603d98 a7 : ffe1f5603dc0 [ 18.743533] s2 : 0003 s3 : ffe1f4b3bdac s4 : 0001 [ 18.743537] s5 : ffe0012f02c8 s6 : ffe0012f02f0 s7 : 0002 [ 18.743542] s8 : ffe1f5d46000 s9 : 002ab15da010 s10: 0002 [ 18.743546] s11: ffe1f35a3680 t3 : 0002 t4 : 0402 [ 18.743553] t5 : ffe001220348 t6 : ffe001220350 [ 18.750909] macb 1009.ethernet: GEM doesn't support hardware ptp. [ 18.757942] status: 00020100 badaddr: 005f8141b42c cause: 000c [ 18.757998] ---[ end trace ecc2ef275d977b47 ]--- [ 18.765916] libphy: MACB_mii_bus: probed [ 18.772384] Kernel panic - not syncing: Fatal exception in interrupt [ 18.821245] SMP: stopping secondary CPUs [ 18.825167] ---[ end Kernel panic - not syncing: Fatal exception in interrupt ]--- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-29-generic 5.8.0-29.31~20.04.1 ProcVersionSignatu
[Bug 1934387] Re: Kernel panic booting on Unmatched with kernel 5.8
apport information ** Tags added: apport-collected ** Description changed: This doesn't happen every time a boot is attempted, but very frequently. Log below: [ 15.024548] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969' [ 15.038870] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19' [ 15.048759] zswap: loaded using pool lzo/zbud [ 15.053091] Key type ._fscrypt registered [ 15.056452] Key type .fscrypt registered [ 15.060276] GPT:Primary header thinks Alt. header is not at the end of the disk. [ 15.060376] Key type fscrypt-provisioning registered [ 15.067784] GPT:7340031 != 62333951 [ 15.067790] GPT:Alternate GPT header not at the end of the disk. [ 15.082195] GPT:7340031 != 62333951 [ 15.085655] GPT: Use GNU Parted to correct GPT errors. [ 15.089268] Key type encrypted registered [ 15.090848] mmcblk0: p1 p12 p13 p14 p15 [ 15.094794] AppArmor: AppArmor sha1 policy hashing enabled [ 15.104197] ima: No TPM chip found, activating TPM-bypass! [ 15.109690] ima: Allocated hash algorithm: sha1 [ 15.114191] ima: No architecture policies found [ 15.118816] evm: Initialising EVM extended attributes: [ 15.123787] evm: security.selinux [ 15.127086] evm: security.SMACK64 [ 15.130380] evm: security.SMACK64EXEC [ 15.134030] evm: security.SMACK64TRANSMUTE [ 15.138108] evm: security.SMACK64MMAP [ 15.141755] evm: security.apparmor [ 15.145142] evm: security.ima [ 15.148081] evm: security.capability [ 15.151656] evm: HMAC attrs: 0x1 [ 18.062579] Freeing unused kernel memory: 308K [ 18.071639] [ cut here ] [ 18.075533] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 18.084242] WARNING: CPU: 2 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 18.092116] Modules linked in: [ 18.095142] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.103320] epc: ffe00020891a ra : ffe00020891a sp : ffe1f5bebb30 [ 18.110425] gp : ffe0013206b8 tp : ffe1f5be6780 t0 : ffe001336fa0 [ 18.117650] t1 : ffe001336f38 t2 : 0001fecd4000 s0 : ffe1f5bebb80 [ 18.124859] s1 : ffe1f5bebe10 a0 : 0053 a1 : 00020020 [ 18.132067] a2 : ffe1f5beb870 a3 : a4 : ffe0012200a0 [ 18.139277] a5 : ffe0012200a0 a6 : 00c6 a7 : ffe0006ebfee [ 18.146485] s2 : ffdff8001000 s3 : s4 : 0004 [ 18.153698] s5 : s6 : s7 : ffe1f5bebd20 [ 18.160917] s8 : ffdff8001000 s9 : ffe001322148 s10: ffdff8002000 [ 18.168116] s11: ffe000c16e20 t3 : 0003cca8 t4 : 0003cca8 [ 18.175323] t5 : t6 : ffe001331462 [ 18.180605] status: 00020120 badaddr: ffe1f5bebb30 cause: 0003 [ 18.188525] ---[ end trace ecc2ef275d977b46 ]--- [ 18.193629] Checked W+X mappings: failed, 513 W+X pages found [ 18.198865] Run /init as init process Loading, please wait... Starting version 245.4-4ubuntu3.7 [ 18.683096] Unable to handle kernel paging request at virtual address 005f8141b42c [ 18.690315] Oops [#1] [ 18.692526] Modules linked in: phylink i2c_ocores(+) [ 18.697489] CPU: 0 PID: 147 Comm: systemd-udevd Tainted: GW 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.707566] epc: ffdf8141b42c ra : ffe000266012 sp : ffe1f4b3bd20 [ 18.714668] gp : ffe0013206b8 tp : ffe1f46f t0 : 0040 [ 18.721931] t1 : t2 : 000a s0 : ffe1f4b3bda0 [ 18.729123] s1 : a0 : 0003 a1 : ffe1f4a39018 [ 18.736314] a2 : 0001 a3 : a4 : ffdf8141b42c [ 18.739498] macb 1009.ethernet: Registered clk switch 'sifive-gemgxl-mgmt' [ 18.743528] a5 : 0003 a6 : ffe1f5603d98 a7 : ffe1f5603dc0 [ 18.743533] s2 : 0003 s3 : ffe1f4b3bdac s4 : 0001 [ 18.743537] s5 : ffe0012f02c8 s6 : ffe0012f02f0 s7 : 0002 [ 18.743542] s8 : ffe1f5d46000 s9 : 002ab15da010 s10: 0002 [ 18.743546] s11: ffe1f35a3680 t3 : 0002 t4 : 0402 [ 18.743553] t5 : ffe001220348 t6 : ffe001220350 [ 18.750909] macb 1009.ethernet: GEM doesn't support hardware ptp. [ 18.757942] status: 00020100 badaddr: 005f8141b42c cause: 000c [ 18.757998] ---[ end trace ecc2ef275d977b47 ]--- [ 18.765916] libphy: MACB_mii_bus: probed [ 18.772384] Kernel panic - not syncing: Fatal exception in interrupt [ 18.821245] SMP: stopping secondary CPUs
[Bug 1934387] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1934387/+attachment/5508490/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934387 Title: Kernel panic booting on Unmatched with kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv-5.8/+bug/1934387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934387] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1934387/+attachment/5508491/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934387 Title: Kernel panic booting on Unmatched with kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv-5.8/+bug/1934387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934387] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1934387/+attachment/5508492/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934387 Title: Kernel panic booting on Unmatched with kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv-5.8/+bug/1934387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934387] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1934387/+attachment/5508494/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934387 Title: Kernel panic booting on Unmatched with kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv-5.8/+bug/1934387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934387] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1934387/+attachment/5508493/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934387 Title: Kernel panic booting on Unmatched with kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv-5.8/+bug/1934387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934791] [NEW] SRU u-boot to focal to enable HiFive Unmatched booting
Public bug reported: In order to boot Ubuntu 20.04 on the Unmatched, the version of u-boot currently in hirsute will need to be SRU'd to focal. Raspberry pi core and classic images will need to be tested with this new version of u-boot as well to ensure nothing was broken by the SRU. ** Affects: u-boot (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934791 Title: SRU u-boot to focal to enable HiFive Unmatched booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1934791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934791] Re: SRU u-boot to focal to enable HiFive Unmatched booting
** Description changed: In order to boot Ubuntu 20.04 on the Unmatched, the version of u-boot currently in hirsute will need to be SRU'd to focal. Raspberry pi core and classic images will need to be tested with this new version of u-boot as well to ensure nothing was broken by the SRU. + + [Impact] + + * Without the hirsute version of u-boot, the HiFive Unmatched +will not boot focal + + [Test Case] + + * Attempt to boot the Unmatched with u-boot 2020.10+dfsg-1ubuntu0~20.04.2 + * Note that it fails to boot + * Attempt to boot the Unmatched with the new version of u-boot + * Verify that u-boot is able to load the kernel + * Ensure u-boot can still boot on the Raspberry pi 2, 3, 3+, +4 (8GB especially), and CM4 + + [Regression Potential] + + There are multiple changes being SRU'd, but since we know they all work + in hirsute on these models the risk is fairly low. Attempts to boot all + the supported Raspberry pi models should still be made to ensure no + regression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934791 Title: SRU u-boot to focal to enable HiFive Unmatched booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1934791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934791] Re: SRU u-boot to focal to enable HiFive Unmatched booting
** Description changed: In order to boot Ubuntu 20.04 on the Unmatched, the version of u-boot currently in hirsute will need to be SRU'd to focal. Raspberry pi core and classic images will need to be tested with this new version of u-boot as well to ensure nothing was broken by the SRU. [Impact] - * Without the hirsute version of u-boot, the HiFive Unmatched -will not boot focal + * Without the hirsute version of u-boot, the HiFive Unmatched + will not boot focal [Test Case] - * Attempt to boot the Unmatched with u-boot 2020.10+dfsg-1ubuntu0~20.04.2 - * Note that it fails to boot - * Attempt to boot the Unmatched with the new version of u-boot - * Verify that u-boot is able to load the kernel - * Ensure u-boot can still boot on the Raspberry pi 2, 3, 3+, -4 (8GB especially), and CM4 + * Attempt to boot the Unmatched with u-boot 2020.10+dfsg-1ubuntu0~20.04.2 + * Note that it fails to boot + * Attempt to boot the Unmatched with the new version of u-boot + * Verify that u-boot is able to load the kernel + * Ensure u-boot can still boot on the Raspberry pi 2, 3, 3+, + 4 (8GB especially), 400, and CM4 [Regression Potential] There are multiple changes being SRU'd, but since we know they all work in hirsute on these models the risk is fairly low. Attempts to boot all the supported Raspberry pi models should still be made to ensure no regression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934791 Title: SRU u-boot to focal to enable HiFive Unmatched booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1934791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927078] Re: Don't allow useradd to use fully numeric names
This patch only disallows usernames that are strictly numeric per vorlon's comment above. It also adds more test cases for invalid usernames such as "0123456789" and valid usernames such as "0root" and "0.o". This time I also remembered that '0' is a digit. ** Patch added: "Fully numeric and more tests patch" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+attachment/5509701/+files/lp1927078_fully_numeric.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935063] Re: gnome-initial-setup: cannot build on RISC-V
I submitted https://github.com/golang/go/issues/47100 which doesn't immediately help us but is the best long term solution. ** Bug watch added: github.com/golang/go/issues #47100 https://github.com/golang/go/issues/47100 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935063 Title: gnome-initial-setup: cannot build on RISC-V To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1935063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933678] Re: FTBFS with go 1.16
Sergio, The only new file added is a patch, is that what you're referring to? This attached patch states which source file is modified by the upstream cherry pick, hopefully that's what you need! ** Patch added: "lp1933678.debdiff" https://bugs.launchpad.net/ubuntu/+source/golang-github-aws-aws-sdk-go/+bug/1933678/+attachment/5510067/+files/lp1933678.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933678 Title: FTBFS with go 1.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-aws-aws-sdk-go/+bug/1933678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933678] Re: FTBFS with go 1.16
Here is the corrected changelog entry. I will keep that in mind for future uploads. On the topic of update-maintainer, I had run that command and the previous patch shows a change in d/control that changes the maintainer from Debian Go Packaging to "Ubuntu Developers". Is there something else that needs to be changed that update-maintainer didn't automatically handle? ** Patch added: "lp1933678.debdiff" https://bugs.launchpad.net/ubuntu/+source/golang-github-aws-aws-sdk-go/+bug/1933678/+attachment/5510084/+files/lp1933678.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933678 Title: FTBFS with go 1.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-aws-aws-sdk-go/+bug/1933678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927078] Re: Don't allow useradd to use fully numeric names
This change disallows floating point and hexadecimal representations of numbers as well as purely numeric, which should be a good compromise. For example, 0x0 is now invalid, as well as 0x123456789 and 0.0, while 0x0x0x0x is considered valid. It also adds these new restrictions to the man page. ** Patch added: "invalid hexadecimal and floating point" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+attachment/5510089/+files/lp1927078_fully_numeric_and_hex.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927078] Re: Don't allow useradd to use fully numeric names
This one adds in a check for octal representation and some test cases for octal representation. ** Patch added: "Octal included this time" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+attachment/5510554/+files/lp1927078_fully_numeric_and_hex_and_octal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927078] Re: Don't allow useradd to use fully numeric names
Per our discussion I just removed floating point checks altogether. "0.123" is now considered valid because it is impossible to have a floating point uid or gid so there will be no confusion with floating point numbers. I have added those floating point numbers to the "validUsernames" test, and added a few more cases that are almost numeric, like "0xdeadbeefjawn-smith" to make sure they are seen as valid. ** Patch added: "Removed float checks" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+attachment/5510618/+files/lp1927078_removed_float_checks.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921915] Re: Bluetooth controller not detected on CM4
** Description changed: - Under later versions of the Ubuntu kernel (5.8) on the CM4 and - (possibly?) some models of the Pi 400, the bluetooth controller is not - activated by the pi-bluetooth package. This appears to be due to two - issues: + [Impact] + + Without these patches, Bluetooth is inoperable on the CM4 + + [Test Case] + + * Boot the Ubuntu Desktop for Pi image on a CM4. + * Start the Settings application and switch to the Bluetooth tab + * Verify that Bluetooth is not enabled and attempting to activate it fails + + [Regression Potential] + + The main concern would be the backported versions of pi-bluetooth not + integrating well with other packages. We are mitigating this concern by + also SRUing Bluez and linux-firmware-raspi2 to focal and groovy. + + [Original Description] + Under later versions of the Ubuntu kernel (5.8) on the CM4 and (possibly?) some models of the Pi 400, the bluetooth controller is not activated by the pi-bluetooth package. This appears to be due to two issues: * The mmcnr device is mistaken for a bluetooth controller. This in itself is harmless, but results in a spurious hci0 device. The existence of this device causes the btuart script to skip configuring the "real" bluetooth device (as it thinks it is already configured) * The btuart script also attempts a match against the device-tree's model name looking for "Raspberry Pi 4" which doesn't match "Raspberry Pi Compute Module 4". The upstream repository currently has commits for both these fixes but no release has been made yet. It is proposed to backport these patches into an -ubuntu2 version of the package in the meantime. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921915 Title: Bluetooth controller not detected on CM4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pi-bluetooth/+bug/1921915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925971] Re: SRU bluetooth fixes and CVEs to focal and groovy
** Description changed: - Hirsute has some patches that address CVEs and enable bluetooth/wifi on - the CM4 and 400. They need to be SRU'd to focal and groovy. + [Impact] + + Without these patches, Bluetooth is inoperable on the CM4 and Pi 400 + + [Test Case] + + * Boot the Ubuntu Desktop for Pi image on a CM4. + * Start the Settings application and switch to the Bluetooth tab + * Verify that Bluetooth is not enabled and attempting to activate it fails + * Repeat the above steps for the Pi 400 + + [Regression Potential] + + There are some diversions and other firmware updates that could + potentially cause issues. These have been tested on lots of different pi + hardware and no issues have been discovered. There is also an included + Spectra CVE fix which is very low risk. + + [Original Description] + Hirsute has some patches that address CVEs and enable bluetooth/wifi on the CM4 and 400. They need to be SRU'd to focal and groovy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925971 Title: SRU bluetooth fixes and CVEs to focal and groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1925971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926378] [NEW] SRU pi-bluetooth from hirsute to focal to enable all models
Public bug reported: [Impact] * Without the pi-bluetooth changes in hirsute, bluetooth will not work on the Pi 4, 400 or CM4. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Raspberry Pi 4. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Boot the Ubuntu Server for Pi image on a Raspberry Pi 4. * Verify `bluetoothctl devices` fails with the error message "No default controller available * Repeat the above steps for the Pi 400 and CM4 [Regression Potential] There are multiple changes being SRU'd, but since the linux-firmware- raspi2 and bluez packages are also being SRUd, the risk of regression should be fairly low. These changes have worked well in hirsute for some time. ** Affects: pi-bluetooth (Ubuntu) Importance: Undecided Status: New ** Description changed: [Impact] - * Without the pi-bluetooth changes in hirsute, bluetooth will not work + * Without the pi-bluetooth changes in hirsute, bluetooth will not work on the Pi 4, 400 or CM4. [Test Case] - * Boot the Ubuntu Desktop for Pi image on a Raspberry Pi 4. - * Start the Settings application and switch to the Bluetooth tab - * Verify that Bluetooth is not enabled and attempting to activate it fails - * Boot the Ubuntu Server for Pi image on a Raspberry Pi 4. - * Run `bluetoothctl devices` - * Repeat the above steps for the Pi 400 and CM4 + * Boot the Ubuntu Desktop for Pi image on a Raspberry Pi 4. + * Start the Settings application and switch to the Bluetooth tab + * Verify that Bluetooth is not enabled and attempting to activate +it fails + * Boot the Ubuntu Server for Pi image on a Raspberry Pi 4. + * Verify `bluetoothctl devices` fails with the error message "No default +controller available + * Repeat the above steps for the Pi 400 and CM4 [Regression Potential] There are multiple changes being SRU'd, but since the linux-firmware- raspi2 and bluez packages are also being SRUd, the risk of regression should be fairly low. These changes have worked well in hirsute for some time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926378 Title: SRU pi-bluetooth from hirsute to focal to enable all models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pi-bluetooth/+bug/1926378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926378] Re: SRU pi-bluetooth from hirsute to focal to enable all models
** Description changed: [Impact] * Without the pi-bluetooth changes in hirsute, bluetooth will not work on the Pi 4, 400 or CM4. [Test Case] - * Boot the Ubuntu Desktop for Pi image on a Raspberry Pi 4. - * Start the Settings application and switch to the Bluetooth tab - * Verify that Bluetooth is not enabled and attempting to activate -it fails * Boot the Ubuntu Server for Pi image on a Raspberry Pi 4. - * Verify `bluetoothctl devices` fails with the error message "No default -controller available + * Verify the command `bluetoothctl devices` fails with the +error "No default controller available" * Repeat the above steps for the Pi 400 and CM4 [Regression Potential] There are multiple changes being SRU'd, but since the linux-firmware- raspi2 and bluez packages are also being SRUd, the risk of regression should be fairly low. These changes have worked well in hirsute for some time. ** Description changed: [Impact] * Without the pi-bluetooth changes in hirsute, bluetooth will not work on the Pi 4, 400 or CM4. [Test Case] - * Boot the Ubuntu Server for Pi image on a Raspberry Pi 4. + * Boot the Ubuntu Server for Pi 20.04 image on a Raspberry Pi 4. * Verify the command `bluetoothctl devices` fails with the -error "No default controller available" + error "No default controller available" * Repeat the above steps for the Pi 400 and CM4 [Regression Potential] There are multiple changes being SRU'd, but since the linux-firmware- raspi2 and bluez packages are also being SRUd, the risk of regression should be fairly low. These changes have worked well in hirsute for some time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926378 Title: SRU pi-bluetooth from hirsute to focal to enable all models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pi-bluetooth/+bug/1926378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926378] Re: SRU pi-bluetooth from hirsute to focal to enable all models
The attached patch enables Bluetooth on the new Pi 400, and CM4 hardware. ** Description changed: [Impact] * Without the pi-bluetooth changes in hirsute, bluetooth will not work - on the Pi 4, 400 or CM4. + on the Pi 400 or CM4. [Test Case] - * Boot the Ubuntu Server for Pi 20.04 image on a Raspberry Pi 4. + * Boot the Ubuntu Server for Pi 20.04 image on a Raspberry Pi 400. * Verify the command `bluetoothctl devices` fails with the error "No default controller available" - * Repeat the above steps for the Pi 400 and CM4 + * Repeat the above steps for the CM4 [Regression Potential] There are multiple changes being SRU'd, but since the linux-firmware- raspi2 and bluez packages are also being SRUd, the risk of regression should be fairly low. These changes have worked well in hirsute for some time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926378 Title: SRU pi-bluetooth from hirsute to focal to enable all models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pi-bluetooth/+bug/1926378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926378] Re: SRU pi-bluetooth from hirsute to focal to enable all models
** Patch added: "lp1921915_focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/pi-bluetooth/+bug/1926378/+attachment/5492937/+files/lp1921915_focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926378 Title: SRU pi-bluetooth from hirsute to focal to enable all models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pi-bluetooth/+bug/1926378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926378] Re: SRU pi-bluetooth from hirsute to focal to enable all models
** Description changed: [Impact] * Without the pi-bluetooth changes in hirsute, bluetooth will not work on the Pi 400 or CM4. [Test Case] * Boot the Ubuntu Server for Pi 20.04 image on a Raspberry Pi 400. - * Verify the command `bluetoothctl devices` fails with the - error "No default controller available" + * "bluetoothctl" + * "list" and verify there is no available bluetooth controller + * Enable proposed (https://wiki.ubuntu.com/Testing/EnableProposed) + * "sudo apt install pi-bluetooth" + * "sudo reboot" (required as bluetooth initialization only occurs during + udev activation) + * "bluetoothctl" + * "list" and verify there is a single available bluetooth controller + * "scan on" and bring another discoverable bluetooth device in range; + verify it is reported under bluetoothctl * Repeat the above steps for the CM4 [Regression Potential] There are multiple changes being SRU'd, but since the linux-firmware- raspi2 and bluez packages are also being SRUd, the risk of regression should be fairly low. These changes have worked well in hirsute for some time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926378 Title: SRU pi-bluetooth from hirsute to focal to enable all models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pi-bluetooth/+bug/1926378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920837] Re: apport bugs from official raspi or riscv images are not identified
The verification passed for focal: ubuntu@ubuntu:~$ apt-cache policy apport apport: Installed: 2.20.11-0ubuntu27.16 Candidate: 2.20.11-0ubuntu27.17 Version table: 2.20.11-0ubuntu27.17 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main armhf Packages *** 2.20.11-0ubuntu27.16 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main armhf Packages 500 http://ports.ubuntu.com/ubuntu-ports focal-security/main armhf Packages 100 /var/lib/dpkg/status 2.20.11-0ubuntu27 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main armhf Packages `ubuntu-bug apport` shows: == Tags = focal uec-images ubuntu@ubuntu:~$ sudo apt install apport Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: python3-apport Suggested packages: apport-gtk | apport-kde The following packages will be upgraded: apport python3-apport 2 upgraded, 0 newly installed, 0 to remove and 23 not upgraded. Need to get 214 kB of archives. After this operation, 1024 B of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main armhf python3-apport all 2.20.11-0ubuntu27.17 [85.2 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main armhf apport all 2.20.11-0ubuntu27.17 [129 kB] Fetched 214 kB in 1s (247 kB/s) (Reading database ... 99636 files and directories currently installed.) Preparing to unpack .../python3-apport_2.20.11-0ubuntu27.17_all.deb ... Unpacking python3-apport (2.20.11-0ubuntu27.17) over (2.20.11-0ubuntu27.16) ... Preparing to unpack .../apport_2.20.11-0ubuntu27.17_all.deb ... Unpacking apport (2.20.11-0ubuntu27.17) over (2.20.11-0ubuntu27.16) ... Setting up python3-apport (2.20.11-0ubuntu27.17) ... Setting up apport (2.20.11-0ubuntu27.17) ... apport-autoreport.service is a disabled or a static unit, not starting it. Processing triggers for man-db (2.9.1-1) ... Processing triggers for systemd (245.4-4ubuntu3.6) ... `ubuntu-bug apport` shows == Tags = armhf-image raspi-image focal uec-images package-from-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920837 Title: apport bugs from official raspi or riscv images are not identified To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1920837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920837] Re: apport bugs from official raspi or riscv images are not identified
The verification passed for groovy: ubuntu@ubuntu:~$ apt-cache policy apport apport: Installed: 2.20.11-0ubuntu50.5 Candidate: 2.20.11-0ubuntu50.6 Version table: 2.20.11-0ubuntu50.6 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/main arm64 Packages *** 2.20.11-0ubuntu50.5 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 Packages 500 http://ports.ubuntu.com/ubuntu-ports groovy-security/main arm64 Packages 100 /var/lib/dpkg/status 2.20.11-0ubuntu50 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages `ubuntu-bug apport` shows == Tags = groovy uec-images ubuntu@ubuntu:~$ sudo apt install apport Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: python3-apport Suggested packages: apport-gtk | apport-kde The following packages will be upgraded: apport python3-apport 2 upgraded, 0 newly installed, 0 to remove and 20 not upgraded. Need to get 214 kB of archives. After this operation, 1024 B of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/main arm64 python3-apport all 2.20.11-0ubuntu50.6 [85.2 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/main arm64 apport all 2.20.11-0ubuntu50.6 [129 kB] Fetched 214 kB in 1s (258 kB/s) (Reading database ... 101926 files and directories currently installed.) Preparing to unpack .../python3-apport_2.20.11-0ubuntu50.6_all.deb ... Unpacking python3-apport (2.20.11-0ubuntu50.6) over (2.20.11-0ubuntu50.5) ... Preparing to unpack .../apport_2.20.11-0ubuntu50.6_all.deb ... Unpacking apport (2.20.11-0ubuntu50.6) over (2.20.11-0ubuntu50.5) ... Setting up python3-apport (2.20.11-0ubuntu50.6) ... Setting up apport (2.20.11-0ubuntu50.6) ... apport-autoreport.service is a disabled or a static unit, not starting it. Processing triggers for man-db (2.9.3-2) ... Processing triggers for systemd (246.6-1ubuntu1.3) ... `ubuntu-bug apport` shows == Tags = arm64-image raspi-image groovy uec-images package-from-proposed ** Tags removed: verification-needed verification-needed-focal verification-needed-groovy ** Tags added: verification-done verification-done-focal verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920837 Title: apport bugs from official raspi or riscv images are not identified To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1920837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923684] Re: Parallel builds for monero are running out of memory
Seb, The builds were failing in the launchpad build farm. The official package builds are failing on multiple architectures with various "out of memory" errors, and preventing this package from migrating out of -proposed. Debian builds don't seem to be affected, so I would think they wouldn't want to slow down their builds. If you think they would accept the patch anyway I would be happy to forward it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923684 Title: Parallel builds for monero are running out of memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monero/+bug/1923684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927231] Re: u-boot-update complains about a syntax error
Some merge markers were left around in the script and manpage. The attached patch removes them. ** Patch added: "lp1927231.debdiff" https://bugs.launchpad.net/ubuntu/+source/u-boot-menu/+bug/1927231/+attachment/5495353/+files/lp1927231.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927231 Title: u-boot-update complains about a syntax error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot-menu/+bug/1927231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926378] Re: SRU pi-bluetooth from hirsute to focal to enable all models
** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926378 Title: SRU pi-bluetooth from hirsute to focal to enable all models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pi-bluetooth/+bug/1926378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926378] Re: SRU pi-bluetooth from hirsute to focal to enable all models
** Description changed: [Impact] * Without the pi-bluetooth changes in hirsute, bluetooth will not work on the Pi 400 or CM4. [Test Case] * Boot the Ubuntu Server for Pi 20.04 image on a Raspberry Pi 400. - * "bluetoothctl" - * "list" and verify there is no available bluetooth controller - * Enable proposed (https://wiki.ubuntu.com/Testing/EnableProposed) - * "sudo apt install pi-bluetooth" - * "sudo reboot" (required as bluetooth initialization only occurs during - udev activation) - * "bluetoothctl" - * "list" and verify there is a single available bluetooth controller - * "scan on" and bring another discoverable bluetooth device in range; - verify it is reported under bluetoothctl + * "bluetoothctl" + * "list" and verify there is no available bluetooth controller + * Enable proposed (https://wiki.ubuntu.com/Testing/EnableProposed) + * "sudo apt install pi-bluetooth" + * "sudo reboot" (required as bluetooth initialization only occurs during + udev activation) + * "bluetoothctl" + * "list" and verify there is a single available bluetooth controller + * "scan on" and bring another discoverable bluetooth device in range; + verify it is reported under bluetoothctl * Repeat the above steps for the CM4 [Regression Potential] There are multiple changes being SRU'd, but since the linux-firmware- raspi2 and bluez packages are also being SRUd, the risk of regression should be fairly low. These changes have worked well in hirsute for some - time. + time. In the past, other updates to this package have caused regressions + on other Pi models such as the 2, 3, and 4. Though unlikely, that could + potentially occur with this change as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926378 Title: SRU pi-bluetooth from hirsute to focal to enable all models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pi-bluetooth/+bug/1926378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927231] Re: u-boot-update complains about a syntax error
This bug was fixed in u-boot-menu version 4.0.3ubuntu2 ** Changed in: u-boot-menu (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927231 Title: u-boot-update complains about a syntax error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot-menu/+bug/1927231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925971] Re: SRU bluetooth fixes and CVEs to focal and groovy
http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages linux-firmware-raspi2: Installed: 4-0ubuntu0~20.04.1 Candidate: 4-0ubuntu0~20.04.1 Version table: *** 4-0ubuntu0~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages 100 /var/lib/dpkg/status 3-0ubuntu2~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse arm64 Packages 1.20200212-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages pi-bluetooth: Installed: 0.1.15ubuntu0~20.04.1 Candidate: 0.1.15ubuntu0~20.04.1 Version table: *** 0.1.15ubuntu0~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages 100 /var/lib/dpkg/status 0.1.10ubuntu6 500 500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages ubuntu@ubuntu:~$ bluetoothctl Agent registered [CHG] Controller DC:A6:32:FE:BA:B2 Pairable: yes [bluetooth]# list Controller DC:A6:32:FE:BA:B2 ubuntu [default] [bluetooth]# scan on Discovery started [CHG] Controller DC:A6:32:FE:BA:B2 Discovering: yes [NEW] Device 28:11:A5:D5:CB:47 28-11-A5-D5-CB-47 [NEW] Device 28:11:A5:D5:AC:98 LE-Lemonade [CHG] Device 28:11:A5:D5:CB:47 TxPower: 8 [CHG] Device 28:11:A5:D5:CB:47 Name: LE-reserved_M [CHG] Device 28:11:A5:D5:CB:47 Alias: LE-reserved_M [NEW] Device E2:70:8C:88:51:C0 E2-70-8C-88-51-C0 [bluetooth]# ** Changed in: linux-firmware-raspi2 (Ubuntu) Assignee: (unassigned) => William Wilson (jawn-smith) ** Changed in: linux-firmware-raspi2 (Ubuntu Focal) Assignee: (unassigned) => William Wilson (jawn-smith) ** Changed in: linux-firmware-raspi2 (Ubuntu Groovy) Assignee: (unassigned) => William Wilson (jawn-smith) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925971 Title: SRU bluetooth fixes and CVEs to focal and groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1925971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926378] Re: SRU pi-bluetooth from hirsute to focal to enable all models
http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages linux-firmware-raspi2: Installed: 4-0ubuntu0~20.04.1 Candidate: 4-0ubuntu0~20.04.1 Version table: *** 4-0ubuntu0~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages 100 /var/lib/dpkg/status 3-0ubuntu2~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse arm64 Packages 1.20200212-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages pi-bluetooth: Installed: 0.1.15ubuntu0~20.04.1 Candidate: 0.1.15ubuntu0~20.04.1 Version table: *** 0.1.15ubuntu0~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages 100 /var/lib/dpkg/status 0.1.10ubuntu6 500 500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages ubuntu@ubuntu:~$ bluetoothctl Agent registered [CHG] Controller DC:A6:32:FE:BA:B2 Pairable: yes [bluetooth]# list Controller DC:A6:32:FE:BA:B2 ubuntu [default] [bluetooth]# scan on Discovery started [CHG] Controller DC:A6:32:FE:BA:B2 Discovering: yes [NEW] Device 28:11:A5:D5:CB:47 28-11-A5-D5-CB-47 [NEW] Device 28:11:A5:D5:AC:98 LE-Lemonade [CHG] Device 28:11:A5:D5:CB:47 TxPower: 8 [CHG] Device 28:11:A5:D5:CB:47 Name: LE-reserved_M [CHG] Device 28:11:A5:D5:CB:47 Alias: LE-reserved_M [NEW] Device E2:70:8C:88:51:C0 E2-70-8C-88-51-C0 [bluetooth]# ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal ** Changed in: pi-bluetooth (Ubuntu) Assignee: (unassigned) => William Wilson (jawn-smith) ** Changed in: pi-bluetooth (Ubuntu Focal) Assignee: (unassigned) => William Wilson (jawn-smith) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926378 Title: SRU pi-bluetooth from hirsute to focal to enable all models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pi-bluetooth/+bug/1926378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925971] Re: SRU bluetooth fixes and CVEs to focal and groovy
** Tags added: verification-done-focal verification-needed verification- needed-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925971 Title: SRU bluetooth fixes and CVEs to focal and groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1925971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
The verification passed for focal. * On Pi 400 ** ubuntu@ubuntu:~$ apt-cache policy bluez pi-bluetooth linux-firmware-raspi2 bluez: Installed: 5.53-0ubuntu3 Candidate: 5.53-0ubuntu3.1 Version table: 5.53-0ubuntu3.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 Packages *** 5.53-0ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages 100 /var/lib/dpkg/status pi-bluetooth: Installed: 0.1.10ubuntu6 Candidate: 0.1.15ubuntu0~20.04.1 Version table: 0.1.15ubuntu0~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages *** 0.1.10ubuntu6 500 500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages 100 /var/lib/dpkg/status linux-firmware-raspi2: Installed: 3-0ubuntu2~20.04.1 Candidate: 4-0ubuntu0~20.04.1 Version table: 4-0ubuntu0~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages *** 3-0ubuntu2~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse arm64 Packages 100 /var/lib/dpkg/status 1.20200212-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages ubuntu@ubuntu:~$ bluetoothctl devices No default controller available ubuntu@ubuntu:~$ apt-cache policy bluez pi-bluetooth linux-firmware-raspi2 bluez: Installed: 5.53-0ubuntu3.1 Candidate: 5.53-0ubuntu3.1 Version table: *** 5.53-0ubuntu3.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 Packages 100 /var/lib/dpkg/status 5.53-0ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages pi-bluetooth: Installed: 0.1.15ubuntu0~20.04.1 Candidate: 0.1.15ubuntu0~20.04.1 Version table: *** 0.1.15ubuntu0~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages 100 /var/lib/dpkg/status 0.1.10ubuntu6 500 500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages linux-firmware-raspi2: Installed: 4-0ubuntu0~20.04.1 Candidate: 4-0ubuntu0~20.04.1 Version table: *** 4-0ubuntu0~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages 100 /var/lib/dpkg/status 3-0ubuntu2~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse arm64 Packages 1.20200212-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages ubuntu@ubuntu:~$ bluetoothctl Agent registered [CHG] Controller DC:A6:32:F6:84:4E Pairable: yes [bluetooth]# scan on Discovery started [CHG] Controller DC:A6:32:F6:84:4E Discovering: yes [NEW] Device 28:11:A5:D5:AC:98 28-11-A5-D5-AC-98 [NEW] Device 68:27:37:05:F4:ED [TV] Samsung 6 Series (55) [NEW] Device 5B:1B:6F:46:F3:00 5B-1B-6F-46-F3-00 [NEW] Device 28:11:A5:D5:CB:47 LE-reserved_M [NEW] Device 42:25:C8:1B:5F:D2 42-25-C8-1B-5F-D2 [NEW] Device 64:FF:0A:21:B1:70 64-FF-0A-21-B1-70 [CHG] Device 28:11:A5:D5:AC:98 RSSI: -62 [CHG] Device 28:11:A5:D5:AC:98 TxPower: 8 [CHG] Device 28:11:A5:D5:AC:98 Name: LE-Lemonade [CHG] Device 28:11:A5:D5:AC:98 Alias: LE-Lemonade [NEW] Device 4B:04:19:F1:60:90 4B-04-19-F1-60-90 [bluetooth]# ** On CM4 ** apt-cache policy bluez pi-bluetooth linux-firmware-raspi2 bluez: Installed: 5.53-0ubuntu3 Candidate: 5.53-0ubuntu3.1 Version table: 5.53-0ubuntu3.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 Packages *** 5.53-0ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages 100 /var/lib/dpkg/status pi-bluetooth: Installed: 0.1.10ubuntu6 Candidate: 0.1.15ubuntu0~20.04.1 Version table: 0.1.15ubuntu0~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages *** 0.1.10ubuntu6 500 500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages 100 /var/lib/dpkg/status linux-firmware-raspi2: Installed: 3-0ubuntu2~20.04.1 Candidate: 4-0ubuntu0~20.04.1 Version table: 4-0ubuntu0~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages *** 3-0ubuntu2~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse arm64 Packages 100 /var/lib/dpkg/status 1.20200212-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages ubuntu@ubuntu:~$ bluetoothctl devices No default controller available ubuntu@ubuntu:~$ apt-cache policy bluez linux-firmware-raspi2 pi-bluetooth bluez: Installed: 5.53-0ubuntu3.1 Candidate: 5.53-0ubuntu3.1 Version table: *** 5.53-0ubuntu3.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 Packages 100 /var/lib/dpkg/status 5.53-0ubuntu3 500 500 h
[Bug 1925971] Re: SRU bluetooth fixes and CVEs to focal and groovy
The verification passed for Groovy. *** On Pi 400 ** ubuntu@ubuntu:~$ apt-cache policy pi-bluetooth linux-firmware-raspi2 pi-bluetooth: Installed: 0.1.15ubuntu1 Candidate: 0.1.15ubuntu1.1~20.10.1 Version table: 0.1.15ubuntu1.1~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages *** 0.1.15ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 Packages 100 /var/lib/dpkg/status linux-firmware-raspi2: Installed: 3-0ubuntu2~20.10.1 Candidate: 4-0ubuntu0~20.10.1 Version table: 4-0ubuntu0~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages *** 3-0ubuntu2~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/restricted arm64 Packages 100 /var/lib/dpkg/status 2-0ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 Packages ubuntu@ubuntu:~$ bluetoothctl Agent registered [bluetooth]# list [bluetooth]# devices No default controller available [bluetooth]# ubuntu@ubuntu:~$ apt-cache policy pi-bluetooth linux-firmware-raspi2 pi-bluetooth: Installed: 0.1.15ubuntu1.1~20.10.1 Candidate: 0.1.15ubuntu1.1~20.10.1 Version table: *** 0.1.15ubuntu1.1~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages 100 /var/lib/dpkg/status 0.1.15ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 Packages linux-firmware-raspi2: Installed: 4-0ubuntu0~20.10.1 Candidate: 4-0ubuntu0~20.10.1 Version table: *** 4-0ubuntu0~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages 100 /var/lib/dpkg/status 3-0ubuntu2~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/restricted arm64 Packages 2-0ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 Packages ubuntu@ubuntu:~$ bluetoothctl Agent registered [CHG] Controller DC:A6:32:F6:84:4E Pairable: yes [bluetooth]# devices [bluetooth]# list Controller DC:A6:32:F6:84:4E ubuntu [default] [bluetooth]# scan on Discovery started [CHG] Controller DC:A6:32:F6:84:4E Discovering: yes [NEW] Device 28:11:A5:D5:CB:47 LE-reserved_M [NEW] Device 28:11:A5:D5:AC:98 LE-Lemonade [NEW] Device E2:70:8C:88:51:C0 E2-70-8C-88-51-C0 [bluetooth]# * On CM4 ** ubuntu@ubuntu:~$ apt-cache policy pi-bluetooth linux-firmware-raspi2 pi-bluetooth: Installed: 0.1.15ubuntu1 Candidate: 0.1.15ubuntu1.1~20.10.1 Version table: 0.1.15ubuntu1.1~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages *** 0.1.15ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 Packages 100 /var/lib/dpkg/status linux-firmware-raspi2: Installed: 3-0ubuntu2~20.10.1 Candidate: 4-0ubuntu0~20.10.1 Version table: 4-0ubuntu0~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages *** 3-0ubuntu2~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/restricted arm64 Packages 100 /var/lib/dpkg/status 2-0ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 Packages ubuntu@ubuntu:~$ bluetoothctl Agent registered [bluetooth]# list [bluetooth]# devices No default controller available [bluetooth]# ubuntu@ubuntu:~$ !apt apt-cache policy pi-bluetooth linux-firmware-raspi2 pi-bluetooth: Installed: 0.1.15ubuntu1.1~20.10.1 Candidate: 0.1.15ubuntu1.1~20.10.1 Version table: *** 0.1.15ubuntu1.1~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages 100 /var/lib/dpkg/status 0.1.15ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 Packages linux-firmware-raspi2: Installed: 4-0ubuntu0~20.10.1 Candidate: 4-0ubuntu0~20.10.1 Version table: *** 4-0ubuntu0~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages 100 /var/lib/dpkg/status 3-0ubuntu2~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/restricted arm64 Packages 2-0ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 Packages ubuntu@ubuntu:~$ bluetoothctl Agent registered [CHG] Controller DC:A6:32:FE:BA:B2 Pairable: yes [bluetooth]# devices [bluetooth]# list Controller DC:A6:32:FE:BA:B2 ubuntu [default] [bluetooth]# scan on Discovery started [CHG] Controller DC:A6:32:FE:BA:B2 Discovering: yes [NEW] Device 28:11:A5:D5:AC:98 LE-Lemonade [NEW] Device 28:11:A5:D5:CB:47 LE-reserved_M [bluetooth]# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925971 Title: SRU bluetooth fixes and CVEs
[Bug 1921915] Re: Bluetooth controller not detected on CM4
The verification passed for Groovy. *** On Pi 400 ** ubuntu@ubuntu:~$ apt-cache policy pi-bluetooth linux-firmware-raspi2 pi-bluetooth: Installed: 0.1.15ubuntu1 Candidate: 0.1.15ubuntu1.1~20.10.1 Version table: 0.1.15ubuntu1.1~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages *** 0.1.15ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 Packages 100 /var/lib/dpkg/status linux-firmware-raspi2: Installed: 3-0ubuntu2~20.10.1 Candidate: 4-0ubuntu0~20.10.1 Version table: 4-0ubuntu0~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages *** 3-0ubuntu2~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/restricted arm64 Packages 100 /var/lib/dpkg/status 2-0ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 Packages ubuntu@ubuntu:~$ bluetoothctl Agent registered [bluetooth]# list [bluetooth]# devices No default controller available [bluetooth]# ubuntu@ubuntu:~$ apt-cache policy pi-bluetooth linux-firmware-raspi2 pi-bluetooth: Installed: 0.1.15ubuntu1.1~20.10.1 Candidate: 0.1.15ubuntu1.1~20.10.1 Version table: *** 0.1.15ubuntu1.1~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages 100 /var/lib/dpkg/status 0.1.15ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 Packages linux-firmware-raspi2: Installed: 4-0ubuntu0~20.10.1 Candidate: 4-0ubuntu0~20.10.1 Version table: *** 4-0ubuntu0~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages 100 /var/lib/dpkg/status 3-0ubuntu2~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/restricted arm64 Packages 2-0ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 Packages ubuntu@ubuntu:~$ bluetoothctl Agent registered [CHG] Controller DC:A6:32:F6:84:4E Pairable: yes [bluetooth]# devices [bluetooth]# list Controller DC:A6:32:F6:84:4E ubuntu [default] [bluetooth]# scan on Discovery started [CHG] Controller DC:A6:32:F6:84:4E Discovering: yes [NEW] Device 28:11:A5:D5:CB:47 LE-reserved_M [NEW] Device 28:11:A5:D5:AC:98 LE-Lemonade [NEW] Device E2:70:8C:88:51:C0 E2-70-8C-88-51-C0 [bluetooth]# * On CM4 ** ubuntu@ubuntu:~$ apt-cache policy pi-bluetooth linux-firmware-raspi2 pi-bluetooth: Installed: 0.1.15ubuntu1 Candidate: 0.1.15ubuntu1.1~20.10.1 Version table: 0.1.15ubuntu1.1~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages *** 0.1.15ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 Packages 100 /var/lib/dpkg/status linux-firmware-raspi2: Installed: 3-0ubuntu2~20.10.1 Candidate: 4-0ubuntu0~20.10.1 Version table: 4-0ubuntu0~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages *** 3-0ubuntu2~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/restricted arm64 Packages 100 /var/lib/dpkg/status 2-0ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 Packages ubuntu@ubuntu:~$ bluetoothctl Agent registered [bluetooth]# list [bluetooth]# devices No default controller available [bluetooth]# ubuntu@ubuntu:~$ !apt apt-cache policy pi-bluetooth linux-firmware-raspi2 pi-bluetooth: Installed: 0.1.15ubuntu1.1~20.10.1 Candidate: 0.1.15ubuntu1.1~20.10.1 Version table: *** 0.1.15ubuntu1.1~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages 100 /var/lib/dpkg/status 0.1.15ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 Packages linux-firmware-raspi2: Installed: 4-0ubuntu0~20.10.1 Candidate: 4-0ubuntu0~20.10.1 Version table: *** 4-0ubuntu0~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-proposed/restricted arm64 Packages 100 /var/lib/dpkg/status 3-0ubuntu2~20.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/restricted arm64 Packages 2-0ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/restricted arm64 Packages ubuntu@ubuntu:~$ bluetoothctl Agent registered [CHG] Controller DC:A6:32:FE:BA:B2 Pairable: yes [bluetooth]# devices [bluetooth]# list Controller DC:A6:32:FE:BA:B2 ubuntu [default] [bluetooth]# scan on Discovery started [CHG] Controller DC:A6:32:FE:BA:B2 Discovering: yes [NEW] Device 28:11:A5:D5:AC:98 LE-Lemonade [NEW] Device 28:11:A5:D5:CB:47 LE-reserved_M [bluetooth]# ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of
