Arguably, the "/usr/lib/netplan/00-network-manager-all.yaml" should be
shipped by the network-manager package, instead of ubuntu-settings...
The community flavors using Calamares, might be covered by this PR:
https://github.com/calamares/calamares/pull/2284
** Also affects: ubuntu-settings (Ubunt
** Changed in: netplan
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2060311
Title:
Setting "optional: true" to overcome he ti
You filed the bug report against NetworkManager. But the "up.d" hook is
called differently in NM, see https://netplan.io/faq#use-pre-up-post-up-
etc-hook-scripts
If this is about /etc/network/if-up.d then it should be targeted towards
the "ifupdown" package. I'm adding a corresponding bug task.
*
You can put your trunk (enp3s0) as "optional: true" and it will still
wait for the vlans to be up. We might consider marking interfaces with
empty configuration (like "enp3s0: {}") to be "optional: true" by
default...
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You rec
This sounds like it needs a backported feature for systemd-networkd in
Focal, i.e. something that got fixed in networkd.
Did you try adding the "on-link: true" setting to your static routes in
the Netplan configuration? That might be able to work around the issue.
** Changed in: netplan.io (Ubunt
Public bug reported:
The failure was introduced by this change in Debian:
https://salsa.debian.org/debian/libgpg-error/-/commit/0c11fe4ae16c2800e13758ff1ee64c561354e628
It started to fail for i386 on autopkgtest.u.c:
https://autopkgtest.ubuntu.com/packages/libgpg-error/kinetic/i386
https://autopk
** Changed in: netplan.io (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1951653
Title:
can't use NM for ether
Thank you for all the background information, Dave!
I've drafted a PR at upstream netplan, to allow setting the regulatory
domain via wpa_supplicant.conf as well as setting it "globally" via 'iw
reg set XX', using a systemd service unit.
https://github.com/canonical/netplan/pull/281
--
You rece
** Tags added: fr-2436
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1969375
Title:
systemd-cryptenroll does not support TPM2 devices
Status in systemd package in Ubuntu
emd (Ubuntu Jammy)
Assignee: (unassigned) => Lukas Märdian (slyon)
** Changed in: systemd (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Kinetic)
Status: Confirme
After the autopkgtest branch was merged, we're now testing a Multi-Arch fix:
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13655308/+listing-archive-extra
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lib
Public bug reported:
[Impact]
* The deb to snap transitional 'lxd' package was removed post feature-freeze
in Jammy
* this leads to systemd's 'tests-in-lxd' autopkgtest being skipped:
* "tests-in-lxd SKIP installation fails and skip-not-installable set"
* It reduces systemd's test
This patch should probably do the trick (to be verified).
** Patch added:
"0001-Run-tests-in-lxd-autopkgtest-via-LXD-snap-the-deb-is.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1976607/+attachment/5594484/+files/0001-Run-tests-in-lxd-autopkgtest-via-LXD-snap-the-deb-is.patch
** Description changed:
- This build log provides an example of the problem:
- https://autopkgtest.ubuntu.com/results/autopkgtest-
- impish/impish/ppc64el/s/systemd/20220331_190433_fdbbe@/log.gz.
+ [Impact]
+
+ * The "tests-in-lxd/boot-and-services/test_no_failed" autopkgtest fails
+ * it did n
** Tags added: block-proposed-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1969375
Title:
systemd-cryptenroll does not support TPM2 devices
Status in systemd pack
** Description changed:
+ [Impact]
+
+ * TPM2/FIDO cannot be used to unlock luks encrpyted block devices
+ * due to missing build-time support in systemd
+ * Error message: "TPM2 not supported on this build."
+
+ [Test Plan]
+
+ # prepare test
+ $ sudo apt install libtss2-rc0 # runtime depen
We're combining this SRU with LP: #1964494 (and other autopkgtest
related changes) so I'm removing the block-proposed-jammy tag.
** Tags removed: block-proposed-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
This SRU should be combined with LP: #1969375 as uploaded in
249.11-0ubuntu3.3 (containing some more autopkgtest related changes)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bu
@tbennett6421 Yes, please make use of the "optional: true" stanza in
your interface definitions.
https://netplan.io/reference/#common-properties-for-all-device-types
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
** Changed in: systemd (Ubuntu Jammy)
Status: New => In Progress
** Changed in: systemd (Ubuntu Jammy)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to syst
Looks like this was obsoleted by
https://launchpad.net/ubuntu/+source/logrotate/3.20.1-1ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1973607
Title:
Please merg
Looks like this was obsoleted by
https://launchpad.net/ubuntu/+source/logrotate/3.20.1-1ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1973607
Title:
Please merg
** Changed in: systemd (Ubuntu Kinetic)
Status: Triaged => Fix Committed
** Changed in: systemd (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https:
** Changed in: systemd (Ubuntu Jammy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1969375
Title:
systemd-cryptenroll does not supp
** Changed in: netplan
Status: New => In Progress
** Changed in: netplan
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Thank you for the review!
Turns out there is a new binary dependency after all: "libssl3", but
fortunately that one is already installed by default, so should still be fine.
I've added test-case #1 (binary-depends), #2 (undefined-symbols), #3
(non-tpm/password/recovery-key), #4 (fido2) in additio
The patch pasted above doesn't fully work. We need something like this:
diff --git a/debian/tests/control b/debian/tests/control
index e7d7c3ab045..0e3ab7625b2 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -122,7 +122,7 @@ Depends: systemd-tests,
libpam-systemd,
autopkgtest,
gned) => Nick Rosbrook (enr0n)
** Changed in: systemd (Ubuntu Jammy)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1976
Marking as "In Progress" (for Kinetic) according to:
https://discourse.ubuntu.com/t/foundation-team-updates-
thursday-09-june-2022/28788/9
** Changed in: systemd (Ubuntu)
Status: New => In Progress
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
Yo
Marking as "In Progress" for Kinetic, as this will be brought in via the
systemd v251 merge from Debian unstable, planned for end of June.
** Changed in: systemd (Ubuntu Kinetic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch
I've tested systemd 249.11-0ubuntu3.3 from jammy-proposed, all looking good!
$ apt list systemd
Listing... Done
systemd/jammy-proposed,now 249.11-0ubuntu3.3 amd64 [installed]
# 1: only "libssl3" is added as a binary dependency (as expected) plus some new
"Suggests":
$ apt-cache depends systemd >
** Bug watch added: Red Hat Bugzilla #1941170
https://bugzilla.redhat.com/show_bug.cgi?id=1941170
** Also affects: systemd (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1941170
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
autopkgtests passed after re-triggering some.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bug
I've tested systemd 249.11-0ubuntu3.3 from jammy-proposed, all tests
passed, especially the "boot-and-services" test cases:
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/s/systemd/20220611_235311_cd56e@/log.gz
autopkgtest [23:52:23]: summary
timedated
I've tested systemd 249.11-0ubuntu3.3 from jammy-proposed, all tests
passed, especially the "tests-in-lxd" test cases, on all architectures
but armhf. This is expected as armhf test runners are using a LXD
backend and do not run nested LXD tests.
https://autopkgtest.ubuntu.com/results/autopkgtest-
** Tags added: rls-jj-incoming
** Tags added: rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1972159
Title:
systemd-oomd frequently kills firefox and visu
As discussed on the mailing list, would you be able to test a
modification to the systemd-oomd configuration by placing a new file in
/etc and report back if that improves the situation for you (after a
reboot)?
$ cat /etc/systemd/system/-.slice.d/10-oomd-root-slice-defaults.conf
[Slice]
ManagedO
Netplan generates configuration snippets to make sure an interface is
only handled by the backend renderer (networking-daemon: sd-networkd or
NetworkManager) that is instructed to control that interface nowadays.
This logic has been improved recently:
https://github.com/canonical/netplan/pull/276
This seems to be working nowadays. I cannot reproduce using the config
provided in the description:
$ netplan apply
$ ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
vali
This is still an issue. I like the idea of deleting the bond (e.g.
"networkctl delete bond0" during the "netplan apply" call. But as stated
before by daxtens, we need to make sure not to bring down critical
interfaces, that might be in use.
We could either only apply this only to interfaces, that
** Tags added: fr-2547
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Tags removed: rls-jj-incoming rls-kk-incoming
--
You received this bug notification because you ar
** Tags added: fr-2548
** Tags removed: rls-kk-incoming
** Also affects: powermgmt-base (Ubuntu Kinetic)
Importance: High
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu.
The fix is already included in systemd >= v250 (i.e. Kinetic+)
** Tags added: fr-2550
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Tags removed: rls-jj-incoming
--
You received this bu
** Tags added: fr-2552
** Also affects: isc-dhcp (Ubuntu Kinetic)
Importance: Undecided
Status: Confirmed
** Also affects: isc-dhcp (Ubuntu Jammy)
Importance: Undecided
Status: New
** Tags removed: rls-jj-incoming
--
You received this bug notification because you are a memb
I can reproduce this, did some investigation on it and I agree that this
behavior of overriding /etc/resolv.conf -> /run/systemd/resolve/stub-
resolv.conf (managed by sd-resolved) is very bad.
The sd-resolved hook was moved from
https://launchpad.net/ubuntu/+source/systemd/246-2ubuntu1 to
https://
This hits an assert() in systemd-networkd so I'm assigning it to the
src:systemd package.
=> Assertion 'ifindex' failed at src/network/networkd-link.c:757,
function link_get(). Aborting.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notif
** Tags added: rls-ff-incoming
** Changed in: netplan
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930482
Title:
netplan crash on ubuntu
Thanks for confirming, Pedro. My local testing and running of some rev-
deps autopkgtests in Bileto passed as well.
I've now uploaded this into Kinetic and proposed it for Jammy SRU.
Thanks for already preparing the testcase/SRU template on this bug.
** Changed in: isc-dhcp (Ubuntu Kinetic)
** Tags added: rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1982462
Title:
Some modprobe loading services requested by the pstore service fail
Status in
Staged for kinetic: https://git.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/systemd/commit/?h=ubuntu-
kinetic&id=46c36d4c73df8980f6b6137142fb16ba90465a94
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
ht
** Tags added: fr-2564
** Also affects: systemd (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Kinetic)
Status: New => In Progress
** Changed in: systemd (Ubun
** Also affects: software-properties (Ubuntu Kinetic)
Importance: Low
Status: Confirmed
** Also affects: software-properties (Ubuntu Jammy)
Importance: Undecided
Status: New
** Tags added: fr-2565
** Tags removed: fr-2565 rls-jj-incoming
--
You received this bug notificatio
** Tags added: fr-2566
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1981622
Title:
mtd device must be supplied (device name is empty)
Status in systemd package in Ubunt
Sould be fixed in systemd v246+
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Focal)
Status: New => Triaged
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => Medium
** Tags added: fr-2567
** Tags remove
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
ht
Alfonso, would this also affect Focal (Ubuntu Core 20), after this patch
is shipped to that series via SRU (as it happened on Jammy already)?
https://git.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/systemd/commit/?h=ubuntu-
focal&id=6e60756f2079d6408abdb967127a1d9b9a0eba8c
Do we need to includ
Impish is EOL
** Changed in: ifupdown (Ubuntu Impish)
Status: Triaged => Won't Fix
** Changed in: isc-dhcp (Ubuntu Impish)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown i
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1982462
Title:
Some modprobe loading ser
The fix is already included in upstream v251 (Kinetic+)
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bu
** Changed in: systemd (Ubuntu Kinetic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1982462
Title:
Some modprobe loading ser
** Changed in: systemd (Ubuntu Kinetic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1981042
Title:
/etc/localtime symlink not correc
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1981622
Title:
mtd device must be supplied (devi
Closing this bug for systemd, as it's not relevant anymore IMO and is a
red herring in proposed-migration.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sy
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1897932
Title:
systemd-repart not packaged
Status in systemd package in Ubuntu:
Fix Releas
** Merge proposal linked:
https://code.launchpad.net/~bluca/ubuntu/+source/systemd/+git/systemd/+merge/427557
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1897932
Titl
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Kinetic)
Importance: Medium
Status: Tria
** Tags removed: fr-2591 rls-jj-incoming rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1979952
Title:
Bind mount to NFS mount fails on Ubuntu 22.04
Statu
This might actually be an issue/change in systemd-resolved between Focal
and Jammy.
On Focal the search domain is appended even to FQDNs.
On Jammy the search domain is only appended to single-label hostnames
(hostnames containing no dots), to make them FQDNs.
Would you mind sharing your output o
I've uploaded the fix into Kinetic and proposed it for Jammy SRU.
But @vorlon had some reservations: "I want to understand why the partner is
invoking dhclient at all, when it is not part of our standard network stack in
jammy (or even focal)."
I'll leave the decision to accept/reject this to hi
The zlib patch is already waiting in Jammy's unapproved queue, so I'm
marking it "In Progress".
** Changed in: zlib (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubun
** Tags added: fr-2601
** Tags removed: fr-2601 rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1820584
Title:
seahorse assert failure: seahorse: glib-watch.
Thanks for the investigation, I'm 100% +1 on comment #5.
The MR introduces some (low) risk of breaking existing use cases (#5.1),
while not fixing the issue for anyone directly. Instead, it provides an
(easier/additional?) workaround to the issue, which still needs to be
applied to any individual
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1945225
Title:
udev produces unpredictable net names when PCI device is a bridge
Status in s
Thanks for doing the SRU verification @pprincipeza!
I re-triggered the flaky autopkgtest on systemd/249.11-0ubuntu3.4 (armhf) to
make it pass.
All looking good.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubu
We got some response from the SRU team (@racb):
https://lists.ubuntu.com/archives/ubuntu-devel/2022-August/042250.html
Basically he suggests doing this change in a PPA/jammy-backports, or as
a entirely new package:
* "what if you were to put systemd-repart as a new package into a PPA, or into
j
This bug was fixed in the package keyutils - 1.6.3-1
Sponsored for Olivier Gayot (ogayot)
---
keyutils (1.6.3-1) unstable; urgency=medium
* New upstream release. (Closes: #1012606)
- Add Mark-test-requiring-root-as-such.patch
- Drop endianness-and-PIE.patch
- Refresh pat
Thanks, LGTM!
** Changed in: sysvinit (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1987257
Title:
Please merge sysvinit 3.04
I think this might be a real regression in NM.
Netplan is testing something like this (which worked nicely in the past):
mybond:
parameters:
mode: 802.3ad
ad-select: bandwidth
Therefore, /sys/class/net/mybond/bonding/ad_select should actually
contain "bandwidth 1", not t
Thank you very much, Dave, for providing a git-ubuntu style merge! This
is so much easier to review. I'll upload it using git-ubuntu style, too,
so it will be easier to do the next merge.
LGTM!
A few comments (but nothing that would hold back sponsoring of this
upload):
commit 96edb47fa870a9dfd6
I agree, done!
** This bug is no longer a duplicate of bug 1951653
can't use NM for ethernet device on 20.04 LTS because it is 'strictly
unmanaged'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu
Public bug reported:
depmod: WARNING: could not open modules.builtin.modinfo at
/tmp/autopkgtest.tKMBKb/autopkgtest_tmp/mkinitramfs_uvT4BW/lib/modules/5.15.0-27-generic:
No such file or directory
https://autopkgtest.ubuntu.com/results/autopkgtest-
kinetic/kinetic/amd64/i/initramfs-tools/20220823_
It's interesting that for both of you the output of "resolvctl" shows
"resolv.conf mode: foreign", which is non-default and unsupported by
Ubuntu. It should be using "stub" mode.
/etc/resolv.conf should be a symlink to /run/systemd/resolve/stub-
resolv.conf in order to be managed by sd-resolved. B
Thanks for the feedback! I'm closing it "wontfix" then. Please re-open
if you feel like this still is an issue in Ubuntu's default sd-resolved
setup.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
To
Done:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1072
(I might not have the time to follow through with this, though)
** Bug watch added:
gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #1072
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/
Upstream is working on a solution.
** Changed in: network-manager (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/19870
** Description changed:
[Impact]
systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
Ubuntu/Debian packages of systemd - probably because it has an extra
dependency?
The bug reporter would like to use it in their new raspberry pi images
where they don't have cloud-init i
** Description changed:
[Impact]
systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
Ubuntu/Debian packages of systemd - probably because it has an extra
dependency?
The bug reporter would like to use it in their new raspberry pi images
where they don't have cloud-init i
** Description changed:
[Impact]
systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
Ubuntu/Debian packages of systemd - probably because it has an extra
dependency?
The bug reporter would like to use it in their new raspberry pi images
where they don't have cloud-init i
After the discussion on the mailing list (ubuntu-devel@) has settled, and
@bluca provided an updated MP#427557 to ship systemd-repart as an additional
binary package in Jammy (universe, not installed by default), I've moved ahead
and staged the changes to provide an upgrade path (removal of syst
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https:/
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1988300
Title:
systemd-resolved is not installab
** Tags removed: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2041491
Title:
Provide an option to avoid the yaml NM backend
Status in netplan.io
** Changed in: netplan.io (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2040153
Title:
Network Manager will not remove
Netplan is not involved with setting the hostname at all. Marking
invalid for that package.
** Changed in: netplan.io (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
h
This should have been fixed upstream as of
https://github.com/canonical/netplan/pull/371 and should be fixed in
Mantic.
Can you still re-produce this issue today?
** Changed in: netplan.io (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are
So if I understand correctly, this does not affect Focal or Bionic.
It also does not affect Mantic or Noble.
We're just hitting this issue on Jammy = systemd v249.11 (and probably
Lunar = systemd v252.5).
Netplan's behavior seems to be correct, here. It writes sensible
configuration for systemd-n
Fixed in v0.107 https://github.com/canonical/netplan/releases/tag/0.107
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bu
** Tags added: netplan-everywhere
** Changed in: netplan
Status: New => Triaged
** Changed in: netplan
Importance: Undecided => High
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Tags added: fr-6121
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2045096
Title
The RequiredForOnline=no flag can be controlled using Netplan's "optional:
true" setting.
In your specific case (cable not connected) you might also be interested in
Netplan's "ignore-carrier: true" setting, which brings up the interface
regardless.
Please check /etc/netplan/ for those settings
301 - 400 of 552 matches
Mail list logo
