[Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE
We are seeing this issue with Ubuntu Core 24 too, for instance when running logger from a confined snap. The workaround of adding "attach_disonnected attach_disconnected.path=/run/" does work as well. As an interesting data point, I have done some experiments and I see that using systemd 253.5-1ubuntu1 (an older version that was at some point in noble) with kernel 6.8 does not show the issue, while systemd 255.4-1ubuntu8 with kernel 6.8 triggers it. So some change in systemd triggers this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: Services fail to start in noble deployed with TPM+FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE
(note that the version of systemd in my comment refers to the version in the UC initramfs) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: Services fail to start in noble deployed with TPM+FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058976] Re: Configuration files for networkd are created when NetworkManager is the default renderer
To be clear, that carrier is set to "failed" when retriggering uevents is not the main problem. The main problem is that after 5-10 minutes, networkd silently takes control again of the ethernet interface. The retriggering of uevents and the reaction on the networkd side is just an indication that it still cares about the interface. Maybe a better way to check if the issue is around without having to wait for minutes would be to look at /run/systemd/netif/links/* and check if the content still references the removed .network files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058976 Title: Configuration files for networkd are created when NetworkManager is the default renderer To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2058976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060676] Re: login: remove pam_lastlog.so from config
/etc/pam.d/login references the module: sessionoptional pam_lastlog.so -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060676 Title: login: remove pam_lastlog.so from config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2060676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060676] [NEW] login: remove pam_lastlog.so from config
Public bug reported: Imported from Debian bug http://bugs.debian.org/1068229: Package: libpam-modules Version: 1.5.3-6 Severity: normal I noticed the following line in my logs: login[2449]: PAM unable to dlopen(pam_lastlog.so): /usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory I looked in the deb files from snapshot.debian.org, and noticed the last version that had it was 1.5.2-9.1 - starting from 1.5.3-1 it disappeared. Maybe it's fallout from the time_t transition and you're already aware of it, in which case feel free to close. Thanks, -- M -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libpam-modules depends on: ii debconf [debconf-2.0] 1.5.86 ii libaudit1 1:3.1.2-2.1 ii libc6 2.37-15.1 ii libcrypt1 1:4.4.36-4 ii libpam-modules-bin 1.5.3-6 ii libpam0g 1.5.3-6 ii libselinux13.5-2 ii libsystemd0255.4-1+b1 libpam-modules recommends no packages. libpam-modules suggests no packages. -- debconf information excluded ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Affects: shadow (Debian) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #1068229 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068229 ** Changed in: shadow (Debian) Remote watch: None => Debian Bug tracker #1068229 ** Changed in: shadow (Ubuntu) Milestone: None => noble-updates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060676 Title: login: remove pam_lastlog.so from config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2060676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973835] Re: Ubuntu 22.04, Bluetooth issues
** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** No longer affects: snappy-hwe-snaps -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973835 Title: Ubuntu 22.04, Bluetooth issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1973835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976352] Re: The plymouth label plugin pulls in too many dependencies
** Summary changed: - The plymouth label pulls in too many dependencies + The plymouth label plugin pulls in too many dependencies ** Description changed: - The plymouth label pulls in too many dependencies (libpango, libcairo, X - libs, etc.). This is an issue for integration in the initramfs. + The plymouth label plugin pulls in too many dependencies (libpango, + libcairo, X libs, etc.). This is an issue for integration in the + initramfs. There is an alternative plugin (label-ft) that has been proposed upstream: https://gitlab.freedesktop.org/plymouth/plymouth/-/merge_requests/91 I have attached a debdiff that integrates that plugin in our packaging. As it is a separate plugin, core parts of plymouth are only slightly changed. The package built for kinetic can be found here too: https://launchpad.net/~alfonsosanchezbeato/+archive/ubuntu/build2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976352 Title: The plymouth label plugin pulls in too many dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1976352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976352] [NEW] The plymouth label pulls in too many dependencies
Public bug reported: The plymouth label pulls in too many dependencies (libpango, libcairo, X libs, etc.). This is an issue for integration in the initramfs. There is an alternative plugin (label-ft) that has been proposed upstream: https://gitlab.freedesktop.org/plymouth/plymouth/-/merge_requests/91 I have attached a debdiff that integrates that plugin in our packaging. As it is a separate plugin, core parts of plymouth are only slightly changed. The package built for kinetic can be found here too: https://launchpad.net/~alfonsosanchezbeato/+archive/ubuntu/build2 ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Patch added: "label-ft.debdiff" https://bugs.launchpad.net/bugs/1976352/+attachment/5594049/+files/label-ft.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976352 Title: The plymouth label pulls in too many dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1976352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975688] [NEW] Accessing squashfs with lzma compression is ~16% slower in 5.15 when compared to 5.4, on an RPi3 B+
Public bug reported:
On the server image on an RPi3 B+, I run this script:
```
#!/bin/bash -eu
mount_and_read()
{
local snap=$1
local mnt_d=$2
mount "$snap" "$mnt_d"
# We should not use /dev/null here, see
#
https://unix.stackexchange.com/questions/512362/why-does-tar-appear-to-skip-file-contents-when-output-file-is-dev-null
tar -cO "$mnt_d"/ > /dev/zeros
}
snap_d=$(mktemp -d)
for i in {1..3}; do
sync && echo 3 > /proc/sys/vm/drop_caches
time mount_and_read "$1" "$snap_d"
umount "$snap_d"
done
rmdir "$snap_d"
```
With these commands:
$ sudo mount -t tmpfs -o size=400M tmpfs tmpfs/
$ cd tmpfs
$ snap download core22
$ sudo ../measure-snap-mnt.sh core22_169.snap
I get these results on 20.04:
real0m21.667s
user0m0.302s
sys 0m20.299s
real0m21.650s
user0m0.351s
sys 0m20.417s
real0m21.718s
user0m0.285s
sys 0m20.528s
On 22.04 server image:
real0m25.084s
user0m0.407s
sys 0m23.778s
real0m25.064s
user0m0.397s
sys 0m23.768s
real0m25.051s
user0m0.369s
sys 0m23.803s
Which is a considerable difference. This affects snaps compressed with
xz, and although these measurements are for server the bigger impact is
on UC images, where the boot time increases considerably because of
this.
** Affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Accessing squashfs with lzma compression is ~16% slower in 5.15 when compared
to 5.4
+ Accessing squashfs with lzma compression is ~16% slower in 5.15 when compared
to 5.4, on an RPi3 B+
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975688
Title:
Accessing squashfs with lzma compression is ~16% slower in 5.15 when
compared to 5.4, on an RPi3 B+
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1975688/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971430] [NEW] lz4 is not a dependency of initramfs-tools-core
Public bug reported: lz4 is not a dependency of initramfs-tools-core, although it uses lz4cat in the unmkinitramfs script. ** Affects: initramfs-tools (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/1971430 Title: lz4 is not a dependency of initramfs-tools-core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1971430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968617] Re: uc22 no serial console on rpi
@Paul is this still happening for you? I think I saw some comment in mattermost saying this was not happening anymore. I know that at some point in time the pi gadget missed enable_uart=1 in config.txt, but this was fixed and hopefully already released to beta. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968617 Title: uc22 no serial console on rpi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1968617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968111] Re: uc22 rpi3 ethernet getting renamed on every boot
Reported upstream: https://github.com/raspberrypi/firmware/issues/1720 ** Bug watch added: github.com/raspberrypi/firmware/issues #1720 https://github.com/raspberrypi/firmware/issues/1720 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968111 Title: uc22 rpi3 ethernet getting renamed on every boot To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1968111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968111] Re: uc22 rpi3 ethernet getting renamed on every boot
After debugging the driver, it looked like it was not able to find the device tree node with the MAC address, and was therefore assigning a random MAC address. Further debugging showed that the device was actually being detected as an RPi3b instead of an RPi3b+: $ cat /proc/device-tree/compatible raspberrypi,3-model-b\0brcm,bcm2837\0 While in rpi jammy classic images you see: $ cat /proc/device-tree/compatible raspberrypi,3-model-b-plus\0brcm,bcm2837\0 Even though all firmware and device trees are the same. The only difference was that in UC22 we set os_prefix [1] to ask the firmware to load files from a different folder. After copying to the root of the seed partition kernel, initrd, device trees, and cmdline.txt files, I removed the os_prefix and rebooted. After that, an RPi3b+ is properly detected and the MAC has a fixed address. So, it turns out that this is a firmware bug in the implementation of os_prefix. [1] https://www.raspberrypi.com/documentation/computers/config_txt.html#os_prefix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968111 Title: uc22 rpi3 ethernet getting renamed on every boot To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1968111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968111] Re: uc22 rpi3 ethernet getting renamed on every boot
** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968111 Title: uc22 rpi3 ethernet getting renamed on every boot To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1968111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960340] Re: gnu-efi sets a wrong number of symbols in the COFF header
** Patch added: "gnu-efi.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnu-efi/+bug/1960340/+attachment/5559760/+files/gnu-efi.debdiff ** Description changed: According to what the spec says about the number of symbols [1]: "This value should be zero for an image because COFF debugging information is deprecated." + Upstream commit fixing this: https://sourceforge.net/p/gnu- + efi/code/ci/31a6aab44cf5a2fdaf746caf67cab371f9b748af/ + [1] https://docs.microsoft.com/en-us/windows/win32/debug/pe-format -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960340 Title: gnu-efi sets a wrong number of symbols in the COFF header To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnu-efi/+bug/1960340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960340] [NEW] gnu-efi sets a wrong number of symbols in the COFF header
Public bug reported: According to what the spec says about the number of symbols [1]: "This value should be zero for an image because COFF debugging information is deprecated." [1] https://docs.microsoft.com/en-us/windows/win32/debug/pe-format ** Affects: gnu-efi (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/1960340 Title: gnu-efi sets a wrong number of symbols in the COFF header To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnu-efi/+bug/1960340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960300] Re: llvm-objcopy cannot generate EFI images valid for Ubuntu Core on arm64
** Summary changed: - llvm-objcopy cannot generate EFI images valid for Ubuntu Core + llvm-objcopy cannot generate EFI images valid for Ubuntu Core on arm64 ** Description changed: - llvm-objcopy cannot generate EFI images valid for Ubuntu Core, due to - some bugs already fixed in upstream: + llvm-objcopy cannot generate EFI images valid for Ubuntu Core on arm64, + due to some bugs already fixed in upstream: https://llvm.org/PR51243 https://llvm.org/PR51244 Patches fixing the issues: https://github.com/llvm/llvm-project/commit/cdd407286a9652ec62b33f437a298754fe3ba7ab https://github.com/llvm/llvm-project/commit/b25ab4f313f38d3dee9674789cf56b9143515034 https://github.com/llvm/llvm-project/commit/b33fd3177229c67fe44b65fff8666a7746595daa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960300 Title: llvm-objcopy cannot generate EFI images valid for Ubuntu Core on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-13/+bug/1960300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960300] Re: llvm-objcopy cannot generate EFI images valid for Ubuntu Core
** Patch added: "llvm-toolchain-13-objcopy.debdiff" https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-13/+bug/1960300/+attachment/5559660/+files/llvm-toolchain-13-objcopy.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960300 Title: llvm-objcopy cannot generate EFI images valid for Ubuntu Core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-13/+bug/1960300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960300] [NEW] llvm-objcopy cannot generate EFI images valid for Ubuntu Core
Public bug reported: llvm-objcopy cannot generate EFI images valid for Ubuntu Core, due to some bugs already fixed in upstream: https://llvm.org/PR51243 https://llvm.org/PR51244 Patches fixing the issues: https://github.com/llvm/llvm-project/commit/cdd407286a9652ec62b33f437a298754fe3ba7ab https://github.com/llvm/llvm-project/commit/b25ab4f313f38d3dee9674789cf56b9143515034 https://github.com/llvm/llvm-project/commit/b33fd3177229c67fe44b65fff8666a7746595daa ** Affects: llvm-toolchain-13 (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/1960300 Title: llvm-objcopy cannot generate EFI images valid for Ubuntu Core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-13/+bug/1960300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959570] Re: netplan crashes on UbuntuCore with the network-manager snap installed
FTR, there is an alias registered in the store for network- mananger.nmcli -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959570 Title: netplan crashes on UbuntuCore with the network-manager snap installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1959570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed
With systemd debug trace enabled. Look for Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=RestartUnit cookie=22 reply_cookie=0 signature=ss error-name=n/a error-message=n/a ** Attachment added: "journal-debug.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1958676/+attachment/5556977/+files/journal-debug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958676 Title: error: too early for operation, device not yet seeded or device model not acknowledged Install failed To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1958676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed
Full journal attached ** Attachment added: "journal-fail.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1958676/+attachment/5556929/+files/journal-fail.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958676 Title: error: too early for operation, device not yet seeded or device model not acknowledged Install failed To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1958676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed
This is what I see in a jammy lxd container: Jan 21 17:47:55 jammy systemd[1]: Starting Load AppArmor profiles managed internally by snapd... Jan 21 17:47:55 jammy systemd[1]: Condition check resulted in Auto import assertions from block devices being skipped. Jan 21 17:47:55 jammy systemd[1]: Condition check resulted in Automatically repair incorrect owner/permissions on core devices being skipped. Jan 21 17:47:55 jammy systemd[1]: Condition check resulted in Wait for the Ubuntu Core chooser trigger being skipped. Jan 21 17:47:55 jammy snapd-apparmor[1217]: /usr/lib/snapd/snapd-apparmor: 47: ns_stacked: not found Jan 21 17:47:55 jammy snapd-apparmor[1217]: /usr/lib/snapd/snapd-apparmor: 48: ns_name: not found Jan 21 17:47:55 jammy systemd[1]: Starting Socket activation for snappy daemon... Jan 21 17:47:55 jammy snapd-apparmor[1220]: find: ‘/var/lib/snapd/apparmor/profiles/’: No such file or directory Jan 21 17:47:55 jammy systemd[1]: Listening on Socket activation for snappy daemon. Jan 21 17:47:55 jammy systemd[1]: Starting Wait until snapd is fully seeded... Jan 21 17:47:55 jammy systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Jan 21 17:47:55 jammy systemd[1]: Starting Snap Daemon... Jan 21 17:47:55 jammy systemd[1]: Condition check resulted in Timer to automatically fetch and run repair assertions being skipped. Jan 21 17:47:55 jammy systemd[1]: snapd.socket: Deactivated successfully. Jan 21 17:47:55 jammy systemd[1]: Closed Socket activation for snappy daemon. Jan 21 17:47:55 jammy systemd[1]: Stopping Socket activation for snappy daemon... Jan 21 17:47:55 jammy systemd[1]: snapd.socket: Socket service snapd.service already active, refusing. Jan 21 17:47:55 jammy systemd[1]: Failed to listen on Socket activation for snappy daemon. Jan 21 17:47:55 jammy systemd[1]: Dependency failed for Snap Daemon. Jan 21 17:47:55 jammy systemd[1]: snapd.service: Job snapd.service/start failed with result 'dependency'. Jan 21 17:47:55 jammy systemd[1]: snapd.service: Triggering OnFailure= dependencies. Jan 21 17:47:55 jammy systemd[1]: Dependency failed for Wait until snapd is fully seeded. Jan 21 17:47:55 jammy systemd[1]: snapd.seeded.service: Job snapd.seeded.service/start failed with result 'dependency'. Jan 21 17:47:55 jammy systemd[1]: Starting Failure handling of the snapd snap... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958676 Title: error: too early for operation, device not yet seeded or device model not acknowledged Install failed To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1958676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948476] Re: [SRU] Allow target units to fail
This fixes https://github.com/snapcore/core-initrd/issues/33. Tested by building a core20 snap from focal proposed. Before: [6.611137] systemd[1]: systemd 245.4-4ubuntu3.13 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid) [6.628034] systemd[1]: Detected virtualization kvm. [6.629644] systemd[1]: Detected architecture x86-64. [6.706930] systemd[1]: Set hostname to . [7.212069] systemd[1]: emergency.target: Requested dependency OnFailure=reboot.target ignored (target units cannot fail). [7.499630] systemd[1]: Unnecessary job for /dev/vda4 was removed. With the change: [6.160462] systemd[1]: systemd 245.4-4ubuntu3.14 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid) [6.164774] systemd[1]: Detected virtualization kvm. [6.165851] systemd[1]: Detected architecture x86-64. [6.176059] systemd[1]: Set hostname to . [6.521391] systemd[1]: Unnecessary job for /dev/vda4 was removed. ** Bug watch added: github.com/snapcore/core-initrd/issues #33 https://github.com/snapcore/core-initrd/issues/33 ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948476 Title: [SRU] Allow target units to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1948476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943564] Re: [SRU] Backport xrt 202020.2.8.743-0ubuntu1 to focal
** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943564 Title: [SRU] Backport xrt 202020.2.8.743-0ubuntu1 to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrt/+bug/1943564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943564] Re: [SRU] Backport xrt 202020.2.8.743-0ubuntu1 to focal
Search for "Tags:", it is right under the bug description. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943564 Title: [SRU] Backport xrt 202020.2.8.743-0ubuntu1 to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrt/+bug/1943564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948807] Re: Boot time from snap in 20/stable increses boot time on 3.5 seconds
snaps and dmesg when building from model ** Attachment added: "stable.txt" https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1948807/+attachment/5536290/+files/stable.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948807 Title: Boot time from snap in 20/stable increses boot time on 3.5 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1948807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948807] Re: Boot time from snap in 20/stable increses boot time on 3.5 seconds
snaps and dmesg from cdimage ** Attachment added: "cdimage.txt" https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1948807/+attachment/5536289/+files/cdimage.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948807 Title: Boot time from snap in 20/stable increses boot time on 3.5 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1948807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948807] [NEW] Boot time from snap in 20/stable increses boot time on 3.5 seconds
Public bug reported: I am seeing what looks as a regression in pi-kernel snap for UC20: there are around 3.5 additional seconds spent in boot time. In the image from cdimage (2021-06-30), I see: [1.856540] random: crng init done [1.871798] loop: module loaded (see https://paste.ubuntu.com/p/CkfWXY5Vgf/) while if I build an image from latest snaps in the 20/stable channel, I get: [1.855481] random: crng init done [5.349491] loop: module loaded (see https://paste.ubuntu.com/p/CNt42gdDcZ/) The pi-kernel snap revision is 353. ** 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/1948807 Title: Boot time from snap in 20/stable increses boot time on 3.5 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1948807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943564] Re: [SRU] Backport xrt 202020.2.8.743-0ubuntu1 to focal
@Tony could you please change the tag from verification-needed-focal to verification-done-focal? Also it would be good if you paste the output of "apt policy xrt" on your testing device, to make sure the version tested is the right one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943564 Title: [SRU] Backport xrt 202020.2.8.743-0ubuntu1 to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrt/+bug/1943564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948476] [NEW] [SRU] Allow target units to fail
Public bug reported: [Impact] A systemd regression in focal made it think that target units cannot fail, which produced warnings like: emergency.target: Requested dependency OnFailure=reboot.target ignored (target units cannot fail). So the OnFailure settings are ignored for targets (see https://github.com/snapcore/core-initrd/issues/33 for details). Upstream fixed the issue in v246: https://github.com/systemd/systemd/commit/94d1ddbd7cd15b1073757eb5ae0645c83f0b414c [Test Plan] Test on a UC system and check that the above warnings are not shown anymore. Check that when a target service type fails, the OnFailure setting is used and the mentioned service is run. [Where problems could occur] Issues might happen if some target has an OnFailure setting that was never run in the past because of this bug, and the behavior is not really right because it was never tested. However, OnFailure is not used that much on 20.04 in target services: /lib/systemd $ find . -name \*.target | xargs grep OnFailure /lib/systemd $ /etc/systemd $ find . -name \*.target | xargs grep OnFailure /etc/systemd $ I've seen it only in emergency.target for UC20. [Other Info] None ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "target-units-can-fail.patch" https://bugs.launchpad.net/bugs/1948476/+attachment/5535284/+files/target-units-can-fail.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948476 Title: [SRU] Allow target units to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1948476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943542] Re: [SRU] Create package for focal
Tested on kria platform, the reboot did work after updating the firmware: ubuntu@kria:~$ apt policy xlnx-kria-firmware xlnx-kria-firmware: Installed: 0.6~20.04.1 Candidate: 0.6~20.04.1 Version table: *** 0.6~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages 100 /var/lib/dpkg/status ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943542 Title: [SRU] Create package for focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xlnx-kria-firmware/+bug/1943542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945965] Re: vitis-ai 1.3.2 contains 1.3.1 libraries
This is actually, for my understanding, a bug in Vitis AI 1.3.2 code, that did not change the libraries version properly when it increased the version (the package itself is taking the sources from https://github.com/Xilinx/Vitis-AI/releases/tag/v1.3.2). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945965 Title: vitis-ai 1.3.2 contains 1.3.1 libraries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vitis-ai/+bug/1945965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1943984] Re: No archive files for static compilation are included in the -dev package
On Wed, Sep 29, 2021 at 1:35 PM Mattia Rizzolo <1943...@bugs.launchpad.net> wrote: > > As a member of the Debian LibreOffice Team, and also as an Ubuntu > Developer, I'm likewise not convinced that starting to build and ship > graphite2's static library is a really useful thing to do. > > I'm personally generically against static libraries, since I regularly see > grief caused by poor tracking of statically-builtand or embedded things. Well, I have seen grief caused by shared libraries pulling too many dependencies or by shared libraries updates that break applications even though in theory the ABI compatibility has been kept. Also, there is actually a trend towards static compilation (golang, rust), so I do not think I'm the only one seeing this. But that is not really relevant. There are valid uses of static libraries, and the developers should have the option to choose between shared and static. The patch does not prevent using shared libraries, it just gives more options to application developers. > > And I don't really buy the need to save space when talking about a 137328 > bytes shared lib (taken from the last build of graphite2 in Sid, that's the > size of the .so). > It feels like you are building some kind to system image that you'd then > flash into some embedded thingy. I don't think there is much value in > saving...what, a dozen kB perhaps? (I haven't tried building the .a, so > happy to get the number). If your system is so constrained in space you're > likely going to need some much more dedicated work to reduce the size of > all components anyway; similarly if you are after the (normally > uncountable) performance improvement of statically linked binaries. Nobody said this was about saving space. libgraphite was being pulled as many other dependencies and I wanted to have all statically compiled instead of some static, some dynamic. Said this, I agree in not carrying a delta between Debian and Ubuntu as this library does not pull additional dependencies and is small, so additional maintenance is not worth the effort. > > On Wed, 29 Sep 2021, 1:06 pm Sebastien Bacher, <1943...@bugs.launchpad.net> > wrote: > > > Debian wontfixed the change so it means we will need to carry a delta at > > the cost of increased workload from our team if we take the change. Not > > saying that we should be we need to weight the cost over time and the > > benefit > > > > -- > > You received this bug notification because you are subscribed to Ubuntu. > > https://bugs.launchpad.net/bugs/1943984 > > > > Title: > > No archive files for static compilation are included in the -dev > > package > > > > Status in graphite2 package in Ubuntu: > > New > > Status in graphite2 package in Debian: > > Won't Fix > > > > Bug description: > > There is no libgraphite2.a file, so it is not possible to compile > > statically against this library. See attached patch to solve this. > > > > To manage notifications about this bug go to: > > > > https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+subscriptions > > > > > > > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1943984 > > Title: > No archive files for static compilation are included in the -dev > package > > Status in graphite2 package in Ubuntu: > New > Status in graphite2 package in Debian: > Won't Fix > > Bug description: > There is no libgraphite2.a file, so it is not possible to compile > statically against this library. See attached patch to solve this. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943984 Title: No archive files for static compilation are included in the -dev package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943984] Re: No archive files for static compilation are included in the -dev package
Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994757 ** Bug watch added: Debian Bug tracker #994757 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994757 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943984 Title: No archive files for static compilation are included in the -dev package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943859] Re: The development package does not include static libraries
Debian bug report: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=994752 ** Bug watch added: Debian Bug tracker #994752 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994752 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943859 Title: The development package does not include static libraries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1943859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944107] [NEW] No archive files for static compilation are included in the -dev package
Public bug reported: There are no libdrm.a, libdrm_amdgpu.a, etc. files, so it is not possible to compile statically against this library. See attached debdiff to solve this. ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Attachment added: "debdiff.patch" https://bugs.launchpad.net/bugs/1944107/+attachment/5526398/+files/debdiff.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944107 Title: No archive files for static compilation are included in the -dev package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1944107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943984] [NEW] No archive files for static compilation are included in the -dev package
Public bug reported: There is no libgraphite2.a file, so it is not possible to compile statically against this library. See attached patch to solve this. ** Affects: graphite2 (Ubuntu) Importance: Undecided Status: New ** Patch added: "debdiff.patch" https://bugs.launchpad.net/bugs/1943984/+attachment/5525961/+files/debdiff.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943984 Title: No archive files for static compilation are included in the -dev package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943859] [NEW] The development package does not include static libraries
Public bug reported: The development package for pango (libpango1.0-dev) does not include static libraries so it is not possible to link these libraries statically. See attached patch with the fix. ** Affects: pango1.0 (Ubuntu) Importance: Undecided Status: New ** Patch added: "debdiff.patch" https://bugs.launchpad.net/bugs/1943859/+attachment/5525735/+files/debdiff.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943859 Title: The development package does not include static libraries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1943859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943564] [NEW] [SRU] Backport xrt 202020.2.8.743-0ubuntu1 to focal
Public bug reported: [Impact] Some problems have been detected in the xrt package that need to be fixed: a missing configuration file (LP: #1939613) and a problem with reading the AIE counter that has been fixed upstream. Additionally, the packages for amd64 are not really tested and won't be, so it is preferable to remove from the build. [Test Plan] To test, install the xrt package on a ZCU or Kria platform. The command $ sudo xbutil scan should detect a valid card in the system. Also, the file "/etc/OpenCL/vendor/xilinx.icd" should exist now. [Where problems could occur] There is some potential for regression, although the changes are minor. The package will disappear from amd64 arch, but anyway it was not really working and it is preferable to remove it rather than leaving people with a not working binary around. [Other Info] Xilinx expects to have their own package feed for xrt/amd64, so there will be an alternative for that arch quite soon. ** Affects: xrt (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/1943564 Title: [SRU] Backport xrt 202020.2.8.743-0ubuntu1 to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrt/+bug/1943564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943542] [NEW] [SRU] Create package for focal
Public bug reported: [Impact] The xlnx-kria-firmware has been recently added to the Ubuntu archive, for the development release (impish). We would like to have it backported to 20.04 (focal), to allow support of the Xilinx Kria platform for that release. There should be no effect on users as the package does not exist yet on focal. [Test Plan] To test, build a Kria image with this package installed. The package includes the device tree for the platform, so if a reboot works, the package has been installed successfully. [Where problems could occur] In theory, there is little potential for regression as this is a new package. [Other Info] NA ** Affects: xlnx-kria-firmware (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/1943542 Title: [SRU] Create package for focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xlnx-kria-firmware/+bug/1943542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939613] Re: xrt package does not create xilinx.icd
** Changed in: xrt (Ubuntu) Assignee: (unassigned) => Alfonso Sanchez-Beato (alfonsosanchezbeato) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939613 Title: xrt package does not create xilinx.icd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrt/+bug/1939613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939613] Re: xrt package does not create xilinx.icd
New version of the patch, fixing the build for x86 too. ** Patch added: "debdiff.patch" https://bugs.launchpad.net/ubuntu/+source/xrt/+bug/1939613/+attachment/5517756/+files/debdiff.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939613 Title: xrt package does not create xilinx.icd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrt/+bug/1939613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939613] Re: xrt package does not create xilinx.icd
The attached patch solves the problem and an FTBFS. ** Patch added: "debdiff.patch" https://bugs.launchpad.net/ubuntu/+source/xrt/+bug/1939613/+attachment/5517751/+files/debdiff.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939613 Title: xrt package does not create xilinx.icd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrt/+bug/1939613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931987] Re: [SRU] Creating FIT images is not supported
I have verified in focal. Installation generated FIT images on my Kria system, and reboot was successful. I cannot verify on hirsute though as I do not have a Kria image for that Ubuntu version. $ apt policy flash-kernel flash-kernel: Installed: 3.103ubuntu1~20.04.3 Candidate: 3.103ubuntu1~20.04.3 Version table: *** 3.103ubuntu1~20.04.3 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 Packages 100 /var/lib/dpkg/status 3.103ubuntu1~20.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages 3.98ubuntu12 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931987 Title: [SRU] Creating FIT images is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1931987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938530] Re: arm64: virtio_blk is not included in the initramfs
I'm trying to boot UC20 on qemu. Note that the module is present in the x86 initramfs, and we can use UC20 on qemu/x86. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938530 Title: arm64: virtio_blk is not included in the initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1938530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938530] [NEW] arm64: virtio_blk is not included in the initramfs
Public bug reported: The virtio_blk module is not included by default in the initramfs for arm64, so UC20 cannot boot as expected. ** Affects: linux-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/1938530 Title: arm64: virtio_blk is not included in the initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1938530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926137] Re: Error when starting copy to disk due to processes accessing /var/log
** Attachment added: "sub-crash.log" https://bugs.launchpad.net/subiquity/+bug/1926137/+attachment/5514063/+files/sub-crash.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926137 Title: Error when starting copy to disk due to processes accessing /var/log To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1926137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926137] Re: Error when starting copy to disk due to processes accessing /var/log
I have tried the fix, but unfortunately it failed. See attached logs. ** Attachment added: "sub-crash.install.log" https://bugs.launchpad.net/subiquity/+bug/1926137/+attachment/5514062/+files/sub-crash.install.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926137 Title: Error when starting copy to disk due to processes accessing /var/log To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1926137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1926137] Re: Error when starting copy to disk due to processes accessing /var/log
On Fri, Jul 23, 2021 at 2:35 AM Michael Hudson-Doyle < 1926...@bugs.launchpad.net> wrote: > This should be fixed in the latest impish dailies -- Alfonso, do you > still have a way to test this? > Yes, I can reproduce it. I can try the fix if it is available in some subiquity snap channel. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1926137 > > Title: > Error when starting copy to disk due to processes accessing /var/log > > Status in subiquity: > New > Status in casper package in Ubuntu: > Fix Released > > Bug description: > Installation fails when subiquity starts copying to disk due to some > process accessing /var/log. The full crash log is > > https://paste.ubuntu.com/p/Jw4ndyQFzk/ > > The error happens only if re-installing on top of an already > partitioned disk. I am using version 21.04.2+git1.2719c57c. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/subiquity/+bug/1926137/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926137 Title: Error when starting copy to disk due to processes accessing /var/log To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1926137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934780] Re: shim crashes on Mellanox BF1 SmartNIC
Things look good after updating: u@nic:~$ apt policy shim-signed shim-signed: Installed: 1.40.6+15.4-0ubuntu7 Candidate: 1.40.6+15.4-0ubuntu7 Version table: *** 1.40.6+15.4-0ubuntu7 500 500 http://tw.ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 Packages 100 /var/lib/dpkg/status 1.40.4+15+1552672080.a4a1fbe-0ubuntu2 500 500 http://tw.ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages 1.40.3+15+1533136590.3beb971-0ubuntu1 500 500 http://tw.ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages I get these messages when booting, but I think that is expected (booting goes on just fine): Could not get variable storage info: Unsupported Could not get variable storage info: Unsupported Could not get variable storage info: Unsupported Could not get variable storage info: Unsupported I cannot test on hirsute as there is no hirsute image for this device. Considering the validation done there anyway (same binary). ** Tags removed: verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-focal verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934780 Title: shim crashes on Mellanox BF1 SmartNIC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1934780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934780] Re: shim crashes on Mellanox BF1 SmartNIC
Logs with https://github.com/rhboot/shim/pull/369 (certificate from PPA added to DB). ** Attachment added: "new-shim-sb.txt" https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1934780/+attachment/5509432/+files/new-shim-sb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934780 Title: shim crashes on Mellanox BF1 SmartNIC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1934780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934780] Re: shim crashes on Mellanox BF1 SmartNIC
Attached logs after "mokutil --set-verbosity true" and resetting state with "mokutil --reset". In this case the shim was able to load grub, but then grub failed to verify the kernel: error: /vmlinuz has invalid signature. Loading Ram Disk... error: you need to load the kernel first. ** Attachment added: "ok.txt" https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1934780/+attachment/5509400/+files/ok.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934780 Title: shim crashes on Mellanox BF1 SmartNIC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1934780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934780] Re: shim crashes on Mellanox BF1 SmartNIC
** Attachment added: "commands.txt" https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1934780/+attachment/5509397/+files/commands.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934780 Title: shim crashes on Mellanox BF1 SmartNIC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1934780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934780] [NEW] shim crashes on Mellanox BF1 SmartNIC
Public bug reported: shim in focal-proposed (shim-signed 1.40.5) is crashing on Mellanox BF1 SmartNIC, showing this trace: >>Start PXE over IPv4. Station IP address is 192.168.100.2 Server IP address is 192.168.100.1 NBP filename is shimaa64.efi.signed NBP filesize is 840024 Bytes Downloading NBP file... NBP file downloaded successfully. Could not get variable storage info: Unsupported Could not create MokListRT: Unsupported Could not get variable storage info: Unsupported Could not create MokListXRT: Unsupported Could not get variable storage info: Unsupported Could not create MokListRT: Unsupported Could not get variable storage info: Unsupported Could not create MokListXRT: Unsupported Something has gone seriously wrong: import_mok_state() failed: Unsupported ERROR: System Off: operation not handled. PANIC at PC : 0x0045c488 Some EFI related kernel output: [0.00] efi: EFI v2.70 by EDK II [0.00] efi: SMBIOS=0xfafb SMBIOS 3.0=0xf5b7 ACPI=0xf5c1 ACPI 2.0=0xf5c10014 MEMATTR=0xf769e018 ESRT=0xf7593098 MEMRESERVE=0xf49e9018 [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz console=hvc0 console=ttyAMA0 earlycon=pl011,0x0100 fixrtc ip=:tmfifo_net0:dhcp url=http://192.168.100.1/tftp/bluefield.iso cloud-config-url=/dev/null nopersistent [0.085871] Remapping and enabling EFI services. [0.377821] DMI: https://www.mellanox.com BlueField SoC/BlueField SoC, BIOS BlueField:3.6.0-24-gd4db9c4 Apr 6 2021 [1.028977] Registered efivars operations [2.481241] rtc-efi rtc-efi: registered as rtc0 [2.593647] EFI Variables Facility v0.08 2004-May-17 ** Affects: shim (Ubuntu) Importance: Undecided Status: New ** Description changed: shim in focal-proposed (shim-signed 1.40.5) is crashing on Mellanox BF1 SmartNIC, showing this trace: >>Start PXE over IPv4. - Station IP address is 192.168.100.2 + Station IP address is 192.168.100.2 - Server IP address is 192.168.100.1 - NBP filename is shimaa64.efi.signed - NBP filesize is 840024 Bytes - Downloading NBP file... + Server IP address is 192.168.100.1 + NBP filename is shimaa64.efi.signed + NBP filesize is 840024 Bytes + Downloading NBP file... - NBP file downloaded successfully. + NBP file downloaded successfully. Could not get variable storage info: Unsupported Could not create MokListRT: Unsupported Could not get variable storage info: Unsupported Could not create MokListXRT: Unsupported Could not get variable storage info: Unsupported Could not create MokListRT: Unsupported Could not get variable storage info: Unsupported Could not create MokListXRT: Unsupported Something has gone seriously wrong: import_mok_state() failed: Unsupported ERROR: System Off: operation not handled. PANIC at PC : 0x0045c488 + + Some EFI related kernel output: + + [0.00] efi: EFI v2.70 by EDK II + [0.00] efi: SMBIOS=0xfafb SMBIOS 3.0=0xf5b7 ACPI=0xf5c1 ACPI 2.0=0xf5c10014 MEMATTR=0xf769e018 ESRT=0xf7593098 MEMRESERVE=0xf49e9018 + [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 + [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz console=hvc0 console=ttyAMA0 earlycon=pl011,0x0100 fixrtc ip=:tmfifo_net0:dhcp url=http://192.168.100.1/tftp/bluefield.iso cloud-config-url=/dev/null nopersistent + [0.085871] Remapping and enabling EFI services. + [0.377821] DMI: https://www.mellanox.com BlueField SoC/BlueField SoC, BIOS BlueField:3.6.0-24-gd4db9c4 Apr 6 2021 + [1.028977] Registered efivars operations + [2.481241] rtc-efi rtc-efi: registered as rtc0 + [2.593647] EFI Variables Facility v0.08 2004-May-17 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934780 Title: shim crashes on Mellanox BF1 SmartNIC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1934780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934780] Re: shim crashes on Mellanox BF1 SmartNIC
See attached kernel log. ** Attachment added: "kernel-out.txt" https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1934780/+attachment/5509396/+files/kernel-out.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934780 Title: shim crashes on Mellanox BF1 SmartNIC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1934780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932035] Re: Enable features for supporting PXE installer
I have successfully finished an installation with this kernel, changing to verified. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932035 Title: Enable features for supporting PXE installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1932035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929834] Re: Backport xilinx packages to focal
Tested on focal: ubuntu@zynqmp:~$ apt policy xlnx-firmware xlnx-firmware: Installed: 0.1ubuntu17~20.04 Candidate: 0.1ubuntu17~20.04 Version table: *** 0.1ubuntu17~20.04 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages 100 /var/lib/dpkg/status After installation, /boot/firmware/boot*.bin files are re-generated, and reboot is successful. I cannot actually test on hirsute as there is no hirsute image for this hw, so marking as verification-done-hirsute anyway. ** Tags removed: verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-focal verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929834 Title: Backport xilinx packages to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bootgen-xlnx/+bug/1929834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932044] Re: [SRU] Backport xf86-video-armsoc-endlessm to hirsute/focal
Validated from focal-proposed: ubuntu@zynqmp:~$ apt policy xserver-xorg-video-armsoc-endlessm xserver-xorg-video-armsoc-endlessm: Installed: 1.4.1-0ubuntu6~20.04 Candidate: 1.4.1-0ubuntu6~20.04 Version table: *** 1.4.1-0ubuntu6~20.04 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/universe arm64 Packages 100 /var/lib/dpkg/status On an arm platform with mali, things look good. It is not possible to verify on hirsute as there is no hirsute image for this platform, so marking it verified for hirsute anyway. ** Tags removed: verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-focal verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932044 Title: [SRU] Backport xf86-video-armsoc-endlessm to hirsute/focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-video-armsoc-endlessm/+bug/1932044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932031] Re: [SRU] Add console=tty1 to bootargs and set cma to 1200M on ZCU106
Verified in focal. After installation and a reboot, system starts as expected and has the right kernel command line: ubuntu@zynqmp:~$ apt policy u-boot-zynqmp u-boot-zynqmp: Installed: 2020.2-0ubuntu11~20.04 Candidate: 2020.2-0ubuntu11~20.04 Version table: *** 2020.2-0ubuntu11~20.04 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/universe arm64 Packages 100 /var/lib/dpkg/status ubuntu@zynqmp:~$ cat /proc/cmdline earlycon console=ttyPS0,115200 console=tty1 root=/dev/mmcblk0p2 uio_pdrv_genirq.of_id=generic-uio cma=1200M Changing also hirsute to verified without testing, as anyway we do not have any hirsute image for these devices. ** Tags removed: verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-focal verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932031 Title: [SRU] Add console=tty1 to bootargs and set cma to 1200M on ZCU106 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot-xlnx/+bug/1932031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932044] [NEW] [SRU] Backport xf86-video-armsoc-endlessm to hirsute/focal
Public bug reported: [Impact] Backport xf86-video-armsoc-endlessm package to hirsute/focal, which implements X driver for mali on some platforms. This package is not there currently. [Test Plan] For testing, a ZCU device is needed. By install xf86-video-armsoc- endlessm it will be possible to have X11 graphics via DisplayPort monitor. [Where problems could occur] The package is not present in hirsute/focal, so regressions are not really expected. [Other Info] - ** Affects: xf86-video-armsoc-endlessm (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/1932044 Title: [SRU] Backport xf86-video-armsoc-endlessm to hirsute/focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-video-armsoc-endlessm/+bug/1932044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932031] [NEW] [SRU] Add console=tty1 to bootargs and set cma to 1200M on ZCU106
Public bug reported: [Impact] Some kernel command line changes are needed in Xilinx ZCU platforms for the system to work properly. This is about backporting those changes from impish to hirsute and focal. [Test Plan] For testing, a ZCU device is needed. By install u-boot-xlnx with the fix, the newer configuration will be installed and we will get the default console via DisplayPort monitor and the change in reserved CMA memory. [Where problems could occur] The u-boot-xlnx package is for a platform that is not yet in the field, so regressions are not really expected. [Other Info] See LP: #1932008. ** Affects: u-boot-xlnx (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/1932031 Title: [SRU] Add console=tty1 to bootargs and set cma to 1200M on ZCU106 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot-xlnx/+bug/1932031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932008] [NEW] Add console=tty1 to bootargs and set cma to 1200M on ZCU106
Public bug reported: * Add console=tty1 to bootargs (LP: #1925227) * Set cma to 1200M on ZCU106 (LP: #1920872) * Restore debian/bin/u-boot-install-targets, which was removed by mistake when porting to hirsute. ** Affects: u-boot-xlnx (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/1932008 Title: Add console=tty1 to bootargs and set cma to 1200M on ZCU106 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot-xlnx/+bug/1932008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931987] Re: [SRU] Creating FIT images is not supported
Hirsute debdiff ** Patch added: "flash-kernel-hirsute.debdiff" https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1931987/+attachment/5504749/+files/flash-kernel-hirsute.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931987 Title: [SRU] Creating FIT images is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1931987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931987] Re: [SRU] Creating FIT images is not supported
Focal debdiff ** Patch added: "flash-kernel-focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1931987/+attachment/5504750/+files/flash-kernel-focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931987 Title: [SRU] Creating FIT images is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1931987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931987] [NEW] [SRU] Creating FIT images is not supported
Public bug reported: [Impact] flash-kernel does currently not support creating FIT images. There are some platforms where this is preferred, for instance for the Kria SOM platform. This have been just fixed in flash-kernel 3.104ubuntu4 in impish (dev) (LP: #1931278), and we would like this ported back to hirsute/focal to support Kria SOM platform in focal. [Test Plan] For testing, a Kria SOM device is needed. By install flash-kernel with the fix, a file in path /boot/firmware/image.fit will be created, and the system should be able to boot. [Where problems could occur] The change adds new functionality which should not interfere with the previous one. However, there is some small potential for a regression happening. If that is the case, some hardware platforms that use flash- kernel might not be able to update the bootloader or will break it, making the system unable to boot. [Other Info] See LP: #1931278 ** Affects: flash-kernel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931987 Title: [SRU] Creating FIT images is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1931987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931278] Re: Creating FIT images is not supported
Fixed in 3.104ubuntu4 in impish (dev). ** Changed in: flash-kernel (Ubuntu) Assignee: (unassigned) => Alfonso Sanchez-Beato (alfonsosanchezbeato) ** Changed in: flash-kernel (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/1931278 Title: Creating FIT images is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1931278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931278] Re: Creating FIT images is not supported
New debdiff after the review. ** Patch added: "flash-kernel.debdiff" https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1931278/+attachment/5504533/+files/flash-kernel.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931278 Title: Creating FIT images is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1931278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912844] Re: Bond with OVS bridging RuntimeError: duplicate mac found!
@Dan, was this released to focal in the end? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912844 Title: Bond with OVS bridging RuntimeError: duplicate mac found! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1912844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931718] [NEW] No login prompt on serial if no monitor connected
Public bug reported: In a device that has both HDMI ouput *and* a serial console, no log-in prompt appears in the serial console if no monitor is connected, when "splash" is added to the kernel command line. I see plymouthd taking 100% of the CPU. If I connect a monitor, then I get the serial console and plymouthd stops. That HDMI is connected or not should not influence the serial console prompt. plymouthd backtrace shows it waiting for events: #0 0x9a948754 in __GI_epoll_pwait (epfd=3, events=events@entry=0x9aa3e2a0 , maxevents=maxevents@entry=64, timeout=-1, set=set@entry=0x0) at ../sysdeps/unix/sysv/linux/epoll_pwait.c:42 #1 0x9a9488e0 in epoll_wait (epfd=, events=events@entry=0x9aa3e2a0 , maxevents=maxevents@entry=64, timeout=) at ../sysdeps/unix/sysv/linux/epoll_wait.c:32 #2 0x9aa1b818 in ply_event_loop_process_pending_events (loop=0xd24b53e0) at ply-event-loop.c:1230 #3 ply_event_loop_process_pending_events (loop=0xd24b53e0) at ply-event-loop.c:1210 #4 0x9aa1be98 in ply_event_loop_run (loop=0xd24b53e0) at ply-event-loop.c:1310 #5 0xce94c62c in main (argc=4, argv=0xefe2d748) at main.c:2294 ** Affects: plymouth (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/1931718 Title: No login prompt on serial if no monitor connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1931718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931278] Re: Creating FIT images is not supported
@lool I have updated again the branch/MP: * Use generic instead of fit method and remove the latter * Add parameter to control copy of the dtb file to /boot/ * Add support for ZCU boards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931278 Title: Creating FIT images is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1931278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931278] Re: Creating FIT images is not supported
@lool I have pushed some more commits to the branch/MP: * Move .its files to /usr/share/flash-kernel/its * Remove Mkimage-FIT-Options field (as you suggested, it was not really needed) * Make sure temp FIT file lives in same filesystem as final (so mv can be "more atomic") -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931278 Title: Creating FIT images is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1931278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1931278] Re: Creating FIT images is not supported
On Wed, Jun 9, 2021 at 1:55 AM Loïc Minier <1931...@bugs.launchpad.net> wrote: > thanks for the patch! > Thanks for the review! > > this might be easier to review as smaller atomic changes, but perhaps I > can still follow around the debdiff :) > I have this branch based on the auto-imported ubuntu repos (focal branch) that probably will make your review easier: https://code.launchpad.net/~alfonsosanchezbeato/ubuntu/+source/flash-kernel/+git/flash-kernel/+ref/kria-support There is now a commit with the changes you have requested. I have also created an MP, purely to help with the review (obviously not for merging to the auto-imported repo): https://code.launchpad.net/~alfonsosanchezbeato/ubuntu/+source/flash-kernel/+git/flash-kernel/+merge/403942 When things are ready, I will create a new debdiff for impish. > > 1) The its files are data, so they should to /usr/share; I wouldn't > encourage local customizations by dropping them in /etc unless that's an > important function; a way to give control would be to install a local > flash-kernel database entry that overrides the shipped defaults for that > hardware; this should be possible with /etc/flash-kernel/db? > I actually fully agree with you, the reason that I've put the "its" file under /etc is just to be coherent as that's where the boot script files are stored (/etc/flash-kernel/bootscript/) too. And I think that /usr/share/ would be a better place for those files as well. So, should I put the "its" file in /usr/share and maybe move the bootscript files with another debdiff? > > 2) would you add the new Boot-FIT-Path and Boot-ITS-Path to README? > Done. > > 3) seems "Boot-ITS-Path: /.../foo.its" should be written "U-Boot-ITS- > Name: foo.its" and should be searched in the default flash-kernel > directory > Done. > > 4) would it be possible to avoid the cp calls for kernel and initrd and > just generate the fit image from their locations? the kernels / initrds > tend to be big, so I suspect this adds non-trivial time to the run on SD > cards > I have now changed things to use macros in the "its" files (@@XXX@@) and replace them with the file names using sed, so no copy is necessary anymore. > > 5) mkimage_fit(): why is padding needed? perhaps deserves a comment. > Should this be a config? > Added Mkimage-FIT-Options option now. > > 6) the full path name in DTB-Id is the first one in the database, > perhaps this suggests the corresponding deb should be in Required- > Packages? would help with d-i usage > I've added xlnx-kria-firmware to Required-Packages. > > 6) "cd" looks pretty singular compared to rest of functions; could it be > avoided? > The problem here was that mkimage was searching the files defined in the .its in the current folder, but with the macros and using absolute paths this is not needed anymore. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1931278 > > Title: > Creating FIT images is not supported > > Status in flash-kernel package in Ubuntu: > New > > Bug description: > flash-kernel does currently not support creating FIT images method. > The attached debdiff (for impish) supports that, and additionally add > supports for the Kria SOM platform. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1931278/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931278 Title: Creating FIT images is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1931278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931278] [NEW] Creating FIT images is not supported
Public bug reported: flash-kernel does currently not support creating FIT images method. The attached debdiff (for impish) supports that, and additionally add supports for the Kria SOM platform. ** Affects: flash-kernel (Ubuntu) Importance: Undecided Status: New ** Attachment added: "flash-kernel.debdiff" https://bugs.launchpad.net/bugs/1931278/+attachment/5503192/+files/flash-kernel.debdiff ** Description changed: flash-kernel does currently not support creating FIT images method. The - attached debdiff supports that, and additionally add supports for the - Kria SOM platform. + attached debdiff (for impish) supports that, and additionally add + supports for the Kria SOM platform. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931278 Title: Creating FIT images is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1931278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929834] Re: Backport xilinx packages to focal
For hirsute, it is not really possible to test the packages as the only available image for this HW os for focal. So, changing verification- needed-hirsute to verification-done-hirsute. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-focal verification-done-hirsute ** Description changed: [Impact] - * Packages from xilinx need to be backported to focal, including: + * Packages from xilinx need to be backported to focal, including: -bootgen-xlnx -fpga-manager-xlnx -libegl-mali-xlnx -linux-firmware-xilinx-vcu -u-boot-xlnx -vitis-ai -xilinx-vcu-ctrl -xilinx-vcu-omx -xlnx-firmware -xrt -xf86-video-armsoc-endlessm + bootgen-xlnx + fpga-manager-xlnx + libegl-mali-xlnx + linux-firmware-xilinx-vcu + vitis-ai + xilinx-vcu-ctrl + xilinx-vcu-omx + xlnx-firmware + xrt + xf86-video-armsoc-endlessm [Test Plan] - * HWE team will perform validation of these packages + * HWE team will perform validation of these packages [Where problems could occur] - * This is a low-risk SRU as the packages do not exist on focal yet, so + * This is a low-risk SRU as the packages do not exist on focal yet, so in theory no current user would be affected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929834 Title: Backport xilinx packages to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bootgen-xlnx/+bug/1929834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929834] Re: Backport xilinx packages to focal
I have now verified the packages on focal, and things work as expected: ubuntu@zynqmp$ apt policy bootgen-xlnx bootgen-xlnx: Installed: 2020.2-0ubuntu4~20.04.1 Candidate: 2020.2-0ubuntu4~20.04.1 Version table: *** 2020.2-0ubuntu4~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/universe arm64 Packages 100 /var/lib/dpkg/status ubuntu@zynqmp:~$ apt policy fpga-manager-xlnx fpga-manager-xlnx: Installed: 2020.2ubuntu2~20.04 Candidate: 2020.2ubuntu2~20.04 Version table: *** 2020.2ubuntu2~20.04 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/universe arm64 Packages 100 /var/lib/dpkg/status ubuntu@zynqmp:~$ apt policy libegl-mali-xlnx libegl-mali-xlnx: Installed: 9p0.01rel0-0ubuntu5~20.04.1 Candidate: 9p0.01rel0-0ubuntu5~20.04.1 Version table: *** 9p0.01rel0-0ubuntu5~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages 100 /var/lib/dpkg/status ubuntu@zynqmp:~$ apt policy vitis-ai-library vitis-ai-library: Installed: 1.3.2-0ubuntu5~20.04.1 Candidate: 1.3.2-0ubuntu5~20.04.1 Version table: *** 1.3.2-0ubuntu5~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/universe arm64 Packages 100 /var/lib/dpkg/status ubuntu@zynqmp:~$ apt policy xilinx-vcu-ctrl xilinx-vcu-ctrl: Installed: 2020.2-0ubuntu4~20.04.1 Candidate: 2020.2-0ubuntu4~20.04.1 Version table: *** 2020.2-0ubuntu4~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages 100 /var/lib/dpkg/status ubuntu@zynqmp:~$ apt policy libxilinx-vcu-omx1 libxilinx-vcu-omx1: Installed: 2020.2-0ubuntu4~20.04.1 Candidate: 2020.2-0ubuntu4~20.04.1 Version table: *** 2020.2-0ubuntu4~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages 100 /var/lib/dpkg/status ubuntu@zynqmp:~$ apt policy xrt-embedded xrt-embedded: Installed: 202020.2.8.726-0ubuntu7~20.04 Candidate: 202020.2.8.726-0ubuntu7~20.04 Version table: *** 202020.2.8.726-0ubuntu7~20.04 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/universe arm64 Packages 100 /var/lib/dpkg/status ** No longer affects: u-boot-xlnx (Ubuntu) ** Tags removed: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929834 Title: Backport xilinx packages to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bootgen-xlnx/+bug/1929834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929834] [NEW] Backport xilinx packages to focal
Public bug reported: [Impact] * Packages from xilinx need to be backported to focal, including: bootgen-xlnx fpga-manager-xlnx libegl-mali-xlnx linux-firmware-xilinx-vcu u-boot-xlnx vitis-ai xilinx-vcu-ctrl xilinx-vcu-omx xlnx-firmware xrt xf86-video-armsoc-endlessm [Test Plan] * HWE team will perform validation of these packages [Where problems could occur] * This is a low-risk SRU as the packages do not exist on focal yet, so in theory no current user would be affected ** Affects: bootgen-xlnx (Ubuntu) Importance: Undecided Status: New ** Affects: fpga-manager-xlnx (Ubuntu) Importance: Undecided Status: New ** Affects: libegl-mali-xlnx (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware-xilinx-vcu (Ubuntu) Importance: Undecided Status: New ** Affects: u-boot-xlnx (Ubuntu) Importance: Undecided Status: New ** Affects: vitis-ai (Ubuntu) Importance: Undecided Status: New ** Affects: xilinx-vcu-ctrl (Ubuntu) Importance: Undecided Status: New ** Affects: xrt (Ubuntu) Importance: Undecided Status: New ** Also affects: vitis-ai (Ubuntu) Importance: Undecided Status: New ** Also affects: fpga-manager-xlnx (Ubuntu) Importance: Undecided Status: New ** Also affects: libegl-mali-xlnx (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-firmware-xilinx-vcu (Ubuntu) Importance: Undecided Status: New ** Also affects: u-boot-xlnx (Ubuntu) Importance: Undecided Status: New ** Also affects: xilinx-vcu-ctrl (Ubuntu) Importance: Undecided Status: New ** Also affects: xrt (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/1929834 Title: Backport xilinx packages to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bootgen-xlnx/+bug/1929834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914044] Re: [SRU] gstreamer fails with "cannot allocate memory in static TLS block" error on aarch64
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914044 Title: [SRU] gstreamer fails with "cannot allocate memory in static TLS block" error on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1914044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914044] Re: [SRU] gstreamer fails with "cannot allocate memory in static TLS block" error on aarch64
Verified in focal: ubuntu@host:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal ubuntu@host:~$ apt policy libc6 libc6: Installed: 2.31-0ubuntu9.2 Candidate: 2.31-0ubuntu9.2 Version table: *** 2.31-0ubuntu9.2 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages 100 /var/lib/dpkg/status 2.31-0ubuntu9 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages ubuntu@host:~$ rm .cache/gstreamer-1.0/registry.aarch64.bin ubuntu@host:~$ gst-inspect-1.0 >/dev/null (gst-plugin-scanner:5268): GStreamer-WARNING **: 10:45:38.430: Failed to load plugin '/usr/lib/aarch64-linux-gnu/gstreamer-1.0/libgstchromaprint.so': /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block (gst-plugin-scanner:5268): GStreamer-WARNING **: 10:45:38.529: Failed to load plugin '/usr/lib/aarch64-linux-gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block ubuntu@host:~$ apt policy libc6 libc6: Installed: 2.31-0ubuntu9.3 Candidate: 2.31-0ubuntu9.3 Version table: *** 2.31-0ubuntu9.3 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 Packages 100 /var/lib/dpkg/status 2.31-0ubuntu9.2 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages 2.31-0ubuntu9 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages ubuntu@host:~$ rm .cache/gstreamer-1.0/registry.aarch64.bin ubuntu@host:~$ gst-inspect-1.0 >/dev/null (no errors now) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914044 Title: [SRU] gstreamer fails with "cannot allocate memory in static TLS block" error on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1914044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912844] Re: Bond with OVS bridging RuntimeError: duplicate mac found!
Is this going to be backported to focal (see LP: #1919493)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912844 Title: Bond with OVS bridging RuntimeError: duplicate mac found! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1912844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914044] Re: [SRU] gstreamer fails with "cannot allocate memory in static TLS block" error on aarch64
On Mon, Mar 15, 2021 at 11:42 AM RussianNeuroMancer < 1914...@bugs.launchpad.net> wrote: > For me Totem works now, but not totem-video-thumbnailer. > > Alfonso, Balint, how totem-video-thumbnailer works for you now? > It works for me, but I have just done a quick try. gstlaunch was what was failing before and now is fine with the focal packages from the PPA. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1914044 > > Title: > [SRU] gstreamer fails with "cannot allocate memory in static TLS > block" error on aarch64 > > Status in glibc package in Ubuntu: > Fix Released > Status in glibc source package in Focal: > Confirmed > Status in glibc package in Debian: > Fix Released > > Bug description: > [Impact] > > gstreamer cannot load some plugins on 20.04, aarch64 due to TLS memory > exhaustion, so these plugins cannot be used. See LP#1846837 and > LP#1914030. > > This is solved apparently on glibc 2.32: > https://sourceware.org/bugzilla/show_bug.cgi?id=25051 > by patch > > https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=ffb17e7ba3a5ba9632cee97330b325072fbe41dd > > [Test Case] > > Running totem-video-thumbnailer shows these errors: > > (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740: > Failed to load plugin '/usr/lib/aarch64-linux- > gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- > gnu/libgomp.so.1: cannot allocate memory in static TLS block > > [Where problems could occur] > > This is delicate code in glibc with quite regression potential. Said > this, the code is in the next minor release (2.32, while focal has > 2.31), which has been running groovy for a while. > > Also, apparently there is a 2.31 patch for groovy, before it moved to > 2.32: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964141 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1914044/+subscriptions > ** Bug watch added: Sourceware.org Bugzilla #25051 https://sourceware.org/bugzilla/show_bug.cgi?id=25051 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914044 Title: [SRU] gstreamer fails with "cannot allocate memory in static TLS block" error on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1914044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914044] Re: [SRU] gstreamer fails with "cannot allocate memory in static TLS block" error on aarch64
I have given a try to the test PPA and I can confirm it fixes the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914044 Title: [SRU] gstreamer fails with "cannot allocate memory in static TLS block" error on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1914044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
Just FTR, note that the change in NM upstream was needed so the network- manager snap was able to correctly detect if udevd is running. We currently build the snap from the source package + some patches including this one. But, the long term target is to be able to create the snap by simply staging the network-manager debs. So, please keep this in mind and try to put back this change as soon as is feasible again, so we do not need to remove the change in the deb and then put it back in the snap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383858] Re: expr-simplify optimization slows click/snap policy compilation
This MR for apparmor_parser: https://gitlab.com/apparmor/apparmor/-/merge_requests/711 helps quite a bit with accelerating the expression optimization, and actually makes it worth enabling them back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383858 Title: expr-simplify optimization slows click/snap policy compilation To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1383858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
There is here a change in behavior in lxc/lxd. Running https://paste.ubuntu.com/p/vz7SXcX3K9/: On hirsute lxd container: root@hirsute:~# ./test access errno 13 path is read only: 0 root@hirsute:~# mount | grep 'sysfs on /sys ' sysfs on /sys type sysfs (rw,relatime) On focal lxd container: root@focal:~# ./test path is read only: 1 root@focal:~# mount | grep 'sysfs on /sys ' sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) sysfs on /sys type sysfs (ro,nosuid,nodev,noexec,relatime) (no idea why there are two mounts in focal) According to https://systemd.io/CONTAINER_INTERFACE/ , /sys should be mounted read-only? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1914062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846837] Re: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64
This is, I think, a glibc bug. See https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1914044 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846837 Title: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1846837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846837] Re: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64
This is, I think, a glibc bug. See LP:#1914044 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846837 Title: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1846837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846837] Re: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64
This is, I think, a glib bug. See LP:#1846837. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846837 Title: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1846837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914044] Re: gstreamer fails with "cannot allocate memory in static TLS block" error on aarch64
** Description changed: [Impact] gstreamer cannot load some plugins on 20.04, aarch64 due to TLS memory exhaustion, so these plugins cannot be used. See LP#1846837 and LP#1914030. This is solved apparently on glibc 2.32: https://sourceware.org/bugzilla/show_bug.cgi?id=25051 by patch https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=ffb17e7ba3a5ba9632cee97330b325072fbe41dd [Test Case] Running totem-video-thumbnailer shows these errors: (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block [Where problems could occur] This is delicate code in glibc with quite regression potential. Said this, the code is in the next minor release (2.32, while focal has 2.31), which has been running groovy for a while. + + Also, apparently there is a 2.31 patch for groovy, before it moved to + 2.32: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964141 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914044 Title: gstreamer fails with "cannot allocate memory in static TLS block" error on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1914044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914044] [NEW] gstreamer fails with "cannot allocate memory in static TLS block" error on aarch64
Public bug reported: [Impact] gstreamer cannot load some plugins on 20.04, aarch64 due to TLS memory exhaustion, so these plugins cannot be used. See LP#1846837 and LP#1914030. This is solved apparently on glibc 2.32: https://sourceware.org/bugzilla/show_bug.cgi?id=25051 by patch https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=ffb17e7ba3a5ba9632cee97330b325072fbe41dd [Test Case] Running totem-video-thumbnailer shows these errors: (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block [Where problems could occur] This is delicate code in glibc with quite regression potential. Said this, the code is in the next minor release (2.32, while focal has 2.31), which has been running groovy for a while. Also, apparently there is a 2.31 patch for groovy, before it moved to 2.32: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964141 ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Tags: focal rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914044 Title: gstreamer fails with "cannot allocate memory in static TLS block" error on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1914044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862279] Re: arm64 Secure Boot fails w/ "error: cannot load image."
After working on LP: #1892770, I think that this is the same problem. grub in focal/arm64 is trying to use EFI boot services to start the kernel, after having verified the kernel with the shim. EFI does not have access to the cert in the shim so it refuses to load the kernel. There is a workaround which is adding Canonical Master key to the EFI DB, so EFI can actually verify the kernel. Looking at "loader/arm64/linux.c" in the sources seems to validate this. In focal [1], grub_arch_efi_linux_boot_image() calls EFI boot services b->load_image() and b->start_image() which is the same in upstream code. However, in disco [2] the EFI boot services are not used - the sequence is grub_armxx_efi_linux_boot_image() -> grub_efi_linux_boot() -> calls directly an address in the loaded kernel. The patch that makes the change in disco is debian/patches/linuxefi_load_arm_with_sb.patch (https://github.com/rhboot/grub2/commit/2786ab864cf00c15123320671f653e9a36ba12b4). [1] https://git.launchpad.net/ubuntu/+source/grub2/tree/grub-core/loader/arm64/linux.c?h=applied/ubuntu/focal-updates#n122 [2] https://git.launchpad.net/ubuntu/+source/grub2/tree/grub-core/loader/arm64/linux.c?h=applied/ubuntu/disco-updates#n157 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862279 Title: arm64 Secure Boot fails w/ "error: cannot load image." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1862279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880968] Re: fixrtc fails due to bad format of input to the date command
I have updated to focal-proposed and checked that now there is no date: invalid date ' Wed Apr 1 17:23:44 2020' output anymore in the console and that fixrtc finishes as expected. $ apt info initramfs-tools Package: initramfs-tools Version: 0.136ubuntu6.2 ... $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.4.0-1003-bluefield root=LABEL=writable ro console=ttyAMA0 earlycon=pl011,0x0100 fixrtc $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal $ uname -a Linux ubuntu 5.4.0-1003-bluefield #4-Ubuntu SMP PREEMPT Fri Jun 12 17:02:31 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880968 Title: fixrtc fails due to bad format of input to the date command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1880968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882894] [NEW] docker snap does not support custom apparmor profiles per container
Public bug reported: docker supports loading custom apparmor profiles that can be different for each container [1] by using the option "--security-opt apparmor=". However, this does not work with the docker snap because the docker snapd interface only allows sending signals to a profile named "docker- default" (the default profile for docker containers), so if the name of the profile is different, you cannot stop the container using the docker cli. You get denials when trying to send the kill signal to the container. Allowing the docker snap to handle custom apparmor profiles for the containers would allow further confinement of the payloads. [1] https://docs.docker.com/engine/security/apparmor/ ** Affects: docker (Ubuntu) Importance: Undecided Status: New ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Also affects: snapd (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/1882894 Title: docker snap does not support custom apparmor profiles per container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker/+bug/1882894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881966] Re: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** No longer affects: snappy-hwe-snaps -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881966 Title: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1881966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880968] Re: fixrtc fails due to bad format of input to the date command
** Description changed: The fixrtc script is failing with message: date: invalid date ' Wed Apr 1 17:23:44 2020' when calling the date command. It looks like it does not like the leading spaces for the input date. The date is taken from 'dumpe2fs -h' ouptput, and some clean-up on it happens, but it looks like it is not enough for BusyBox' date command, at least for the version in focal. + + [Impact] + + The system date shown on first boot is incorrect, which can be + problematic on first boot if at that point in time there is no network + connection. If fixrtc works correctly at least we get the date of the + last time the rootfs was mounted, which is modern enough to avoid + problems with snap assertions validation, etc. + + [Test case] + + Boot an image with fixrtc in the kernel command line in a system with no + network. snap seeding will fail without the patch. + + [Regression Potential] + + Quite small, as the fix is small and targeted. ** Description changed: The fixrtc script is failing with message: date: invalid date ' Wed Apr 1 17:23:44 2020' when calling the date command. It looks like it does not like the leading spaces for the input date. The date is taken from 'dumpe2fs -h' ouptput, and some clean-up on it happens, but it looks like it is not enough for BusyBox' date command, at least for the version in focal. + + Backporting this to focal is needed. [Impact] The system date shown on first boot is incorrect, which can be problematic on first boot if at that point in time there is no network connection. If fixrtc works correctly at least we get the date of the last time the rootfs was mounted, which is modern enough to avoid problems with snap assertions validation, etc. [Test case] Boot an image with fixrtc in the kernel command line in a system with no network. snap seeding will fail without the patch. [Regression Potential] Quite small, as the fix is small and targeted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880968 Title: fixrtc fails due to bad format of input to the date command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1880968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881074] Re: Support btrfs when writable is converted to btrfs
@Woodrow thanks for your changes - you are right the binaries are already included by hooks from dependencies. LGTM from my side - although I cannot review formally apparently :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881074 Title: Support btrfs when writable is converted to btrfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-devices/+bug/1881074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881074] Re: Support btrfs when writable is converted to btrfs
Some comments on the debdiff:
Use
blkid -s TYPE "$writable_part" -o value
instead of
blkid -s TYPE "$writable_part" | awk '{print $2}' | grep -o '".*"' | tr -d '"'
No need to redirect to >>$LOGFILE in resize_filesystem() which is
already redirected when called. Also, you should not redirect to
/dev/kmsg - I guess that was for debugging purposes.
Is it really necessary to mount the partition to find out the filesystem usage?
"btrfs filesystem show" apparently can work on devices according to [1]. But it
also looks like btrfs commands are mostly used with mounted systems, so it is
fine if you want to keep things like that.
Finally, you will need to use copy_exec for btrfs and blkid to the
fixtrtc hook to get them included in the initramfs (although maybe blkid
comes from busybox in this case, not sure).
Otherwise, looks good to me.
[1] https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-filesystem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881074
Title:
Support btrfs when writable is converted to btrfs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-devices/+bug/1881074/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880968] Re: fixrtc fails due to bad format of input to the date command
See attached debdiff for the fix ** Patch added: "initramfs-tools_debdiff.patch" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1880968/+attachment/5377425/+files/initramfs-tools_debdiff.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880968 Title: fixrtc fails due to bad format of input to the date command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1880968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880968] [NEW] fixrtc fails due to bad format of input to the date command
Public bug reported: The fixrtc script is failing with message: date: invalid date ' Wed Apr 1 17:23:44 2020' when calling the date command. It looks like it does not like the leading spaces for the input date. The date is taken from 'dumpe2fs -h' ouptput, and some clean-up on it happens, but it looks like it is not enough for BusyBox' date command, at least for the version in focal. ** Affects: initramfs-tools (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/1880968 Title: fixrtc fails due to bad format of input to the date command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1880968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781597] Re: [SRU] WoWLAN settings are not supported
It looks like the VPN related SRU that was previous to this one was reverted. Could we land this into bionic? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781597 Title: [SRU] WoWLAN settings are not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
