Thank you @wdoekes for confirming it works on Focal!
I've tested netplan.io 0.103-0ubuntu7.1 from impish-proposed and
attached the autopkgtest logs to the bug description, according to
https://wiki.ubuntu.com/NetplanUpdates.
The 'netplan try' command was run successfully without any "An error
** Description changed:
[Impact]
- * On virtualization hosts disable GRO and LRO, otherwise, with
-receive offload on, the guests will receive packets that are
-larger than the MTU. This can cause issues in certain scenarios,
-e.g. when the guest is a VPN server that needs to
** Description changed:
[Impact]
The last netplan SRU (0.103-0ubuntu5~20.04.2) introduced a state tracking
feature, that regressed the 'netplan try' CLI command, if no such --state
argument is passed, making it fail with a error message like this:
An error occurred: 'NetplanApply'
** Description changed:
[Impact]
The NetworkManager snap (using the libnetplan YAML backend) makes use of the
"link" routing scope in certain situations, which is represented by an empty
or
unspecified gateway/next_hop field in the keyfile definition (e.g.
"route3=2.2.2.2/7",
I'm working around this issue by applying this to systemd's
debian/rules:
diff --git a/debian/rules b/debian/rules
index 70060a482a..9946d20895 100755
--- a/debian/rules
+++ b/debian/rules
@@ -299,6 +299,11 @@ ifeq ($(DEB_VENDOR),Ubuntu)
cp -a debian/extra/units-ubuntu/*
Public bug reported:
systemd FTBFS on i386, due to errors from debugedit during dh_strip.
The interesting part seems to be this:
debugedit: Failed to update file: invalid section entry size
dh_strip: error: debugedit --build-id --build-id-seed=systemd/249.5-2ubuntu1
** No longer affects: systemd (Ubuntu Jammy)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949089
Title:
systemd randomly fails to activate mount units in Ubuntu Core 18
To manage notifications
That's certainly possible. In the first attempt (that failed according
to mvo's tests) I only backported
https://github.com/systemd/systemd-stable/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0
and
https://github.com/systemd/systemd-stable/commit/cc6271f17d3c5c200e8a391f10d0afb71403fc28
(as a
** Merge proposal linked:
https://code.launchpad.net/~slyon/ubuntu/+source/systemd/+git/systemd/+merge/411528
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949089
Title:
systemd randomly fails
Thank you for testing the revert!
Do we know if the same issue happens in Focal/UC20 as well? Or can we somehow
falsify that? The regressing patches had been introduced to
Hirsute/Focal/Bionic to fix LP: #1934147
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Summary changed:
- Please remove src:aufs-tools from Ubuntu
+ Please remove src:aufs-tools from Ubuntu Jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947004
Title:
Please remove
** Changed in: netplan
Status: In Progress => 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/1942930
Title:
Unset a subtree crashes
To manage notifications about this bug go to:
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943120
Title:
interface not removed
To manage notifications about this bug go
** Description changed:
+ [Impact]
+ The last netplan SRU (0.103-0ubuntu5~20.04.2) introduced a state tracking
+ feature, that regressed the 'netplan try' CLI command, if no such --state
+ argument is passed, making it fail with a error message like this:
+
+ An error occurred: 'NetplanApply'
** Description changed:
+ [Impact]
+ The NetworkManager snap (using the libnetplan YAML backend) makes use of the
+ "link" routing scope in certain situations, which is represented by an empty
or
+ unspecified gateway/next_hop field in the keyfile definition (e.g.
+ "route3=2.2.2.2/7",
** Description changed:
[Impact]
- * On virtualization hosts disable GRO and LRO, otherwise, with
- receive offload on, the guests will receive packets that are
- larger than the MTU. This can cause issues in certain scenarios,
- e.g. when the guest is a VPN server that needs to
Sounds like we cannot have an easy fix by simply applying
04eb582acc203eab0bc5c2cc5e13986f16e09df0 (and its dependencies).
So let's first try to pinpoint if f0831ed2a03fcef582660be1c3b1a9f3e267e656
really introduced the regression. I've built a new core18 snap with my previous
work and the
** Also affects: systemd (Ubuntu Bionic)
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/1949089
Title:
systemd randomly fails to activate mount units in
Thank you Alfonso, I staged this patch for the next Focal SRU:
https://git.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/systemd/commit/?h=ubuntu-
focal=fe0cb0bd66baea89d8bbe47cb47d88540f46d470
** Changed in: systemd (Ubuntu)
Status: New => Invalid
** Changed in: systemd (Ubuntu Focal)
** Also affects: systemd (Ubuntu Focal)
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/1948476
Title:
[SRU] Allow target units to fail
To manage
Thank you for the patch. LGTM.
In the future please remember to run `update-maintainer` if the package carries
an Ubuntu delta.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946767
Title:
Build
Public bug reported:
NetworkManager keyfiles allows to specify "scope: link" routes, by
leaving the gateway/next_hop field unspecified, e.g.:
route3=2.2.2.2/7
route4=3.3.3.3/6,0.0.0.0,4
route3=4:5:6:7:8:9:0:1/63,::,5
To keep compatibility, netplan needs to be able to accept "scope: link"
Sure, I put that custom core18 snap into
https://people.ubuntu.com/~slyon/uc18/ as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949089
Title:
systemd randomly fails to activate mount units
As a workaround you can execute the "netplan try" command as:
netplan try --state /etc/netplan
This will mitigate the problem for the time being.
** Tags added: regression-update
** Also affects: netplan.io (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: netplan.io
I can confirm that this issue was introduced with the latest update. A
fix is being worked on here:
https://github.com/canonical/netplan/pull/243
** Changed in: netplan.io (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Not having a reliable reproducer is always a tricky situation to be
in...
Indeed that other commit might be related. I've backported the following
patches and created a custom systemd build in
https://launchpad.net/~slyon/+archive/ubuntu/lp1949089
Thank you for the small fixups to the packaging and for providing the
breadcrumbs wrt. manual and automated testing. This makes me feel
confident that this package will be in good shape by the end of the
22.04 cycle.
MIR team ACK.
** Changed in: wsl-setup (Ubuntu)
Status: New => In
Some more smaller remarks:
* We can drop the bundled
"Implement-YAML-state-tracking-and-use-it-in-the-DBus.patch" from the Hirsute
and Focal debdiffs (it has already been SRUed in the meantime).
* We need to fix the version strings
** Changed in: netplan.io (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771740
Title:
Expose link offload options
To manage notifications about
Thank you for this very clean MIR request.
TODO: MIR team ACK, pending clarification of the testing situation.
I understand that proper testing is a 22.04 item, but we should at
least have an example from the current local testing to feel confident
that this will be fully in place before 22.04
Thank you Brian for accepting it into hirsute-proposed!
I've tested usrmerge 24ubuntu3.1 from hirsute-proposed, all good:
$ lxc launch ubuntu:bionic usrmerge
$ lxc exec usrmerge bash
# do-release-upgrade
[...]
# reboot
# ls -la /
total 96
drwxr-xr-x 22 root root 4096 Oct 21 15:54 .
Thank you Brian for accepting it into impish-proposed!
I've tested usrmerge 25ubuntu1.1 from impish-proposed, all good:
$ lxc launch ubuntu:bionic usrmerge
$ lxc exec usrmerge bash
# do-release-upgrade
[...]
# reboot
# ls -l /
total 88
drwxr-xr-x 2 root root12288 Oct 27 13:39 bin
tus: New => Incomplete
** Changed in: vulkan (Ubuntu Bionic)
Status: New => Incomplete
** Changed in: vulkan (Ubuntu Bionic)
Assignee: (unassigned) => Lukas Märdian (slyon)
** Also affects: vulkan (Ubuntu Jammy)
Importance: Undecided
Status: Invalid
** Also affects
Hi Miriam!
I checked the vulkan-tools MIR for Jammy/Impish/Hirsute/Focal, which looks
rather straight forwards, but requires a few additional changes before the MIR
team can give the final ACK.
Also, I checked the vulkan MIR for Bionic, that seems to be much more
complicated. Please see my
** Changed in: wsl-setup (Ubuntu)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948392
Title:
[MIR] wsl-setup
To manage notifications ab
** Description changed:
+ [Impact]
+
+ * Starting with Ubuntu Hirsute, the 'usrmerge' package is pulled into
+ the default installation, doing the merging of /{bin,sbin,lib}/ and
+ /usr/{bin,sbin,lib} on upgrade. If there are left-over generated files
+ it will fail with an error like this:
+
** Also affects: usrmerge (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: usrmerge (Ubuntu Jammy)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you Nicolas,
I cleaned up some fuzz and whitespace around the "activation_mode" field
in src/parse.h but other than that the patch looks like I wanted it to
be (wrt. ABI compatibility).
I've uploaded it to Jammy. Let's see how that works out wrt.
autopkgtests. If everything is good and
** Also affects: netplan.io (Ubuntu Jammy)
Importance: Wishlist
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/1771740
Title:
Expose link offload options
To manage
I Tested netplan.io 0.103-0ubuntu5~20.04.2 inside a fresh Focal LXD container:
$ lxc launch ubuntu-daily:focal ff
$ lxc exec ff bash
=> Enabled focal-proposed & installed/upgraded netplan.io
root@ff:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.103-0ubuntu5~20.04.2
ii
I Tested netplan.io 0.103-0ubuntu5~20.04.2 inside a fresh Focal LXD container:
$ lxc launch ubuntu-daily:focal ff
$ lxc exec ff bash
=> Enabled focal-proposed & installed/upgraded netplan.io
root@ff:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.103-0ubuntu5~20.04.2
ii
I Tested netplan.io 0.103-0ubuntu5~21.04.2 inside a fresh Hirsute LXD container:
$ lxc launch ubuntu-daily:hirsute hh
$ lxc exec hh bash
=> Enabled hirsute-proposed & installed/upgraded netplan.io
root@hh:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.103-0ubuntu5~21.04.2
ii
Indeed, a `netplan set network=null` would basically be the same as `rm
/etc/netplan/*.yaml`.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942930
Title:
Unset a subtree crashes
To manage
I Tested netplan.io 0.103-0ubuntu5~21.04.2 inside a fresh Hirsute LXD container:
$ lxc launch ubuntu-daily:hirsute hh
$ lxc exec hh bash
=> Enabled hirsute-proposed & installed/upgraded netplan.io
root@hh:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.103-0ubuntu5~21.04.2
ii
** Changed in: libunity (Ubuntu Impish)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945969
Title:
Update Vala to 0.52.6 in Impish
To manage notifications
** Changed in: netplan
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814012
Title:
netplan type wifis needs a device option
To manage notifications about
A related change to automatically fallback inside wpa_supplicant itself
just landed: https://launchpad.net/ubuntu/+source/wpa/2:2.9.0-23
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814012
Title:
** Also affects: util-linux (Ubuntu Jammy)
Importance: Low
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/1944741
Title:
HiFive Unmatched partitions are named "Unleashed"
To
Thank you Steve, for accepting glm into impish-proposed.
The reported autopkgtest regression on asymptote/2.70+ds-2 (armhf) was
resolved by retry.
Also, the build in impish-proposed passed for version
"0.9.9.8+ds-1ubuntu1":
** Also affects: glm (Ubuntu Jammy)
Importance: Undecided
Status: 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/1946750
Title:
FTBFS with GCC-11
To manage notifications
Public bug reported:
Switching applications between normal and fullscreen got slower and also it
won't remember position and size of the window on exiting fullscreen compared
to gnome 3.x.
I can also confirm this on a 20.04 installation with gnome 40 installed, that
this is a degradation for
** Changed in: docker.io (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947004
Title:
Please remove src:aufs-tools from Ubuntu
To manage notifications
** Patch added: "docker.debdiff"
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1947004/+attachment/5532829/+files/docker.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947004
Hi Nicolas,
yes I meant to simply add it to the struct at the correct (upstream)
location, so that the data structure won't change (only append new
fields) when we release the next upstream version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
- Please remove src:aufs-tools and all its binaries from Ubuntu.
+ Please remove src:aufs-tools and all its binaries from Ubuntu (JJ).
This includes:
src:aufs-tools 1:4.14+20190211-1ubuntu1
aufs-tools[-dbgsym] 1:4.14+20190211-1ubuntu1
aufs-tools has been
No need for 0-day SRU. This has been sponsored into Debian unstable and
will be synced to Ubuntu. Thanks @seb128!
https://tracker.debian.org/news/1266939/accepted-
libunity-714190420190319-6-source-into-unstable/
** Summary changed:
- FTBFS with valac 0.52.6 in impish
+ Update to 0.52.6 in
Public bug reported:
Please remove src:aufs-tools and all its binaries from Ubuntu.
This includes:
src:aufs-tools 1:4.14+20190211-1ubuntu1
aufs-tools[-dbgsym] 1:4.14+20190211-1ubuntu1
aufs-tools has been dropped from Debian testing last year
Yes indeed only releases later than Impish will support this
functionality in netplan as it depends on some fixes in systemd v249.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938299
Title:
** Summary changed:
- Update to 0.52.6 in impish
+ FTBFS with valac 0.52.6 in impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945969
Title:
FTBFS with valac 0.52.6 in impish
To manage
** Also affects: vala (Ubuntu Impish)
Importance: High
Assignee: Rico Tzschichholz (ricotz)
Status: Fix Released
** Also affects: libunity (Ubuntu Impish)
Importance: High
Assignee: Lukas Märdian (slyon)
Status: Fix Committed
--
You received this bug notification
** Description changed:
+ [Impact]
+
+ * glm FTBFS using GCC 11, which makes it hard to apply any (security)
+ updates in a timely manner.
+
+ [Test Plan]
+
+ * Check the Launchpad build logs to make sure that glm
+ 0.9.9.8+ds-1ubuntu1 built successfully
+ * Attach build logs to this bug
+
This is a FTBFS fix for libunity that could become an impish 0-day SRU.
PPA pre-testing has been done here:
https://launchpad.net/~slyon/+archive/ubuntu/testing/+sourcepub/12784335/+listing-
archive-extra
** Description changed:
+ [Impact]
+
+ * libunity FTBFS using valac 0.52.6, which makes
From a netplan POV this has already been changed upstream as part of
https://github.com/canonical/netplan/pull/200
I.e. the "systemctl stop/start systemd-networkd.service" have been
replaced by "networkctl reload/reconfigure" calls instead. Due to an
incompatibility with systemd v247 that change
Thank you! You changes LGTM.
The first patch resembles the upstream commit, the 2nd patch (that touches the
translation files) is not yet merged upstream, but makes sense.
With all builds passing in a PPA and a successful autopkgtest run, I'll
stage this to be a 0-day SRU, as discussed with the
Public bug reported:
Unit-tests are failing if built using GCC-11.
```
99% tests passed, 2 tests failed out of 188
Total Test time (real) = 3.86 sec
The following tests FAILED:
39 - test-core_func_integer (Child aborted)
97 - test-ext_vector_integer (Child aborted)
```
** Also affects: util-linux (Ubuntu Impish)
Importance: Low
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/1944741
Title:
HiFive Unmatched partitions are named "Unleashed"
To
** Also affects: libunity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libunity (Ubuntu)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** Tags added: fr-1793
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830507
Title:
Missing support of mDNS
To manage notifications about this bug go to:
Some work is being proposed here:
https://github.com/canonical/netplan/pull/237
** Changed in: netplan
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830507
Title:
** Changed in: egl-wayland (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935082
Title:
[MIR] egl-wayland
To manage notifications about this bug go
There is some documentation around how to implement this with netplan
here: https://netplan.io/faq/#use-pre-up%2C-post-up%2C-etc.-hook-scripts
But its basically using the underlying renderer's (NM or networkd-
dispatcher) hooks, as netplan itself is not a networking daemon and
cannot easily
Thank you for testing. The Focal backport might need some more work, as
that version of systemd is even older and the patches did not apply
cleanly.
For Hirsute it was a straightforward cherry-pick of patches from
systemd-stable v247 (MergeProposal attached to this bug report). So I
wonder if we
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu
I am generally +1 with SRUing this, BUT this is a special in a few ways:
1/ In order to land this in Focal, we first need to apply it to Impish
and Hirsute (according to SRU process), as ddstreet mentioned.
2/ We are already post Feature Freeze for Impish and this is adding new
functionality IMO
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu
Hello Brian, thanks for accepting this SRU into bionic-proposed.
I've tested netplan.io 0.99-0ubuntu3~18.04.5
root@bb:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.99-0ubuntu3~18.04.5 amd64
ii netplan.io 0.99-0ubuntu3~18.04.5 amd64
** Changed in: systemd (Ubuntu Impish)
Status: Fix Released => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938259
Title:
Add ACCEL_LOCATION=base property for Dell clamshell
** Changed in: netplan.io (Ubuntu Hirsute)
Status: Fix Committed => Fix Released
** Changed in: netplan.io (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan
Status: Triaged => Fix Committed
** Also affects: netplan.io (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu Focal)
Importance:
Well.. considering this is a SRU, we should probably not fix the memory-leak
within this bug but restrict ourselves to the minimal required change, as
provided here.
Also, checking out the upstream github repo shows a 664 filemode for curl.* so
that must have been a hiccup on my side.
So LGTM
Closing, as agreed upon with the SRU team:
https://code.launchpad.net/~slyon/ubuntu/+source/systemd/+git/systemd/+merge/408816/comments/1079349
** Changed in: systemd (Ubuntu Focal)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received
For focal the patches look good, too. The cherry-picks match upstream
and the backport looks sane.
I only have two small questions regarding the backpor:
1/ Should we cherry-pick
https://github.com/ibm-s390-linux/s390-tools/commit/db6f272607842a6279fee589fb101f3a1f6148f3
as well? This would
The patch applied to Hirsute resembles the upstream commit and applies
cleanly. LGTM.
$ dput ubuntu ../s390-tools_2.16.0-0ubuntu1.1_source.changes
D: Setting host argument.
Checking signature on .changes
gpg: ../s390-tools_2.16.0-0ubuntu1.1_source.changes: Valid signature from
5889C17AB1C8D890
** Changed in: binutils (Ubuntu)
Status: Invalid => Confirmed
** Changed in: binutils (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940505
Title:
In more recent kernels (i.e. linux-meta-aws/azure 5.13) I can see
messages like this: " watchdog: BUG: soft lockup - CPU#3 stuck for
238s!" that seems to indicate the kernel is not giving back control to
the userspace/systemd.
Also a message about a missing autofs4 module, that might be related:
** Changed in: binutils (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940505
Title:
monero FTBFS on riscv64
To manage notifications about this bug go to:
Thanks for confirming Denys, that's unfortunate...
Would you mind giving the version from this PPA a try
https://launchpad.net/~slyon/+archive/ubuntu/lp1934221 (for Hirsute)?
And maybe also for Focal once the build is ready?
--
You received this bug notification because you are a member of
Public bug reported:
Happened during the upgrade from Ubuntu 20.10 to 21.04
ProblemType: Package
DistroRelease: Ubuntu 21.04
Package: dovecot-core 1:2.3.13+dfsg1-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
** Merge proposal linked:
https://code.launchpad.net/~slyon/ubuntu/+source/systemd/+git/systemd/+merge/408816
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943982
Title:
Revert
Unfortunately, this patch does not seem to be sufficient.
It produces very similar segfaults in on_query_timeout
(https://errors.ubuntu.com/problem/c4e5be3f1c7af9483993c7e6007b9325ab5b78cd)
that the segfault we could observe before
Public bug reported:
[impact]
The initial patch for LP: #1934221 was not sufficient to fix the root
cause of the segfault, but rather moved it to a slightly different
location in the code (still inside the on_query_timeout handler).
[test case]
this bug is only to revert the previous patch
Some more findings after testing with systemd-run:
FAIL: lxc-tests: lxc-test-autostart (360s)
FAIL: lxc-tests: lxc-test-no-new-privs (361s)
This two tests fail during the (local) autopkgtest run. But after logging into
the local autopkgtest VM via its debug shell (--shell-fail|-s parameter) and
From a side-channel discussion:
all the fully unprivileged tests need to be disabled on
cgroup v2. You can't run fully unprivileged containers on pure cgroup2
layouts. The delegation model doesn't allow it. Not without systemd
making a fully empty delegated cgroup hierarchy available.
I think
Addressed in FR-1460
** Tags removed: rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
dbus timeout-ed during an upgrade, taking services down including gdm
To manage
Thanks for working out the kinks, Didier!
MIR team ACK
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936907
Title:
[MIR] ADSys
To manage notifications about this bug go to:
** Changed in: snapd
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850667
Title:
Switch to "unified" cgroup hierarchy (cgroupv2)
To manage notifications
** Attachment added: "lxc-vs-old-systemd.log"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1943704/+attachment/5525407/+files/lxc-vs-old-systemd.log
** Description changed:
lxc fails 4 autopkgtests if ran on a cgroups v2 enabled systemd
(248.3-1ubuntu7) using a pure unified
Public bug reported:
lxc fails 4 autopkgtests if ran on a cgroups v2 enabled systemd
(248.3-1ubuntu7) using a pure unified hierarchy (in favor of the hybrid
hierarchy used before).
https://autopkgtest.ubuntu.com/packages/lxc
FAIL: lxc-tests: lxc-test-apparmor-mount (0s)
FAIL: lxc-tests:
[Summary]
Overall this is looking fine, but we need to make sure to fix a few things
around it. As this is a go binary with many vendorized dependencies, you also
need to explicitly state your commitment to support the security team with
security and dependency updates. Please do so in this bug
snapd landed the support in upstream git as of yesterday
(https://github.com/snapcore/snapd) and it is expected to be shipped
with snapd v2.53
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850667
601 - 700 of 2500 matches
Mail list logo
