** Description changed:
- TBD
+ [Availability]
+ The package src:dh-elpa is already in Ubuntu universe.
+ The package dh-elpa-helper build for the architectures it is designed to work
on
+ It currently builds and works for architectures: all (arch independent)
+ Link to package [[https://launchpa
This is about the lz4 binary package. src:lz4 is in main already.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953407
Title:
[MIR] lz4 (again!)
To manage notifications about this bug go to:
https
I'm pretty much with @ddstreet here, introducing another hack to handle
Ubuntu Core quirks is not nice, as those hacks will make our systemd
more unstable over time and will break regularly after merging upstream
changes.
As stated before, we already carry such hacks since 2014 and I just want
to
Do I see that right, that this means for people wanting to use wayland
and have working screensharing (which is a kind of important thing to
have working right now), are forced to use a non-LTS Ubuntu version
21.04+?
And until the fix for [1] makes it into 21.10, it's basically 21.04 only that's
** Also affects: cmake (Ubuntu)
Importance: Undecided
Status: New
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951066
Title:
[MIR] dh-elpa
To manage notifi
I'm pulling the verification-done-focal tag, because netplan.io
0.103-0ubuntu5~20.04.4 FTBFS on focal/risvv64, due to a slow dbus test
at build time.
I've uploaded 0.103-0ubuntu5~20.04.5 into Focal UNAPPROVED that carries
a patch to give some more time to this specific test and fixes the build
in
Thanks for the clarification. Now it all makes sense to me (as Impish is
on kernel >= 3.13) and it means that the revert wasn't actually needed
for Impish.
So on Impish I will apply the same patch as in Jammy, which is basically
the same that was reverted before due to a mistake in SRU verificatio
Thanks! I'm taking the upstream commit
https://github.com/systemd/systemd/commit/5ed0ea29287621fb3c51b7917c34c7b8ac280eba
(LP: #1926547) instead of squeezing that change into the Impish/systemd
v248 debdiff. Otherwise this LGTM!
--
You received this bug notification because you are a member of Ub
Hey, thank you for providing an updated patch!
I've included it in todays systemd v249 upload in jammy:
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?h=ubuntu-jammy&id=9f99081482b76a7b717e39ef4380f08093e4359a
Jammy uses kernel 5.15 so it is fine to drop the modalias na
This affects Impish as well. The commit was included in upstream v249.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926547
Title:
Add Dell Privacy Mic Mute Key mapping
To manage notifications abo
** Also affects: systemd (Ubuntu Impish)
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/1926547
Title:
Add Dell Privacy Mic Mute Key mapping
To manage not
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
** Also affects: systemd (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Hirsute)
Yes.. LXD's system containers and systemd/udev have a special kind of
relationship and we should strive to resolve that situation properly
long-term. I already talked to stgraber about that, but I guess we
should lay out a proper path forward as continuously patching more and
more components of sys
** Also affects: systemd (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Medium
Status: New
** Also affects: systemd (Ubuntu Hirsute)
I
released in 249.5-2ubuntu1
** Changed in: systemd (Ubuntu Jammy)
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/1950511
Title:
FTBFS due to meson disallowi
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950787
Title:
systemd-sysusers cannot mount /dev in privileged containers
** Changed in: pastebinit (Ubuntu)
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/1844128
Title:
deprecation warnings
To manage notifications about this bug go to:
** Changed in: pastebinit (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785821
Title:
"pastebinit -i file" to paste.openstack.org fails: Object of t
** Tags added: fr-1896
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952733
Title:
Add Dell Privacy Mic Mute Key mapping for another Dell machine
To manage notifications about this bug go to:
http
** Tags added: fr-1897
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952735
Title:
Add Microphone mute key mapping for Dell machine
To manage notifications about this bug go to:
https://bugs.launc
** Tags added: fr-1895
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943561
Title:
Add ACCEL_LOCATION=base property for 6 Dell clamshell models
To manage notifications about this bug go to:
https:
I tested netplan.io 0.103-0ubuntu5~20.04.4 from focal-proposed and
attached the official autopkgtest logs, all passed.
root@ff:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.103-0ubuntu5~20.04.4
ii netplan.io 0.103-0ubuntu5~20.04.4
root@ff:~# ./netplan-dbus-perculiar2.sh
method return time=163
I tested netplan.io 0.103-0ubuntu5~20.04.4 from focal-proposed and
attached the official autopkgtest logs, all passed.
root@ff:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.103-0ubuntu5~20.04.4
ii netplan.io 0.103-0ubuntu5~20.04.4
root@ff:~# cat check.sh
#!
I tested netplan.io 0.103-0ubuntu5~21.04.4 from hirsute-proposed and
attached the official autopkgtest logs, all passed.
root@hh:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.103-0ubuntu5~21.04.4
ii netplan.io 0.103-0ubuntu5~21.04.4
root@hh:~# ./netplan-dbus-perculiar2.sh
method return time=1
I tested netplan.io 0.103-0ubuntu5~21.04.4 from hirsute-proposed and
attached the official autopkgtest logs, all passed.
root@hh:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.103-0ubuntu5~21.04.4
ii netplan.io 0.103-0ubuntu5~21.04.4
root@hh:~# cat check.sh
#
I tested netplan.io 0.103-0ubuntu7.2 from impish-proposed and attached
the official autopkgtest logs, all passed.
root@ii:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.103-0ubuntu7.2
ii netplan.io 0.103-0ubuntu7.2
root@ii:~# ./netplan-dbus-perculiar2.sh
method return time=1638359097.746850 s
I tested netplan.io 0.103-0ubuntu7.2 from impish-proposed and attached
the official autopkgtest logs, all passed.
root@ii:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.103-0ubuntu7.2
ii netplan.io 0.103-0ubuntu7.2
root@ii:~# cat check.sh
#!/bin/bash
path=$(d
The netplan.io/0.103-0ubuntu5~21.04.4 (arm64) autopkgtest regression was
resolved by retry.
** Description changed:
[Impact]
snapd uses netplan's DBus API to create config objects and set/try/apply
changed configuration. It uses origin-hints (like 90-snapd-conf.yaml) to
separate it's config
The netplan.io/0.103-0ubuntu5~21.04.4 (arm64) autopkgtest regression was
resolved by retry.
** Description changed:
[Impact]
snapd uses netplan's DBus API to create config objects and set/try/apply
changed configuration.
There is a race condition in io.netplan.Netplan.Config.Try() that
** Changed in: netplan
Status: In Progress => 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/1949893
Title:
new interface does not show up after dbus config apply
To manage noti
** Changed in: netplan
Status: In Progress => 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/1946957
Title:
Unset of a subtree crashes with invalid (non existing) origin-hint
To
** Description changed:
+ [Impact]
+ snapd uses netplan's DBus API to create config objects and set/try/apply
changed configuration.
+
+ There is a race condition in io.netplan.Netplan.Config.Try() that
+ returns the DBus call too early, when the 'netplan try' subprocess call
+ is not yet fully
** Description changed:
+ [Impact]
+ snapd uses netplan's DBus API to create config objects and set/try/apply
changed configuration. It uses origin-hints (like 90-snapd-conf.yaml) to
separate it's configuration from the user owned YAML configuration.
+
+ If this origin-hint file does not exist
Yes, indeed. NetworkManager tries to control all interfaces that are
available by default and netplan implemented some quirks in the past to
avoid this. But we should review those quirks and rather implement a
per-interface/netdef deny- or accept-list.
** Tags added: fr-1888
** Changed in: netpla
** Tags added: fr-1887
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949893
Title:
new interface does not show up after dbus config apply
To manage notifications about this bug go to:
https://bugs
** Tags added: fr-1886
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952599
Title:
virt: Support detection for ARM64 Hyper-V guests (fixed upstream)
To manage notifications about this bug go to:
h
Adding another reproducer script to check for all the different cases
reported (also from the duplicate bugs).
** Attachment added: "repro.sh"
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1946957/+attachment/5544083/+files/repro.sh
--
You received this bug notification because y
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu Foca
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu Impis
** Also affects: systemd (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Hirsute)
This is already included in v249.5 stable, that is to be uploaded soon.
(https://git.launchpad.net/~slyon/ubuntu/+source/systemd/log/?h=ubuntu-
jammy-249)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
no use of user nobody
- no use of setuid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- not part of the UI for extra checks
- no translation present, but none needed for this case
Problems:
- use of sudo in src/wg-quick/linux.b
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951399
Title:
Ubuntu, Budgie, Kubuntu, Kylin, MATE, Xubuntu: jammy daily fails to
install
To manage notifications about this bug go to:
https://bugs.
** Tags added: fr-1885
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650688
Title:
timedatectl set-timezone fails on UC16
To manage notifications about this bug go to:
https://bugs.launchpad.net/s
** Tags added: fr-1884
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951214
Title:
ubuntu-bug isn't opening firefox (snap) on jammy, instead gedit gets
data
To manage notifications about this bu
Indeed our current default networking setup is lacking some
functionality from "wg", that is the key generation and display of
dynamic information (like "lastest-handshake" and "transfer-rx/tx" from
"wg show"), while most of the other static information of a current
WireGuard setup is also availabl
Hi Andreas, thank you for this high quality MIR!
Unfortunately this is a tentative MIR team NACK, as it duplicates
functionality that we already have in Ubuntu main.
I understand you point of openvpn != wireguard and therefore we need
wireguard VPN support in main, too.
But netplan.io has been s
** Changed in: systemd (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/1950794
Title:
DHCPv4 (IAID+DUID) networking broken in LXC containers
To manage not
versions, I am
sticking to 21.04 for now.
Best regards
Lukas
** Affects: linux (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/1951717
Title
I'm still suspecting dbus to be at fault here. We might need to bisect
dbus in order to find out more about this, but that is hard without a
reliable reproducer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Thanks ddstreet, I agree 918e6f1c0151429f5095355f4f3f74f16e79724a could
be related as well, but unfortunately that commit produced quite some
fall-out.
Nevertheless, I've prepared a new systemd build in my PPA and the
"core18_2028_amd64.snap" at https://people.ubuntu.com/~slyon/uc18/
cherry-pi
Reverting this upstream commit seems to fix the problem:
https://github.com/systemd/systemd/commit/0299deab53d2a087727a5d04c1500c322c48b63e
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950794
Title:
Turns out dropping "debian/patches/units-Don-t-start-systemd-udev-
trigger.service-in-a-conta.patch" (that we want to drop anyway) makes a
difference here, i.e. removing the "ConditionVirtualization=!container"
line from /usr/lib/systemd/service/systemd-udev-trigger.service.
# apt install systemd
As in the past, we do not really need a MIR re-review for a version bump
like this, so this is just a formalism:
MIR team ACK
But please add a bug-subscriber (=ubuntu-server) for the new
postgresql-14 package and let's make sure to demote the old
postgresql-13 package before the end of the Jammy
Public bug reported:
TBD
** Affects: raqm (Ubuntu)
Importance: Undecided
Status: New
** Tags: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951069
Title:
[MIR] raqm
To mana
Public bug reported:
TBD
** Affects: libio-prompt-tiny-perl (Ubuntu)
Importance: Undecided
Status: New
** Tags: jammy
** Changed in: libio-prompt-tiny-perl (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Public bug reported:
TBD
** Affects: dh-elpa (Ubuntu)
Importance: Undecided
Status: New
** Tags: jammy
** Changed in: dh-elpa (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
TBD
** Affects: libio-interactive-perl (Ubuntu)
Importance: Undecided
Status: New
** Tags: jammy
** Changed in: libio-interactive-perl (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Thank you, having a reliable reproducer is very helpful! I can confirm
this reproduces locally for me on QEMU.
I prepared a new systemd package [0], containing backports from the
above mentioned PR that indeed sounds very related (I wonder why the
issue didn't happen before, tho, as this is unrela
I've implemented the workaround in systemd's debian/test/tests-in-lxd.
** Changed in: systemd (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/1950787
Title:
Public bug reported:
DHCPv4 networking does not work in the default IAID+DUID
(ClientIdentifier=duid) mode in LXC containers, using systemd-networkd
v249.5-2ubuntu1. Static configuration and DHCPv6 work without problem.
Reproducer:
$ lxc launch ubuntu-daily:jammy jj
$ lxc exec jj bash
# add-apt-r
This commit seems to be related:
https://github.com/lxc/distrobuilder/commit/33a4302ca5a62ed9eb9009dcc5059aecfb55ba41
But why does it not work in privileged containers?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Attachment added: "debug.log"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950787/+attachment/5540415/+files/debug.log
** Description changed:
systemd-sysusers.service/systemd.exec fails to start in privileged
containers, due to being unable to properly mount /dev for passing
Public bug reported:
systemd-sysusers.service/systemd.exec fails to start in privileged containers,
due to being unable to properly mount /dev for passing credentials, caused by
the following config in the .service unit:
```
# Optionally, pick up a root password and shell for the root user from
I've tested netplan.io 0.103-0ubuntu5~20.04.3 from focal-proposed.
The netplan generator command was run successfully, producing correct
*Offload=1 settings for networkd.
root@sru-ff:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.103-0ubuntu5~20.04.3 amd64 YAML network configuration
abstractio
I've tested netplan.io 0.103-0ubuntu5~20.04.3 from focal-proposed.
The 'netplan try' command was run successfully without any "An error
occurred" message:
root@sru-ff:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.103-0ubuntu5~20.04.3amd64
YAML network conf
I've tested netplan.io 0.103-0ubuntu5~20.04.3 from focal-proposed.
The netplan generator command was run successfully, producing correct
"scope: link" routes with empty gateway/next_hop:
root@sru-ff:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.103-0ubuntu5~20.04.3 amd64 YAML network configura
I've tested netplan.io 0.103-0ubuntu5~21.04.3 from hirsute-proposed.
The netplan generator command was run successfully, producing correct
*Offload=1 settings for networkd.
root@sru-hh:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.103-0ubuntu5~21.04.3 amd64 YAML network configuration
abstract
I've tested netplan.io 0.103-0ubuntu5~21.04.3 from hirsute-proposed.
The 'netplan try' command was run successfully without any "An error
occurred" message:
root@sru-hh:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.103-0ubuntu5~21.04.3
I've tested netplan.io 0.103-0ubuntu5~21.04.3 from hirsute-proposed.
The netplan generator command was run successfully, producing correct
"scope: link" routes with empty gateway/next_hop:
root@sru-hh:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.103-0ubuntu5~21.04.3 amd64 YAML network configu
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 generator command was run successfully, producing correct
*Offload=1 settings for networkd.
root@sru-ii:~# dpkg -
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 generator command was run successfully, producing correct
"scope: link" routes with empty gateway/next_hop:
root@
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
occ
** 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 for
** 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' obj
** 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", "route4=3.
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/* debian/systemd/lib/sys
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
debian/systemd/usr/lib/system
** 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 ab
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 de
** 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, whi
** 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 src:aufs-t
** 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 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' obj
** 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", "route4=3.
** 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 for
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 inclu
** 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 Ub
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&id=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 notificat
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 fa
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" route
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 i
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
https://github.com/systemd/systemd-stable/commit/
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 Progres
701 - 800 of 2676 matches
Mail list logo
