[Bug 2067080] [NEW] [SRU] Please bump firmware revision to 8 from jammy
Public bug reported: [ Impact ] The rev 1.4 variant of the 3B+ requires an updated boot firmware, specifically one at least as recent as that in jammy-updates (version 8). This should be back-ported to focal, and preferably bionic to provide support for Core 18 booting on these devices. [ Test Plan ] As a closed boot firmware this will need validation on all supported Pis. For bionic, this is the 2B, 3B, 3A+, and 3B+. For focal, this is the 2B, 3B, 3A+, 3B+, and 4B. Because the package includes wifi and bluetooth firmware as well as boot firmware, the following should be verified: * Ability to boot successfully * Ability to reboot successfully * Ability to shutdown successfully * That wifi can connect successfully on relevant models (all except the 2B) * That bluetooth can pair successfully on relevant models (all except the 2B) [ Regression Potential ] Fairly low; the firmware in question has been in use on all relevant models in jammy for quite some time, so the regression potential for the operation of the firmware itself is low. That said, the wifi and bluetooth firmware still interacts with the kernel, and bionic and focal have different kernel versions to jammy, hence why the operation of these components will still need (re-)verification. If issues arise they are most likely to come from the fact that linux- firmware-raspi2 was renamed to linux-firmware-raspi in jammy which affected the diversions in the package. This means the backport isn't *entirely* straight-forward and care must be taken to ensure that all relevant files end up in their correct locations with the correct diversions. ** Affects: linux-firmware-raspi2 (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: New ** Affects: linux-firmware-raspi2 (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux-firmware-raspi2 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-firmware-raspi2 (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Also affects: linux-firmware-raspi2 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-firmware-raspi2 (Ubuntu Bionic) Importance: Undecided Status: New ** Summary changed: - Please bump firmware revision to 8 from jammy + [SRU] Please bump firmware revision to 8 from jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067080 Title: [SRU] Please bump firmware revision to 8 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/2067080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044382] Re: Some Qt-based applications open "another" icon under Gnome
** Summary changed: - Quassel opens "another" icon under Gnome + Some Qt-based applications open "another" icon under Gnome ** Description changed: - I'm unsure if this is a bug in quassel, or in the gnome dock itself. - Under Ubuntu 23.10 (mantic), running Quassel from a pinned icon on the - left bar results in the pinned icon appearing "idle" (not running), and - a second icon appearing below those that are pinned which apparently - represents the running quassel instance. + I'm unsure if this is a bug in the affected applications, or in the + gnome dock itself. Under Ubuntu 23.10 (mantic) and 24.04 (noble), + running Quassel, Veusz, or OpenSCAD from a pinned icon on the left bar + results in the pinned icon appearing "idle" (not running), and a second + icon appearing below those that are pinned which apparently represents + the running instance. - Pressing the idle quassel icon (or pressing the Super+4 shortcut for it) - runs *another* instance of quassel rather than switching to the running - instance. The "extra" icon also cannot be pinned (and occasionally - strange "copies" of it are left lying around if one tries to drag it to - the pinned icon locations). + Pressing the idle application icon (or pressing the Super+N shortcut for + it) runs *another* instance of the application rather than switching to + the running instance. The "extra" icon also cannot be pinned (and + occasionally strange "copies" of it are left lying around if one tries + to drag it to the pinned icon locations). - This may be because quassel is a Qt based application, but I also run + This may be because these are all Qt-based applications, but I also run KeepassXC (another Qt application) without such issues (other than unusual window borders and icons which appear on both applications), - hence why I'm unsure this is an issue in quassel or in the gnome dock. - I'll attach a screenshot demonstrating the issue. + hence why I'm unsure this is an issue in these applications or in the + gnome dock. I'll attach a screenshot demonstrating the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044382 Title: Some Qt-based applications open "another" icon under Gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2044382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066881] Re: Copied icons in dash after application run
Curiously, I've seen this issue with several Qt-based applications (Quassel, Veusz, and OpenSCAD) under noble, as reported in LP: #2044382, but I've not seen it with Firefox (which isn't Qt-based to the best of my knowledge?). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066881 Title: Copied icons in dash after application run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2066881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066894] [NEW] Log spam from querying snaps on noble
Public bug reported:
After registering my Ubuntu 24.04 desktop for Raspberry Pi with
Landscape, the following warnings periodically appear in the system
journal (every few minutes):
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:29:23,114 WARNING
[MainThread] Unable to get config for snap gnome-42-2204:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:29:25,989 INFO
[MainThread] Ping indicates message available. Scheduling an urgent exchange.
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:29:32,875 INFO
[MainThread] Starting urgent message exchange with
https://landscape.canonical.com/message-system.
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:29:36,253 INFO
[PoolThread-twisted.internet.reactor-0] Sent 223188 bytes and received 5382
bytes in 3.37s.
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:29:36,257 INFO
[MainThread] Switching to normal exchange mode.
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:29:36,267 INFO
[MainThread] Message exchange completed in 3.39s.
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:06,301 INFO
[MainThread] Ping indicates message available. Scheduling an urgent exchange.
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:32,847 INFO
[MainThread] Got notification of impending exchange. Notifying all plugins.
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:32,847 INFO
[MainThread] Got notification of impending exchange. Notifying all plugins.
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:32,912 INFO
[MainThread] Queueing a message with updated data watcher info for
landscape.client.monitor.activeprocessinfo.ActiveProcessInfo.
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,015 WARNING
[MainThread] Unable to get config for snap snapd-desktop-integration:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,020 WARNING
[MainThread] Unable to get config for snap core22:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,024 WARNING
[MainThread] Unable to get config for snap rpi-imager:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,029 WARNING
[MainThread] Unable to get config for snap signal-desktop:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,033 WARNING
[MainThread] Unable to get config for snap snapd:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,038 WARNING
[MainThread] Unable to get config for snap bare:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,043 WARNING
[MainThread] Unable to get config for snap core24:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,047 WARNING
[MainThread] Unable to get config for snap gtk-common-themes:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,052 WARNING
[MainThread] Unable to get config for snap thunderbird:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,056 WARNING
[MainThread] Unable to get config for snap snap-store:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,061 WARNING
[MainThread] Unable to get config for snap telegram-desktop:
b'{"type":"error","status-code":401,"status":"Unauthorized","result":{"message":"access
denied","kind":"login-required"}}'
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:30:33,066 WARNING
[MainThread] Unable to get config for snap ubuntu-image:
[Bug 2066885] [NEW] On Pi desktop, numerous reports of lack of landlock supported ABI
Public bug reported: On the Ubuntu noble desktop for Raspberry Pi, the system journal has numerous of the following entries: May 23 10:30:29 kermit tracker-miner-f[11130]: Could not get landlock supported ABI: Operation not supported May 23 10:30:29 kermit tracker-miner-f[11130]: Refusing to extract file data since Landlock could not be enabled. Update your kernel to fix this warning. These appear to be written every time a file in my home directory is modified. The kernel is the stock noble kernel from linux-raspi, 6.8.0-1004-raspi. ** Affects: tracker-miners (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066885 Title: On Pi desktop, numerous reports of lack of landlock supported ABI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/2066885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062564] Re: [FFe] Seed pemmican
** Changed in: pemmican (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062564 Title: [FFe] Seed pemmican To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pemmican/+bug/2062564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064208] Re: Installer crashes when booting from USB on Raspberry Pi
@vanvugt Indeed -- I'm confident that's the root cause at this point; just waiting for that to land in devel, then I can convert the bug to SRU, wait for that to land, then request an image re-spin from the release team -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064208 Title: Installer crashes when booting from USB on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2064208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065051] Re: [SRU] Migrate Pi users to KMS
Verified with upgrade of a Pi 4 on an SD card as described in the test plan, only variant being to grab the noble tar-ball manually (as do- release-upgrade won't allow --proposed with --devel). Worked happily, KMS was present in the config.txt after the upgrade, and the HDMI audio outputs appeared correctly when the card was subsequently booted on a Pi 5. ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065051 Title: [SRU] Migrate Pi users to KMS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2065051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058970] Re: deepin-log-viewer 5.9.7+ds1-2build6 FTBFS on 32-bit time64 architectures
** Changed in: deepin-log-viewer (Ubuntu Noble) Assignee: Shengjing Zhu (zhsj) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058970 Title: deepin-log-viewer 5.9.7+ds1-2build6 FTBFS on 32-bit time64 architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deepin-log-viewer/+bug/2058970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921914] Re: [SRU] package quickml 0.7-5.1 failed to install/upgrade: installed quickml package post-installation script subprocess returned error exit status 1
I've re-sponsored updated debdiffs as requested -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921914 Title: [SRU] package quickml 0.7-5.1 failed to install/upgrade: installed quickml package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quickml/+bug/1921914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060882] Re: [SRU] usrpctl fails to run
Confirmed; fix looks minimal and reasonable, sponsoring, thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060882 Title: [SRU] usrpctl fails to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uhd/+bug/2060882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2015017] Re: [SRU] scaling is wrong in SVG output
** Changed in: graphviz (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: graphviz (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: graphviz (Ubuntu Mantic) Status: Confirmed => In Progress ** Changed in: graphviz (Ubuntu Noble) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2015017 Title: [SRU] scaling is wrong in SVG output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/2015017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2015017] Re: [SRU] scaling is wrong in SVG output
** Description changed: + [ Impact ] + + graphivz output is incorrect for SVG output when the "size" attribute is + set, as it implicitly is in several circumstances. + + [ Test Plan ] + + * sudo apt install imagemagick graphviz + * Grab fst.dot attached to this bug + * dot -Tpng fst.dot | display png:- + * Observe correct scaling + * dot -Tsvg fst.dot | display svg:- + * Observe incorrect cropping of output + * Enable proposed (https://wiki.ubuntu.com/Testing/EnableProposed) + * Upgrade graphviz to version from proposed + * dot -Tsvg fst.dot | display svg:- + * Ensure output is not cropped + + [ Regression Potential ] + + Low; the patched applied is from upstream and has been part of the + official sources for many years now (Debian and Ubuntu are rather behind + on their versions of graphviz, but it looks like this may be corrected + in the oracular cycle). Nonetheless, the patch was first applied to our + current version, is minimal in nature, and fixes the issue in tests + without impacting other output. + + There is a very small possibility someone may be relying on the + incorrect truncation of SVG output, but this is almost certainly + outweighed by the number of users impacted by incorrect truncation of + output in, e.g. jupyter notebooks, and by the consistency of having the + same (lack of) cropping in different output formats. + + [ Original Description ] + SVG output brutally truncates large (and even not so large) graphs when the "size" attribute is set. This was fixed *two years ago* upstream. Any chance that we might get more recent graphviz packages in Ubuntu at some point? Failing that, it is quite easy to fix this bug. See https://gitlab.com/graphviz/graphviz/-/issues/1605 The fix is very simple, it seems: https://gitlab.com/graphviz/graphviz/-/commit/a5606d101af1cc949908a6f0bc19caaa4eb31159 Definitely present in 22.04, still present in the Lunar package (graphviz_2.42.2-7build3) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2015017 Title: [SRU] scaling is wrong in SVG output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/2015017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2015017] Re: [SRU] scaling is wrong in SVG output
Brilliant, thanks very much for that -- I've upload the ocular version to proposed, and I'll get the SRU uploads done later this morning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2015017 Title: [SRU] scaling is wrong in SVG output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/2015017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2015017] Re: [SRU] scaling is wrong in SVG output
For SRU purposes, is there any chance I could ask you for a simple reproducer case? It's okay if it uses jupyter, but I'm struggling to come up with one without it and I've run out of time this evening. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2015017 Title: [SRU] scaling is wrong in SVG output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/2015017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2015017] Re: scaling is wrong in SVG output
I quite understand the frustration with something that appears to be abandoned. However, in this case it seems it was actually down to some confusion over the versioning scheme which changed upstream from Debian (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980900 has the gory details). It also seems that Debian's now got a new watch file and version 11 is now in experimental, so I'm hoping that'll migrate to unstable at some point and we'll pick up a modern version for oracular. Anyway, back to the fix at hand -- this definitely needs patching in oracular, noble, mantic, and jammy at the very least. Unfortunately your branch appears to have diff-markers embedded in it, so I can't accept it directly, but the patch is trivial enough I can just apply it to the package directly. I'll target this to the affected releases and start the SRU process once this is in oracular. ** Bug watch added: Debian Bug tracker #980900 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980900 ** Also affects: graphviz (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: graphviz (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: graphviz (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: graphviz (Ubuntu) Status: New => Confirmed ** Changed in: graphviz (Ubuntu Jammy) Status: New => Confirmed ** Changed in: graphviz (Ubuntu Mantic) Status: New => Confirmed ** Changed in: graphviz (Ubuntu Noble) Status: New => Confirmed ** Summary changed: - scaling is wrong in SVG output + [SRU] scaling is wrong in SVG output -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2015017 Title: [SRU] scaling is wrong in SVG output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/2015017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065493] [NEW] Please merge rpi-lgpio 0.6
Public bug reported: New upstream version fixes future re-numbering of the gpiochip device on Pi 5. ** Affects: rpi-lgpio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065493 Title: Please merge rpi-lgpio 0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpi-lgpio/+bug/2065493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060677] Re: Consistent (zfs?) errors at shutdown
Yes, I'm afraid so. In fact I'm occasionally seeing it on boot as well
which seems to result in wayland crashing and the session falling back
to X11. Here's the backtrace from a crash on startup which resulted in
me starting an X11 session (and then wondering why the cursor
[ 47.898381] spl: loading out-of-tree module taints kernel.
[ 47.957978] zfs: module license 'CDDL' taints kernel.
[ 47.957986] Disabling lock debugging due to kernel taint
[ 47.958013] zfs: module license taints kernel.
[ 47.986141] Initializing XFRM netlink socket
[ 48.872585] rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks:
{ 3- } 22 jiffies s: 921 root: 0x8/.
[ 48.872601] rcu: blocking rcu_node structures (internal RCU debug):
[ 48.872605] Sending NMI from CPU 0 to CPUs 3:
[ 48.872610] NMI backtrace for cpu 3
[ 48.872616] CPU: 3 PID: 2797 Comm: modprobe Tainted: P C OE
6.8.0-1004-raspi #4-Ubuntu
[ 48.872619] Hardware name: Raspberry Pi 5 Model B Rev 1.0 (DT)
[ 48.872621] pstate: 8049 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 48.872625] pc : g+0x44/0x80 [zfs]
[ 48.872998] lr : round_fn+0x124/0x1a8 [zfs]
[ 48.873282] sp : 800083b3a9f0
[ 48.873283] x29: 800083b3a9f0 x28: 0010 x27: 0001
[ 48.873288] x26: 0002 x25: 0010 x24: 0040
[ 48.873291] x23: 0010 x22: 3c6e x21: 800083b3aac8
[ 48.873294] x20: a0001eeb1f08 x19: 800083b3aa38 x18:
[ 48.873298] x17: x16: a00084e64e20 x15: daab804bbe5f084f
[ 48.873301] x14: dda7b2c9fd2e0cf6 x13: 8ea05092eab4a56e x12: 7e3c7900fc64dbc7
[ 48.873304] x11: 7e3c7900fc64dbc7 x10: a0001ea5ba80 x9 :
[ 48.873308] x8 : e60eea37 x7 : d00f75b3 x6 : fffd
[ 48.873311] x5 : fc4d5ec9 x4 : 000c x3 : 000b
[ 48.873314] x2 : 0006 x1 : 0001 x0 : 800083b3aac8
[ 48.873317] Call trace:
[ 48.873319] g+0x44/0x80 [zfs]
[ 48.873589] compress_pre+0x1e4/0x270 [zfs]
[ 48.873861] blake3_compress_in_place_generic+0x4c/0xa8 [zfs]
[ 48.874133] hash_one_generic+0x78/0xf0 [zfs]
[ 48.874402] blake3_hash_many_generic+0x74/0xb0 [zfs]
[ 48.874672] compress_chunks_parallel+0xe8/0x1d8 [zfs]
[ 48.874942] blake3_compress_subtree_wide+0x1a4/0x1c8 [zfs]
[ 48.875210] blake3_compress_subtree_wide+0xd8/0x1c8 [zfs]
[ 48.875477] blake3_compress_subtree_wide+0xd8/0x1c8 [zfs]
[ 48.875744] blake3_compress_subtree_wide+0xb0/0x1c8 [zfs]
[ 48.876009] blake3_compress_subtree_wide+0xd8/0x1c8 [zfs]
[ 48.876275] compress_subtree_to_parent_node+0x50/0x110 [zfs]
[ 48.876542] Blake3_Update2+0x168/0x240 [zfs]
[ 48.876809] Blake3_Update+0x54/0x80 [zfs]
[ 48.877074] blake3_incremental+0x2c/0x40 [zfs]
[ 48.877341] abd_iterate_func+0x104/0x150 [zfs]
[ 48.877608] abd_checksum_blake3_native+0x7c/0xb8 [zfs]
[ 48.877875] chksum_run+0xac/0x160 [zfs]
[ 48.878145] chksum_benchit+0x140/0x198 [zfs]
[ 48.878412] chksum_benchmark+0x334/0x3a8 [zfs]
[ 48.878681] chksum_init+0x28/0xa8 [zfs]
[ 48.878950] spa_init+0x130/0x168 [zfs]
[ 48.879221] zfs_kmod_init+0x4c/0x108 [zfs]
[ 48.879489] openzfs_init_os+0x1c/0xc8 [zfs]
[ 48.879755] openzfs_init+0x70/0xcd0 [zfs]
[ 48.880023] do_one_initcall+0x4c/0x368
[ 48.880029] do_init_module+0xa0/0x260
[ 48.880034] load_module+0x790/0x8c8
[ 48.880037] init_module_from_file+0x94/0xf8
[ 48.880040] idempotent_init_module+0x178/0x2a8
[ 48.880043] __arm64_sys_finit_module+0x6c/0xd8
[ 48.880047] invoke_syscall+0x50/0x120
[ 48.880049] el0_svc_common.constprop.0+0x48/0xf0
[ 48.880051] do_el0_svc+0x24/0x38
[ 48.880053] el0_svc+0x48/0x178
[ 48.880057] el0t_64_sync_handler+0x120/0x130
[ 48.880059] el0t_64_sync+0x1a8/0x1b0
[ 48.970724] ZFS: Loaded module v2.2.2-0ubuntu9, ZFS pool version 5000, ZFS
filesystem version 5
[ 49.798958] Key type psk registered
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060677
Title:
Consistent (zfs?) errors at shutdown
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2060677/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065180] Re: performance regression in dracut-install
@viraniac well, you're absolutely right! Same SD card with a fresh noble install, running on a Pi 4, first stock and second with a downgraded dracut from mantic: Pi 4B, stock -- 03:05 Pi 4B, downgrade -- 01:10 That is a pretty substantial regression, and diff'ing the initrds once more showed they're basically identical in content (unsurprisingly), so it's not writing any less. I wonder if it's added some sync points or something similar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065180 Title: performance regression in dracut-install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2065180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065408] [NEW] growroot-almost should be inhibitable from boot partition
Public bug reported: Some users wish to handle post-boot partitioning or fs configuration themselves. For this use-case it is important that the rootfs is *not* expanded on first boot. On the server images, this is relatively trivial by appending "growpart: off", but on the desktop images it's handled by the growroot-almost service and this is only capable of being inhibited by touching /etc/growroot-grown. It should be possible to inhibit this behaviour from the boot partition only which, being FAT, can be mounted from other OS'. ** Affects: ubuntu-raspi-settings (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: Confirmed ** Changed in: ubuntu-raspi-settings (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: ubuntu-raspi-settings (Ubuntu) Milestone: None => ubuntu-24.10 ** Changed in: ubuntu-raspi-settings (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065408 Title: growroot-almost should be inhibitable from boot partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-raspi-settings/+bug/2065408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065180] Re: performance regression in dracut-install
Some results from some local testing. These tests were all performed on the same SD card (a Samsung EVO Select 64GB) with fresh installs of the jammy and noble server images, after running full upgrades and rebooting: Pi 5, noble -- 01:23 Pi 4B, noble -- 03:05 Pi 3B+, noble -- 05:19 Pi 5, jammy -- unsupported Pi 4B, jammy -- 01:06 Pi 3B+, jammy -- 01:59 So, there *appears* to be a substantial slow down from jammy. However, I don't think this is due to dracut or a performance regression in initramfs-tools. I remembered that, this cycle, the kernel team got rid of the linux-modules-extra split in the linux-raspi kernel. This results in a substantially increased initrd size because many more modules are included by default. I took a listing of the jammy and noble initramfs contents and (after some manipulation to remove .zst suffixes, which are also new in the noble initramfs, and removing kernel version numbers). I'll attach the result of diff'ing these outputs, but a quick grep through the results and some calculations shows roughly 1000 extra files in the noble version. In other words, this is not comparing like for like. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065180 Title: performance regression in dracut-install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2065180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065180] Re: performance regression in dracut-install
** Patch added: "initramfs.diff" https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2065180/+attachment/5776701/+files/initramfs.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065180 Title: performance regression in dracut-install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2065180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063365] Re: brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52
I've added some notes to the upstream bug, including an observation about the regulatory-domain. My thoughts earlier that it doesn't affect anything may be partially wrong (the issue still occurs, but *potentially* only when the interface has no regdom prior to authentication? We'll see what upstream say about it -- I may be barking up the wrong tree there). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063365 Title: brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2063365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063365] Re: brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52
Aha! I can reproduce this on RaspiOS bookworm too, but while the messages appear in dmesg, they *don't* appear on the console, but that's just due to different printk default (level 3 instead of 4 on Ubuntu). So, this is an upstream issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063365 Title: brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2063365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063365] Re: brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52
I can reproduce this fairly reliably on the Ubuntu 24.04 Server for Pi image. Strangely, it doesn't seem to occur on the initial use of the wifi on boot, but running "netplan apply" (causing the interface to re- connect to the AP), reliably causes several "set chanspec" messages to appear in dmesg. The issue occurs whether or not ethernet is also in use, and setting the regulatory domain (a common suggestion in various other reports of this issue found online) does not appear to make a difference either. Speaking of other reports, https://github.com/raspberrypi/linux/issues/6049 is an open issue on the upstream kernel that appears to be identical to this one. ** Bug watch added: github.com/raspberrypi/linux/issues #6049 https://github.com/raspberrypi/linux/issues/6049 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063365 Title: brcmfmac: brcmf_set_channel: set chanspec 0x100c fail, reason -52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2063365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065138] Re: Please merge libcec 6.0.2-5 into Oracular
This merge is no longer needed. Our only delta with Debian is adding libraspberrypi-dev as a build-dependency which used to be required to enable raspi compatibility. However, since switching everything over to full KMS (in noble), we no longer need the raspi-specific bits. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065138 Title: Please merge libcec 6.0.2-5 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcec/+bug/2065138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064208] Re: Installer crashes when booting from USB on Raspberry Pi
Oh, many thanks to @marius.quabeck as well -- all the confirmations are extremely helpful! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064208 Title: Installer crashes when booting from USB on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2064208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064208] Re: Installer crashes when booting from USB on Raspberry Pi
@phrogger Brilliant, thanks for the confirmations; I've also tested a Sabrent NVMe drive here (successfully) and an ancient Intel SSD over USB (again successful). I think I'm happy to call this "good" at this point, so I'll push ahead with trying to get LP: #2037015 SRU'd back to noble, and then see if I can get the desktop image re-spun. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064208 Title: Installer crashes when booting from USB on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2064208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065051] Re: [SRU] Migrate Pi users to KMS
** Description changed: + [ Impact ] + In switching Pi Server users over to the KMS overlay (as resolution to LP: #2038924) we need an additional quirk for upgraders to migrate config.txt (this will be similar, but not identical, to the one for LP: #1923673). + + If we do not migrate such users, the immediate impact is that Pi 5 users + will have no sound output on server images (the Pi 5 only has HDMI audio + output, no auxiliary jack). Potentially more problematic in the long- + run, though, is that we will wind up with users on different graphical + stacks (the KMS stack, which is the only upstream supported stack going + forward, and the legacy framebuffer method). + + [ Test Case ] + + * Flash Ubuntu jammy to SD card and boot on Pi 4 + * Check /boot/firmware/config.txt does not contain dtoverlay=vc4-kms-v3d (it should not on Pi server images) + * sudo do-release-upgrade + * Proceed through upgrade and reboot + * Ensure system reboots successfully + * After reboot, check /boot/firmware/config.txt contains dtoverlay=vc4-kms-v3d + * Shutdown, move SD card to Pi 5 and boot it + * Check /proc/asound/cards contains entries for vc4hdmi + + [ Regression Potential ] + + The use of the KMS overlay itself is not concerning; we already use it + on the Pi desktop images, and have for several cycles now with no + serious issues, so the regression potential there is minimal. + + However, the quirk does manipulate the bootloader's config.txt on the + boot partition, which always carries the potential of leaving a system + unbootable. To guard against this, tests are included with the quirk + which check for several scenarios including a config.txt which has + already been migrated to the KMS overlay manually by the user (there are + various reasons to do this, including running kmscon), as well as the + typical expected case. ** Changed in: ubuntu-release-upgrader (Ubuntu Noble) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065051 Title: [SRU] Migrate Pi users to KMS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2065051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065051] Re: [SRU] Migrate Pi users to KMS
** Summary changed: - Migrate Pi users to KMS + [SRU] Migrate Pi users to KMS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065051 Title: [SRU] Migrate Pi users to KMS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2065051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065051] Re: Migrate Pi users to KMS
** Also affects: ubuntu-release-upgrader (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: ubuntu-release-upgrader (Ubuntu Noble) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065051 Title: Migrate Pi users to KMS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2065051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065051] [NEW] Migrate Pi users to KMS
Public bug reported: In switching Pi Server users over to the KMS overlay (as resolution to LP: #2038924) we need an additional quirk for upgraders to migrate config.txt (this will be similar, but not identical, to the one for LP: #1923673). ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: High Assignee: Dave Jones (waveform) Status: Confirmed ** Changed in: ubuntu-release-upgrader (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-release-upgrader (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065051 Title: Migrate Pi users to KMS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2065051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060858] Re: [SRU] rqsh fails to run
It was a little tricky to confirm this one, given that the missing dependency (libterm-readkey-perl) is seeded by server and cloud-image (so the problem didn't immediately manifest in my test containers!), but yes, confirmed. Targetting to affected releases. One question about the proposed fix: it's adding libterm-readkey-perl to Depends, when upstream have fixed this by adding it to Recommends. I suspect upstream is correct in that the "intent" of the package is to provide a library for querying RDF, and rqsh is (presumably?) a simple utility for experimenting with that facility, not the "primary" artifact of the package. In other words, there exist users that could happily install librdf-query-perl as a dependency of some Perl-based system, use it successfully, and never notice (or care) that rqsh doesn't work, and who don't want the overhead of its dependencies installed as well. Still, given the additional dependency in this case is already seeded in server and cloud-image, this really feels like splitting hairs, and I'd much rather the package "just works" for users. So, sponsoring! ** Also affects: librdf-query-perl (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: librdf-query-perl (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: librdf-query-perl (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: librdf-query-perl (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: librdf-query-perl (Ubuntu Focal) Status: New => Confirmed ** Changed in: librdf-query-perl (Ubuntu Jammy) Status: New => Confirmed ** Changed in: librdf-query-perl (Ubuntu Mantic) Status: New => Confirmed ** Changed in: librdf-query-perl (Ubuntu Noble) Status: New => Confirmed ** Changed in: librdf-query-perl (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060858 Title: [SRU] rqsh fails to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librdf-query-perl/+bug/2060858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921914] Re: [SRU] package quickml 0.7-5.1 failed to install/upgrade: installed quickml package post-installation script subprocess returned error exit status 1
Hmm, one thing that a test build in oracular shows is that lintian complains about the package depending on lsb-base, which is now an empty transitional package. It appears the only reason it depends on it is for the init-script in debian/quickml.init and there's no equivalent systemd package. I'll sponsor this anyway because the "fix" should be in oracular before the SRUs are considered, but I have a suspicion this is broken in noble onwards anyway (which is where lsb-base was made transitional IIRC), and will need some minor surgery to add a systemd service definition there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921914 Title: [SRU] package quickml 0.7-5.1 failed to install/upgrade: installed quickml package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quickml/+bug/1921914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921914] Re: [SRU] package quickml 0.7-5.1 failed to install/upgrade: installed quickml package post-installation script subprocess returned error exit status 1
Confirmed on all noted series; targetting accordingly. I was a little
nervous about rm'ing /etc/mailname in the postrm, but an apt-file search
confirms nothing else seems to own it (if something else owned it, it
might be better to create things like this in postinst, and just leave
them there in {pre,post}rm, but in this case it looks okay).
** Also affects: quickml (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: quickml (Ubuntu Oracular)
Importance: Undecided
Status: Confirmed
** Also affects: quickml (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: quickml (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: quickml (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: quickml (Ubuntu Noble)
Status: New => Confirmed
** Changed in: quickml (Ubuntu Mantic)
Status: New => Confirmed
** Changed in: quickml (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: quickml (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921914
Title:
[SRU] package quickml 0.7-5.1 failed to install/upgrade: installed
quickml package post-installation script subprocess returned error
exit status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/quickml/+bug/1921914/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064208] Re: Installer crashes when booting from USB on Raspberry Pi
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu-manual-tests/+git/ubuntu-manual-tests/+merge/465423 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064208 Title: Installer crashes when booting from USB on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2064208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951586] Re: Need option to specify wifi regulatory domain
** Changed in: network-manager (Ubuntu Lunar) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951586 Title: Need option to specify wifi regulatory domain To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064208] Re: Installer crashes when booting from USB on Raspberry Pi
I now have a test image that, using the patch from LP: #2037015, appears to fix the installer issue when booting from USB. If volunteers are interested in testing the image, I've made it available at: https://zoidberg.waveform.org.uk/images/ubuntu-24.04-preinstalled- desktop-arm64+raspi.img.xz The SHA256 of the image, for verification purposes, is b2718d9005a5ea6486b8512b6cf3974ce48ef879d1232a6dc88b2ccaa1dc3390 I've tested booting from two SD cards on both models and both appear fine; I've also tested USB boot on the Pi 4 (which worked happily) and tomorrow I should be able to test NVMe on a Pi 5. However, given the variability displayed by this bug already, the wider the variety of hardware tested, the better. Naturally, no workarounds should be in place when testing (leave the config.txt "as is"). If things work, please report the model and memory size of your Pi (e.g. Pi 4 4GB) and what you're booting from (SD card, SSD, NVMe). make+model of the boot media would be useful too, but largely to judge if we're covering a reasonable range of hardware. If things don't work, please report the above information, plus where in the procedure the crash occurred. If possible, re-flash and try to confirm if the crash occurs in the same place each time (we've already seen cases in this bug where "sometimes it does and sometimes it doesn't"). ** Description changed: After writing the Ubuntu 24.04 Desktop for Raspberry Pi image to an SSD drive with a USB3 interface (specifically; this issue does not occur when booting from an SD card), booting the drive on a Pi 4 or Pi 5, and running through the installer to the point where the (corrupted) slide deck starts to display during setup, the installer crashes. [ Workaround ] + + A test image is now available; please see comment 1 below for details. At the time of writing, some workarounds have been found, but none that consistently work on all boards with all drives. One workaround that has worked on a Pi with a Samsung EVO SSD, and a Crucial SSD is as follows: Before booting the image, find config.txt on the boot partition, and the "dtoverlay=vc4-kms-v3d" line within it. There will be two of these lines, you want the first one under an "[all]" section. Append ",cma-128" to the line. Specifically, the following section: dtoverlay=vc4-kms-v3d disable_fw_kms_setup=1 Should become: dtoverlay=vc4-kms-v3d,cma-128 disable_fw_kms_setup=1 Unmount the drive cleanly, boot it, and run through the installer. You may revert the change (if you wish) after successful installation. Another workaround, reported as working on a Pi 5 with an NVMe drive attached over PCIe: Before booting the image, find config.txt on the boot partition. Under the first "[all]" section append the following line: - dtparam=pciex1 + dtparam=pciex1 Unmount the drive cleanly, boot it, and run through the installer. Please note both workarounds have also been reported as failing with certain drive combinations. [ Background ] Given this crash occurs immediately upon the (corrupted) slide deck starting, that it only occurs when booting from USB (but the exact same image works from an SD card), and that merely changing the pre- allocation of the contiguous memory area affects it, I suspect this at least related to (if not a duplicate of) LP: #2037015, particularly since a crash bug is now associated with it too, LP: #2062146. Still, I'll leave this open as a non-duplicate for now as I'm not positive of root-cause yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064208 Title: Installer crashes when booting from USB on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2064208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064370] Re: Blank screen after boot in raspberry pi 4
> So that means that with different monitors I could potentially not need this vc4.force_hotplug option, right? That is certainly my suspicion; it doesn't much surprise me that an LCD controller isn't *quite* obeying the HDMI spec (or perhaps that it expects to be part of something else which handles asserting the hot- plug line). I would certainly hope a branded monitor behaves properly, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064370 Title: Blank screen after boot in raspberry pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2064370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064370] Re: Blank screen after boot in raspberry pi 4
> If I switch to the KMS overlay, the message is exactly the same, so it means the EDID is accessible from the monitor in either case. Not quite the case I'm afraid. The output you're quoting there is from the pi's bootloader running on the GPU. So, what you've established there is that the GPU (which ignores hotplug, as noted in 6by9's comment in the upstream bug) reads the EDID. This is all that's needed in the FKMS case because there the kernel driver is a thin shim that just talks to the firmware running on the GPU and retrieves EDID data from there. However in the KMS case, the bootloader eventually relinquishes control of the GPU to the linux kernel, and the kernel then attempts to retrieve the EDID independently (as least, this is my understanding of things -- I'm no expert in this area; corrections welcome!). Glad to hear the force_hotplug option works; that largely gels with the idea that the monitor is not correctly asserting hot-plug. If it's not asserting hot-plug on boot, the would also explain why re-plugging the monitor doesn't work either. FKMS doesn't care, it just reads the EDID anyway, but the KMS driver is waiting for a signal to do so and there's none on boot, or later when the monitor is re-plugged. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064370 Title: Blank screen after boot in raspberry pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2064370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064370] Re: Blank screen after boot in raspberry pi 4
You are correct it was introduced for noble as, without the KMS driver, there's no audio output over HDMI on the server image under the Pi 5 (LP: #2038924). KMS is also the only supported stack on the Pi 5 upstream, and rather than trying to support different stacks on different models I opted to move everything to the KMS stack instead (which we were already using on the desktop images). Unfortunately, it seems that as well as causing issues on the older models (LP: #2063255, LP: #2060300 -- incidentally the cma-128 workaround is for this latter bug), it's now even causing issues on the Pi 4. Obviously I didn't see these issues during testing, but then I've only two different models of monitor here that I test with: a BenQ and a Samsung. From the description it sounds like the kernel is either failing to retrieve, or failing to parse the EDID from your monitor. However, from reading a potentially related upstream bug (https://github.com/raspberrypi/linux/issues/5368#issuecomment-1453144837) it may be that the monitor is failing to assert hotplug. I would first try 6by9's work-arounds from that thread, specifically: * Forcing hotplug by appending "vc4.force_hotplug=N (where N is 0x01 for the first HDMI port, or 0x02 for the second) to cmdline.txt on the boot partition: $ sudo sed -i -e 's/$/ vc4.force_hotplug=0x01' /boot/firmware/cmdline.txt $ sudo reboot * If that fails, reboot with the fkms overlay in place, dump the EDID to /lib/firmware/edid.bin, then force that to be parsed under kms: $ sudo sed -i -e 's/vc4-kms-v3d/vc4-fkms-v3d/' /boot/firmware/config.txt $ sudo reboot ... wait for the reboot ... $ sudo cp /sys/class/drm/card1-HDMI-A-1/edid /lib/firmware/edid.bin $ sudo sed -i -e 's/vc4-fkms-v3d/vc4-kms-v3d/' /boot/firmware/config.txt $ sudo sed -i -e 's/$/ drm.edid_firmware=HDMI-A-1:edid.bin' /boot/firmware/cmdline.txt $ sudo reboot ... see if the monitor works ... If you could attach the edid dump from when running under FKMS that may also help the kernel team in their investigation. ** Bug watch added: github.com/raspberrypi/linux/issues #5368 https://github.com/raspberrypi/linux/issues/5368 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064370 Title: Blank screen after boot in raspberry pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2064370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064208] Re: Installer crashes when booting from USB on Raspberry Pi
** Changed in: ubiquity (Ubuntu) Status: New => Triaged ** Changed in: ubiquity (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064208 Title: Installer crashes when booting from USB on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2064208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064208] Re: Installer crashes when booting from USB on Raspberry Pi
** Description changed: After writing the Ubuntu 24.04 Desktop for Raspberry Pi image to an SSD drive with a USB3 interface (specifically; this issue does not occur when booting from an SD card), booting the drive on a Pi 4 or Pi 5, and running through the installer to the point where the (corrupted) slide deck starts to display during setup, the installer crashes. [ Workaround ] - This is a temporary fix, confirmed on a Pi 4 (would be grateful if - others can confirm the workaround on a wider variety of hardware). + At the time of writing, some workarounds have been found, but none that + consistently work on all boards with all drives. One workaround that has + worked on a Pi with a Samsung EVO SSD, and a Crucial SSD is as follows: + Before booting the image, find config.txt on the boot partition, and the "dtoverlay=vc4-kms-v3d" line within it. There will be two of these lines, you want the first one under an "[all]" section. Append ",cma-128" to the line. Specifically, the following section: - dtoverlay=vc4-kms-v3d - disable_fw_kms_setup=1 + dtoverlay=vc4-kms-v3d + disable_fw_kms_setup=1 Should become: - dtoverlay=vc4-kms-v3d,cma-128 - disable_fw_kms_setup=1 + dtoverlay=vc4-kms-v3d,cma-128 + disable_fw_kms_setup=1 Unmount the drive cleanly, boot it, and run through the installer. You may revert the change (if you wish) after successful installation. + + Another workaround, reported as working on a Pi 5 with an NVMe drive + attached over PCIe: + + Before booting the image, find config.txt on the boot partition. Under + the first "[all]" section append the following line: + + dtparam=pciex1 + + Unmount the drive cleanly, boot it, and run through the installer. + + Please note both workarounds have also been reported as failing with + certain drive combinations. [ Background ] Given this crash occurs immediately upon the (corrupted) slide deck starting, that it only occurs when booting from USB (but the exact same image works from an SD card), and that merely changing the pre- allocation of the contiguous memory area affects it, I suspect this at least related to (if not a duplicate of) LP: #2037015, particularly since a crash bug is now associated with it too, LP: #2062146. Still, I'll leave this open as a non-duplicate for now as I'm not positive of root-cause yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064208 Title: Installer crashes when booting from USB on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2064208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064208] [NEW] Installer crashes when booting from USB on Raspberry Pi
Public bug reported: After writing the Ubuntu 24.04 Desktop for Raspberry Pi image to an SSD drive with a USB3 interface (specifically; this issue does not occur when booting from an SD card), booting the drive on a Pi 4 or Pi 5, and running through the installer to the point where the (corrupted) slide deck starts to display during setup, the installer crashes. [ Workaround ] This is a temporary fix, confirmed on a Pi 4 (would be grateful if others can confirm the workaround on a wider variety of hardware). Before booting the image, find config.txt on the boot partition, and the "dtoverlay=vc4-kms-v3d" line within it. There will be two of these lines, you want the first one under an "[all]" section. Append ",cma-128" to the line. Specifically, the following section: dtoverlay=vc4-kms-v3d disable_fw_kms_setup=1 Should become: dtoverlay=vc4-kms-v3d,cma-128 disable_fw_kms_setup=1 Unmount the drive cleanly, boot it, and run through the installer. You may revert the change (if you wish) after successful installation. [ Background ] Given this crash occurs immediately upon the (corrupted) slide deck starting, that it only occurs when booting from USB (but the exact same image works from an SD card), and that merely changing the pre- allocation of the contiguous memory area affects it, I suspect this at least related to (if not a duplicate of) LP: #2037015, particularly since a crash bug is now associated with it too, LP: #2062146. Still, I'll leave this open as a non-duplicate for now as I'm not positive of root-cause yet. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064208 Title: Installer crashes when booting from USB on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2064208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861338] Re: RPI4 wifi unreliable when usb3 storage is attached
That's a different issue, LP: #2063365, which only started occurring after the recent wifi firmware bump -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861338 Title: RPI4 wifi unreliable when usb3 storage is attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063887] Re: debsums warning after upgrade to Ubuntu 24.04 (noble): changed file /etc/X11/xorg.conf.d/99-v3d.conf (from ubuntu-raspi-settings-desktop package)
** Changed in: ubuntu-raspi-settings (Ubuntu) Status: New => Triaged ** Changed in: ubuntu-raspi-settings (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063887 Title: debsums warning after upgrade to Ubuntu 24.04 (noble): changed file /etc/X11/xorg.conf.d/99-v3d.conf (from ubuntu-raspi-settings-desktop package) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-raspi-settings/+bug/2063887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052575] Re: [SRU] Update firmware to support autofocus
Re-uploaded with bug ref -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052575 Title: [SRU] Update firmware to support autofocus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-xilinx-ap1302/+bug/2052575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063445] [NEW] GIMP crashes on close in noble arm64
Public bug reported: On the Ubuntu Desktop for Raspberry Pi (arm64) under noble, GIMP is reliably crashing when closing the application with unsaved changes, and selecting "Discard Changes". Steps to reproduce: * sudo apt install gimp * Open GIMP with an image (right click image in Files, Open With..., select GIMP) * Make some changes to the image (scribble over it) * Close the application * Select Discard Changes * GIMP Crash Debug appears I'll attach the bug information from crash debug window ** Affects: gimp (Ubuntu) Importance: Undecided Status: New ** Attachment added: "gimp-crash.txt" https://bugs.launchpad.net/bugs/2063445/+attachment/5770223/+files/gimp-crash.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063445 Title: GIMP crashes on close in noble arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2063445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038669] Re: Add Raspberry Pi 5 support
I finally got around to testing this on noble: it's broken. Even more than it was in mantic where at least it'd *list* the camera modules. Now it can't even do that (but it works fine on RaspiOS with the same camera modules). Sigh. I'll release note this for now, and try and find time to dig into it next cycle. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038669 Title: Add Raspberry Pi 5 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2038669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062667] Re: Fails on (and should be removed from) raspi desktop
** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062667 Title: Fails on (and should be removed from) raspi desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060920] Re: Noble installer crashes on Raspberry Pi 400 when WPA3 times out/fails to connect
I *think* you may have run into the issue with the installer crashing on the timezone selection screen (which is directly after network selection and which had a fatal issue with an out of date library; LP: #1987454). That issue is now corrected on the current daily (from 4/22 which I'm ISO testing as a release candidate), and I'm unable to replicate a full crash when attempting to connect to a WPA3 AP. Rather, it just sits there and fails to connect to the AP. Incidentally, we do now have the firmware blobs that *allegedly* support WPA3 on the BCM43455 (used on the 3A+, 3B+, 4B, and 5) but apparently they only work with WPA3 under iwd (not wpa_supplicant) currently. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060920 Title: Noble installer crashes on Raspberry Pi 400 when WPA3 times out/fails to connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2060920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063255] Re: Cannot play audio via HDMI on server
** Summary changed: - Cannot play audio from server on older models + Cannot play audio via HDMI on server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063255 Title: Cannot play audio via HDMI on server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2063255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063255] Re: Cannot play audio from server on older models
Another interesting data-point: apparently mpg321 *isn't* broken on noble. It works, but only with the headphone output (on those models that have it, i.e. everything prior to the Pi 5). Same goes with ffmpeg; no buffer xruns when outputting to the headphone socket. Which leans me back towards "something iffy with vc4hdmi and ALSA"... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063255 Title: Cannot play audio from server on older models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2063255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063255] Re: Cannot play audio from server on older models
Hmm, I may have to revise this. It seems mpg321 (with ALSA, which is how I've always tested the audio output) just doesn't work at all on any model; just complains about libao driver everywhere. Meanwhile, ffmpeg (my backup) works happily on the 4 and 5, but just complains about buffer xrun errors on all the earlier models (and takes a bizarrely long time to respond to ctrl-C when it does). However, aplay (ALSA's own userspace utility) works happily, at least on the 3B+ where I tested it, but only plays WAV or PCM, not MP3s, which just adds more complexity to the testing script. Still, that *suggests* ALSA's operating correctly and perhaps it's just ffmpeg trying to allocate a buffer that's too small to avoid overrun on the older platforms (and mpg321's presumably just broken on noble). I'll leave this open for now, but I'd advise the kernel team to ignore it while I dig a bit deeper. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063255 Title: Cannot play audio from server on older models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2063255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063255] Re: Cannot play audio from server on older models
** Description changed: While attempting to play music as part of the ISO tests for the release, while the vc4hdmi sound card appears in /proc/asound/cards, the mpg321 player used by the tests (which has never worked *well* on the older models, but at least worked) failed with: - [0.029s] ubuntu@miss-piggy:~$ mpg321 -o alsa -a hw:1,0 test.mp3 - High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2, and 3. - Version 0.3.2-1 (2012/03/25). Written and copyrights by Joe Drew, - now maintained by Nanakos Chrysostomos and others. - Uses code from various people. See 'README' for more! - THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK! - Title : Love on a Real Train Artist : State Azure - Album : Dreams A Tribute to Tangerin Year : 2020 - Comment :Genre : AmbientElectronic + [0.029s] ubuntu@miss-piggy:~$ mpg321 -o alsa -a hw:1,0 test.mp3 + High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2, and 3. + Version 0.3.2-1 (2012/03/25). Written and copyrights by Joe Drew, + now maintained by Nanakos Chrysostomos and others. + Uses code from various people. See 'README' for more! + THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK! + Title : Love on a Real Train Artist : State Azure + Album : Dreams A Tribute to Tangerin Year : 2020 + Comment :Genre : AmbientElectronic - Playing MPEG stream from test.mp3 ... - MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo - Can't open libao driver with device hw:1,0 (is device in use?) + Playing MPEG stream from test.mp3 ... + MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo + Can't open libao driver with device hw:1,0 (is device in use?) I also tried ffmpeg (which usually works a bit better on the older models) and that fails with a constant series of ALSA buffer xrun errors. The specific models on which this has failed so far are the 2B - and 3B+. It appears to work happily on the 4B, though. + and 3B+. ffmpeg appears to work happily on the 4B, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063255 Title: Cannot play audio from server on older models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2063255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063255] [NEW] Cannot play audio from server on older models
Public bug reported: While attempting to play music as part of the ISO tests for the release, while the vc4hdmi sound card appears in /proc/asound/cards, the mpg321 player used by the tests (which has never worked *well* on the older models, but at least worked) failed with: [0.029s] ubuntu@miss-piggy:~$ mpg321 -o alsa -a hw:1,0 test.mp3 High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2, and 3. Version 0.3.2-1 (2012/03/25). Written and copyrights by Joe Drew, now maintained by Nanakos Chrysostomos and others. Uses code from various people. See 'README' for more! THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK! Title : Love on a Real Train Artist : State Azure Album : Dreams A Tribute to Tangerin Year : 2020 Comment :Genre : AmbientElectronic Playing MPEG stream from test.mp3 ... MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo Can't open libao driver with device hw:1,0 (is device in use?) I also tried ffmpeg (which usually works a bit better on the older models) and that fails with a constant series of ALSA buffer xrun errors. The specific models on which this has failed so far are the 2B and 3B+. It appears to work happily on the 4B, though. ** 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/2063255 Title: Cannot play audio from server on older models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2063255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062414] Re: busybox 1.36.1 FTBFS with current kernel headers on noble
** Bug watch added: Busybox Bugzilla #16042 https://bugs.busybox.net/show_bug.cgi?id=16042 ** Also affects: busybox via https://bugs.busybox.net/show_bug.cgi?id=16042 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/2062414 Title: busybox 1.36.1 FTBFS with current kernel headers on noble To manage notifications about this bug go to: https://bugs.launchpad.net/busybox/+bug/2062414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063204] Re: Desktop-Live ships /etc/netplan/01-network-manager-all.yaml in addition to /usr/lib/netplan/00-network-manager-all.yaml
Ah, so the code in ubuntu-settings postinst is taking care of deleting the file on existing systems (i.e. upgraders) but that doesn't matter for the fresh image where livecd-rootfs is presumably injecting the file after the package is installed as part of the image build. I ... thought I had a branch dealing with that in livecd-rootfs, but I can't find it now. Will prep another merge. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063204 Title: Desktop-Live ships /etc/netplan/01-network-manager-all.yaml in addition to /usr/lib/netplan/00-network-manager-all.yaml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2063204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060300] Re: KMS overlay causes OOM oops on 3A+
Have now also observed this on the Zero 2W with the current noble daily server image. Interestingly, it *didn't* occur directly on the image at first. This booted happily on the Zero 2W. However, this same card was then used to test a 3A+. On the 3A+ I regenerated the initramfs (testing a reported issue on low-memory boards), then moved the card back to the Zero 2W and observed the same OOM issue on boot as the 3A+ does without the CMA-128 workaround. I also tried re-generating the initrd on the Zero 2W, but it still booted happily after that without the workaround. This implies there's something about the initrd, which is triggering the issue (sizing, position in memory, I'm not sure?) but that the Zero 2W may coincidentally run into the issue in normal operation. Placing the CMA-128 workaround on the KMS overlay worked around the issue, so I'll now add a [pi02] section in the config.txt applying the same workaround for this board too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060300 Title: KMS overlay causes OOM oops on 3A+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2060300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062378] Re: Autopkgtests fail with version 2.3.3+dfsg-0ubuntu1
I'm sponsoring this under the assumption that the FFe from LP: #2054477 still applies (it covered the original upload that failed to pass autopkgtests; this upload is intended to correct that failure). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062378 Title: Autopkgtests fail with version 2.3.3+dfsg-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ogre-next/+bug/2062378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062667] [NEW] Fails on (and should be removed from) raspi desktop
Public bug reported: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 ** Affects: protection-domain-mapper (Ubuntu) Importance: Undecided Status: New ** Affects: qrtr (Ubuntu) Importance: Undecided Status: New ** Also affects: qrtr (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Fails (and should be removed from) raspi desktop + Fails on (and should be removed from) raspi desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062667 Title: Fails on (and should be removed from) raspi desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062564] Re: [FFe] Seed pemmican
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu-seeds/+git/ubuntu-seeds/+merge/463674 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062564 Title: [FFe] Seed pemmican To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pemmican/+bug/2062564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062564] [NEW] [FFe] Seed pemmican
Public bug reported: [ Impact ] Add pemmican to raspi server and desktop images in order that Pi 5 users can be notified if/when overcurrent or undervolt events occur (potentially resulting in brownout, data-corruption, and all manner of other symptoms typically caused as a result of undervolt). [ Test Plan ] On all supported models of Pi: * Boot the image with pemmican installed * Ensure boot proceeds normally with package installed and that no warnings appear On the Pi 5 specifically: * Boot the image normally * Ensure boot proceeds normally with package installed and that no warnings appear * Using bench power-supply to back-feed the Pi, lower voltage until brownout occurs * Reboot and ensure undervolt warning is shown * Shutdown and boot with PSU that cannot negotiate 5A * Ensure deficient PSU warning is shown On the Pi 5 desktop image specifically: * Boot desktop image * Attach USB load tester and raise current draw until USB ports fail * Ensure overcurrent warning is displayed [ Regression Potential ] Quite low given all the tests noted above have already been performed on all supported models. ** Affects: pemmican (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [FFe] seed pemmican + [FFe] Seed pemmican -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062564 Title: [FFe] Seed pemmican To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pemmican/+bug/2062564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061990] Re: Please RM armhf binaries
We now have some better confidence that the failure is purely test-suite based, and shouldn't affect the operation of the binary itself. Marking won't fix and leaving the armhf tests disabled until such time as they can be fixed properly (or removed). ** Changed in: mtd-utils (Ubuntu) Status: New => 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/2061990 Title: Please RM armhf binaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtd-utils/+bug/2061990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062414] Re: busybox 1.36.1 FTBFS with current kernel headers on noble
Revised patch with upstream bug links ** Patch added: "2-2062414.debdiff" https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2062414/+attachment/5767659/+files/2-2062414.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062414 Title: busybox 1.36.1 FTBFS with current kernel headers on noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2062414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062414] Re: busybox 1.36.1 FTBFS with current kernel headers on noble
Build reference: https://launchpad.net/ubuntu/+source/busybox/1:1.36.1-6ubuntu2/+build/28036868 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062414 Title: busybox 1.36.1 FTBFS with current kernel headers on noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2062414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062414] Re: busybox 1.36.1 FTBFS with current kernel headers on noble
** Patch added: "1-2062414.debdiff" https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2062414/+attachment/5767655/+files/1-2062414.debdiff ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062414 Title: busybox 1.36.1 FTBFS with current kernel headers on noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2062414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062414] [NEW] busybox 1.36.1 FTBFS with current kernel headers on noble
Public bug reported: The networking/tc.c unit in busybox relies upon the CBQ (class based queue) UAPI in the kernel. Unfortunately this was removed in [1]. At present, there is no upstream patch (or even bug report that I can find), and this close to the release patching the kernel to resolve things is not going to happen. Will attach a patch re-instating the defines from the removed headers. [1]: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/?id=33241dca486264193ed68167c8eeae1fb197f3df ** Affects: busybox (Ubuntu) Importance: Undecided Status: New ** Tags: rls-nn-incoming update-excuse ** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062414 Title: busybox 1.36.1 FTBFS with current kernel headers on noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2062414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038924] Re: No alsa sound cards on Pi 5
** Changed in: linux-raspi (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038924 Title: No alsa sound cards on Pi 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2038924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062176] [NEW] Cannot launch armhf containers on arm64 host under noble
Public bug reported: Under the current noble daily server image for Raspberry Pi (arm64 architecture) I cannot launch an armhf container image using lxd from the channel 5.21/stable/ubuntu-24.04 (build 28284). It *appears* to launch successfully, and lxd reports no error yet afterward the container is stopped: $ lxc launch ubuntu-daily:n/armhf nobletest Creating nobletest Starting nobletest $ lxc list +---+-+--+--+---+---+ |NAME | STATE | IPV4 | IPV6 | TYPE| SNAPSHOTS | +---+-+--+--+---+---+ | nobletest | STOPPED | | | CONTAINER | 0 | +---+-+--+--+---+---+ In case this was an issue with the current noble daily, I also attempted launching the mantic and jammy armhf images, but with the same symptoms: $ lxc launch ubuntu:m/armhf mantictest Creating mantictest Starting mantictest $ lxc list ++-+--+--+---+---+ |NAME| STATE | IPV4 | IPV6 | TYPE| SNAPSHOTS | ++-+--+--+---+---+ | nobletest | STOPPED | | | CONTAINER | 0 | ++-+--+--+---+---+ | mantictest | STOPPED | | | CONTAINER | 0 | ++-+--+--+---+---+ I attempted the same tests under the 23.10 server for Pi images (also arm64 host) and both containers launched successfully, so this appears to be an issue with lxd under noble specifically. ** Affects: lxd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062176 Title: Cannot launch armhf containers on arm64 host under noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2062176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061990] Re: Please RM armhf binaries
Potentially affected images: As noted above this potentially affects *any* armhf image with boot artifacts that require flashing (that are deb based). This potentially affects our older Pi server armhf images (which, although they don't use mtd-utils, do use flash-kernel). However, we're not producing Pi server armhf images this cycle and it is my understanding that do-release- upgrades has a quirk to prevent upgraders on that architecture. It does not affect our Pi desktop images, which have never been armhf based. This change potentially affects any flavours which produce such images. However, there has never (to my knowledge) been an official flavour with an armhf desktop image for the Pi. Further mitigation ideas: flash-kernel *could* be modified to merely recommend mtd-utils and still operate on platforms where mtd-utils itself isn't used for flashing boot artifacts (such as the Pi) but obviously this complicates the dependency situation (and seeds) on those platforms that *do* require mtd-utils. ** Description changed: LP: #2060214 (FTBFS) was eventually resolved by disabling failing tests on armhf to enable migration. Unfortunately, mtd-utils is the facility used by flash-kernel (on several boards, as it's used in the "generic" method) to flash boot artifacts to their destination. - Given that failure to flash these a successfully risks subsequent boot + Given that failure to flash these successfully risks subsequent boot failure (of a nature that is particularly difficult to resolve on certain armhf boards), and given that we're now not certain that the mechanism will operate correctly on armhf, please remove mtd-utils (and its dependency, flash-kernel) from armhf in noble. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061990 Title: Please RM armhf binaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtd-utils/+bug/2061990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061990] Re: Please RM armhf binaries
$ reverse-depends src:mtd-utils Reverse-Recommends == * 0x [armhf](for mtd-utils) * python3-binwalk (for mtd-utils) Reverse-Depends === * flash-kernel [arm64 armhf](for mtd-utils) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ reverse-depends -b src:mtd-utils Reverse-Testsuite-Triggers == * swupdate (for libubi-dev) * swupdate (for libmtd-dev) Reverse-Build-Depends = * swupdate (for libubi-dev) * swupdate (for libmtd-dev) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061990 Title: Please RM armhf binaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtd-utils/+bug/2061990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061990] Re: Please RM armhf binaries
Additional context: flash-kernel has several methods of "flashing" boot artifacts (bootloaders, kernel, initrd, etc.) on various boards. Flashing may actually mean flashing EEPROM (typically done via some other utility, in many cases mtd-utils -- mtd incidentally is "Memory Technology Device", often EEPROM), or may simply mean file-system copies (as in the raspi where most boot artifacts just sit on a FAT partition). Hence, if mtd-utils fails the scenarios range from "everything still works fine" all the way down to "bricked board". Given the potential range of outcomes, that the tests (but only the tests) indicate something is wrong, and that we have no other means of determining the outcome, I would prefer an abundance of caution and to simply prevent flashing in the first place. Additional mitigation: This only affects images that have deb-based boot artifacts like a bootloader and kernel. Container images are not affected, nor are snap- based images. After contacting hardware enablement, and certification we can't find anyone actually producing an armhf image this cycle (for noble) that contains such artifacts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061990 Title: Please RM armhf binaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtd-utils/+bug/2061990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060032] Re: Mitigate lack of space from new initramfs
I'll leave the flash-kernel portion of this open though, as it should not be attempting to flash stuff when the destination is going to run out of space. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060032 Title: Mitigate lack of space from new initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2060032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060032] Re: Mitigate lack of space from new initramfs
No, I'm wrong -- looks like 0.142ubuntu23 fixed it. I'll pull this hack back out, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060032 Title: Mitigate lack of space from new initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2060032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060925] Re: Bluetooth has incorrect MAC on Pi 3B
Fixed with empty transitional package (kernel setup handles this correctly) ** Changed in: pi-bluetooth (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/2060925 Title: Bluetooth has incorrect MAC on Pi 3B To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pi-bluetooth/+bug/2060925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061990] [NEW] Please RM armhf binaries
Public bug reported: LP: #2060214 (FTBFS) was eventually resolved by disabling failing tests on armhf to enable migration. Unfortunately, mtd-utils is the facility used by flash-kernel (on several boards, as it's used in the "generic" method) to flash boot artifacts to their destination. Given that failure to flash these a successfully risks subsequent boot failure (of a nature that is particularly difficult to resolve on certain armhf boards), and given that we're now not certain that the mechanism will operate correctly on armhf, please remove mtd-utils (and its dependency, flash-kernel) from armhf in noble. ** Affects: mtd-utils (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/2061990 Title: Please RM armhf binaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtd-utils/+bug/2061990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097467] Re: bash does not fulfill --rcfile option properly
Attaching new debdiff based on the current noble version. ** Patch added: "1097467-3.debdiff" https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+attachment/5766422/+files/1097467-3.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097467 Title: bash does not fulfill --rcfile option properly To manage notifications about this bug go to: https://bugs.launchpad.net/gnubash/+bug/1097467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061820] [NEW] 0.9.1-3ubuntu1 fails to build on armhf
Public bug reported: chibi-scheme 0.9.1-3ubuntu1 (uploaded as fix for LP: #2009694) fails to build on armhf: dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libchibi-scheme0/DEBIAN/symbols doesn't match completely debian/libchibi-scheme0.symbols --- debian/libchibi-scheme0.symbols (libchibi-scheme0_0.9.1-3ubuntu1_armhf) +++ dpkg-gensymbolsQAvlAq 2024-04-16 10:28:31.046898715 + @@ -38,6 +38,8 @@ sexp_bignum_sub@Base 0.8.0 sexp_bignum_sub_digits@Base 0.8.0 sexp_bignum_to_double@Base 0.8.0 + sexp_bignum_to_sint@Base 0.9.1-3ubuntu1 + sexp_bignum_to_uint@Base 0.9.1-3ubuntu1 sexp_bignum_zerop@Base 0.8.0 sexp_bootstrap_context@Base 0.8.0 sexp_buffered_flush@Base 0.8.0 @@ -71,6 +73,7 @@ sexp_complex_sub@Base 0.8.0 sexp_complex_tan@Base 0.8.0 sexp_cons_op@Base 0.8.0 + sexp_context_align_pos@Base 0.9.1-3ubuntu1 sexp_copy_bignum@Base 0.8.0 sexp_copy_list_op@Base 0.8.0 sexp_cos@Base 0.8.0 @@ -123,8 +126,8 @@ sexp_free_heap@Base 0.8.0 sexp_free_vars@Base 0.8.0 sexp_gc@Base 0.8.0 - sexp_gc_heap_pack@Base 0.8.0 - sexp_gc_heap_walk@Base 0.8.0 +#MISSING: 0.9.1-3ubuntu1# sexp_gc_heap_pack@Base 0.8.0 +#MISSING: 0.9.1-3ubuntu1# sexp_gc_heap_walk@Base 0.8.0 sexp_gc_init@Base 0.8.0 sexp_generate@Base 0.8.0 sexp_generate_op@Base 0.8.0 @@ -150,8 +153,8 @@ sexp_list_to_uvector_op@Base 0.9.0 sexp_list_to_vector_op@Base 0.8.0 sexp_listp_op@Base 0.8.0 - sexp_load_image@Base 0.8.0 - sexp_load_image_err@Base 0.8.0 +#MISSING: 0.9.1-3ubuntu1# sexp_load_image@Base 0.8.0 +#MISSING: 0.9.1-3ubuntu1# sexp_load_image_err@Base 0.8.0 sexp_load_module_file@Base 0.8.0 sexp_load_module_file_op@Base 0.8.0 sexp_load_op@Base 0.8.0 @@ -264,7 +267,7 @@ sexp_rest_unused_p@Base 0.8.0 sexp_reverse_op@Base 0.8.0 sexp_round@Base 0.8.0 - sexp_save_image@Base 0.8.0 +#MISSING: 0.9.1-3ubuntu1# sexp_save_image@Base 0.8.0 sexp_scheme_init@Base 0.8.0 sexp_set_current_environment@Base 0.8.0 sexp_set_parameter@Base 0.8.0 The issue is known upstream, but has no resolution at this time. Requesting removal of armhf binaries. ** Affects: chibi-scheme (Ubuntu) Importance: Undecided Status: New ** Affects: chibi-scheme (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #981872 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981872 ** Also affects: chibi-scheme (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981872 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/2061820 Title: 0.9.1-3ubuntu1 fails to build on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chibi-scheme/+bug/2061820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061552] Re: 0.9.3+git20100816-1build2 fails to build on armhf
Already done ** Changed in: matchbox-panel (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061552 Title: 0.9.3+git20100816-1build2 fails to build on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/matchbox-panel/+bug/2061552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2009694] Re: [SRU] package chibi-scheme-images 0.9.1-3 failed to install in Noble
Noble version sponsored; mantic and jammy versions may need adjustment
as they build with the following lintian error:
E: not-binnmuable-all-depends-any
N:
N: The package is not safely binNMUable because an arch:all package depends
on an arch:any package
N: with a strict (= ${source:Version}), or similar, relationship.
N:
N: It is not possible for arch:all packages to depend so strictly on arch:any
packages while having
N: the package binNMUable, so please use one of these, whichever is more
appropriate:
N:
N: Depends: arch_any (>= ${source:Version})
N: Depends: arch_any (>= ${source:Version}),
N: arch_any (<< ${source:Version}.1~)
N:
N: Visibility: error
N: Show-Always: no
N: Check: debian/version-substvars
N:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2009694
Title:
[SRU] package chibi-scheme-images 0.9.1-3 failed to install in Noble
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chibi-scheme/+bug/2009694/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2009694] Re: [SRU] package chibi-scheme-images 0.9.1-3 failed to install in Noble
Looks good; adding targets for jammy and mantic, and sponsoring. ** Also affects: chibi-scheme (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: chibi-scheme (Ubuntu Mantic) 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/2009694 Title: [SRU] package chibi-scheme-images 0.9.1-3 failed to install in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chibi-scheme/+bug/2009694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2045034] Re: [SRU] vpoll-dkms FTFBS with linux 6.5 in jammy
Updating test case to make clear that both the release and hwe kernels require testing for this patch, but otherwise looks good -- sponsoring. ** Description changed: [Impact] libvpoll-eventfd is completely unusable as it will fail to install for a Jammy user with the following error: ./include/linux/export.h:29:22: error: passing argument 1 of ‘class_create’ from incompatible pointer type [-Werror=incompatible-pointer-types] 29 | #define THIS_MODULE (&__this_module) | ~^~~ | | | struct module * /var/lib/dkms/vpoll/0.1/build/vpoll.c:117:44: note: in expansion of macro ‘THIS_MODULE’ [Test case] - A simple testcase to confirm the build failure is fixed + To be tested on both the release kernel (5.15), which is currently + unaffected but may be affected by the fix, and the hwe kernel (6.5), + which is intended to be fixed by this SRU. + + The following should fail with the current, and succeed with the + proposed vpoll-dkms under kernel 6.5, and should be succeed under both + with release kernel 5.15: $ sudo apt install vpoll-dkms - Another testcase to test the basic sanity of the package to confirm its working: + Another testcase to test the basic sanity of the package to confirm its + working (again, test on both release and hwe kernels): + 1. Build the attached test_vpoll.c 2. Execute it, it will use the kernel driver for execution. [ Where problems could occur ] Users of vpoll may experience regressions (restricted to this module) using the new 6.5 kernel. [ Other Info ] Backport the changes in the vpoll kernel module to properly support the new linux 6.5 kernel ABI. [ Original Bug Description ] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: vpoll-dkms 0.1-2ubuntu1 ProcVersionSignature: User Name 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/vdb) Date: Tue Nov 28 13:50:29 2023 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: libvpoll-eventfd UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2045034 Title: [SRU] vpoll-dkms FTFBS with linux 6.5 in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpoll-eventfd/+bug/2045034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060212] Re: U-Boot misses to invoke the UEFI boot manager
This looks good to me, and libelf1t64 is now built in armhf. Sponsoring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060212 Title: U-Boot misses to invoke the UEFI boot manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2060212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2009885] Re: Timeshift 21.09.1-1 broken after Rsync upgrade to 3.2.7-0ubuntu0.22.04.2
Patch looks mostly good. Needed a couple of trivial changes (run update- maintainer to deal with maintainer address in d/control, and add bug-ref in d/changelog), but I've sponsored with those changes, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2009885 Title: Timeshift 21.09.1-1 broken after Rsync upgrade to 3.2.7-0ubuntu0.22.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/timeshift/+bug/2009885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061552] [NEW] 0.9.3+git20100816-1build2 fails to build on armhf
Public bug reported: matchbox-panel 0.9.3+git20100816-1build2 fails to build on armhf: panel.c: In function ‘panel_main’: panel.c:1026:7: error: implicit declaration of function ‘msg_set_timeout’ [-Werror=implicit-function-declaration] 1026 | msg_set_timeout (panel, , ); | ^~~ This is due to different build-flags on armhf (specifically -Werror=implicit-function-declaration): gcc -DHAVE_CONFIG_H -I. -I.. -DDATADIR=\"/usr/share\" -DPKGDATADIR=\"/usr/share/matchbox\" -DPREFIX=\"/usr\" -g -Wall -fno- strict-aliasing -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -pthread -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=3 -g -O2 -Werror=implicit-function-declaration -ffile-prefix- map=/<>=. -fstack-protector-strong -Wformat -Werror=format- security -fno-stack-clash-protection -fdebug-prefix- map=/<>=/usr/src/matchbox-panel-0.9.3+git20100816-1build2 -c -o panel.o panel.c ** Affects: matchbox-panel (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/2061552 Title: 0.9.3+git20100816-1build2 fails to build on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/matchbox-panel/+bug/2061552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970521] Re: [SRU] boinc-client crashes when started with core dump on Xubuntu 22.04
Looks good to me; sponsoring. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970521 Title: [SRU] boinc-client crashes when started with core dump on Xubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1970521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976312] Re: [SRU] Pathological wont accept any input
Looks good to me! Sponsoring. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976312 Title: [SRU] Pathological wont accept any input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pathological/+bug/1976312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058917] Re: cvise 2.10.0-1 still depends on python-pytest-flake8 although upstream dropped it
Now builds happily on noble; sponsoring. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058917 Title: cvise 2.10.0-1 still depends on python-pytest-flake8 although upstream dropped it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cvise/+bug/2058917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054477] Re: [FFe] Update ogre-next to 2.3.3 for Noble
I've removed ubuntu-sponsors for now, but please feel free to re- subscribe when it's clear ignition-cmake is also ack'd for FFe. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054477 Title: [FFe] Update ogre-next to 2.3.3 for Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ignition-cmake/+bug/2054477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054477] Re: [FFe] Update ogre-next to 2.3.3 for Noble
Okay, ogre-next looks good for sponsoring, so I'm going ahead with that one. I'm not clear from the above if FFe acceptance was given for ignition-cmake so I'm leaving that for now. One thing to bear in mind: the ogre-next build was pretty clean but did throw up some lintian warnings about obsolete packages (specifically libgl1-mesa-dev=>libgl-dev, libfreetype6-dev=>libfreetype-dev, and pkg- config=>pkgconf). I tried a quick test-build on amd64 to see if those broke the build and they didn't (but that doesn't mean the result worked or would on all archs, so I'm not uploading with that change), but it's something that may be worth checking for the future. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054477 Title: [FFe] Update ogre-next to 2.3.3 for Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ignition-cmake/+bug/2054477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052575] Re: [SRU] Update firmware to support autofocus
Okay, this looks good, sponsoring packages from PPA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052575 Title: [SRU] Update firmware to support autofocus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-xilinx-ap1302/+bug/2052575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1987454] Re: Port ubiquity to libsoup3 - ubiquity crashes if gir1.2-soup-3.0 is installed in live system
** Merge proposal linked: https://code.launchpad.net/~waveform/ubiquity/+git/ubiquity/+merge/464248 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1987454 Title: Port ubiquity to libsoup3 - ubiquity crashes if gir1.2-soup-3.0 is installed in live system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1987454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038924] Re: No alsa sound cards on Pi 5
Patched in pi-gadget classic branch with commit https://github.com/snapcore/pi- gadget/commit/cebff92bd4b67d1bfffab5d98cdcefa38809b62e ** Changed in: linux-raspi (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038924 Title: No alsa sound cards on Pi 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2038924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060730] Re: totem cannot install codecs via packagekit
Sorry, I should give a bit more context on this issue to clarify things. The test for this issue comes from the ISO tests for the Ubuntu Desktop for Raspberry Pi images. The test intends to check whether a fresh install can play a video "out of the box". The video used in the test is https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4 which is downloaded and opened normally. The video deliberately uses a codec that isn't seeded and installed by default (but is a commonly used format) in the expectation that totem will guide the user through installing the necessary bits (which it used to back in groovy, but doesn't since -- incidentally the reason this wasn't noticed in jammy is because it failed to even open the video at that point, but that's now been fixed). Seeding gstreamer1.0-packagekit is probably fine (the whole of gstreamer's in main). Seeding gnome-software is likely not (given we're using snap-store for software delivery currently). Is app-center intended to fill that gap in future? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060730 Title: totem cannot install codecs via packagekit To manage notifications about this bug go to: https://bugs.launchpad.net/app-center/+bug/2060730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097467] Re: bash does not fulfill --rcfile option properly
Bah, looks like this upload got accidentally dropped by the subsequent merge for noble. I'll rebase and re-proposed it when I've got some time... ** Changed in: bash (Ubuntu) Status: Fix Committed => Confirmed ** Changed in: bash (Ubuntu) Assignee: Dan Bungert (dbungert) => 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/1097467 Title: bash does not fulfill --rcfile option properly To manage notifications about this bug go to: https://bugs.launchpad.net/gnubash/+bug/1097467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929791] Re: Bluetooth does not start if system boots from USB
I haven't managed to reproduce this on several systems (pi4 booting from USB, pi5 booting from NVMe, etc). Setting to incomplete until anyone can come up with a firm reproduction case. ** Changed in: pi-bluetooth (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/1929791 Title: Bluetooth does not start if system boots from USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1929791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961907] Re: Missing firmware link for Pi Zero 2
Fixed in linux-firmware-raspi 10 ** Changed in: linux-firmware-raspi2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961907 Title: Missing firmware link for Pi Zero 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1961907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971734] Re: Direct firmware load for brcm/brcmfmac43455-sdio.txt failed with error -2
This was fixed in linux-firmware-raspi 10 (finally :) ** Changed in: linux-firmware-raspi2 (Ubuntu Bionic) Status: New => Won't Fix ** Changed in: linux-firmware-raspi2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971734 Title: Direct firmware load for brcm/brcmfmac43455-sdio.txt failed with error -2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1971734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1982839] Re: [SRU] veusz fails to start under Python 3.10
Looks like this was fixed with a sync from Debian. ** Changed in: veusz (Ubuntu Jammy) Status: Confirmed => Fix Released ** Changed in: veusz (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/1982839 Title: [SRU] veusz fails to start under Python 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/veusz/+bug/1982839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
