[Bug 2077981] Re: [SRU] Add HiFive Premier P550 to database
Sponsored for plucky; working on SRU sponsorship for oracular and noble (just need to double-check the noble version; oracular should be done shortly) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077981 Title: [SRU] Add HiFive Premier P550 to database To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2077981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2086774] Re: [SRU] Add CM5 to flash-kernel database
** Description changed: [ Impact ] flash-kernel unable to complete successfully on the CM5 (also implying kernel upgrades will fail). [ Test Plan ] * Boot $series release image on CM5 * sudo flash-kernel * Note "Unsupported platform error" * sudo apt install -t $series-proposed flash-kernel * sudo flash-kernel * flash-kernel complete successfully To guard against regression, re-test on other supported platforms [ Where problems could occur ] Only the database db/all.db is changed. Test plan includes test of operation on other supported platforms to guard against regression, and checks before and after states to ensure issue is present and actually fixed. [ Other Info ] + Note to SRU reviewers: on the subject of the version number, I've bumped + it to the plucky version (plus a ~release suffix) simply because after + diff'ing noble->oracular->plucky the only differences are in the + changelog, so the version may as well reflect that this is effectively + the (current) plucky version back-ported (I say "current" because next + on the todo list is to merge flash-kernel in plucky to upstream's + 3.108). + Add entry for the Raspberry Pi CM5 to the flash-kernel devices database, specifically: Machine: Raspberry Pi Compute Module 5 Rev 1.0 Machine: Raspberry Pi Compute Module 5 Rev * Kernel-Flavors: raspi raspi-realtime Method: pi DTB-Id: bcm2712-rpi-cm5-cm5io.dtb U-Boot-Script-Name: bootscr.rpi Required-Packages: u-boot-tools -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2086774 Title: [SRU] Add CM5 to flash-kernel database To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2086774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2085903] Re: [SRU] Please merge rpi-eeprom 26
** Summary changed: - Please merge rpi-eeprom 26 + [SRU] Please merge rpi-eeprom 26 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2085903 Title: [SRU] Please merge rpi-eeprom 26 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpi-eeprom/+bug/2085903/+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
Sponsored change to plucky; working on sponsoring SRUs for oracular and noble -- 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 2077981] Re: [SRU] Add HiFive Premier P550 to database
** Changed in: flash-kernel (Ubuntu Oracular) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: flash-kernel (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: flash-kernel (Ubuntu Noble) Status: New => Triaged ** Changed in: flash-kernel (Ubuntu) Status: New => Triaged ** Changed in: flash-kernel (Ubuntu Oracular) Status: New => Triaged ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077981 Title: [SRU] Add HiFive Premier P550 to database To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2077981/+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
** Also affects: flash-kernel (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: flash-kernel (Ubuntu Noble) 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/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 2086774] [NEW] Add CM5 to flash-kernel database
Public bug reported: Specifically "Raspberry Pi Compute Module 5 Rev 1.0" ** Affects: flash-kernel (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/2086774 Title: Add CM5 to flash-kernel database To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2086774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2086774] Re: Add CM5 to flash-kernel database
** Also affects: flash-kernel (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: flash-kernel (Ubuntu Oracular) Importance: Undecided Status: New ** Summary changed: - Add CM5 to flash-kernel database + [SRU] Add CM5 to flash-kernel database ** Changed in: flash-kernel (Ubuntu) Status: New => Triaged ** Changed in: flash-kernel (Ubuntu Noble) Status: New => Triaged ** Changed in: flash-kernel (Ubuntu Oracular) Status: New => Triaged ** Changed in: flash-kernel (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: flash-kernel (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: flash-kernel (Ubuntu Oracular) Assignee: (unassigned) => Dave Jones (waveform) ** Tags added: foundations-todo ** Description changed: - Specifically "Raspberry Pi Compute Module 5 Rev 1.0" + [ Impact ] + + flash-kernel unable to complete successfully on the CM5 (also implying + kernel upgrades will fail). + + [ Test Plan ] + + * Boot $series release image on CM5 + * sudo flash-kernel + * Note "Unsupported platform error" + * sudo apt install -t $series-proposed flash-kernel + * sudo flash-kernel + * flash-kernel complete successfully + + To guard against regression, re-test on other supported platforms + + [ Where problems could occur ] + + Only the database db/all.db is changed. Test plan includes test of + operation on other supported platforms to guard against regression, and + checks before and after states to ensure issue is present and actually + fixed. + + [ Other Info ] + + Add entry for the Raspberry Pi CM5 to the flash-kernel devices database, + specifically: + + Machine: Raspberry Pi Compute Module 5 Rev 1.0 + Machine: Raspberry Pi Compute Module 5 Rev * + Kernel-Flavors: raspi raspi-realtime + Method: pi + DTB-Id: bcm2712-rpi-cm5-cm5io.dtb + U-Boot-Script-Name: bootscr.rpi + Required-Packages: u-boot-tools -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2086774 Title: [SRU] Add CM5 to flash-kernel database To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2086774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2032178] Re: Update to 20240926 version
** Tags added: fr-9440 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2032178 Title: Update to 20240926 version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpiboot/+bug/2032178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2086744] Re: [SRU] bulkrename fails with newer curses
** Description changed: + [ Impact ] + + One of ranger's most useful facilities (bulkrename) fails to operate + entirely. + + [ Test Plan ] + + For the affected $series: + + * lxc launch ubuntu:$series renametest + * lxc shell renametest + * apt update && apt install ranger + * touch foo bar baz + * ranger + * Select "bar" and "baz" files with space + * :bulkrename (start bulk-rename operation) + * Edit "bar" and "baz" to something else, e.g. "far" and "faz" + * Exit the editor + * Observe failure with error message "endwin() returned ERR" on the bottom line + * q (exit ranger) + + Upgrade to proposed version and re-test: + + * apt install -t $[series}-proposed ranger + * ranger + * Select "bar" and "baz" files with space + * :bulkrename + * Edit "bar" and "baz" to something else, e.g. "far" and "faz" + * Exit the editor + * Editor appears showing proposed "mv" operations + * Exit the editor + * Observe files are renamed + + Test open_with command too: + + * Select "bar" file with space + * :open_with vim + * Ensure editor opens successfully + * :q + * Ensure ranger re-appears successfully + + [ Regression Potential ] + + The patch is proposed (but not yet applied) as a PR upstream. It is + minimal, affecting a single curses call, and suppressing an error + condition newly introduced in recent versions of the library. The test + plan covers ensuring that the failure is manifest, and fixed by the + proposed change. + + To the best of my knowledge, the bulkrename command is the only one in + ranger that calls execute_file (part of the affected path) *twice* in + its operation and, thus, is the only affected command. However, the plan + includes testing another command using this path (open_with) to ensure + commands calling this *once* are unaffected. + + The package has no reverse dependencies. + + [ Original Description ] + As noted in [1] the ncurses version in Ubuntu noble (and presumably oracular, though I haven't checked this yet) breaks the (extremely useful) bulkrename command. The proposed fix in [2] works, but reading the associated thread [3] indicates it's possible that ranger is incorrectly calling curses.endwin() multiple times. That said, having read through the code I can't see where ranger *is* calling endwin() multiple times [4], and the purpose of the function that's failing (ui.suspend) is clearly to disable curses while an external application that wants the display (e.g. vim) is executed, so there's no harm in simply ignoring an error from curses.endwin(). [1]: https://github.com/ranger/ranger/issues/2934 [2]: https://github.com/ranger/ranger/pull/2935 [3]: https://www.mail-archive.com/debian-bugs- d...@lists.debian.org/msg1944374.html [4]: bulkrename executes the external editor twice and it's the *second* invocation that leads to the failure, which is presumably where endwin is being called twice, but ui.initialize (which sets up curses all over again) *is* being called between the two invocations ... which should be valid? ** Changed in: ranger (Ubuntu) Status: New => Triaged ** Changed in: ranger (Ubuntu Noble) Status: New => Triaged ** Changed in: ranger (Ubuntu Oracular) Status: New => Triaged ** Changed in: ranger (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: ranger (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: ranger (Ubuntu Oracular) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: ranger (Ubuntu) Importance: Undecided => Medium ** Changed in: ranger (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: ranger (Ubuntu Oracular) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2086744 Title: [SRU] bulkrename fails with newer curses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ranger/+bug/2086744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2086744] Re: [SRU] bulkrename fails with newer curses
** Description changed: As noted in [1] the ncurses version in Ubuntu noble (and presumably oracular, though I haven't checked this yet) breaks the (extremely useful) bulkrename command. The proposed fix in [2] works, but reading the associated thread [3] indicates it's possible that ranger is incorrectly calling curses.endwin() multiple times. That said, having read through the code I can't see where ranger *is* - calling endwin() multiple times, and the purpose of the function that's - failing (ui.suspend) is clearly to disable curses while an external - application that wants the display (e.g. vim) is executed, so there's no - harm in simply ignoring an error from curses.endwin(). + calling endwin() multiple times [4], and the purpose of the function + that's failing (ui.suspend) is clearly to disable curses while an + external application that wants the display (e.g. vim) is executed, so + there's no harm in simply ignoring an error from curses.endwin(). [1]: https://github.com/ranger/ranger/issues/2934 [2]: https://github.com/ranger/ranger/pull/2935 [3]: https://www.mail-archive.com/debian-bugs- d...@lists.debian.org/msg1944374.html + + [4]: bulkrename executes the external editor twice and it's the *second* + invocation that leads to the failure, which is presumably where endwin + is being called twice, but ui.initialize (which sets up curses all over + again) *is* being called between the two invocations ... which should be + valid? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2086744 Title: [SRU] bulkrename fails with newer curses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ranger/+bug/2086744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2086744] [NEW] [SRU] bulkrename fails with newer curses
Public bug reported: As noted in [1] the ncurses version in Ubuntu noble (and presumably oracular, though I haven't checked this yet) breaks the (extremely useful) bulkrename command. The proposed fix in [2] works, but reading the associated thread [3] indicates it's possible that ranger is incorrectly calling curses.endwin() multiple times. That said, having read through the code I can't see where ranger *is* calling endwin() multiple times [4], and the purpose of the function that's failing (ui.suspend) is clearly to disable curses while an external application that wants the display (e.g. vim) is executed, so there's no harm in simply ignoring an error from curses.endwin(). [1]: https://github.com/ranger/ranger/issues/2934 [2]: https://github.com/ranger/ranger/pull/2935 [3]: https://www.mail-archive.com/debian-bugs- d...@lists.debian.org/msg1944374.html [4]: bulkrename executes the external editor twice and it's the *second* invocation that leads to the failure, which is presumably where endwin is being called twice, but ui.initialize (which sets up curses all over again) *is* being called between the two invocations ... which should be valid? ** Affects: ranger (Ubuntu) Importance: Undecided Status: New ** Affects: ranger (Ubuntu Noble) Importance: Undecided Status: New ** Affects: ranger (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: ranger (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ranger (Ubuntu Oracular) Importance: Undecided Status: New ** Summary changed: - bulkrename fails with newer curses + [SRU] bulkrename fails with newer curses -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2086744 Title: [SRU] bulkrename fails with newer curses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ranger/+bug/2086744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912075] Re: Ranger fails to start due to screen dependency
This appears to work in focal, jammy, and noble. Marking fix released. ** Changed in: ranger (Ubuntu) Status: Confirmed => 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/1912075 Title: Ranger fails to start due to screen dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ranger/+bug/1912075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2032178] Re: Update to 20240926 version
** Changed in: rpiboot (Ubuntu) Milestone: None => ubuntu-25.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2032178 Title: Update to 20240926 version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpiboot/+bug/2032178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2085903] Re: Please merge rpi-eeprom 26
** Changed in: rpi-eeprom (Ubuntu) Milestone: None => ubuntu-25.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2085903 Title: Please merge rpi-eeprom 26 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpi-eeprom/+bug/2085903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2085903] Re: Please merge rpi-eeprom 26
Targetting to noble and oracular to support back-port of rpiboot ** Also affects: rpi-eeprom (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: rpi-eeprom (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: rpi-eeprom (Ubuntu Noble) Status: New => Triaged ** Changed in: rpi-eeprom (Ubuntu Oracular) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2085903 Title: Please merge rpi-eeprom 26 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpi-eeprom/+bug/2085903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2032178] Re: Update to 20240926 version
** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2032178 Title: Update to 20240926 version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpiboot/+bug/2032178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2085903] Re: Please merge rpi-eeprom 26
** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2085903 Title: Please merge rpi-eeprom 26 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpi-eeprom/+bug/2085903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2085903] [NEW] Please merge rpi-eeprom 26
Public bug reported: This is required to support LP: #2032178 (merge current rpiboot) ** Affects: rpi-eeprom (Ubuntu) Importance: High Assignee: Dave Jones (waveform) Status: Triaged ** Changed in: rpi-eeprom (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: rpi-eeprom (Ubuntu) Status: New => Triaged ** Changed in: rpi-eeprom (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/2085903 Title: Please merge rpi-eeprom 26 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpi-eeprom/+bug/2085903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2032178] Re: Update to 20240926 version
** Summary changed: - Update to 20221225 version + Update to 20240926 version ** Changed in: rpiboot (Ubuntu) Importance: Undecided => High ** Description changed: - Please update to the new upstream version 20221225 + Please update to the new upstream version 20221225. This is now required + for 2712 support. ** Description changed: Please update to the new upstream version 20221225. This is now required - for 2712 support. + for 2712 support, and requires backport to oracular and noble. ** Also affects: rpiboot (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: rpiboot (Ubuntu Oracular) Importance: Undecided Status: New ** Changed in: rpiboot (Ubuntu Noble) Status: New => Triaged ** Changed in: rpiboot (Ubuntu Oracular) Status: New => Triaged ** Changed in: rpiboot (Ubuntu Oracular) Importance: Undecided => High ** Changed in: rpiboot (Ubuntu Noble) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: rpiboot (Ubuntu Oracular) 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/2032178 Title: Update to 20240926 version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpiboot/+bug/2032178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039278] Re: Consistent naming of onboard NIC on all Pi on all Ubuntu
Oh, I actually did this back in ... erm ... mantic maybe (the git blame isn't here because ubuntu-raspi-settings got split out as a separate source package in noble, but this change was definitely before then): https://git.launchpad.net/ubuntu/+source/ubuntu-raspi- settings/tree/10-raspi-eth0.link Anyway, will close as fix released ** Changed in: ubuntu-raspi-settings (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039278 Title: Consistent naming of onboard NIC on all Pi on all Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2039278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2085700] Re: linux-image-5.15.0-1064-raspi package post-installation returned error
> On my amd64 PC, I typically use ext4 for all partitions. > However, I'm not very knowledgeable about ARM architecture. At least in this respect there's no difference: the same partitioning scheme (MBR / GPT) is used on both PCs and Pis, and the same file- systems (FAT, ext4, etc.) within them. > So I trust the partitioning scheme used by the Raspberry Pi Imager. > (I don't remember the specific version of Imager tool I used) It's not the rpi-imager that does the partitioning on the destination media, but the image it's flashing. The imager (more or less) blindly writes all the bytes of the source image to the target media; if there happen to be partitions it doesn't really notice (unless it's doing post-write customization of the boot partition, but that doesn't modify the partitions, just the content of some text files). In the case of the Ubuntu images, we've always defined two partitions on our images: * A small FAT32 partition which mounts at /boot/firmware and... * A large ext4 partition which mounts at / The fact you've got a FAT32 partition mounted at /boot suggests this may be one of the unofficial flavours. I think Ubuntu MATE used that layout? I may be wrong about that though. Do you happen to remember (roughly) which image you flashed to the card? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2085700 Title: linux-image-5.15.0-1064-raspi package post-installation returned error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2085700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2085700] Re: linux-image-5.15.0-1064-raspi package post-installation returned error
I'm not sure this is rpi-imager either. Why is your /boot directory formatted FAT32? Could you attach your "/etc/fstab" file and "/proc/mounts"? The /boot directory should, on our Ubuntu for Raspberry Pi images, be a normal directory under the (ext4) root partition. Under there, /boot/firmware should be the mount of the *actual* boot partition which is FAT32. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2085700 Title: linux-image-5.15.0-1064-raspi package post-installation returned error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2085700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075176] Re: lxd cannot launch (useable) oracular container under focal's kernel
Marked fix released upstream; mirroring here ** Changed in: lxd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075176 Title: lxd cannot launch (useable) oracular container under focal's kernel To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/2075176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075176] Re: lxd cannot launch (useable) oracular container under focal's kernel
** Bug watch added: github.com/canonical/lxd/issues #13844 https://github.com/canonical/lxd/issues/13844 ** Also affects: lxd via https://github.com/canonical/lxd/issues/13844 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075176 Title: lxd cannot launch (useable) oracular container under focal's kernel To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/2075176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083732] Re: kodi and kodi.bin still in memory after closing the app
I've certainly seen Kodi hang around for quite a while after quitting (or even take ages to quit in the first place). However, I've also observed that previously on jammy (I'm fairly sure this isn't new to noble) and, tellingly, if I rename ~/.kodi to reset it to a "base" state with no addons, it always quits (fairly) promptly. Hence I've generally put this down to "some addon I've installed being tardy". If this can be reproduced with the base install (with the default addons) then it's a valid bug for the kodi package. If it's down to a specific addon which isn't part of the base install, then it's best filed with that addon's repository (if possible). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083732 Title: kodi and kodi.bin still in memory after closing the app To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/2083732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079914] Re: [SRU] kodi dies with "PyImport_AppendInittab() may not be called after Py_Initialize()"
Looks like the discussion around shutdown-time should probably continue in LP: #2083732 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079914 Title: [SRU] kodi dies with "PyImport_AppendInittab() may not be called after Py_Initialize()" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/2079914/+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)
** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/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 2083258] Re: [SRU] xdg-dbus-proxy memory leak
With regard to Qwerty's request for an SRU to focal and jammy -- that may well be warranted, but I'd like to land the noble SRU first, and have some confidence that this actually resolves the issue from users affected by it. If it does, I'll be happy to target further series. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083258 Title: [SRU] xdg-dbus-proxy memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-dbus-proxy/+bug/2083258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805417] Re: kodi sports an ugly 'KODI from debian' logo
The reason for this is given in the following blog post: https://balintreczey.hu/blog/introducing-xbmc-from-debian/ (back from when Kodi was XBMC). To quote the relevant section: """ XBMC depends on many libraries and the changes to them in Debian used to break one or another XBMC use case. The XBMC project received many direct bug reports from users of the Debian-shipped XBMC package which were harder than necessary to handle due to the lack of clear differentiation from the .deb packages provided directly by them and using the embedded libraries. To help both users and developers the xbmc package starts using the “XBMC from Debian” name on the main screen and in the logs, the version number used inside the application is set to the Debian package’s version, and README.Debian directs users of the package to Debian’s BTS instead of XBMC’s forums. """ As Ubuntu's version is directly synced from the Debian one, it seems reasonable to keep the naming, to encourage users to report bugs in the appropriate location (i.e. not Kodi's upstream forums, but the relevant distro bug-tracker). If the logo is undesirable, there's a multitude of skins available which won't show it. ** Changed in: kodi (Ubuntu) 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/1805417 Title: kodi sports an ugly 'KODI from debian' logo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1805417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079914] Re: [SRU] kodi dies with "PyImport_AppendInittab() may not be called after Py_Initialize()"
Verification done on Ubuntu 24.04.1. Crash observed with release version, and not observed with version from proposed. Video playback working happily as per test plan. ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079914 Title: [SRU] kodi dies with "PyImport_AppendInittab() may not be called after Py_Initialize()" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/2079914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2082072] Re: No support for Pi 2712D0 stepping
Verification performed according to test plan on D0 and C1 stepping of Pi 5, and older 8GB model of Pi 4. Proposed version operated correctly on all boards. ** 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/2082072 Title: No support for Pi 2712D0 stepping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2082072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2011536] Re: [SRU] Add FK_FORCE_EFI environment variable to skip EFI check
Setting devel to fix released as 3.107 was merged; made one minor change for sponsorship to add the bug number to d/changelog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2011536 Title: [SRU] Add FK_FORCE_EFI environment variable to skip EFI check To manage notifications about this bug go to: https://bugs.launchpad.net/flash-kernel/+bug/2011536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2011536] Re: [SRU] Add FK_FORCE_EFI environment variable to skip EFI check
This looks reasonable (patch matches the change that was made for 3.107), and the SRU template is well filled out. I'll sponsor this shortly. ** Changed in: flash-kernel (Ubuntu) Status: New => Fix Released ** Changed in: flash-kernel (Ubuntu Jammy) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2011536 Title: [SRU] Add FK_FORCE_EFI environment variable to skip EFI check To manage notifications about this bug go to: https://bugs.launchpad.net/flash-kernel/+bug/2011536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2082072] Re: No support for Pi 2712D0 stepping
@racb yes, that's correct -- I forgot to update the title! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2082072 Title: No support for Pi 2712D0 stepping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2082072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2082072] Re: [SRU] Mesa bump to 24.2 required for Pi 2712D0 stepping
@tjaalton -- I think I put this on MM already, but just adding a confirmation here that the staging build in your PPA does indeed fix the mesa issue on the D0. Is there any possibility this is going to make it into noble (and the mesa content snap) before oracular's release? The reason I ask is that, if not then those with D0 stepping Pi 5's (currently only the the 2GB model, but in the coming months it'll cover more models) will be able to login to their desktop (because oracular's mesa is already sufficiently recent), but will find firefox and snap- store won't run (because the snap's mesa is based on noble). If the fix is published *after* oracular's release, then a simple "sudo snap refresh" will fix things for these users. However, I can imagine a scenario where a user needs access to a web-browser to get internet access in the first place (captive portals and such), so it would be preferable if we could include the fix in the release media itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2082072 Title: [SRU] Mesa bump to 24.2 required for Pi 2712D0 stepping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2082072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072534] Re: Kodi crashes immediately when starting to play AV1 on Ubuntu 24.04 noble
No problem -- I've got an SRU ongoing for kodi anyway, so I figured I may as well try and kill two bugs with one stone as it were. Still, it seems you're running into "something else" but without a way to reproduce it here I'm afraid there's not much else I can do. I'll leave this open, though, just in case anyone can shed some more light here! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072534 Title: Kodi crashes immediately when starting to play AV1 on Ubuntu 24.04 noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/2072534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083258] Re: [SRU] xdg-dbus-proxy memory leak
** Description changed: + [ Impact ] + + All the usual issues of memory leaks for long running processes, up to + and including system sluggishness and eventually crashes. + + [ Test Plan ] + + * Using an affected application, e.g. mission-center installed via flat-pak, leave application running for 24 hours and check memory usage + * Enable proposed (https://wiki.ubuntu.com/Testing/EnableProposed) + * sudo apt install -t noble-proposed xdg-dbus-proxy + * sudo reboot + * Run affected application for the same length of time (e.g. 24 hours), observe significantly lower memory usage + + [ Regression Potential ] + + Relatively low. The patch itself is minimal, and is now incorporated in + an upstream (https://github.com/flatpak/xdg-dbus-proxy/pull/58), which + is present in oracular. Please note only the first patch from that PR is + included; the second patch is rather more involved, and it's not clear + that we need it to resolve the issue. + + That said, xdg-dbus-proxy is used by plenty of applications, and it's + very tricky to diagnose whether a memory leak is *actually* fixed, + particularly when not all applications display it, the leak can take a + long time to become particularly noticeable, or the leak is affected by + differing patterns of usage. To guard against this, the test plan + targets an application known to be affected, and requests a particularly + long runtime to make the leak more obvious to detect. + + [ Original Description ] + Reported via IRC and comments on mission-center's GitLab [1]: for users of flatpak installs, xdg-dbus-proxy is leaking memory (causing particular issues for long running processes). The root cause appears to be leaked GVariant references, ultimately fixed in 0.1.6 [2] now available in oracular. However, this still affects the release version on noble, and is likely suitable for SRU. Patch to be prepared... [1]: https://gitlab.com/mission-center-devs/mission-center/-/issues/61#note_1584564638 [2]: https://github.com/flatpak/xdg-dbus-proxy/issues/51#issuecomment-2020464257 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083258 Title: [SRU] xdg-dbus-proxy memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-dbus-proxy/+bug/2083258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083258] Re: xdg-dbus-proxy memory leak
Test builds available in ppa:waveform/xdg-dbus-proxy (https://launchpad.net/~waveform/+archive/ubuntu/xdg-dbus-proxy) ** Summary changed: - xdg-dbus-proxy memory leak + [SRU] xdg-dbus-proxy memory leak -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083258 Title: [SRU] xdg-dbus-proxy memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-dbus-proxy/+bug/2083258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083258] Re: xdg-dbus-proxy memory leak
** Patch added: "lp2083258-1.debdiff" https://bugs.launchpad.net/ubuntu/+source/xdg-dbus-proxy/+bug/2083258/+attachment/5823494/+files/lp2083258-1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083258 Title: [SRU] xdg-dbus-proxy memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-dbus-proxy/+bug/2083258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083258] [NEW] xdg-dbus-proxy memory leak
Public bug reported: Reported via IRC and comments on mission-center's GitLab [1]: for users of flatpak installs, xdg-dbus-proxy is leaking memory (causing particular issues for long running processes). The root cause appears to be leaked GVariant references, ultimately fixed in 0.1.6 [2] now available in oracular. However, this still affects the release version on noble, and is likely suitable for SRU. Patch to be prepared... [1]: https://gitlab.com/mission-center-devs/mission-center/-/issues/61#note_1584564638 [2]: https://github.com/flatpak/xdg-dbus-proxy/issues/51#issuecomment-2020464257 ** Affects: xdg-dbus-proxy (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: xdg-dbus-proxy (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: xdg-dbus-proxy (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: xdg-dbus-proxy (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083258 Title: xdg-dbus-proxy memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-dbus-proxy/+bug/2083258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078638] Re: coredumps with Xymon on 24.04
This is a bit of a tricky one. With regard to the first patch (fortify2.patch), while it's expedient, I really don't like the idea of just turning down the FORTIFY_SOURCE option, so I'm afraid I can't sponsor that one. For the second patch (100_md5_bufferoverflow.patch), this looks much more promising, thank you! The change certainly looks sane and I could easily see how the existing code would potentially lead to buffer overrun. One thing that does concern me is that upstream have apparently had a good tidy-up of their buffer handling code (https://sourceforge.net/p/xymon/code/8123/), but that this change doesn't appear there. To be fair, most of their changes seem either mechanical (ensuring buffer termination after certain operations) or cosmetic, while this proposed change is neither. Still, we generally prefer patches are forwarded upstream so we don't have to maintain them as an Ubuntu delta long term. Could Roland forward the patch upstream? (I note Roland is one of the Debian maintainers of the package, so presumably it doesn't need forwarding to himself there :) Next steps: 1. I'll target this bug to noble and jammy (and oracular implicitly). Although jammy doesn't *appear* affected here, it presumably *is* but it's not noticing the buffer overrun because FORTIFY_SOURCE is lower there. 2. Because we don't appear certain that this patch is indeed the root cause, I'm going to prep a PPA (ppa:waveform/xymon) with builds for oracular, noble, and jammy, containing the second patch here (100_md5_bufferoverflow.patch). Could I ask those interested to try the following and report back if it appears to fix things? ** Also affects: xymon (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: xymon (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: xymon (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/2078638 Title: coredumps with Xymon on 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/2078638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071563] Re: [SRU - Noble] Backport crash fix
Thanks for this! Patch matches the upstream commit, looks reasonable,
and SRU template is well filled out. I'm going to make a couple of minor
tweaks to it just to ease things along a bit. Firstly I know the SRU
team don't like to read "None" in the regression potential. Even in
cases like this where the application doesn't even start (and you might
be tempted to ask, "how much further do you want it to regress ...
catching fire?!"), if there's anything that depends on the application
(e.g. that load modules from it) then it can potentially be broken by
changes. Secondly, I'm going to include explicit commands in the test
plan (so that people unfamiliar with the application can still perform
verification if need be).
After that I'll sponsor, because other than those nitpicks, this looks
good.
** Description changed:
[ Impact ]
CHIRP contains a regression that causes it to crash on launch when no
existing config file is found (e.g. clear installation).
The regression is an oversight in the refactoring of the recent file
handling. It results in the CHIRP application being completely unusable,
crashing every time immediately after startup and there is no easy
workaround available.
[ Test Plan ]
- This fix has already been tested and is implemented in newer CHIRP release
that is already present in Ubuntu Oracular. However, it was not fixed before
FeatureFreeze, and was not available in Debian until post-Noble release.
+ On an installation of noble:
+
+ * sudo apt install chirp
+ * chirpw
+ * Observe failure with the back-trace present in the original description
below
+ * Enable proposed (https://wiki.ubuntu.com/Testing/EnableProposed)
+ * sudo apt install -t noble-proposed chirp
+ * chirpw
+ * Observe application starts successfully
The fix has already been tested manually by others, but as soon as a
version with the patch present is available, a user should install the
updated chirp package and the program should launch without any crashes.
[ Regression Potential ]
- None. The fix simply adds one line of code with an if conditional to remove
the "state" section only if it exists, thus fixing the "No section: 'state'"
error.
+ Very low. The application already fails to start "out of the box" and hence
can't regress much further, and there's only a single reverse-recommends (from
hamradio-rigcontrol) on the package.
+
+ The fix is directly from upstream, already present in Ubuntu Oracular,
+ and minimal, adding one line of code with an if conditional to remove
+ the "state" section only if it exists, thus fixing the "No section:
+ 'state'" error.
[ Where problems could occur ]
The only change is in the one line of code that handles "cleaning of
higher-order entries if they exist" and was previously attempting to remove
them even if they did not exist, resulting in a fatal error.
[ Other Info ]
It has been fixed as a part of the new CHIRP version from the Debian package
20240413-1 which has been synced to Oracular.
Here is the upstream commit that needs to be added as a patch to the
Noble SRU:
https://github.com/kk7ds/chirp/commit/088196b94ffad44acc7ca9b37a1ba67b815e
[ Original Bug Description ]
Chirp (1:20240224-1) on Ubuntu 24.04 LTS crashes on startup with:
Traceback (most recent call last):
File "/usr/bin/chirpw", line 33, in
sys.exit(load_entry_point('chirp==20240224', 'console_scripts',
'chirpw')())
^^
File "/usr/lib/python3/dist-packages/chirp/wxui/__init__.py", line 178, in
chirpmain
mainwindow = main.ChirpMain(None, title='CHIRP')
^^^
File "/usr/lib/python3/dist-packages/chirp/wxui/main.py", line 415, in
__init__
self.SetMenuBar(self.make_menubar())
^^^
File "/usr/lib/python3/dist-packages/chirp/wxui/main.py", line 656, in
make_menubar
self.adj_menu_open_recent(None)
File "/usr/lib/python3/dist-packages/chirp/wxui/main.py", line 1025, in
adj_menu_open_recent
CONF.remove_option('recent%i' % i, 'state')
File "/usr/lib/python3/dist-packages/chirp/wxui/config.py", line 160, in
remove_option
self._config.remove_option(section, key)
File "/usr/lib/python3/dist-packages/chirp/wxui/config.py", line 64, in
remove_option
self.__config.remove_option(section, key)
File "/usr/lib/python3.12/configparser.py", line 924, in remove_option
raise NoSectionError(section) from None
configparser.NoSectionError: No section: 'state'
This is fixed in the latest version from Oracular (1:20240413-1). In
Noble, it is possible to fix it by applying the following simple patch:
https://github.com/kk7ds/chirp/commit/088196b94ffad44acc7ca9b37a1ba67b815e
(Line 1025 instead of 1041 in chirp 20240224-1.)
--
You received this bug notification because you are a member of Ubun
[Bug 2071563] Re: [SRU - Noble] Backport crash fix
** Also affects: chirp (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: chirp (Ubuntu) Status: New => Fix Released ** Changed in: chirp (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/2071563 Title: [SRU - Noble] Backport crash fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chirp/+bug/2071563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053147] Re: CONFIG_EFI_STUB support disabled since 6.5.0-1002.2
I've no specific objection to enabling EFI in the kernel, provided it's clear there's no support from Ubuntu for boot issues in such a configuration. On the subject of security though, I'll defer to those with considerably more experience than myself. Even if we don't use the EFI facilities in our own boot chain, this does presumably increase our attack surface still. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053147 Title: CONFIG_EFI_STUB support disabled since 6.5.0-1002.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2053147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685918] Re: Change font dependency to recommends
Just going through tidying up some old bugs -- looks like this was fixed up in Debian and the changes are in Ubuntu (in noble, the fonts of kodi- data are all in recommends). I'll set Xenial to won't fix since it's out of support, and the devel component to fix released as that appears to be the case. ** Changed in: kodi (Ubuntu Xenial) Status: Triaged => Won't Fix ** Changed in: kodi (Ubuntu) Status: Confirmed => 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/1685918 Title: Change font dependency to recommends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1685918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072534] Re: Kodi crashes immediately when starting to play AV1 on Ubuntu 24.04 noble
Okay, I can't replicate the issue here but that may simply be differing hardware, especially when it comes to video playback. I've uploaded a build to ppa:waveform/kodi (https://launchpad.net/~waveform/+archive/ubuntu/kodi) with the linked patch applied to it. If the original poster is still interested, please wait for the 2:20.5+dfsg-1ubuntu2~ppa1 build to finish, then try the following: * Shut down kodi if it's running * sudo add-apt-repository ppa:waveform/kodi * sudo apt upgrade * Run kodi and try playing AV1 file mentioned in the linked report If that patch fixes it for you, please let me know and I'll see if I can add it to an SRU. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072534 Title: Kodi crashes immediately when starting to play AV1 on Ubuntu 24.04 noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/2072534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072534] Re: Kodi crashes immediately when starting to play AV1 on Ubuntu 24.04 noble
I don't think this is the Python 3.12 issue (which is being tracked in LP: #2079914); the backtrace on the github bug linked doesn't have PyImport anywhere in it. Let me see if I can reproduce the issue on my hardware... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072534 Title: Kodi crashes immediately when starting to play AV1 on Ubuntu 24.04 noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/2072534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079914] Re: [SRU] kodi dies with "PyImport_AppendInittab() may not be called after Py_Initialize()"
Okay, SRU template is now filled out and I've just uploaded the fix to the archive. Please be aware this does *not* mean it is generally available yet. We need to wait for the SRU team to accept the upload and request verification, which may happen sometime next week. After verification is performed, that needs to be accepted, so there's a bit of a wait yet. If you're seeing any error *other* than PyImport_AppendInittab, it's a different bug. Please file that separately. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079914 Title: [SRU] kodi dies with "PyImport_AppendInittab() may not be called after Py_Initialize()" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/2079914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765597] Re: There was a crash while using Kodi
Just going through old bug reports to try and clean things up on kodi a bit; is this still occurring with the current version on noble? ** Changed in: kodi (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765597 Title: There was a crash while using Kodi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1765597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917915] Re: FTBFS on armhf and arm64 in hirsute
Closing as won't fix as impish and hirsute are both out of support at this point. There is currently another issue with kodi on noble (LP: #2079914) which I'm in the process of fixing, but that *should* get kodi working on noble, on the raspberry pi (at least it's work for me with that fix in place, in ppa:waveform/kodi). ** Changed in: kodi (Ubuntu) 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/1917915 Title: FTBFS on armhf and arm64 in hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1917915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079914] Re: [SRU] kodi dies with "PyImport_AppendInittab() may not be called after Py_Initialize()"
** Description changed: [ Impact ] Kodi users are unable to use Python-based extensions under the version currently provided by noble. Attempting to add any results in the program crashing. [ Test Plan ] On a freshly installed, fully upgraded noble desktop installation: * sudo apt install kodi * Run kodi from command line * Select the gear-shaped settings icon * Select Add-ons / Install from repository / Look and feel / Skin * Select a skin with Python dependencies, e.g. eminence * Select Install then OK * Once installed, select Yes on the prompt to change skin * Observe crash, with "Fatal Python error: PyImport_AppendInittab..." reported on the console To demonstrate proposed version fixes the issue: * Enable proposed (https://wiki.ubuntu.com/Testing/EnableProposed) * sudo apt install -t noble-proposed kodi - * rm -rf ~/.kodi # to reset changes we made above + * mv ~/.kodi ~/.kodi.bak # to reset changes we made above * Repeat procedure above, observing no crash in the final step * Exit kodi normally To guard against regression: * cd ~/Videos * Grab a suitable video file, e.g. wget https://archive.org/download/Secret_Life_Of_Machines_102/Secret_Life_Of_Machines_102_The_Sewing_Machine.mp4 * Run kodi from command line (ensure new skin is still in use) * Select Videos / Files / Add videos... * Select Browse / Home folder/ Videos * Select OK, then OK again * Select the newly added Videos folder * Play the downloaded MP4 * Ensure playback operation works normally + + After verification: if you had any kodi settings (plugins, etc.) they + will have been reset by the procedure above (specifically, the movement + of the .kodi directory). This can be reset with: + + * rm -rf ~/.kodi + * mv ~/.kodi.bak ~/.kodi [ Regression Potential ] The patch applied is minimal, directly from the upstream repository, and already incorporated in the latest version present in oracular. The test plan attached should demonstrate that a genuine issue is being solved, and that base functionality is not affected adversely. [ Original Description ] Please update to Version: 2:20.5+dfsg-3 as mentioned here: https://bugs- devel.debian.org/cgi-bin/bugreport.cgi?bug=1074440 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: kodi 2:20.5+dfsg-1build2 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Sep 8 12:07:42 2024 InstallationDate: Installed on 2019-04-03 (1985 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: kodi UpgradeStatus: Upgraded to noble on 2024-09-01 (7 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-07-22T17:59:07 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079914 Title: [SRU] kodi dies with "PyImport_AppendInittab() may not be called after Py_Initialize()" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/2079914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079914] Re: [SRU] kodi dies with "PyImport_AppendInittab() may not be called after Py_Initialize()"
Decided to go with the minimal patch in the end. I've no (trivial) means of producing a test case for the pcre fixup also included, and equally no desire to go back and forth with the team on this, so I've prepped a minimal patch in ppa:waveform/kodi. If this builds and tests happily, I'll upload and we'll see what the SRU team make of it. ** Description changed: + [ Impact ] + + Kodi users are unable to use Python-based extensions under the version + currently provided by noble. Attempting to add any results in the + program crashing. + + [ Test Plan ] + + On a freshly installed, fully upgraded noble desktop installation: + + * sudo apt install kodi + * Run kodi from command line + * Select the gear-shaped settings icon + * Select Add-ons / Install from repository / Look and feel / Skin + * Select a skin with Python dependencies, e.g. eminence + * Select Install then OK + * Once installed, select Yes on the prompt to change skin + * Observe crash, with "Fatal Python error: PyImport_AppendInittab..." reported on the console + + To demonstrate proposed version fixes the issue: + + * Enable proposed (https://wiki.ubuntu.com/Testing/EnableProposed) + * sudo apt install -t noble-proposed kodi + * rm -rf ~/.kodi # to reset changes we made above + * Repeat procedure above, observing no crash in the final step + * Exit kodi normally + + To guard against regression: + + * cd ~/Videos + * Grab a suitable video file, e.g. wget https://archive.org/download/Secret_Life_Of_Machines_102/Secret_Life_Of_Machines_102_The_Sewing_Machine.mp4 + * Run kodi from command line (ensure new skin is still in use) + * Select Videos / Files / Add videos... + * Select Browse / Home folder/ Videos + * Select OK, then OK again + * Select the newly added Videos folder + * Play the downloaded MP4 + * Ensure playback operation works normally + + [ Regression Potential ] + + The patch applied is minimal, directly from the upstream repository, and + already incorporated in the latest version present in oracular. The test + plan attached should demonstrate that a genuine issue is being solved, + and that base functionality is not affected adversely. + + [ Original Description ] + Please update to Version: 2:20.5+dfsg-3 as mentioned here: https://bugs- devel.debian.org/cgi-bin/bugreport.cgi?bug=1074440 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: kodi 2:20.5+dfsg-1build2 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Sep 8 12:07:42 2024 InstallationDate: Installed on 2019-04-03 (1985 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: kodi UpgradeStatus: Upgraded to noble on 2024-09-01 (7 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-07-22T17:59:07 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079914 Title: [SRU] kodi dies with "PyImport_AppendInittab() may not be called after Py_Initialize()" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/2079914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079914] Re: [SRU] kodi dies with "PyImport_AppendInittab() may not be called after Py_Initialize()"
** Summary changed: - kodi dies with "PyImport_AppendInittab() may not be called after Py_Initialize()" + [SRU] kodi dies with "PyImport_AppendInittab() may not be called after Py_Initialize()" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079914 Title: [SRU] kodi dies with "PyImport_AppendInittab() may not be called after Py_Initialize()" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/2079914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070443] Re: SRU: Fix critical regression in Mercurial 6.7.x < 6.7.4
Looks good enough to me, thank you! I've replicated the verification here just for completeness sake, but hopefully this should be good enough for SRU team to approve during the next review. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070443 Title: SRU: Fix critical regression in Mercurial 6.7.x < 6.7.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/2070443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079914] Re: kodi dies with "PyImport_AppendInittab() may not be called after Py_Initialize()"
It is not fixed on noble yet -- I've merely marked that the bug does not affect the development series (oracular), but is confirmed on noble. The next step is for someone to come up with the minimal patch set and convert this to an SRU (stable release update) bug. I'll try and have a look at this at the weekend. The original report suggests we can just update to the Debian -3 release but unfortunately that seems to have been pulled due to bad merge. There is -4 release which does incorporate this fix but also includes another fix too (pcre2 use after free). If I want to include that in the same upload, I'll need to come up with a test case demonstrating the initial failure for that bug too. Or I could just cherry pick the fix for PyImport, but I don't like the thought of leaving a known buffer use after free just lying around. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079914 Title: kodi dies with "PyImport_AppendInittab() may not be called after Py_Initialize()" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/2079914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054092] Re: [SRU] Add support for FIT images to rpi config
That indeed only applied to the abandoned Core 24 case, so no issues there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054092 Title: [SRU] Add support for FIT images to rpi config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2054092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2082072] Re: [SRU] Mesa bump to 24.2 required for Pi 2712D0 stepping
** Description changed: + [ Impact ] + + Pi 5 owners with the D0 stepping will find the noble (24.04) desktop + doesn't work at all, including login. While oracular desktop users have + a sufficiently up to date mesa, all snaps relying on noble's mesa + (firefox, thunderbird, and the snap-store -- all seeded and thus + "essential" applications) do not work either on the D0 stepping. + + [ Test Plan ] + + Given the patches proposed only affect the v3d driver, which is only + used on the Pi 4 and Pi 5 hardware, the test plan can reasonably be + restricted to boards of this type. + + * Flash a 24.04.1 Pi desktop image to a fresh card + * Boot card on a D0-stepping Pi 5 (e.g. 2GB board) + * Verify that mesa fails to even display the initial setup + * Shutdown + * Boot card on a pre-D0-stepping board + * Run through initial setup + * Enable proposed (https://wiki.ubuntu.com/Testing/EnableProposed) + * Upgrade mesa to proposed version + * Reboot + * Ensure login and desktop works properly on the pre-D0 board + * Test applications; ignore snapped applications until the mesa content snap is updated -- test deb-packaged applications, including video players + * Shutdown + + For all Pi 4 and Pi 5 boards including a D0-stepping board (e.g. Pi 5 + 2GB), using the upgraded card: + + * Boot card on board + * Ensure login and desktop works properly on the D0 board + * Test applications; ignore snapped applications until the mesa content snap is updated -- test deb-packaged applications, including video players + + [ Regression Potential ] + + Given the changes are restricted to the v3d driver, which itself is only + used on the Pi 4 and Pi 5 boards (no other hardware uses this chipset), + we can be reasonably confident that only Pi boards are likely to be + affected. The test plan above should cover operation on all pre and + post-D0 boards, to ensure we do not regress existing operation of the + desktop. + + [ Original Description ] + The Raspberry Pi 5 2GB model now uses the D0 stepping of the 2712 SoC. Unfortunately, this is only supported from Mesa 24.2.0 (see https://docs.mesa3d.org/relnotes/24.2.0.html -- search for 2712D0). The result is corrupted or blank output for the current Ubuntu 24.04.1 Pi desktop (using Mesa 24.0.9). The forthcoming oracular desktop does work as far as login goes, but snapped applications are still relying on an older mesa, thus the software center, firefox, and thunderbird all fail to operate. Although the D0 is only on the 2GB model *currently*, it is anticipated to become common to the entire Pi 5 line up going forward, and will be present on the forthcoming CM5. Could we investigate either bumping mesa in noble, and the corresponding content snap, or finding the minimal patch-set necessary to support the D0 stepping and back-porting that? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2082072 Title: [SRU] Mesa bump to 24.2 required for Pi 2712D0 stepping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2082072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2082072] Re: [SRU] Mesa bump to 24.2 required for Pi 2712D0 stepping
** Summary changed: - Mesa bump to 24.2 required for Pi 2712D0 stepping + [SRU] Mesa bump to 24.2 required for Pi 2712D0 stepping -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2082072 Title: [SRU] Mesa bump to 24.2 required for Pi 2712D0 stepping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2082072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2082072] Re: Mesa bump to 24.2 required for Pi 2712D0 stepping
I'm informed the three commits that require backporting for D0 support are: b545e78f12b v3dv: support 2712D0 1fc846dce39 v3d: support 2712D0 7b807c3e948 broadcom/cle: fix up shader record for V3D 7.1.10 / 2712D0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2082072 Title: Mesa bump to 24.2 required for Pi 2712D0 stepping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2082072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2082072] Re: Mesa bump to 24.2 required for Pi 2712D0 stepping
My uneducated guess is that this is the source of the incompatibility: /* 2712D0 (V3D 7.1.10) has included draw index and base vertex, * shuffling all the fields in the packet. Since the versioning * framework doesn't handle revision numbers, the XML has a * different shader state record packet including the new fields * and we decide at run time which packet we need to emit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2082072 Title: Mesa bump to 24.2 required for Pi 2712D0 stepping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2082072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2082072] Re: Mesa bump to 24.2 required for Pi 2712D0 stepping
Related mesa bug: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29189 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2082072 Title: Mesa bump to 24.2 required for Pi 2712D0 stepping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2082072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2082072] [NEW] Mesa bump to 24.2 required for Pi 2712D0 stepping
Public bug reported: The Raspberry Pi 5 2GB model now uses the D0 stepping of the 2712 SoC. Unfortunately, this is only supported from Mesa 24.2.0 (see https://docs.mesa3d.org/relnotes/24.2.0.html -- search for 2712D0). The result is corrupted or blank output for the current Ubuntu 24.04.1 Pi desktop (using Mesa 24.0.9). The forthcoming oracular desktop does work as far as login goes, but snapped applications are still relying on an older mesa, thus the software center, firefox, and thunderbird all fail to operate. Although the D0 is only on the 2GB model *currently*, it is anticipated to become common to the entire Pi 5 line up going forward, and will be present on the forthcoming CM5. Could we investigate either bumping mesa in noble, and the corresponding content snap, or finding the minimal patch-set necessary to support the D0 stepping and back-porting that? ** Affects: mesa (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: mesa (Ubuntu Noble) Importance: Undecided Status: Confirmed ** Also affects: mesa (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu Noble) Status: New => Confirmed ** Changed in: mesa (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/2082072 Title: Mesa bump to 24.2 required for Pi 2712D0 stepping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2082072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081238] Re: colors inverted on qxl graphics on lubuntu installer only with qxl graphics on vm.
Well, not exactly duplicate given that's targetting the snap-store- desktop package specifically, but the symptom sounds identical, and I wonder if it's the mesa package underlying both these things (given that snap-store-desktop is packaged as a snap and is thus using the snap version of mesa which typically lags the debs). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081238 Title: colors inverted on qxl graphics on lubuntu installer only with qxl graphics on vm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2081238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081238] Re: colors inverted on qxl graphics on lubuntu installer only with qxl graphics on vm.
Possible duplicate of LP: #2076919 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081238 Title: colors inverted on qxl graphics on lubuntu installer only with qxl graphics on vm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2081238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078525] Re: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi
Ran a full do-release-upgrade cycle on the Zero 2W according to the test plan above and with noble-proposed pinned for flash-kernel, everything worked perfectly. Additional verification on noble performed on a Pi 4 8GB, Pi 400, and Zero 2W (separately from a fresh noble install as well). ** Tags removed: verification-needed-jammy verification-needed-noble ** Tags added: verification-done-jammy 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/2078525 Title: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2078525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038087] Re: [FFe] flash-kernel displays wrong "selected" DTB on various Pi models
Verified on a Pi Zero 2W and 400 running the jammy arm64 server for Pi image. Additional verification on the Zero 2W performed for LP: #2078525 (also fixed in this upload). ** Description changed: [ Impact ] flash-kernel displays a "selected" DTB at the top of its output. On a Pi this isn't actually that relevant as it goes on to copy every DTB associated with the kernel anyway, but this is still confusing for users, especially when they see a completely different board model than the one they expected (e.g. at present on the Pi 400 or Pi 5, the output will indicate that the rpi-4-b dtb is being used). [ Test Plan ] - * Boot a mantic daily image on an affected model of Pi (400, 5, CM3, CM3+, Zero 2W) + * Boot a jammy image on an affected model of Pi (400, 5, CM3, CM3+, Zero 2W) * Run "sudo flash-kernel" and confirm it outputs "Using DTB: bcm2711-rpi-4-b.dtb" at the top of its messages * Enable the -proposed pocket and "sudo apt update" * "sudo apt install flash-kernel" to update flash-kernel to the proposed version * Run "sudo flash-kernel" and confirm it outputs the correct DTB for the selected model of Pi. [ Regression Potential ] Low; the existing flash-kernel already copies all DTBs found and the proposed one will too (all Pi related entries use "Method: pi", the method isn't changing in its behaviour, the only db entries that are changing are Pi related). Thus the worst-case scenario is that flash- kernel continues to output the "wrong" DTB at the top of its output, which is no worse than the present situation. [ Original Description ] flash-kernel probably shouldn't even be dealing with the DTBs on Pi but it's picking the wrong one for some machine models. For example on a Raspberry Pi 400 Rev 1.0 it uses bcm2711-rpi-4-b.dtb. Same one Compute Module 3 and 3+. It's probably because in /usr/share/flash-kernel/db/all.db the catch-all Machine: Raspberry Pi * is listed before these above mentioned models (and others as well). ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038087 Title: [FFe] flash-kernel displays wrong "selected" DTB on various Pi models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2038087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079914] Re: kodi dies with "PyImport_AppendInittab() may not be called after Py_Initialize()"
** Also affects: kodi (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: kodi (Ubuntu Noble) Status: New => Confirmed ** Changed in: kodi (Ubuntu) Status: Confirmed => 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/2079914 Title: kodi dies with "PyImport_AppendInittab() may not be called after Py_Initialize()" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/2079914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078525] Re: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi
** Description changed: + [ Impact ] + + This is affecting upgraders from jammy to noble on the Raspberry Pi Zero + 2W. Specifically, flash-kernel is failing to find the expected dtb once + the noble version of flash-kernel is in place, causing it to fail. This + terminates the apt operation, breaking do-release-upgrade. + + [ Test Plan ] + + To be repeated on all supported models of Pi: + + * Install the -proposed version of flash-kernel + * Run "sudo flash-kernel" and ensure operation completes successfully + * On the Zero 2W specifically, ensure the *-zero-2-w.dtb or *-zero-2.dtb is reported in the first few lines of output (on the release version it will, erroneously, be the *-4-b.dtb instead) + + [ Regression Potential ] + + Minimal; the change uses a well-tested mechanism within flash-kernel to + probe for the correct dtb. Moreover, the change has already undergone + testing on all supported boards during the jammy .5 ISO tests (while + doing the server tests, I added my flash-kernel PPA and re-ran the + flash-kernel test), the oracular beta ISO tests, and random noble + testing in between. + + [ Original Description ] + package plymouth 24.004.60-1ubuntu7 failed to install/upgrade: installed plymouth package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: plymouth 24.004.60-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-1061.64-raspi 5.15.160 Uname: Linux 5.15.0-1061-raspi aarch64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: arm64 BootLog: - + CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: - + CloudSubPlatform: config-disk (/dev/mmcblk0p1) Date: Fri Aug 30 23:05:22 2024 ErrorMessage: installed plymouth package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20230807.2 Lspci: - + Lspci-vt: - + Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=dwc2/1p, 480M ProcCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:D7:09:57 vc_mem.mem_base=0x1fa0 vc_mem.mem_size=0x2000 console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash cfg80211.ieee80211_regdom=UA ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:D7:09:57 vc_mem.mem_base=0x1fa0 vc_mem.mem_size=0x2000 console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash cfg80211.ieee80211_regdom=UA Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: - dpkg 1.22.6ubuntu6.1 - apt 2.7.14build2 + dpkg 1.22.6ubuntu6.1 + apt 2.7.14build2 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Title: package plymouth 24.004.60-1ubuntu7 failed to install/upgrade: installed plymouth package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-08-30 (0 days ago) acpidump: - + mtime.conffile..etc.init.d.apport: 2024-07-22T17:59:07 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078525 Title: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2078525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077981] Re: [SRU] Add HiFive Premier P550 to database
** Changed in: flash-kernel (Ubuntu Noble) 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/2077981 Title: [SRU] Add HiFive Premier P550 to database To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2077981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081313] Re: Please merge flash-kernel 3.108 from Debian unstable
** Changed in: flash-kernel (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: flash-kernel (Ubuntu) Milestone: None => later -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081313 Title: Please merge flash-kernel 3.108 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2081313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081312] [NEW] flash-kernel producing boot.scr on oracular
Public bug reported: The oracular images no longer include u-boot on the boot partition at all. However, flash-kernel is still producing a boot.scr artefact on each run. This means we won't be able to unseed u-boot-rpi as planned, unless this operation is fixed. Remove U-Boot-Script-Name from all relevant Raspberry Pi entries in the db. ** Affects: flash-kernel (Ubuntu) Importance: High Assignee: Dave Jones (waveform) Status: Confirmed ** Tags: foundations-todo ** Changed in: flash-kernel (Ubuntu) Milestone: None => ubuntu-24.10 ** Changed in: flash-kernel (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: flash-kernel (Ubuntu) Status: New => Confirmed ** Changed in: flash-kernel (Ubuntu) Importance: Undecided => High ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081312 Title: flash-kernel producing boot.scr on oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2081312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081313] [NEW] Please merge flash-kernel 3.108 from Debian unstable
Public bug reported: Please merge flash-kernel 3.108 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. ** Affects: flash-kernel (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/2081313 Title: Please merge flash-kernel 3.108 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2081313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060693] Re: No welcome/login sound on Ubuntu desktop
** Description changed: Under the Ubuntu desktop for Raspberry Pi, for several recent releases, the startup sound from the Yaru sound theme has failed to play both at the initial setup (from oem-config, where it used to play just before language selection), and at the greeter. This worked in Jammy (22.04), but on at least mantic (23.10) and the forthcoming noble (24.04) (and possibly earlier), this has failed. It's not due to a crash in canberra-gtk-play (used to play the sound). The only hint that something has failed appears in the oem-config.log: - Failed to play sound: Not available + Failed to play sound: Not available Unfortunately there's nothing else in the log that hints at why canberra-gtk-play is failing. There are several similar bug report, but I doubt they are related given their age (e.g. LP: #1002114 relates to ubuntu 12.04 which had a very different sound stack and predates the preinstalled desktop images). + + Additional note: the desktop login sound on oracular *is* working; it's + just the oem-config sound that isn't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060693 Title: No welcome/login sound on Ubuntu desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/2060693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081287] [NEW] oem-config in oracular still display noble slides
Public bug reported: The first time setup on the Pi desktop images (run by oem-config, source package ubiquity) is still showing slides with noble's livery on them. ** 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/2081287 Title: oem-config in oracular still display noble slides To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2081287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080368] Re: Support CM5
** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080368 Title: Support CM5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpi-eeprom/+bug/2080368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081117] Re: Mercurial FTBFS with python 3.12.6
** Also affects: mercurial (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: mercurial (Ubuntu Noble) Status: New => Confirmed ** Changed in: mercurial (Ubuntu Noble) 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/2081117 Title: Mercurial FTBFS with python 3.12.6 To manage notifications about this bug go to: https://bugs.launchpad.net/hg/+bug/2081117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054092] Re: [SRU] Add support for FIT images to rpi config
Updated verification case, and verified SRU as working accordingly on a
Pi 3B and Pi 4B with the noble image specified in the test plan, and the
u-boot currently in -proposed.
** Description changed:
[ Impact ]
The current u-boot-rpi package does not include support for FIT images.
Enabling this feature has been requested by an internal team.
[ Test Plan ]
To test FIT image generation:
* Flash the Ubuntu Server for Raspberry Pi 24.04.1 image [1] to an SD card
- * Place the following content in a file named "image.its":
-
+ * Boot Ubuntu Server and login
+ * cp /boot/firmware/vmlinuz .
+ * cp /boot/firmware/initrd.img .
+ * cat << EOF > image.its
/dts-v1/;
/ {
- description = "FIT payload";
- #address-cells = <2>;
- images {
- kernel {
- description = "kernel";
- data = /incbin/("vmlinux.zst");
- type = "kernel";
- arch = "arm64";
- os = "linux";
- compression = "zstd";
- load = <0x20>;
- entry = <0x20>;
- hash {
- algo = "sha1";
- };
- };
- initrd {
- description = "initramfs";
- data = /incbin/("initrd.cpio.zst");
- type = "ramdisk";
- arch = "arm64";
- os = "linux";
- compression = "none";
- hash {
- algo = "sha1";
- };
- };
- };
- configurations {
- default = "standard";
- standard {
- description = "config";
- kernel = "kernel";
- ramdisk = "initrd";
- hash {
- algo = "sha1";
- };
- };
- };
+ description = "FIT payload";
+ #address-cells = <2>;
+ images {
+ kernel {
+ description = "kernel";
+ data = /incbin/("vmlinuz");
+ type = "kernel";
+ arch = "arm64";
+ os = "linux";
+ compression = "gzip";
+ load = <0x20>;
+ entry = <0x20>;
+ hash {
+ algo = "sha1";
+ };
+ };
+ initrd {
+ description = "initramfs";
+ data = /incbin/("initrd.img");
+ type = "ramdisk";
+ arch = "arm64";
+ os = "linux";
+ compression = "none";
+ hash {
+ algo = "sha1";
+ };
+ };
+ };
+ configurations {
+ default = "standard";
+ standard {
+ description = "config";
+ kernel = "kernel";
+ ramdisk = "initrd";
+ hash {
+ algo = "sha1";
+ };
+ };
+ };
};
-
- * Run mkimage -f image.its -T flat_dt
+ EOF
+ * Run mkimage -f image.its -T flat_dt image.fit
* Observe failure with current version
* Upgrade u-boot-rpi to version in -proposed
- * Run mkimage -f image.its -T flat_dt
- * Observe successful generation of image
+ * Run mkimage -f image.its -T flat_dt image.fit
+ * Observe successful generation of image in image.fit
- To test no regression in boot operation:
+ To test no regression in boot operation (carrying on from previous
+ instructions):
- * Flash the Ubuntu Server for Raspberry Pi 24.04.1 image [1] to an SD card
* Modify the boot sequence to include u-boot. In config.txt:
- - Set kernel=uboot_rpi_4.bin (adjust as appropriate for test board)
- - Set device_tree_address=0x0300
+ - Set kernel=uboot_rpi_4.bin (adjust as appropriate for test board)
+ - Set device_tree_address=0x0300
+ - Comment out initramfs line
+ * sudo cp image.fit /boot/firmware/
* sudo reboot
+ * Interrupt u-boot
+ * setexpr loadaddr $fdt_addr + 0x10
+ * load mmc 0:1 $loadaddr image.fit
+ * bootm :kernel :initrd $fdt_addr
* Ensure boot succeeds
[1]:
http://cdimage.ubuntu.com/releases/24.04.1/release/ubuntu-24.04.1-preinstalled-
desktop-arm64+raspi.img.xz
[ Regression Potential ]
Varied; the u-boot package hasn't been used in the classic images since
focal (and jammy upgrades includes a quirk to remove it from the boot
chain), so the impact on the server and desktop images should be nil
even if it failed entirely. However, the Core images still use u-boot so
its operation should be checked on all boards supported by Core 24
(specifically the Pi 3, 4, and 5 series) by following the second part of
the test plan above.
[ Original Description ]
Support for signed FIT images has been requested; the following config
items should be enabled for the rpi 3 and 4 configurations (in both
armhf and arm64):
CONFIG_FIT=y
CONFIG_FIT_SIGNATURE=y
CONFIG_FIT_VERBOSE=y
CONFIG_FIT_PRINT=y
CONFIG_TOOLS_FIT=y
CONFIG_TOOLS_FIT_SIGNATURE=y
CONFIG_TOOLS_FIT_VERBOSE=y
CONFIG_TOOLS_FIT_PRINT=y
CONFIG_ZSTD=y
Check this doesn't affect core
[Bug 2054092] Re: [SRU] Add support for FIT images to rpi config
I've confirmed u-boot is not used on the Core 24 images. It's still present ... it's just not used, so that's something else to clean up in the gadget. Currently working on an updated verification case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054092 Title: [SRU] Add support for FIT images to rpi config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2054092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081117] Re: Mercurial FTBFS with python 3.12.6
** Bug watch added: bz.mercurial-scm.org/ #6917 https://bz.mercurial-scm.org/show_bug.cgi?id=6917 ** Also affects: hg via https://bz.mercurial-scm.org/show_bug.cgi?id=6917 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081117 Title: Mercurial FTBFS with python 3.12.6 To manage notifications about this bug go to: https://bugs.launchpad.net/hg/+bug/2081117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081117] [NEW] Mercurial FTBFS with python 3.12.6
Public bug reported: Mercurial's patchbomb module's tests are incompatible with the email.utils changes introduced in Python 3.12.6. A trivial modification is necessary to permit the tests to pass. ** Affects: mercurial (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: Confirmed ** Changed in: mercurial (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: mercurial (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/2081117 Title: Mercurial FTBFS with python 3.12.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/2081117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081112] [NEW] Wacom tablet in Wayland stops working when apps are fullscreen
Public bug reported: I'm using a Wacom tablet (CTH-661) with Ubuntu 24.04.1 and Wayland. Whenever I make an app go full screen (such as Xournal, VS Code, or others), the tablet stops working correctly. The mouse disappears on the screen. I can sometimes bring it back by using alt-tab, or alternatively by using the trackpad on my laptop, but ultimately it is a very unstable experience. This problem doesn't occur under X11. I'm happy to supply additional information if it would be helpful. I tried to use ubuntu-bug, but it wouldn't let me proceed without indicating what package was problematic, and I didn't know in what package this problem was. ** Affects: 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/2081112 Title: Wacom tablet in Wayland stops working when apps are fullscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2081112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081111] [NEW] Wacom tablet buttons settings don't work under fractional scaling
Public bug reported: I'm using a Wacom tablet (CTH-661) with Ubuntu 24.04.1 and Wayland. The "Wacom Tablet" settings have a screen for configuring the button on the tablet. That screen is unresponsive when I have fractional scaling enabled; clicking on any of the tablet buttons don't make anything happen. This problem doesn't occur when fractional scaling is off. The problem also doesn't occur when running X11 with fractional scaling. It seems to be purely related to fractional scaling in Wayland. I'm happy to supply additional information if it would be helpful. I tried to use ubuntu-bug, but it wouldn't let me proceed without indicating what package was problematic, and I didn't know in what package this problem was. ** Affects: 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/208 Title: Wacom tablet buttons settings don't work under fractional scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081052] [NEW] audio
Public bug reported: i get sound through speakers for about 30 seconds and then sound cuts off.sound through a headset is ok ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: pulseaudio 1:16.1+dfsg1-2ubuntu10 ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12 Uname: Linux 6.8.0-45-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dave 1388 F pipewire /dev/snd/controlC0: dave 1396 F wireplumber CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 18 11:23:05 2024 InstallationDate: Installed on 2020-02-07 (1685 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: RM Education RM ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to noble on 2024-09-18 (0 days ago) dmi.bios.date: 04/20/2011 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 202 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: RM MOBILE ONE 310 dmi.board.vendor: RM Education dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: RM Education dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr202:bd04/20/2011:br4.6:svnRMEducation:pnRM:pvr1.0:rvnRMEducation:rnRMMOBILEONE310:rvr1.0:cvnRMEducation:ct10:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: PEGA Family dmi.product.name: RM dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: RM Education mtime.conffile..etc.init.d.apport: 2024-07-22T15:59:07 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081052 Title: audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2081052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054092] Re: [SRU] Add support for FIT images to rpi config
I may have been too hasty above. Apparently Core may no longer rely on u-boot either. I've reset the tags pending further investigation. If Core does indeed not require u-boot, we'll still need some means of determining that the change leaves u-boot operable (for anybody actually using it in practice, although it's not supported on Classic images). If that's the case, I'll update the second part of the verification instructions accordingly. ** Tags removed: verification-failed-noble ** Tags added: verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054092 Title: [SRU] Add support for FIT images to rpi config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2054092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054092] Re: [SRU] Add support for FIT images to rpi config
The first part of the test plan (generating test FIT images) has passed successfully. Unfortunately the second part, ensuring existing boot scripts continue to operate normally, has failed. I need to figure out if there's a way to support FIT images *and* support loading of kernel/initrd from straight images. This change can remain in the devel (oracular) series as firstly Classic images no longer rely on u-boot and secondly interim releases aren't used for generation of Core images (which do rely on u-boot). ** Tags removed: verification-needed-noble ** Tags added: verification-failed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054092 Title: [SRU] Add support for FIT images to rpi config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2054092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080368] Re: Support CM5
** Tags added: block-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080368 Title: Support CM5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpi-eeprom/+bug/2080368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076152] Re: SRU: add threading to the list of modules which cannot be lazy imported
** Description changed: + [ Impact ] + + The current release of mercurial fails to start with Python 3.12.5 or + later. Although this version of Python is not currently in noble, it is + planned to be as part of noble's LTS lifecycle. + + [ Test Plan ] + + Start a noble container, install mercurial and verify it works: + + lxc launch ubuntu:n merctest + lxc shell merctest + apt update + apt install -y mercurial + hg --version + + Upgrade to a version of python >=3.12.5. Because this is not yet + available in noble, we'll use the oracular debs. Still within the + container: + + apt install ubuntu-dev-tools + pull-lp-debs python3-defaults + pull-lp-debs python3.12 + pull-lp-debs openssl + apt install ./python3_3.12.6-0ubuntu1_amd64.deb ./python3-minimal_3.12.6-0ubuntu1_amd64.deb ./libpython3-stdlib_3.12.6-0ubuntu1_amd64.deb ./libpython3.12-stdlib_3.12.6-1_amd64.deb ./python3.12-minimal_3.12.6-1_amd64.deb ./python3.12_3.12.6-1_amd64.deb ./libpython3.12-minimal_3.12.6-1_amd64.deb ./libssl3t64_3.3.1-2ubuntu1_amd64.deb ./libpython3.12t64_3.12.6-1_amd64.deb + hg --version + + At this point, mercurial should crash complaining "AttributeError: + partially initialized module 'threading' has no attribute 'RLock' (most + likely due to a circular import)" + + Upgrade mercurial to the version in noble-proposed, and re-run hg + --version to verify the fix. + + [ Regression Potential ] + + Minimal; the patch in question is already part of the mercurial release + in oracular, which has a version of python >=3.12.5. The patch itself is + minimal, simply marking two modules (threading and _weakrefset) for + standard import (not lazy), and altering a couple of test cases to deal + with modified output syntax in the later version. Mercurial itself also + has a comprehensive test suite. + + [ Original Description ] + hg fails to start with Python 3.12.5 and Python 3.13.0rc1 (see the Debian bug for details). This patch adds the threading module to the list of modules which cannot be lazy imported. We will backport Python 3.12.5 to the 24.04 LTS release, so update mercurial first to avoid later breakage. There are no code changes, except for the threading module now being loaded at startup. Test case: hg starts with Python 3.12.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076152 Title: SRU: add threading to the list of modules which cannot be lazy imported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/2076152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070443] Re: SRU: Fix critical regression in Mercurial 6.7.x < 6.7.4
** Changed in: mercurial (Ubuntu Noble) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070443 Title: SRU: Fix critical regression in Mercurial 6.7.x < 6.7.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/2070443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076152] Re: SRU: add threading to the list of modules which cannot be lazy imported
Ah, sorry forgot I needed to update this one as well as LP: #2070443. Will put something together... ** Changed in: mercurial (Ubuntu) Status: New => Fix Released ** Changed in: mercurial (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/2076152 Title: SRU: add threading to the list of modules which cannot be lazy imported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/2076152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054092] Re: [SRU] Add support for FIT images to rpi config
** Description changed:
+ [ Impact ]
+
+ The current u-boot-rpi package does not include support for FIT images.
+ Enabling this feature has been requested by an internal team.
+
+ [ Test Plan ]
+
+ To test FIT image generation:
+
+ * Flash the Ubuntu Server for Raspberry Pi 24.04.1 image [1] to an SD card
+ * Place the following content in a file named "image.its":
+
+ /dts-v1/;
+ / {
+ description = "FIT payload";
+ #address-cells = <2>;
+ images {
+ kernel {
+ description = "kernel";
+ data = /incbin/("vmlinux.zst");
+ type = "kernel";
+ arch = "arm64";
+ os = "linux";
+ compression = "zstd";
+ load = <0x20>;
+ entry = <0x20>;
+ hash {
+ algo = "sha1";
+ };
+ };
+ initrd {
+ description = "initramfs";
+ data = /incbin/("initrd.cpio.zst");
+ type = "ramdisk";
+ arch = "arm64";
+ os = "linux";
+ compression = "none";
+ hash {
+ algo = "sha1";
+ };
+ };
+ };
+ configurations {
+ default = "standard";
+ standard {
+ description = "config";
+ kernel = "kernel";
+ ramdisk = "initrd";
+ hash {
+ algo = "sha1";
+ };
+ };
+ };
+ };
+
+ * Run mkimage -f image.its -T flat_dt
+ * Observe failure with current version
+ * Upgrade u-boot-rpi to version in -proposed
+ * Run mkimage -f image.its -T flat_dt
+ * Observe successful generation of image
+
+ To test no regression in boot operation:
+
+ * Flash the Ubuntu Server for Raspberry Pi 24.04.1 image [1] to an SD card
+ * Modify the boot sequence to include u-boot. In config.txt:
+ - Set kernel=uboot_rpi_4.bin (adjust as appropriate for test board)
+ - Set device_tree_address=0x0300
+ * sudo reboot
+ * Ensure boot succeeds
+
+ [1]:
+
http://cdimage.ubuntu.com/releases/24.04.1/release/ubuntu-24.04.1-preinstalled-
+ desktop-arm64+raspi.img.xz
+
+ [ Regression Potential ]
+
+ Varied; the u-boot package hasn't been used in the classic images since
+ focal (and jammy upgrades includes a quirk to remove it from the boot
+ chain), so the impact on the server and desktop images should be nil
+ even if it failed entirely. However, the Core images still use u-boot so
+ its operation should be checked on all boards supported by Core 24
+ (specifically the Pi 3, 4, and 5 series) by following the second part of
+ the test plan above.
+
+ [ Original Description ]
+
Support for signed FIT images has been requested; the following config
items should be enabled for the rpi 3 and 4 configurations (in both
armhf and arm64):
CONFIG_FIT=y
CONFIG_FIT_SIGNATURE=y
CONFIG_FIT_VERBOSE=y
CONFIG_FIT_PRINT=y
CONFIG_TOOLS_FIT=y
CONFIG_TOOLS_FIT_SIGNATURE=y
CONFIG_TOOLS_FIT_VERBOSE=y
CONFIG_TOOLS_FIT_PRINT=y
CONFIG_ZSTD=y
Check this doesn't affect core 24 images (there will inevitably be a
size increase as a result of enabling more flags; this is probably a
good time to unseed u-boot on the pi images 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/2054092
Title:
[SRU] Add support for FIT images to rpi config
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2054092/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054092] Re: [SRU] Add support for FIT images to rpi config
** Summary changed: - Add support for FIT images to rpi config + [SRU] Add support for FIT images to rpi config -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054092 Title: [SRU] Add support for FIT images to rpi config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2054092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078761] Re: Update Raspberry Pi Firmware
I've been holding off on bumping rpi-eeprom (which is what you actually want for the Pi 5) to get the latest boot firmware into oracular in the hopes that it will work on the CM5 when that launches (LP: #2080368). Unfortunately, I don't have time to do more than one bump of the package per cycle (especially when there are added complexities of new dependencies which aren't in main -- i.e. flashrom). The SRU rules are such that this won't be back-ported to noble without a request to fix a problem you're encountering (i.e. we need to verify the change fixes something as part of an SRU test plan). If there is a specific issue you're encountering, and you've got an idea which firmware version fixes it, I can certainly look at pushing that into current releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078761 Title: Update Raspberry Pi Firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi/+bug/2078761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080407] [NEW] Please merge rpi-imager 1.9.0
Public bug reported: New version released upstream: https://github.com/raspberrypi/rpi- imager/releases/tag/v1.9.0 ** Affects: rpi-imager (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: Confirmed ** Changed in: rpi-imager (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: rpi-imager (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/2080407 Title: Please merge rpi-imager 1.9.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpi-imager/+bug/2080407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080368] Re: Support CM5
The new version includes the signing tools for the EEPROM, which introduce a dependency on python3-pycryptodome. This is in universe, but rpi-eeprom needs to remain in main in order to be seeded on the images. As a result, I'm going to split the signing tools into their own package: rpi-eeprom-sign which can remain in universe. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080368 Title: Support CM5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpi-eeprom/+bug/2080368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080368] [NEW] Support CM5
Public bug reported:
In order to provide support for the forthcoming CM5, we should
incorporate all possible boot fixes for the CM5 into the oracular
release. Of particular note are the following releases:
* https://github.com/raspberrypi/rpi-
eeprom/releases/tag/v2024.07.30-2712 -- support CM5 on the CM4IO board
* https://github.com/raspberrypi/rpi-
eeprom/releases/tag/v2024.06.05-2712 -- support for CM5 in [pi5]
conditional sections of config.txt
* https://github.com/raspberrypi/rpi-
eeprom/releases/tag/v2024.02.17-2712 -- preliminary support for CM5
Merging the current rpi-eeprom 24.0 release would incorporate these
changes. These changes should also be SRU'd to noble as part of ongoing
hardware support in the current LTS, but this can likely wait until
oracular's release.
** Affects: rpi-eeprom (Ubuntu)
Importance: High
Assignee: Dave Jones (waveform)
Status: Confirmed
** Affects: rpi-eeprom (Ubuntu Noble)
Importance: Medium
Assignee: Dave Jones (waveform)
Status: Confirmed
** Tags: foundations-todo raspi-image
** Changed in: rpi-eeprom (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: rpi-eeprom (Ubuntu)
Milestone: None => ubuntu-24.10
** Changed in: rpi-eeprom (Ubuntu)
Status: New => Confirmed
** Also affects: rpi-eeprom (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: rpi-eeprom (Ubuntu)
Importance: Undecided => High
** Changed in: rpi-eeprom (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: rpi-eeprom (Ubuntu Noble)
Status: New => Confirmed
** Changed in: rpi-eeprom (Ubuntu Noble)
Assignee: (unassigned) => Dave Jones (waveform)
** Tags added: foundations-todo
** Tags added: raspi-image
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080368
Title:
Support CM5
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rpi-eeprom/+bug/2080368/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078525] Re: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi
Setting priorities: high for noble as this is breaking people upgrading on a Pi Zero 2W; medium for jammy as it will be needed there when LP: #2038087 is SRU'd (which turns out to be why I didn't notice this bug on jammy); low for oracular as I'm not 100% sure this fix is required in oracular (given users *must* pass through noble to get to oracular, and in theory at least shouldn't have any jammy kernels left around when they get there). ** Changed in: flash-kernel (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: flash-kernel (Ubuntu Noble) Importance: Undecided => High ** Changed in: flash-kernel (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: flash-kernel (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078525 Title: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2078525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038087] Re: [FFe] flash-kernel displays wrong "selected" DTB on various Pi models
Turns out we'll need this fix (minus the 5B entries) in Jammy as well. The cause of this is why I didn't notice LP: #2078525 until jammy users started upgrading to noble. The fix there will also be required when this is backported so they should be combined for jammy at least. ** Also affects: flash-kernel (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: flash-kernel (Ubuntu Jammy) Status: New => Incomplete ** Changed in: flash-kernel (Ubuntu Jammy) Status: Incomplete => Confirmed ** Changed in: flash-kernel (Ubuntu Jammy) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: flash-kernel (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038087 Title: [FFe] flash-kernel displays wrong "selected" DTB on various Pi models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2038087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078525] Re: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi
This may also need fixing on oracular. Theoretically there could still be a jammy kernel hanging around after jammy->noble->oracular (it *shouldn't* happen under normal circumstances where there should at a maximum be the running kernel, last stable, and current stable installed -- but there may well be edge cases). ** Changed in: flash-kernel (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078525 Title: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2078525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066885] Re: On Pi desktop, numerous reports of lack of landlock supported ABI
I'm going to add linux-raspi as affected here given this is (at least partially) down to a linux-raspi configuration difference. Kernel team: is there a reason landlock is disabled in the Pi kernel? Seems to work happily on a Pi 5, but perhaps there was some incompatibility with earlier models? ** 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/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/linux-raspi/+bug/2066885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
