[Bug 2072490] Re: [needs-packaging] U-Boot for Microchip PIC64GX
It looks like Steve's comments are addressed by the current PPA version (and I'll make a note to check that MCD_tasks.c disappears in the forthcoming merge of u-boot main!). I do note there's a few lintian errors / warnings to clean up. Most are trivial and I'm happy to just deal with them myself while sponsoring, specifically: E: u-boot-pic64gx source: build-depends-indep-without-arch-indep This is because, now the u-boot-pic64gx package is riscv64 only, there are no arch-indep packages left. Trivial fix: make gcc-riscv64-linux-gnu part of build-depends instead. W: u-boot-pic64gx source: missing-license-paragraph-in-dep5-copyright gpl-2.0 [debian/copyright:126] W: u-boot-pic64gx source: missing-license-paragraph-in-dep5-copyright gpl-2.0+ [debian/copyright:119] Here the lines in d/copyright refer to GPL-2.0 instead of GPL-2 and GPL-2.0+ instead of GPL-2+. Trivial fix: delete .0 in each case W: u-boot-pic64gx source: patch-file-present-but-not-mentioned-in-series [debian/patches/riscv-update-PIC64GX-model-property.patch] This one I need a bit of guidance on. I *think* this patch is not meant to be there; if I add it to d/p/series it complains about a reversed/already applied patch so I'm guessing this patch was in an earlier bit of packaging, but was then applied upstream and so removed from d/p/series, but the patch itself didn't get removed from the directory? If so, I'm happy to just remove it while sponsoring. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072490 Title: [needs-packaging] U-Boot for Microchip PIC64GX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2072490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072500] Re: [SRU] Add Microchip PIC64GX Curiosity Kit support
Looks good, sponsoring for oracular -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072500 Title: [SRU] Add Microchip PIC64GX Curiosity Kit support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2072500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072490] Re: [needs-packaging] U-Boot for Microchip PIC64GX
Sponsoring for oracular; this will need an ack from an AA to enter the archive. The question then is whether to MIR this package, given the intent is obviously to include it in images. I guess that'll come down to how "official" we want those images to be (and that may come down to a question of timing given there's only a month to go before noble's .1 release). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072490 Title: [needs-packaging] U-Boot for Microchip PIC64GX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2072490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069036] Re: Remove wireless-tools dependency
Re: the armhf and arm64 build failures, this is already tracked in LP: #2039967 but given they also failed in noble's release pocket these shouldn't matter for migration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069036 Title: Remove wireless-tools dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aircrack-ng/+bug/2069036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060240] Re: Pi DAC+ fails on Pi 5
@nathan-openid-1 That's a separate issue to this one -- I would suggest opening a separate issue against the linux-raspi package (https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+filebug), providing steps to reproduce if possible, and a link to the upstream bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060240 Title: Pi DAC+ fails on Pi 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2060240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854588] Re: gdebi-gtk calls pkexec inappropriately
I included mantic as well since it's technically affected, but I suspect it may go EOL before the fix lands there. Sponsoring for oracular in the meantime, and I'll paste Doug's SRU template in shortly (thanks very much for preparing that!) ** Summary changed: - gdebi-gtk calls pkexec inappropriately + [SRU] gdebi-gtk calls pkexec inappropriately ** Description changed: + [ Impact ] + + The bug causes GDebi to quit as soon as you click Install Package to try + to install a .deb package, which is confusing to newer Linux users who + might not know about alternative command-line options such as dpkg. + + In particular, this bug happens when you download a .deb using Google + Chrome (or other browsers that aren't installed through snap) and tell + it to open the .deb file. GDebi is the default GUI .deb installer for + Ubuntu flavors such as MATE and Xubuntu, so this is a common situation + for people to run into. + + This should be backported to the stable release because it fixes a + severe usability bug in Ubuntu MATE and Xubuntu. The system's default + package installer should not crash when you click the Install Package + button. + + The upload fixes the bug by changing the way GDebi launches pkexec. The + non-privileged instance of GDebi will stay open in the background so + that pkexec will always have a parent process. + + [ Test Plan ] + + Simple test to simulate the situation that Chrome creates: + + - Download a random .deb file you don't mind installing. In a terminal window, type: + setsid gdebi-gtk /path/to/the/deb/file/you/downloaded.deb + - Click Install Package. + + Prior to this bug fix, you will see an error "Refusing to render service to dead parents." in your terminal window. + With this fix applied, it will ask you for your password and then install properly. + + Longer test that actually demonstrates the bug as users experience it: + + - Start with a fresh install of Ubuntu MATE 24.04 or Xubuntu 24.04. + - Install Google Chrome from Google using their latest .deb file. + - Start with Chrome closed. + - If you're using MATE, drag the Google Chrome icon from the MATE menu to the top panel bar. The reason for this is because the problem doesn't happen if you launch Chrome from the MATE menu. + - Open Chrome by clicking the icon you dragged to the panel (or on Xubuntu, you can just launch it from the menu). + - In Chrome, download any .deb file that you don't mind installing. + - Open it from Chrome's downloads. If you are asked which program to use, choose GDebi (it will be the default). + - Click Install Package. + + Prior to this bug fix, GDebi will just disappear when you click Install Package. Nothing will be installed. + With this fix applied, it will ask you for your password and then install properly. + + [ Where problems could occur ] + + If there is a mistake in this change that breaks the GDebi GUI for other + users who currently don't experience this bug (because they use a + browser that isn't affected such as the firefox snap), it could cause + them to be unable to install downloaded .deb files easily through the + GUI. Essentially it would result in the existing problem widening its + scope to more users. + + [ Other Info ] + + This problem was originally introduced with Ubuntu 17.10 when GDebi + switched from using gksu to pkexec. Over the years it has become more + and more rare as browsers installed through snap became more popular, + but as you can see from the reproduction steps above, it's still pretty + easy for people to experience since Chrome is so popular. + + It has historically been difficult to reproduce (people will claim it's + already fixed or doesn't affect them anymore) because the behavior + depends on how the browser and GDebi are parented, which can vary based + on how the browser is launched. + + [ Original Description ] + Steps to reproduce: 1. Have Ubuntu with gdebi-gtk installed 2. Open Firefox 3. Visit some site with deb-package download link or use direct link like https://github.com/jgm/pandoc/releases/download/2.9.2.1/pandoc-2.9.2.1-1-amd64.deb 4. Proceed with file downloading 5. In Firefox select Library → Downloads, click on downloaded deb-file Expected results: * gdebi-gtk is opened, the package installs normally after users clicks Install button Actual results: * gdebi-gtk is opened, the package is not installed because of vanishing of gdebi-gtk window just after clicking Install button - Before anyone says this bug already exists... it doesn't (at least as far as I can see). It's just that a lot of similar bugs do/did exist where people have also experienced the same symptoms (of gdebi-gtk vanishing upon clicking 'Install'). So yes this is the same symptoms, but it must be a different cause as the circumstances are different and doesn't have the same resolution. The meat of it... Basically on a fresh install of Ubuntu MATE 18.04.3
[Bug 1854588] Re: gdebi-gtk calls pkexec inappropriately
Targetting to jammy, noble, and oracular. ** Also affects: gdebi (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: gdebi (Ubuntu Oracular) Importance: Medium Assignee: Utkarsh Gupta (utkarsh) Status: Confirmed ** Also affects: gdebi (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: gdebi (Ubuntu Jammy) 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/1854588 Title: [SRU] gdebi-gtk calls pkexec inappropriately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1854588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872002] Re: cqrlog needs to depend on mariadb instead of mysql
** Changed in: cqrlog (Ubuntu) Status: Confirmed => Fix Released ** Changed in: cqrlog (Ubuntu) Assignee: (unassigned) => Dave Hibberd (hibby) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872002 Title: cqrlog needs to depend on mariadb instead of mysql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cqrlog/+bug/1872002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070151] Re: package linux-image-6.8.0-35-lowlatency 6.8.0-35.35.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
I haven't had the time to try it myself, but I'm guessing the installer *may* well work, provided the lowlatency kernel option is deselected. There may be some amd64-only packages it attempts to pull in though, I'm not sure. That said a while back I did succeed in hammering together something ubuntu-studio-like on a Pi by overlaying ubuntustudio-desktop on a Pi server install (https://waldorf.waveform.org.uk/2023/the-ubuntu- studio.html), which worked pretty well (and that was on a Pi 4 -- I should retry that on a 5 when I get a mo). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070151 Title: package linux-image-6.8.0-35-lowlatency 6.8.0-35.35.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2070151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067080] Re: [SRU] Please bump firmware revision to 8 from jammy
@kevinyeh Oh, then I'm wondering if it is a boot firmware issue at all; the current Core 20 images were generated in January 2023, after the current point release of focal from August 2022, so they should have firmware at least as recent as the focal images. How far does the boot process get on the rev 1.4? Does it get past the rainbow screen or not? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067080 Title: [SRU] Please bump firmware revision to 8 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/2067080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070151] Re: package linux-image-6.8.0-35-lowlatency 6.8.0-35.35.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
The lowlatency kernel isn't supported on the Pi, and flash-kernel won't permit it to be flashed (because you'd be left with an unbootable system). Ideally the studio installer should detect this and not select the option by default (or better still, disable it), but I'm not sure there's a simple way for them to do that (at least "properly"; it's fairly easy to detect if you're on a Pi, but ideally the installer should be checking the flash-kernel database to see if there's a kernel- flavor limit in place and act accordingly). I need to have a think about this -- I'm reasonably confident this is a studio installer bug too (so I'll add that as affected), but I suspect flash-kernel needs to grow some facility for exposing the kernel-flavor limits imposed on the running system. ** Also affects: ubuntustudio-installer (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/2070151 Title: package linux-image-6.8.0-35-lowlatency 6.8.0-35.35.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2070151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070268] Re: pollen man-page in wrong section
** Merge proposal linked: https://code.launchpad.net/~waveform/pollinate/+git/pollinate/+merge/468065 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070268 Title: pollen man-page in wrong section To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/2070268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070268] [NEW] pollen man-page in wrong section
Public bug reported: The pollinate(1) man-page specifies pollen(8) references in several places, which are turned into links on manpages.ubuntu.com [1]. Unfortunately, pollen is documented in section 1 [2], so these links are all dead. [1]: https://manpages.ubuntu.com/manpages/noble/en/man1/pollinate.1.html [2]: https://manpages.ubuntu.com/manpages/noble/en/man1/pollen.1.html ** Affects: pollinate (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/2070268 Title: pollen man-page in wrong section To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/2070268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062667] Re: Fails on (and should be removed from) raspi desktop
** Merge proposal linked: https://code.launchpad.net/~tobhe/ubuntu-seeds/+git/ubuntu-seeds/+merge/467849 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062667 Title: Fails on (and should be removed from) raspi desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067080] Re: [SRU] Please bump firmware revision to 8 from jammy
If the bump enables the new boards to boot we will have to look at a potential point release for focal on the Pi images. Note to self: because this bump involves a rename of the package (from linux-firmware-raspi2 to linux-firmware-raspi) this will also involve adjusting the seed ... argh, which doesn't exist! The raspi seed was added in groovy; may need to backport that as well to focal for the purposes of rebuild. Can we even build focal images with ubuntu-image? Need to test... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067080 Title: [SRU] Please bump firmware revision to 8 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/2067080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067080] Re: [SRU] Please bump firmware revision to 8 from jammy
Test firmware is available in https://launchpad.net/~waveform/+archive/ubuntu/firmware. Please run through these steps for testing: * Flash current focal server images (armhf and arm64) from http://cdimage.ubuntu.com/releases/20.04.5/release/ to boot media (SD card) for testing * Boot the media on a model *other than* the 3B+ rev 1.4 (as the current image will not boot on these) * Once booted and logged in, fully upgrade and reboot system: sudo apt update; sudo apt full-upgrade; sudo reboot * Once rebooted, add PPA, upgrade and reboot: sudo add-apt-repository ppa:waveform/firmware; sudo apt full-upgrade; sudo reboot * After ensuring everything is fine (system boots, ethernet, wifi and bluetooth still operate), shut down the Pi: sudo poweroff * Move boot media to the 3B+ rev 1.4 board and boot the new pi * Ensure everything is fine (system boots, ethernet, wifi and bluetooth still operate). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067080 Title: [SRU] Please bump firmware revision to 8 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/2067080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069802] Re: [SRU] flash-kernel to support xilinx kria platforms with noble kernel
Some quick clarifications to Loic's excellent notes: > ... it should probably also run when f-k gets updated but I think it doesn't right now ... It should indeed be running when f-k is updated. That's something I fixed a while ago (LP: #1667742), and then fixed the fix (LP: #2007827). As you noted, it's complex :) > ... I haven't looked at how the two would get sorted; would the highest version win, or would the name be preponderant? This depends on the implementation of "linux-version sort", which it turns out is just doing Debian version comparison on the kernel version *including the suffix*. So if two versions are otherwise identical the suffix which sorts alphabetically later will be "latest". For example: $ cat versions 6.8.0-1005-raspi 6.8.0-1005-generic $ linux-version sort < versions 6.8.0-1005-generic 6.8.0-1005-raspi Worth bearing in mind when "moving flavours". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069802 Title: [SRU] flash-kernel to support xilinx kria platforms with noble kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2069802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872002] Re: cqrlog needs to depend on mariadb instead of mysql
Hi all, It turns out I agreed after some more thinking on the subject, so have committed a fix for this as 2.5.2-5 in Debian: https://tracker.debian.org/news/1538653/accepted-cqrlog-252-5-source- into-unstable/ Code's on salsa if you want to try a build and install - I ran it through my build infrastructure for jammy and noble and it builds successfully, but I haven't tested installing and running as I don't have a VM to hand. Cheers! Hibby -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872002 Title: cqrlog needs to depend on mariadb instead of mysql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cqrlog/+bug/1872002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
** Tags removed: indeed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.13/+bug/1977919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069827] Re: Place cloud-init seed on boot partition for desktop images
** Changed in: ubuntu-raspi-settings (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: ubuntu-raspi-settings (Ubuntu) Milestone: None => ubuntu-24.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069827 Title: Place cloud-init seed on boot partition for desktop images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-raspi-settings/+bug/2069827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069827] [NEW] Place cloud-init seed on boot partition for desktop images
Public bug reported: The Ubuntu Desktop for Raspberry Pi images include cloud-init since noble. The cloud-init seed is redirected to the (FAT formatted) boot partition on the Ubuntu Server for Raspberry Pi images, and for consistency and ease of use, this should be replicated for the desktop images too. We could add 99-fake-cloud.cfg to ubuntu-raspi-settings-desktop as well as ubuntu-raspi-settings-server (where it currently resides) which would allow us to remove it again in future, if that becomes necessary. However, that would necessarily create a conflict between both packages and it's conceivable that some may wish to install both (for desktop-on- server type installs). Therefore it is probably best to simply move 99-fake-cloud.cfg over to the common ubuntu-raspi-settings package, and add Breaks/Replaces to ensure the configuration is moved appropriately by dpkg. Note to self: the gadget will need updating to include the cloud-init seed on the boot partition of the desktop images. However, the seed must be *different* (don't auto-create users), and must not include network- config (as the desktop settings include a network-manager override). ** Affects: ubuntu-raspi-settings (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/2069827 Title: Place cloud-init seed on boot partition for desktop images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-raspi-settings/+bug/2069827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067125] Re: CVE-2024-21096 et al affects MariaDB in Ubuntu
Triggered autopkgtests via requested link, and added targetting for affected series (and package). ** Also affects: mariadb-10.6 (Ubuntu) Importance: Undecided Status: New ** Also affects: mariadb (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: mariadb-10.6 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: mariadb (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: mariadb-10.6 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: mariadb (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: mariadb-10.6 (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: mariadb-10.6 (Ubuntu Mantic) ** No longer affects: mariadb-10.6 (Ubuntu Noble) ** No longer affects: mariadb (Ubuntu Jammy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067125 Title: CVE-2024-21096 et al affects MariaDB in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb/+bug/2067125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058622] Re: [needs-packaging] lenovo-wwan-unlock
> - This package does not yield massive lintian Warnings, Errors Building locally against oracular presents the following: E: lenovo-cfgservice: dir-or-file-in-opt [opt/fcc_lenovo/] E: lenovo-cfgservice: dir-or-file-in-opt [opt/fcc_lenovo/configservice_lenovo] E: lenovo-cfgservice: dir-or-file-in-opt [opt/fcc_lenovo/sar_config_files/1016__EM05CN__ThinkPad-X1-Carbon-Gen-12__Intel.bin] E: lenovo-cfgservice: dir-or-file-in-opt [opt/fcc_lenovo/sar_config_files/Linux_0104__RM520NGL__X1CG12__Intel__29619.bin] E: lenovo-cfgservice: dir-or-file-in-opt [opt/fcc_lenovo/sar_config_files/Linux_0104__RM520NGL__X1CG12__Intel__30007.bin] E: lenovo-cfgservice: dir-or-file-in-opt [opt/fcc_lenovo/sar_config_files/Linux_1019__EM061KGL__ThinkPad_L13_2-in-1_Gen_5__Intel__48001.bin] E: lenovo-cfgservice: dir-or-file-in-opt [opt/fcc_lenovo/sar_config_files/Linux_1019__EM061KGL__ThinkPad_L13_Gen_5__Intel__48001.bin] E: lenovo-cfgservice: dir-or-file-in-opt [opt/fcc_lenovo/sar_config_files/Linux_1221__EM160RGL__ThinkPad_X1_Carbon_Gen_12__Intel__29619.bin] E: lenovo-cfgservice: dir-or-file-in-opt [opt/fcc_lenovo/sar_config_files/Linux_1226__EM160RGL__ThinkPad_X1_2-in-1_Gen_9__Intel__29619.bin] E: lenovo-cfgservice: dir-or-file-in-opt [opt/fcc_lenovo/sar_config_files/Linux__0105__RM520NGL__X12-in1G9__Intel__29619.bin] E: lenovo-cfgservice: dir-or-file-in-opt [opt/fcc_lenovo/sar_config_files/Linux__0105__RM520NGL__X12-in1G9__Intel__30007.bin] E: lenovo-cfgservice: dir-or-file-in-opt [opt/fcc_lenovo/sar_config_files/] E: lenovo-fccunlock: dir-or-file-in-opt [opt/fcc_lenovo/DPR_Fcc_unlock_service] E: lenovo-fccunlock: dir-or-file-in-opt [opt/fcc_lenovo/] E: lenovo-fccunlock: file-in-root-and-usr already in: usr/lib/systemd/system/lenovo-fccunlock.service [lib/systemd/system/lenovo-fccunlock.service] E: lenovo-cfgservice: lacks-ldconfig-trigger usr/lib/libconfigservice350.so usr/lib/libconfigserviceR+.so E: lenovo-cfgservice: lacks-versioned-link-to-shared-library usr/lib/libconfigservice350_dummy.so [usr/lib/libconfigservice350.so] E: lenovo-fccunlock: sharedobject-in-library-directory-missing-soname [usr/lib/libmodemauth.so] E: lenovo-wwan-unlock source: source-is-missing [DPR_Fcc_unlock_service] E: lenovo-wwan-unlock source: source-is-missing [configservice_lenovo] E: lenovo-wwan-unlock source: source-is-missing [libconfigservice350.so] E: lenovo-wwan-unlock source: source-is-missing [libconfigserviceR+.so] E: lenovo-wwan-unlock source: source-is-missing [libmbimtools.so] E: lenovo-wwan-unlock source: source-is-missing [libmodemauth.so] W: lenovo-cfgservice-dbgsym: debug-file-with-no-debug-symbols [usr/lib/debug/.build-id/ab/9d4087aa7de358a14bb19f9038f2347e8c37b3.debug] W: lenovo-cfgservice: package-name-doesnt-match-sonames libconfigservice350-dummy libconfigserviceR+ W: lenovo-cfgservice: shared-library-lacks-version usr/lib/libconfigservice350.so libconfigservice350_dummy.so W: lenovo-cfgservice: shared-library-lacks-version usr/lib/libconfigserviceR+.so libconfigserviceR+.so W: lenovo-cfgservice: unknown-field Modaliases W: lenovo-cfgservice-dbgsym: unknown-field Modaliases W: lenovo-fccunlock: unknown-field Modaliases W: lenovo-fccunlock-dbgsym: unknown-field Modaliases Quite a few of these can be trivially overridden (e.g. all the "source- is-missing" ones are simply down to the nature of the package). However, there's a few here that need corrective action. Specifically, file-in- root-and-usr definitely needs correcting, along with the modaliases bits (is dh-modaliases actually doing anything in this package?). The shared-library related tags are presumably because these aren't really "shared" (outside of this package) and can probably just be overridden with an appropriate justification in lintian-overrides. Unsubscribing ubuntu-sponsors for now, but please do re-subscribe when these have been actioned, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058622 Title: [needs-packaging] lenovo-wwan-unlock To manage notifications about this bug go to: https://bugs.launchpad.net/lenovo-wwan-unlock/+bug/2058622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066148] Re: Ubuntu Noble lacks of CRIU package
Hi Aleksandr -- thanks for the patch. There's a few things I'd like to rectify, and a couple of questions which should probably be answered before this can be sponsored. If we're going to introduce a delta on Debian, we should ensure things are forwarded so the delta can be resolved in time. To that end, the patches should have the Origin: or Forwarded: tag so we can track what's been forwarded and where. Looking through the patches added: d/p/criu-fix-compatibility-with-python3-12.patch: It would be preferable to add this as the two original patches it's made of so that each patch can have a simple Origin: header indicating where it came from (no need for Fowarded: in this case). Also, Author: should be Radostin (your name goes in d/changelog as the editor of the package, but Radostin is the author of the patch). d/p/make-disable-Wformat-truncation-warning-with-gcc-13-2.patch: Likewise, Author: should be Radostin. I'm a little confused about the origin of this patch. The referenced bug (https://github.com/checkpoint-restore/criu/issues/2398) has quite a different resolution upstream to the content of this patch (https://github.com/checkpoint-restore/criu/pull/2413/files). I'm guessing the upstream resolution is more recent; does the patch need revising? d/p/time-t-64bit-transition-fixes.patch: I'm assuming the Author: tag is correct here, as there's no other origin, but there's also no Forwarded: tag. Does this patch need forwarding upstream? Finally, d/changelog currently references noble but I *suspect* this will need to go into oracular first and then be SRU'd to noble (I've requested clarification on #ubuntu-release, but I think this is the procedure when something's been absent for more than one release). Anyway, I'll unsubscribe ubuntu-sponsors for now, but please feel free to add this back in if these points can be addressed. ** Bug watch added: github.com/checkpoint-restore/criu/issues #2398 https://github.com/checkpoint-restore/criu/issues/2398 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066148 Title: Ubuntu Noble lacks of CRIU package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/criu/+bug/2066148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1975641] Re: Can't download or update signatures within clamtk
Hi Dave, The computer I had been using when I reported the problem physically broke. I was without a personal computer for a long time. However, I recently got a new one, put Manjaro Linux on it, and am pleased to report that downloading malware definitions was a lot easier compared to when I first tried using ClamTK. The definitions did not download immediately after I clicked on intuitive options. I think I had to set ClamTK to automatically download updates until I saw evidence that the program had loaded malware definitions. Thanks, David From: nore...@launchpad.net on behalf of Dave M <1975...@bugs.launchpad.net> Sent: Thursday, January 25, 2024 12:58 PM To: dlavr...@hotmail.com Subject: [Bug 1975641] Re: Can't download or update signatures within clamtk Hi, Has this issue been resolved? respectfully, Dave M -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1975641 Title: Can't download or update signatures within clamtk Status in ClamTk: New Status in Ubuntu: New Bug description: Hi, I have Manjaro Linux and installed clamtk v6.14-1 via Pamac 10.4.0-2. clamtk indicates that it has 0 virus signatures, and this does not change once I click update. I was able to update the virus signatures, but only once I found the terminal commands required to do so. I was successful using the commands mentioned at https://wiki.manjaro.org/index.php/ClamAV TLDR: clamtk doesn't come with any virus signatures when installed on Manjaro, and updates via the GUI don't work. The only way to get virus signatures was by typing commands into Terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/clamtk/+bug/1975641/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975641 Title: Can't download or update signatures within clamtk To manage notifications about this bug go to: https://bugs.launchpad.net/clamtk/+bug/1975641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060240] Re: Pi DAC+ fails on Pi 5
Oh, one other thing to check -- I did note that for some reason the boards aren't auto-detected under Ubuntu. I did need to add "dtoverlay=iqaudio-dacplus" to /boot/firmware/config.txt on my board. I'm not sure why the auto-detection isn't operating for us (the overlays are present and in the right place, as otherwise the dtoverlay= line wouldn't work), but it's another thing worth checking. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060240 Title: Pi DAC+ fails on Pi 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2060240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060240] Re: Pi DAC+ fails on Pi 5
I was testing with a black IQaudIO Pi-DAC+ board (I don't have one of the newer ones) -- and that was working for me. Are you seeing the same symptoms, i.e. the particular lines of output in dmesg quoted in the original report? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060240 Title: Pi DAC+ fails on Pi 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2060240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065180] Re: performance regression in dracut-install 060
As requested, results from running stock noble on the same Pi 4B with the same SD card as before. First, stock noble (with all available upgrades): $ sudo hyperfine --warmup 1 -r 5 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 193.558 s ± 2.334 s[User: 77.577 s, System: 118.253 s] Range (min … max): 190.964 s … 196.165 s5 runs Second, noble after update from the specified PPA (ppa:bdrung/ppa): $ sudo hyperfine --warmup 1 -r 5 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 81.116 s ± 2.468 s[User: 16.125 s, System: 67.027 s] Range (min … max): 78.409 s … 84.017 s5 runs So a pretty substantial improvement :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065180 Title: performance regression in dracut-install 060 To manage notifications about this bug go to: https://bugs.launchpad.net/dracut/+bug/2065180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062176] Re: Cannot launch armhf containers on arm64 host under noble
I think the consensus at this point is that, while this manifests in LXD (and chroot), it's ultimately a kernel configuration issue. Marking lxd invalid. Just to fill in a bit of background, there's been some discussion between kernel team and foundations what the correct course of action here is and I think the consensus is "just flip COMPAT_32BIT_TIME back on". The one remaining question, looking at the original bug that flipped that switch in the first place (LP: #2038582) is: should this change be limited to linux-raspi? ** Changed in: lxd (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062176 Title: Cannot launch armhf containers on arm64 host under noble To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/2062176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062667] Re: Fails on (and should be removed from) raspi desktop
> Was it it more than a red line in systemctl status output? Does it have annoying logging behaviour or break some other service if it isn't running? A red line in systemctl status output is sufficient, to my understanding? I was under the impression that, absent any hardware issues, a freshly installed copy of Ubuntu ought to boot to the "running" state, and that booting to the "degraded" state was a bug (e.g. LP: #1660598). Not necessarily a high-priority one if it doesn't break any other functionality (and I acknowledge this does not, as far as I can tell), but a bug nonetheless as it interferes with the ability to notice when something else is failing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062667 Title: Fails on (and should be removed from) raspi desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060240] Re: Pi DAC+ fails on Pi 5
Verified on a Pi 5 8GB running the current release of noble with an IQaudio DAC+ HAT. Played some Rolling Stones, and some Tangerine Dream very nicely! Also verified SPI still appeared operable (at least with a low-speed ADC), and that the DAC+ still operated on a 3B+ board. ** Tags removed: verification-needed-noble-linux-raspi ** Tags added: verification-done-noble-linux-raspi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060240 Title: Pi DAC+ fails on Pi 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2060240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067766] [NEW] Software Updater Unable to Open Required List
Public bug reported: An unresolvable problem occurred while initializing the package information. Please report this bug against the 'update-manager' package and include the following error message: E:can not open /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_jammy-backports_InRelease - fopen (13: Permission denied), E:The package lists or status file could not be parsed or opened. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: update-manager 1:22.04.20 ProcVersionSignature: Ubuntu 6.5.0-35.35~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 31 12:04:59 2024 InstallationDate: Installed on 2022-10-20 (589 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067766 Title: Software Updater Unable to Open Required List To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2067766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062176] Re: Cannot launch armhf containers on arm64 host under noble
This is likely to be a linux-raspi issue since armhf containers are apparently working happily in the autopkgtest cloud. Further, armhf chroots are also failing under linux-raspi with a Futex error from the kernel (will attempt to add some detail on this in due course). ** Also affects: linux-raspi (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/2062176 Title: Cannot launch armhf containers on arm64 host under noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2062176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065180] Re: performance regression in dracut-install 060
Results on a Pi 4B booting from SD card. Stock noble: $ sudo hyperfine -r 5 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 189.984 s ± 1.618 s[User: 75.720 s, System: 115.323 s] Range (min … max): 187.319 s … 191.142 s5 runs Then running the branch from https://code.launchpad.net/~bdrung/ubuntu/+source/initramfs- tools/+git/initramfs-tools/+ref/ubuntu/devel : $ sudo hyperfine -r 5 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 98.473 s ± 2.263 s[User: 26.061 s, System: 73.138 s] Range (min … max): 95.923 s … 101.560 s5 runs So that's a pretty substantial improvement. Still not *quite* at the mantic level, but it's in the same ball-park now, and that's not including the changes to lvm2 or cryptsetup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065180 Title: performance regression in dracut-install 060 To manage notifications about this bug go to: https://bugs.launchpad.net/dracut/+bug/2065180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062948] Re: intel-mediasdk: ftbfs with GCC-13
Sponsored linked branch after patching for oracular. Once this lands for oracular, this should be converted to SRU for noble. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062948 Title: intel-mediasdk: ftbfs with GCC-13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-mediasdk/+bug/2062948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061637] Re: [SRU] xx-svn-review crashed with ModuleNotFoundError
@teward -- yes, I'm aware of the requirement that each release needs a higher version, and the versions proposed in the patches do conform to this requirement. It just seems a bit odd that the mantic patch proposes a 0.1 suffix while the noble patch proposes a 0.24.04.1 suffix. Could/should the mantic patch not propose a 0.23.10.1 suffix? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061637 Title: [SRU] xx-svn-review crashed with ModuleNotFoundError To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xxdiff/+bug/2061637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957168] Re: [SRU] fwbuilder crashes in Noble when trying to create almost any type of new object
Leaving ubuntu-sponsors subscribed for the SRU uploads -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957168 Title: [SRU] fwbuilder crashes in Noble when trying to create almost any type of new object To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwbuilder/+bug/1957168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062948] Re: intel-mediasdk: ftbfs with GCC-13
** Merge proposal linked: https://code.launchpad.net/~liushuyu-011/ubuntu/+source/intel-mediasdk/+git/intel-mediasdk/+merge/464771 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062948 Title: intel-mediasdk: ftbfs with GCC-13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-mediasdk/+bug/2062948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062947] Re: chmlib: FTBFS: chm_http.c:167:32: error: implicit declaration of function ‘inet_addr’ [-Werror=implicit-function-declaration]
The branch in the linked merge proposal is for noble, but the issue is still present in the oracular package (by the looks of the version numbers it's presumably present in at least noble, mantic and possibly earlier too). I've sponsored this for oracular for now; if that lands successfully (I can't currently test locally due to armhf issues on the Pi images), this should probably be converted to an SRU bug for the affected series. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062947 Title: chmlib: FTBFS: chm_http.c:167:32: error: implicit declaration of function ‘inet_addr’ [-Werror=implicit-function-declaration] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chmlib/+bug/2062947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062947] Re: chmlib: FTBFS: chm_http.c:167:32: error: implicit declaration of function ‘inet_addr’ [-Werror=implicit-function-declaration]
** Merge proposal linked: https://code.launchpad.net/~liushuyu-011/ubuntu/+source/chmlib/+git/chmlib/+merge/464769 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062947 Title: chmlib: FTBFS: chm_http.c:167:32: error: implicit declaration of function ‘inet_addr’ [-Werror=implicit-function-declaration] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chmlib/+bug/2062947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061637] Re: [SRU] xx-svn-review crashed with ModuleNotFoundError
Reviewing the patches, they mostly look fine but I'm a bit confused as to why the version numbering goes from a ubuntu0.24.04.1 suffix in the noble patch, to a ubuntu0.1 suffix in the mantic patch (noting that both have the same base version, 1:5.1+git20220924+dfsg-1). Obviously that'll still work (0.1 < 0.24.04.1), it's just ... odd? I've sponsored the noble upload now, but just wanted to check if the version numbers are as intended or if you wanted to revise the mantic/jammy ones first? (I'm happy to revise them on upload if you want -- it's a trivial change after all) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061637 Title: [SRU] xx-svn-review crashed with ModuleNotFoundError To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xxdiff/+bug/2061637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061637] Re: [SRU] xx-svn-review crashed with ModuleNotFoundError
Sync to oracular is now done so I'll mark this Fix Released, and target to the affected series ** Also affects: xxdiff (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: xxdiff (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: xxdiff (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: xxdiff (Ubuntu) Status: Confirmed => Fix Released ** Changed in: xxdiff (Ubuntu Noble) Status: New => Confirmed ** Changed in: xxdiff (Ubuntu Mantic) Status: New => Confirmed ** Changed in: xxdiff (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061637 Title: [SRU] xx-svn-review crashed with ModuleNotFoundError To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xxdiff/+bug/2061637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061668] Re: [SRU] evtx_filter_records.py crashed with ModuleNotFoundError in Noble
Confirmed on oracular; targetting for affected series and sponsoring for oracular, thanks! ** Also affects: python-evtx (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: python-evtx (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: python-evtx (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: python-evtx (Ubuntu Jammy) 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/2061668 Title: [SRU] evtx_filter_records.py crashed with ModuleNotFoundError in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-evtx/+bug/2061668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957168] Re: [SRU] fwbuilder crashes in Noble when trying to create almost any type of new object
Confirmed on an oracular desktop VM with the current release (5.3.7-8). Patch needed a quick rebase against that current version (and update- maintainer running, but that may be because the current release has no Ubuntu changes). Anyway, sponsoring for oracular, and adding noble to the targetting. ** Also affects: fwbuilder (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: fwbuilder (Ubuntu Noble) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957168 Title: [SRU] fwbuilder crashes in Noble when trying to create almost any type of new object To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwbuilder/+bug/1957168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060976] Re: Create autopkgtest
I do like the addition of the compare test; it's a bit "magic" but the fact it's comparing against an image from the actual installation (/usr/share/xrdp/xrdp_logo.bmp) does demonstrate the operation of the package very nicely. I did try and run the tests locally under autopkgtest but unfortunately they fail because the test is using "sudo" without declaring "needs- sudo" in the restrictions (without this, sudo isn't installed/configured for the test suite). Having patched that, the tests failed to run in a chroot due to the presence of needs-sudo (unsurprisingly), so I attempted with a full VM, but that failed with a badpkg error in imagemagick. So, this looks promising, but may need a bit more work to be certain it'll pass in production. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060976 Title: Create autopkgtest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/2060976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067080] [NEW] [SRU] Please bump firmware revision to 8 from jammy
Public bug reported: [ Impact ] The rev 1.4 variant of the 3B+ requires an updated boot firmware, specifically one at least as recent as that in jammy-updates (version 8). This should be back-ported to focal, and preferably bionic to provide support for Core 18 booting on these devices. [ Test Plan ] As a closed boot firmware this will need validation on all supported Pis. For bionic, this is the 2B, 3B, 3A+, and 3B+. For focal, this is the 2B, 3B, 3A+, 3B+, and 4B. Because the package includes wifi and bluetooth firmware as well as boot firmware, the following should be verified: * Ability to boot successfully * Ability to reboot successfully * Ability to shutdown successfully * That wifi can connect successfully on relevant models (all except the 2B) * That bluetooth can pair successfully on relevant models (all except the 2B) [ Regression Potential ] Fairly low; the firmware in question has been in use on all relevant models in jammy for quite some time, so the regression potential for the operation of the firmware itself is low. That said, the wifi and bluetooth firmware still interacts with the kernel, and bionic and focal have different kernel versions to jammy, hence why the operation of these components will still need (re-)verification. If issues arise they are most likely to come from the fact that linux- firmware-raspi2 was renamed to linux-firmware-raspi in jammy which affected the diversions in the package. This means the backport isn't *entirely* straight-forward and care must be taken to ensure that all relevant files end up in their correct locations with the correct diversions. ** Affects: linux-firmware-raspi2 (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: New ** Affects: linux-firmware-raspi2 (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux-firmware-raspi2 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-firmware-raspi2 (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Also affects: linux-firmware-raspi2 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-firmware-raspi2 (Ubuntu Bionic) Importance: Undecided Status: New ** Summary changed: - Please bump firmware revision to 8 from jammy + [SRU] Please bump firmware revision to 8 from jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067080 Title: [SRU] Please bump firmware revision to 8 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/2067080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044382] Re: Some Qt-based applications open "another" icon under Gnome
** Summary changed: - Quassel opens "another" icon under Gnome + Some Qt-based applications open "another" icon under Gnome ** Description changed: - I'm unsure if this is a bug in quassel, or in the gnome dock itself. - Under Ubuntu 23.10 (mantic), running Quassel from a pinned icon on the - left bar results in the pinned icon appearing "idle" (not running), and - a second icon appearing below those that are pinned which apparently - represents the running quassel instance. + I'm unsure if this is a bug in the affected applications, or in the + gnome dock itself. Under Ubuntu 23.10 (mantic) and 24.04 (noble), + running Quassel, Veusz, or OpenSCAD from a pinned icon on the left bar + results in the pinned icon appearing "idle" (not running), and a second + icon appearing below those that are pinned which apparently represents + the running instance. - Pressing the idle quassel icon (or pressing the Super+4 shortcut for it) - runs *another* instance of quassel rather than switching to the running - instance. The "extra" icon also cannot be pinned (and occasionally - strange "copies" of it are left lying around if one tries to drag it to - the pinned icon locations). + Pressing the idle application icon (or pressing the Super+N shortcut for + it) runs *another* instance of the application rather than switching to + the running instance. The "extra" icon also cannot be pinned (and + occasionally strange "copies" of it are left lying around if one tries + to drag it to the pinned icon locations). - This may be because quassel is a Qt based application, but I also run + This may be because these are all Qt-based applications, but I also run KeepassXC (another Qt application) without such issues (other than unusual window borders and icons which appear on both applications), - hence why I'm unsure this is an issue in quassel or in the gnome dock. - I'll attach a screenshot demonstrating the issue. + hence why I'm unsure this is an issue in these applications or in the + gnome dock. I'll attach a screenshot demonstrating the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044382 Title: Some Qt-based applications open "another" icon under Gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2044382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066881] Re: Copied icons in dash after application run
Curiously, I've seen this issue with several Qt-based applications (Quassel, Veusz, and OpenSCAD) under noble, as reported in LP: #2044382, but I've not seen it with Firefox (which isn't Qt-based to the best of my knowledge?). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066881 Title: Copied icons in dash after application run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2066881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066894] [NEW] Log spam from querying snaps on noble
Public bug reported:
After registering my Ubuntu 24.04 desktop for Raspberry Pi with
Landscape, the following warnings periodically appear in the system
journal (every few minutes):
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:29:23,114 WARNING
[MainThread] Unable to get config for snap gnome-42-2204:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:29:25,989 INFO
[MainThread] Ping indicates message available. Scheduling an urgent exchange.
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:29:32,875 INFO
[MainThread] Starting urgent message exchange with
https://landscape.canonical.com/message-system.
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:29:36,253 INFO
[PoolThread-twisted.internet.reactor-0] Sent 223188 bytes and received 5382
bytes in 3.37s.
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:29:36,257 INFO
[MainThread] Switching to normal exchange mode.
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:29:36,267 INFO
[MainThread] Message exchange completed in 3.39s.
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:06,301 INFO
[MainThread] Ping indicates message available. Scheduling an urgent exchange.
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:32,847 INFO
[MainThread] Got notification of impending exchange. Notifying all plugins.
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:32,847 INFO
[MainThread] Got notification of impending exchange. Notifying all plugins.
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:32,912 INFO
[MainThread] Queueing a message with updated data watcher info for
landscape.client.monitor.activeprocessinfo.ActiveProcessInfo.
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,015 WARNING
[MainThread] Unable to get config for snap snapd-desktop-integration:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,020 WARNING
[MainThread] Unable to get config for snap core22:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,024 WARNING
[MainThread] Unable to get config for snap rpi-imager:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,029 WARNING
[MainThread] Unable to get config for snap signal-desktop:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,033 WARNING
[MainThread] Unable to get config for snap snapd:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,038 WARNING
[MainThread] Unable to get config for snap bare:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,043 WARNING
[MainThread] Unable to get config for snap core24:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,047 WARNING
[MainThread] Unable to get config for snap gtk-common-themes:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,052 WARNING
[MainThread] Unable to get config for snap thunderbird:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,056 WARNING
[MainThread] Unable to get config for snap snap-store:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,061 WARNING
[MainThread] Unable to get config for snap telegram-desktop:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,066 WARNING
[MainThread] Unable to get config for snap ubuntu-image:
[Bug 2066885] [NEW] On Pi desktop, numerous reports of lack of landlock supported ABI
Public bug reported: On the Ubuntu noble desktop for Raspberry Pi, the system journal has numerous of the following entries: May 23 10:30:29 kermit tracker-miner-f[11130]: Could not get landlock supported ABI: Operation not supported May 23 10:30:29 kermit tracker-miner-f[11130]: Refusing to extract file data since Landlock could not be enabled. Update your kernel to fix this warning. These appear to be written every time a file in my home directory is modified. The kernel is the stock noble kernel from linux-raspi, 6.8.0-1004-raspi. ** Affects: tracker-miners (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/2066885 Title: On Pi desktop, numerous reports of lack of landlock supported ABI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/2066885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062564] Re: [FFe] Seed pemmican
** Changed in: pemmican (Ubuntu) Status: Triaged => 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/2062564 Title: [FFe] Seed pemmican To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pemmican/+bug/2062564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064208] Re: Installer crashes when booting from USB on Raspberry Pi
@vanvugt Indeed -- I'm confident that's the root cause at this point; just waiting for that to land in devel, then I can convert the bug to SRU, wait for that to land, then request an image re-spin from the release team -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064208 Title: Installer crashes when booting from USB on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2064208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065051] Re: [SRU] Migrate Pi users to KMS
Verified with upgrade of a Pi 4 on an SD card as described in the test plan, only variant being to grab the noble tar-ball manually (as do- release-upgrade won't allow --proposed with --devel). Worked happily, KMS was present in the config.txt after the upgrade, and the HDMI audio outputs appeared correctly when the card was subsequently booted on a Pi 5. ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065051 Title: [SRU] Migrate Pi users to KMS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2065051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058970] Re: deepin-log-viewer 5.9.7+ds1-2build6 FTBFS on 32-bit time64 architectures
** Changed in: deepin-log-viewer (Ubuntu Noble) Assignee: Shengjing Zhu (zhsj) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058970 Title: deepin-log-viewer 5.9.7+ds1-2build6 FTBFS on 32-bit time64 architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deepin-log-viewer/+bug/2058970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921914] Re: [SRU] package quickml 0.7-5.1 failed to install/upgrade: installed quickml package post-installation script subprocess returned error exit status 1
I've re-sponsored updated debdiffs as requested -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921914 Title: [SRU] package quickml 0.7-5.1 failed to install/upgrade: installed quickml package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quickml/+bug/1921914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060882] Re: [SRU] usrpctl fails to run
Confirmed; fix looks minimal and reasonable, sponsoring, thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060882 Title: [SRU] usrpctl fails to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uhd/+bug/2060882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2015017] Re: [SRU] scaling is wrong in SVG output
** Changed in: graphviz (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: graphviz (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: graphviz (Ubuntu Mantic) Status: Confirmed => In Progress ** Changed in: graphviz (Ubuntu Noble) Status: Confirmed => 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/2015017 Title: [SRU] scaling is wrong in SVG output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/2015017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2015017] Re: [SRU] scaling is wrong in SVG output
** Description changed: + [ Impact ] + + graphivz output is incorrect for SVG output when the "size" attribute is + set, as it implicitly is in several circumstances. + + [ Test Plan ] + + * sudo apt install imagemagick graphviz + * Grab fst.dot attached to this bug + * dot -Tpng fst.dot | display png:- + * Observe correct scaling + * dot -Tsvg fst.dot | display svg:- + * Observe incorrect cropping of output + * Enable proposed (https://wiki.ubuntu.com/Testing/EnableProposed) + * Upgrade graphviz to version from proposed + * dot -Tsvg fst.dot | display svg:- + * Ensure output is not cropped + + [ Regression Potential ] + + Low; the patched applied is from upstream and has been part of the + official sources for many years now (Debian and Ubuntu are rather behind + on their versions of graphviz, but it looks like this may be corrected + in the oracular cycle). Nonetheless, the patch was first applied to our + current version, is minimal in nature, and fixes the issue in tests + without impacting other output. + + There is a very small possibility someone may be relying on the + incorrect truncation of SVG output, but this is almost certainly + outweighed by the number of users impacted by incorrect truncation of + output in, e.g. jupyter notebooks, and by the consistency of having the + same (lack of) cropping in different output formats. + + [ Original Description ] + SVG output brutally truncates large (and even not so large) graphs when the "size" attribute is set. This was fixed *two years ago* upstream. Any chance that we might get more recent graphviz packages in Ubuntu at some point? Failing that, it is quite easy to fix this bug. See https://gitlab.com/graphviz/graphviz/-/issues/1605 The fix is very simple, it seems: https://gitlab.com/graphviz/graphviz/-/commit/a5606d101af1cc949908a6f0bc19caaa4eb31159 Definitely present in 22.04, still present in the Lunar package (graphviz_2.42.2-7build3) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2015017 Title: [SRU] scaling is wrong in SVG output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/2015017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2015017] Re: [SRU] scaling is wrong in SVG output
Brilliant, thanks very much for that -- I've upload the ocular version to proposed, and I'll get the SRU uploads done later this morning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2015017 Title: [SRU] scaling is wrong in SVG output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/2015017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2015017] Re: [SRU] scaling is wrong in SVG output
For SRU purposes, is there any chance I could ask you for a simple reproducer case? It's okay if it uses jupyter, but I'm struggling to come up with one without it and I've run out of time this evening. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2015017 Title: [SRU] scaling is wrong in SVG output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/2015017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2015017] Re: scaling is wrong in SVG output
I quite understand the frustration with something that appears to be abandoned. However, in this case it seems it was actually down to some confusion over the versioning scheme which changed upstream from Debian (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980900 has the gory details). It also seems that Debian's now got a new watch file and version 11 is now in experimental, so I'm hoping that'll migrate to unstable at some point and we'll pick up a modern version for oracular. Anyway, back to the fix at hand -- this definitely needs patching in oracular, noble, mantic, and jammy at the very least. Unfortunately your branch appears to have diff-markers embedded in it, so I can't accept it directly, but the patch is trivial enough I can just apply it to the package directly. I'll target this to the affected releases and start the SRU process once this is in oracular. ** Bug watch added: Debian Bug tracker #980900 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980900 ** Also affects: graphviz (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: graphviz (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: graphviz (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: graphviz (Ubuntu) Status: New => Confirmed ** Changed in: graphviz (Ubuntu Jammy) Status: New => Confirmed ** Changed in: graphviz (Ubuntu Mantic) Status: New => Confirmed ** Changed in: graphviz (Ubuntu Noble) Status: New => Confirmed ** Summary changed: - scaling is wrong in SVG output + [SRU] scaling is wrong in SVG output -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2015017 Title: [SRU] scaling is wrong in SVG output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/2015017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065493] [NEW] Please merge rpi-lgpio 0.6
Public bug reported: New upstream version fixes future re-numbering of the gpiochip device on Pi 5. ** Affects: rpi-lgpio (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/2065493 Title: Please merge rpi-lgpio 0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpi-lgpio/+bug/2065493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060677] Re: Consistent (zfs?) errors at shutdown
Yes, I'm afraid so. In fact I'm occasionally seeing it on boot as well
which seems to result in wayland crashing and the session falling back
to X11. Here's the backtrace from a crash on startup which resulted in
me starting an X11 session (and then wondering why the cursor
[ 47.898381] spl: loading out-of-tree module taints kernel.
[ 47.957978] zfs: module license 'CDDL' taints kernel.
[ 47.957986] Disabling lock debugging due to kernel taint
[ 47.958013] zfs: module license taints kernel.
[ 47.986141] Initializing XFRM netlink socket
[ 48.872585] rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks:
{ 3- } 22 jiffies s: 921 root: 0x8/.
[ 48.872601] rcu: blocking rcu_node structures (internal RCU debug):
[ 48.872605] Sending NMI from CPU 0 to CPUs 3:
[ 48.872610] NMI backtrace for cpu 3
[ 48.872616] CPU: 3 PID: 2797 Comm: modprobe Tainted: P C OE
6.8.0-1004-raspi #4-Ubuntu
[ 48.872619] Hardware name: Raspberry Pi 5 Model B Rev 1.0 (DT)
[ 48.872621] pstate: 8049 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 48.872625] pc : g+0x44/0x80 [zfs]
[ 48.872998] lr : round_fn+0x124/0x1a8 [zfs]
[ 48.873282] sp : 800083b3a9f0
[ 48.873283] x29: 800083b3a9f0 x28: 0010 x27: 0001
[ 48.873288] x26: 0002 x25: 0010 x24: 0040
[ 48.873291] x23: 0010 x22: 3c6e x21: 800083b3aac8
[ 48.873294] x20: a0001eeb1f08 x19: 800083b3aa38 x18:
[ 48.873298] x17: x16: a00084e64e20 x15: daab804bbe5f084f
[ 48.873301] x14: dda7b2c9fd2e0cf6 x13: 8ea05092eab4a56e x12: 7e3c7900fc64dbc7
[ 48.873304] x11: 7e3c7900fc64dbc7 x10: a0001ea5ba80 x9 :
[ 48.873308] x8 : e60eea37 x7 : d00f75b3 x6 : fffd
[ 48.873311] x5 : fc4d5ec9 x4 : 000c x3 : 000b
[ 48.873314] x2 : 0006 x1 : 0001 x0 : 800083b3aac8
[ 48.873317] Call trace:
[ 48.873319] g+0x44/0x80 [zfs]
[ 48.873589] compress_pre+0x1e4/0x270 [zfs]
[ 48.873861] blake3_compress_in_place_generic+0x4c/0xa8 [zfs]
[ 48.874133] hash_one_generic+0x78/0xf0 [zfs]
[ 48.874402] blake3_hash_many_generic+0x74/0xb0 [zfs]
[ 48.874672] compress_chunks_parallel+0xe8/0x1d8 [zfs]
[ 48.874942] blake3_compress_subtree_wide+0x1a4/0x1c8 [zfs]
[ 48.875210] blake3_compress_subtree_wide+0xd8/0x1c8 [zfs]
[ 48.875477] blake3_compress_subtree_wide+0xd8/0x1c8 [zfs]
[ 48.875744] blake3_compress_subtree_wide+0xb0/0x1c8 [zfs]
[ 48.876009] blake3_compress_subtree_wide+0xd8/0x1c8 [zfs]
[ 48.876275] compress_subtree_to_parent_node+0x50/0x110 [zfs]
[ 48.876542] Blake3_Update2+0x168/0x240 [zfs]
[ 48.876809] Blake3_Update+0x54/0x80 [zfs]
[ 48.877074] blake3_incremental+0x2c/0x40 [zfs]
[ 48.877341] abd_iterate_func+0x104/0x150 [zfs]
[ 48.877608] abd_checksum_blake3_native+0x7c/0xb8 [zfs]
[ 48.877875] chksum_run+0xac/0x160 [zfs]
[ 48.878145] chksum_benchit+0x140/0x198 [zfs]
[ 48.878412] chksum_benchmark+0x334/0x3a8 [zfs]
[ 48.878681] chksum_init+0x28/0xa8 [zfs]
[ 48.878950] spa_init+0x130/0x168 [zfs]
[ 48.879221] zfs_kmod_init+0x4c/0x108 [zfs]
[ 48.879489] openzfs_init_os+0x1c/0xc8 [zfs]
[ 48.879755] openzfs_init+0x70/0xcd0 [zfs]
[ 48.880023] do_one_initcall+0x4c/0x368
[ 48.880029] do_init_module+0xa0/0x260
[ 48.880034] load_module+0x790/0x8c8
[ 48.880037] init_module_from_file+0x94/0xf8
[ 48.880040] idempotent_init_module+0x178/0x2a8
[ 48.880043] __arm64_sys_finit_module+0x6c/0xd8
[ 48.880047] invoke_syscall+0x50/0x120
[ 48.880049] el0_svc_common.constprop.0+0x48/0xf0
[ 48.880051] do_el0_svc+0x24/0x38
[ 48.880053] el0_svc+0x48/0x178
[ 48.880057] el0t_64_sync_handler+0x120/0x130
[ 48.880059] el0t_64_sync+0x1a8/0x1b0
[ 48.970724] ZFS: Loaded module v2.2.2-0ubuntu9, ZFS pool version 5000, ZFS
filesystem version 5
[ 49.798958] Key type psk registered
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060677
Title:
Consistent (zfs?) errors at shutdown
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2060677/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065180] Re: performance regression in dracut-install
@viraniac well, you're absolutely right! Same SD card with a fresh noble install, running on a Pi 4, first stock and second with a downgraded dracut from mantic: Pi 4B, stock -- 03:05 Pi 4B, downgrade -- 01:10 That is a pretty substantial regression, and diff'ing the initrds once more showed they're basically identical in content (unsurprisingly), so it's not writing any less. I wonder if it's added some sync points or something similar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065180 Title: performance regression in dracut-install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2065180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065408] [NEW] growroot-almost should be inhibitable from boot partition
Public bug reported: Some users wish to handle post-boot partitioning or fs configuration themselves. For this use-case it is important that the rootfs is *not* expanded on first boot. On the server images, this is relatively trivial by appending "growpart: off", but on the desktop images it's handled by the growroot-almost service and this is only capable of being inhibited by touching /etc/growroot-grown. It should be possible to inhibit this behaviour from the boot partition only which, being FAT, can be mounted from other OS'. ** Affects: ubuntu-raspi-settings (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: Confirmed ** Changed in: ubuntu-raspi-settings (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: ubuntu-raspi-settings (Ubuntu) Milestone: None => ubuntu-24.10 ** Changed in: ubuntu-raspi-settings (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065408 Title: growroot-almost should be inhibitable from boot partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-raspi-settings/+bug/2065408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065180] Re: performance regression in dracut-install
Some results from some local testing. These tests were all performed on the same SD card (a Samsung EVO Select 64GB) with fresh installs of the jammy and noble server images, after running full upgrades and rebooting: Pi 5, noble -- 01:23 Pi 4B, noble -- 03:05 Pi 3B+, noble -- 05:19 Pi 5, jammy -- unsupported Pi 4B, jammy -- 01:06 Pi 3B+, jammy -- 01:59 So, there *appears* to be a substantial slow down from jammy. However, I don't think this is due to dracut or a performance regression in initramfs-tools. I remembered that, this cycle, the kernel team got rid of the linux-modules-extra split in the linux-raspi kernel. This results in a substantially increased initrd size because many more modules are included by default. I took a listing of the jammy and noble initramfs contents and (after some manipulation to remove .zst suffixes, which are also new in the noble initramfs, and removing kernel version numbers). I'll attach the result of diff'ing these outputs, but a quick grep through the results and some calculations shows roughly 1000 extra files in the noble version. In other words, this is not comparing like for like. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065180 Title: performance regression in dracut-install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2065180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065180] Re: performance regression in dracut-install
** Patch added: "initramfs.diff" https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2065180/+attachment/5776701/+files/initramfs.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065180 Title: performance regression in dracut-install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2065180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063365] Re: brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52
I've added some notes to the upstream bug, including an observation about the regulatory-domain. My thoughts earlier that it doesn't affect anything may be partially wrong (the issue still occurs, but *potentially* only when the interface has no regdom prior to authentication? We'll see what upstream say about it -- I may be barking up the wrong tree there). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063365 Title: brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2063365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063365] Re: brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52
Aha! I can reproduce this on RaspiOS bookworm too, but while the messages appear in dmesg, they *don't* appear on the console, but that's just due to different printk default (level 3 instead of 4 on Ubuntu). So, this is an upstream issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063365 Title: brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2063365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063365] Re: brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52
I can reproduce this fairly reliably on the Ubuntu 24.04 Server for Pi image. Strangely, it doesn't seem to occur on the initial use of the wifi on boot, but running "netplan apply" (causing the interface to re- connect to the AP), reliably causes several "set chanspec" messages to appear in dmesg. The issue occurs whether or not ethernet is also in use, and setting the regulatory domain (a common suggestion in various other reports of this issue found online) does not appear to make a difference either. Speaking of other reports, https://github.com/raspberrypi/linux/issues/6049 is an open issue on the upstream kernel that appears to be identical to this one. ** Bug watch added: github.com/raspberrypi/linux/issues #6049 https://github.com/raspberrypi/linux/issues/6049 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063365 Title: brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2063365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065138] Re: Please merge libcec 6.0.2-5 into Oracular
This merge is no longer needed. Our only delta with Debian is adding libraspberrypi-dev as a build-dependency which used to be required to enable raspi compatibility. However, since switching everything over to full KMS (in noble), we no longer need the raspi-specific bits. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065138 Title: Please merge libcec 6.0.2-5 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcec/+bug/2065138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064208] Re: Installer crashes when booting from USB on Raspberry Pi
Oh, many thanks to @marius.quabeck as well -- all the confirmations are extremely helpful! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064208 Title: Installer crashes when booting from USB on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2064208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064208] Re: Installer crashes when booting from USB on Raspberry Pi
@phrogger Brilliant, thanks for the confirmations; I've also tested a Sabrent NVMe drive here (successfully) and an ancient Intel SSD over USB (again successful). I think I'm happy to call this "good" at this point, so I'll push ahead with trying to get LP: #2037015 SRU'd back to noble, and then see if I can get the desktop image re-spun. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064208 Title: Installer crashes when booting from USB on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2064208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065051] Re: [SRU] Migrate Pi users to KMS
** Description changed: + [ Impact ] + In switching Pi Server users over to the KMS overlay (as resolution to LP: #2038924) we need an additional quirk for upgraders to migrate config.txt (this will be similar, but not identical, to the one for LP: #1923673). + + If we do not migrate such users, the immediate impact is that Pi 5 users + will have no sound output on server images (the Pi 5 only has HDMI audio + output, no auxiliary jack). Potentially more problematic in the long- + run, though, is that we will wind up with users on different graphical + stacks (the KMS stack, which is the only upstream supported stack going + forward, and the legacy framebuffer method). + + [ Test Case ] + + * Flash Ubuntu jammy to SD card and boot on Pi 4 + * Check /boot/firmware/config.txt does not contain dtoverlay=vc4-kms-v3d (it should not on Pi server images) + * sudo do-release-upgrade + * Proceed through upgrade and reboot + * Ensure system reboots successfully + * After reboot, check /boot/firmware/config.txt contains dtoverlay=vc4-kms-v3d + * Shutdown, move SD card to Pi 5 and boot it + * Check /proc/asound/cards contains entries for vc4hdmi + + [ Regression Potential ] + + The use of the KMS overlay itself is not concerning; we already use it + on the Pi desktop images, and have for several cycles now with no + serious issues, so the regression potential there is minimal. + + However, the quirk does manipulate the bootloader's config.txt on the + boot partition, which always carries the potential of leaving a system + unbootable. To guard against this, tests are included with the quirk + which check for several scenarios including a config.txt which has + already been migrated to the KMS overlay manually by the user (there are + various reasons to do this, including running kmscon), as well as the + typical expected case. ** Changed in: ubuntu-release-upgrader (Ubuntu Noble) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065051 Title: [SRU] Migrate Pi users to KMS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2065051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065051] Re: [SRU] Migrate Pi users to KMS
** Summary changed: - Migrate Pi users to KMS + [SRU] Migrate Pi users to KMS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065051 Title: [SRU] Migrate Pi users to KMS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2065051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065051] Re: Migrate Pi users to KMS
** Also affects: ubuntu-release-upgrader (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: ubuntu-release-upgrader (Ubuntu Noble) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065051 Title: Migrate Pi users to KMS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2065051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065051] [NEW] Migrate Pi users to KMS
Public bug reported: In switching Pi Server users over to the KMS overlay (as resolution to LP: #2038924) we need an additional quirk for upgraders to migrate config.txt (this will be similar, but not identical, to the one for LP: #1923673). ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: High Assignee: Dave Jones (waveform) Status: Confirmed ** Changed in: ubuntu-release-upgrader (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-release-upgrader (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065051 Title: Migrate Pi users to KMS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2065051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060858] Re: [SRU] rqsh fails to run
It was a little tricky to confirm this one, given that the missing dependency (libterm-readkey-perl) is seeded by server and cloud-image (so the problem didn't immediately manifest in my test containers!), but yes, confirmed. Targetting to affected releases. One question about the proposed fix: it's adding libterm-readkey-perl to Depends, when upstream have fixed this by adding it to Recommends. I suspect upstream is correct in that the "intent" of the package is to provide a library for querying RDF, and rqsh is (presumably?) a simple utility for experimenting with that facility, not the "primary" artifact of the package. In other words, there exist users that could happily install librdf-query-perl as a dependency of some Perl-based system, use it successfully, and never notice (or care) that rqsh doesn't work, and who don't want the overhead of its dependencies installed as well. Still, given the additional dependency in this case is already seeded in server and cloud-image, this really feels like splitting hairs, and I'd much rather the package "just works" for users. So, sponsoring! ** Also affects: librdf-query-perl (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: librdf-query-perl (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: librdf-query-perl (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: librdf-query-perl (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: librdf-query-perl (Ubuntu Focal) Status: New => Confirmed ** Changed in: librdf-query-perl (Ubuntu Jammy) Status: New => Confirmed ** Changed in: librdf-query-perl (Ubuntu Mantic) Status: New => Confirmed ** Changed in: librdf-query-perl (Ubuntu Noble) Status: New => Confirmed ** Changed in: librdf-query-perl (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060858 Title: [SRU] rqsh fails to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librdf-query-perl/+bug/2060858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921914] Re: [SRU] package quickml 0.7-5.1 failed to install/upgrade: installed quickml package post-installation script subprocess returned error exit status 1
Hmm, one thing that a test build in oracular shows is that lintian complains about the package depending on lsb-base, which is now an empty transitional package. It appears the only reason it depends on it is for the init-script in debian/quickml.init and there's no equivalent systemd package. I'll sponsor this anyway because the "fix" should be in oracular before the SRUs are considered, but I have a suspicion this is broken in noble onwards anyway (which is where lsb-base was made transitional IIRC), and will need some minor surgery to add a systemd service definition there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921914 Title: [SRU] package quickml 0.7-5.1 failed to install/upgrade: installed quickml package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quickml/+bug/1921914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921914] Re: [SRU] package quickml 0.7-5.1 failed to install/upgrade: installed quickml package post-installation script subprocess returned error exit status 1
Confirmed on all noted series; targetting accordingly. I was a little
nervous about rm'ing /etc/mailname in the postrm, but an apt-file search
confirms nothing else seems to own it (if something else owned it, it
might be better to create things like this in postinst, and just leave
them there in {pre,post}rm, but in this case it looks okay).
** Also affects: quickml (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: quickml (Ubuntu Oracular)
Importance: Undecided
Status: Confirmed
** Also affects: quickml (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: quickml (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: quickml (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: quickml (Ubuntu Noble)
Status: New => Confirmed
** Changed in: quickml (Ubuntu Mantic)
Status: New => Confirmed
** Changed in: quickml (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: quickml (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921914
Title:
[SRU] package quickml 0.7-5.1 failed to install/upgrade: installed
quickml package post-installation script subprocess returned error
exit status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/quickml/+bug/1921914/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064208] Re: Installer crashes when booting from USB on Raspberry Pi
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu-manual-tests/+git/ubuntu-manual-tests/+merge/465423 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064208 Title: Installer crashes when booting from USB on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2064208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951586] Re: Need option to specify wifi regulatory domain
** Changed in: network-manager (Ubuntu Lunar) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951586 Title: Need option to specify wifi regulatory domain To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064208] Re: Installer crashes when booting from USB on Raspberry Pi
I now have a test image that, using the patch from LP: #2037015, appears to fix the installer issue when booting from USB. If volunteers are interested in testing the image, I've made it available at: https://zoidberg.waveform.org.uk/images/ubuntu-24.04-preinstalled- desktop-arm64+raspi.img.xz The SHA256 of the image, for verification purposes, is b2718d9005a5ea6486b8512b6cf3974ce48ef879d1232a6dc88b2ccaa1dc3390 I've tested booting from two SD cards on both models and both appear fine; I've also tested USB boot on the Pi 4 (which worked happily) and tomorrow I should be able to test NVMe on a Pi 5. However, given the variability displayed by this bug already, the wider the variety of hardware tested, the better. Naturally, no workarounds should be in place when testing (leave the config.txt "as is"). If things work, please report the model and memory size of your Pi (e.g. Pi 4 4GB) and what you're booting from (SD card, SSD, NVMe). make+model of the boot media would be useful too, but largely to judge if we're covering a reasonable range of hardware. If things don't work, please report the above information, plus where in the procedure the crash occurred. If possible, re-flash and try to confirm if the crash occurs in the same place each time (we've already seen cases in this bug where "sometimes it does and sometimes it doesn't"). ** Description changed: After writing the Ubuntu 24.04 Desktop for Raspberry Pi image to an SSD drive with a USB3 interface (specifically; this issue does not occur when booting from an SD card), booting the drive on a Pi 4 or Pi 5, and running through the installer to the point where the (corrupted) slide deck starts to display during setup, the installer crashes. [ Workaround ] + + A test image is now available; please see comment 1 below for details. At the time of writing, some workarounds have been found, but none that consistently work on all boards with all drives. One workaround that has worked on a Pi with a Samsung EVO SSD, and a Crucial SSD is as follows: Before booting the image, find config.txt on the boot partition, and the "dtoverlay=vc4-kms-v3d" line within it. There will be two of these lines, you want the first one under an "[all]" section. Append ",cma-128" to the line. Specifically, the following section: dtoverlay=vc4-kms-v3d disable_fw_kms_setup=1 Should become: dtoverlay=vc4-kms-v3d,cma-128 disable_fw_kms_setup=1 Unmount the drive cleanly, boot it, and run through the installer. You may revert the change (if you wish) after successful installation. Another workaround, reported as working on a Pi 5 with an NVMe drive attached over PCIe: Before booting the image, find config.txt on the boot partition. Under the first "[all]" section append the following line: - dtparam=pciex1 + dtparam=pciex1 Unmount the drive cleanly, boot it, and run through the installer. Please note both workarounds have also been reported as failing with certain drive combinations. [ Background ] Given this crash occurs immediately upon the (corrupted) slide deck starting, that it only occurs when booting from USB (but the exact same image works from an SD card), and that merely changing the pre- allocation of the contiguous memory area affects it, I suspect this at least related to (if not a duplicate of) LP: #2037015, particularly since a crash bug is now associated with it too, LP: #2062146. Still, I'll leave this open as a non-duplicate for now as I'm not positive of root-cause yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064208 Title: Installer crashes when booting from USB on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2064208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064370] Re: Blank screen after boot in raspberry pi 4
> So that means that with different monitors I could potentially not need this vc4.force_hotplug option, right? That is certainly my suspicion; it doesn't much surprise me that an LCD controller isn't *quite* obeying the HDMI spec (or perhaps that it expects to be part of something else which handles asserting the hot- plug line). I would certainly hope a branded monitor behaves properly, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064370 Title: Blank screen after boot in raspberry pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2064370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064370] Re: Blank screen after boot in raspberry pi 4
> If I switch to the KMS overlay, the message is exactly the same, so it means the EDID is accessible from the monitor in either case. Not quite the case I'm afraid. The output you're quoting there is from the pi's bootloader running on the GPU. So, what you've established there is that the GPU (which ignores hotplug, as noted in 6by9's comment in the upstream bug) reads the EDID. This is all that's needed in the FKMS case because there the kernel driver is a thin shim that just talks to the firmware running on the GPU and retrieves EDID data from there. However in the KMS case, the bootloader eventually relinquishes control of the GPU to the linux kernel, and the kernel then attempts to retrieve the EDID independently (as least, this is my understanding of things -- I'm no expert in this area; corrections welcome!). Glad to hear the force_hotplug option works; that largely gels with the idea that the monitor is not correctly asserting hot-plug. If it's not asserting hot-plug on boot, the would also explain why re-plugging the monitor doesn't work either. FKMS doesn't care, it just reads the EDID anyway, but the KMS driver is waiting for a signal to do so and there's none on boot, or later when the monitor is re-plugged. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064370 Title: Blank screen after boot in raspberry pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2064370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064370] Re: Blank screen after boot in raspberry pi 4
You are correct it was introduced for noble as, without the KMS driver, there's no audio output over HDMI on the server image under the Pi 5 (LP: #2038924). KMS is also the only supported stack on the Pi 5 upstream, and rather than trying to support different stacks on different models I opted to move everything to the KMS stack instead (which we were already using on the desktop images). Unfortunately, it seems that as well as causing issues on the older models (LP: #2063255, LP: #2060300 -- incidentally the cma-128 workaround is for this latter bug), it's now even causing issues on the Pi 4. Obviously I didn't see these issues during testing, but then I've only two different models of monitor here that I test with: a BenQ and a Samsung. From the description it sounds like the kernel is either failing to retrieve, or failing to parse the EDID from your monitor. However, from reading a potentially related upstream bug (https://github.com/raspberrypi/linux/issues/5368#issuecomment-1453144837) it may be that the monitor is failing to assert hotplug. I would first try 6by9's work-arounds from that thread, specifically: * Forcing hotplug by appending "vc4.force_hotplug=N (where N is 0x01 for the first HDMI port, or 0x02 for the second) to cmdline.txt on the boot partition: $ sudo sed -i -e 's/$/ vc4.force_hotplug=0x01' /boot/firmware/cmdline.txt $ sudo reboot * If that fails, reboot with the fkms overlay in place, dump the EDID to /lib/firmware/edid.bin, then force that to be parsed under kms: $ sudo sed -i -e 's/vc4-kms-v3d/vc4-fkms-v3d/' /boot/firmware/config.txt $ sudo reboot ... wait for the reboot ... $ sudo cp /sys/class/drm/card1-HDMI-A-1/edid /lib/firmware/edid.bin $ sudo sed -i -e 's/vc4-fkms-v3d/vc4-kms-v3d/' /boot/firmware/config.txt $ sudo sed -i -e 's/$/ drm.edid_firmware=HDMI-A-1:edid.bin' /boot/firmware/cmdline.txt $ sudo reboot ... see if the monitor works ... If you could attach the edid dump from when running under FKMS that may also help the kernel team in their investigation. ** Bug watch added: github.com/raspberrypi/linux/issues #5368 https://github.com/raspberrypi/linux/issues/5368 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064370 Title: Blank screen after boot in raspberry pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2064370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064208] Re: Installer crashes when booting from USB on Raspberry Pi
** Changed in: ubiquity (Ubuntu) Status: New => Triaged ** Changed in: ubiquity (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064208 Title: Installer crashes when booting from USB on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2064208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064208] Re: Installer crashes when booting from USB on Raspberry Pi
** Description changed: After writing the Ubuntu 24.04 Desktop for Raspberry Pi image to an SSD drive with a USB3 interface (specifically; this issue does not occur when booting from an SD card), booting the drive on a Pi 4 or Pi 5, and running through the installer to the point where the (corrupted) slide deck starts to display during setup, the installer crashes. [ Workaround ] - This is a temporary fix, confirmed on a Pi 4 (would be grateful if - others can confirm the workaround on a wider variety of hardware). + At the time of writing, some workarounds have been found, but none that + consistently work on all boards with all drives. One workaround that has + worked on a Pi with a Samsung EVO SSD, and a Crucial SSD is as follows: + Before booting the image, find config.txt on the boot partition, and the "dtoverlay=vc4-kms-v3d" line within it. There will be two of these lines, you want the first one under an "[all]" section. Append ",cma-128" to the line. Specifically, the following section: - dtoverlay=vc4-kms-v3d - disable_fw_kms_setup=1 + dtoverlay=vc4-kms-v3d + disable_fw_kms_setup=1 Should become: - dtoverlay=vc4-kms-v3d,cma-128 - disable_fw_kms_setup=1 + dtoverlay=vc4-kms-v3d,cma-128 + disable_fw_kms_setup=1 Unmount the drive cleanly, boot it, and run through the installer. You may revert the change (if you wish) after successful installation. + + Another workaround, reported as working on a Pi 5 with an NVMe drive + attached over PCIe: + + Before booting the image, find config.txt on the boot partition. Under + the first "[all]" section append the following line: + + dtparam=pciex1 + + Unmount the drive cleanly, boot it, and run through the installer. + + Please note both workarounds have also been reported as failing with + certain drive combinations. [ Background ] Given this crash occurs immediately upon the (corrupted) slide deck starting, that it only occurs when booting from USB (but the exact same image works from an SD card), and that merely changing the pre- allocation of the contiguous memory area affects it, I suspect this at least related to (if not a duplicate of) LP: #2037015, particularly since a crash bug is now associated with it too, LP: #2062146. Still, I'll leave this open as a non-duplicate for now as I'm not positive of root-cause yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064208 Title: Installer crashes when booting from USB on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2064208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064208] [NEW] Installer crashes when booting from USB on Raspberry Pi
Public bug reported: After writing the Ubuntu 24.04 Desktop for Raspberry Pi image to an SSD drive with a USB3 interface (specifically; this issue does not occur when booting from an SD card), booting the drive on a Pi 4 or Pi 5, and running through the installer to the point where the (corrupted) slide deck starts to display during setup, the installer crashes. [ Workaround ] This is a temporary fix, confirmed on a Pi 4 (would be grateful if others can confirm the workaround on a wider variety of hardware). Before booting the image, find config.txt on the boot partition, and the "dtoverlay=vc4-kms-v3d" line within it. There will be two of these lines, you want the first one under an "[all]" section. Append ",cma-128" to the line. Specifically, the following section: dtoverlay=vc4-kms-v3d disable_fw_kms_setup=1 Should become: dtoverlay=vc4-kms-v3d,cma-128 disable_fw_kms_setup=1 Unmount the drive cleanly, boot it, and run through the installer. You may revert the change (if you wish) after successful installation. [ Background ] Given this crash occurs immediately upon the (corrupted) slide deck starting, that it only occurs when booting from USB (but the exact same image works from an SD card), and that merely changing the pre- allocation of the contiguous memory area affects it, I suspect this at least related to (if not a duplicate of) LP: #2037015, particularly since a crash bug is now associated with it too, LP: #2062146. Still, I'll leave this open as a non-duplicate for now as I'm not positive of root-cause yet. ** Affects: ubiquity (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/2064208 Title: Installer crashes when booting from USB on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2064208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861338] Re: RPI4 wifi unreliable when usb3 storage is attached
That's a different issue, LP: #2063365, which only started occurring after the recent wifi firmware bump -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861338 Title: RPI4 wifi unreliable when usb3 storage is attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063887] Re: debsums warning after upgrade to Ubuntu 24.04 (noble): changed file /etc/X11/xorg.conf.d/99-v3d.conf (from ubuntu-raspi-settings-desktop package)
** Changed in: ubuntu-raspi-settings (Ubuntu) Status: New => Triaged ** Changed in: ubuntu-raspi-settings (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063887 Title: debsums warning after upgrade to Ubuntu 24.04 (noble): changed file /etc/X11/xorg.conf.d/99-v3d.conf (from ubuntu-raspi-settings-desktop package) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-raspi-settings/+bug/2063887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052575] Re: [SRU] Update firmware to support autofocus
Re-uploaded with bug ref -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052575 Title: [SRU] Update firmware to support autofocus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-xilinx-ap1302/+bug/2052575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063445] [NEW] GIMP crashes on close in noble arm64
Public bug reported: On the Ubuntu Desktop for Raspberry Pi (arm64) under noble, GIMP is reliably crashing when closing the application with unsaved changes, and selecting "Discard Changes". Steps to reproduce: * sudo apt install gimp * Open GIMP with an image (right click image in Files, Open With..., select GIMP) * Make some changes to the image (scribble over it) * Close the application * Select Discard Changes * GIMP Crash Debug appears I'll attach the bug information from crash debug window ** Affects: gimp (Ubuntu) Importance: Undecided Status: New ** Attachment added: "gimp-crash.txt" https://bugs.launchpad.net/bugs/2063445/+attachment/5770223/+files/gimp-crash.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063445 Title: GIMP crashes on close in noble arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2063445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038669] Re: Add Raspberry Pi 5 support
I finally got around to testing this on noble: it's broken. Even more than it was in mantic where at least it'd *list* the camera modules. Now it can't even do that (but it works fine on RaspiOS with the same camera modules). Sigh. I'll release note this for now, and try and find time to dig into it next cycle. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038669 Title: Add Raspberry Pi 5 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2038669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062667] Re: Fails on (and should be removed from) raspi desktop
** Also affects: ubuntu-meta (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/2062667 Title: Fails on (and should be removed from) raspi desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060920] Re: Noble installer crashes on Raspberry Pi 400 when WPA3 times out/fails to connect
I *think* you may have run into the issue with the installer crashing on the timezone selection screen (which is directly after network selection and which had a fatal issue with an out of date library; LP: #1987454). That issue is now corrected on the current daily (from 4/22 which I'm ISO testing as a release candidate), and I'm unable to replicate a full crash when attempting to connect to a WPA3 AP. Rather, it just sits there and fails to connect to the AP. Incidentally, we do now have the firmware blobs that *allegedly* support WPA3 on the BCM43455 (used on the 3A+, 3B+, 4B, and 5) but apparently they only work with WPA3 under iwd (not wpa_supplicant) currently. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060920 Title: Noble installer crashes on Raspberry Pi 400 when WPA3 times out/fails to connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2060920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063255] Re: Cannot play audio via HDMI on server
** Summary changed: - Cannot play audio from server on older models + Cannot play audio via HDMI on server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063255 Title: Cannot play audio via HDMI on server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2063255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063255] Re: Cannot play audio from server on older models
Another interesting data-point: apparently mpg321 *isn't* broken on noble. It works, but only with the headphone output (on those models that have it, i.e. everything prior to the Pi 5). Same goes with ffmpeg; no buffer xruns when outputting to the headphone socket. Which leans me back towards "something iffy with vc4hdmi and ALSA"... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063255 Title: Cannot play audio from server on older models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2063255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063255] Re: Cannot play audio from server on older models
Hmm, I may have to revise this. It seems mpg321 (with ALSA, which is how I've always tested the audio output) just doesn't work at all on any model; just complains about libao driver everywhere. Meanwhile, ffmpeg (my backup) works happily on the 4 and 5, but just complains about buffer xrun errors on all the earlier models (and takes a bizarrely long time to respond to ctrl-C when it does). However, aplay (ALSA's own userspace utility) works happily, at least on the 3B+ where I tested it, but only plays WAV or PCM, not MP3s, which just adds more complexity to the testing script. Still, that *suggests* ALSA's operating correctly and perhaps it's just ffmpeg trying to allocate a buffer that's too small to avoid overrun on the older platforms (and mpg321's presumably just broken on noble). I'll leave this open for now, but I'd advise the kernel team to ignore it while I dig a bit deeper. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063255 Title: Cannot play audio from server on older models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2063255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063255] Re: Cannot play audio from server on older models
** Description changed: While attempting to play music as part of the ISO tests for the release, while the vc4hdmi sound card appears in /proc/asound/cards, the mpg321 player used by the tests (which has never worked *well* on the older models, but at least worked) failed with: - [0.029s] ubuntu@miss-piggy:~$ mpg321 -o alsa -a hw:1,0 test.mp3 - High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2, and 3. - Version 0.3.2-1 (2012/03/25). Written and copyrights by Joe Drew, - now maintained by Nanakos Chrysostomos and others. - Uses code from various people. See 'README' for more! - THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK! - Title : Love on a Real Train Artist : State Azure - Album : Dreams A Tribute to Tangerin Year : 2020 - Comment :Genre : AmbientElectronic + [0.029s] ubuntu@miss-piggy:~$ mpg321 -o alsa -a hw:1,0 test.mp3 + High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2, and 3. + Version 0.3.2-1 (2012/03/25). Written and copyrights by Joe Drew, + now maintained by Nanakos Chrysostomos and others. + Uses code from various people. See 'README' for more! + THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK! + Title : Love on a Real Train Artist : State Azure + Album : Dreams A Tribute to Tangerin Year : 2020 + Comment :Genre : AmbientElectronic - Playing MPEG stream from test.mp3 ... - MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo - Can't open libao driver with device hw:1,0 (is device in use?) + Playing MPEG stream from test.mp3 ... + MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo + Can't open libao driver with device hw:1,0 (is device in use?) I also tried ffmpeg (which usually works a bit better on the older models) and that fails with a constant series of ALSA buffer xrun errors. The specific models on which this has failed so far are the 2B - and 3B+. It appears to work happily on the 4B, though. + and 3B+. ffmpeg appears to work happily on the 4B, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063255 Title: Cannot play audio from server on older models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2063255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
