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
(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
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
/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
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:
** 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,
** 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.
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:
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
#
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
@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
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
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
** 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
** 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
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:
** 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:
+
** 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
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
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
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
**
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.
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]:
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
** 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:
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
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.
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.
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
@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
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
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
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
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
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.
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.
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"
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"
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:
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,
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
** 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 cre
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
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
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:
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:
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,
** 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:
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
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.
>
>
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
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
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: "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
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
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.
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.
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
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
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
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
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
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:
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
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.
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
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
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
@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
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
@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.
@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
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
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
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
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
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
** 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
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:
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
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
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
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
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
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:
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
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
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
** 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
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
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
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
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
** 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
** 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
@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.
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
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,
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
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
1 - 100 of 794 matches
Mail list logo
