Same problem for me. I did not upgrade to the beta version of 22.04, but
waited until the official upgrade was available. Nevertheless, kdesu
does not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
maybe netplan systemd generator should spit out stderr to /run
somewhere, and then later have a unit that would cat that file and exit
1, to have a failed unit on boot with errors in the journal, something
like netplan-boot-generator-failed.service
Or another approach would
** 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/1959475
Title:
"machinectl shell" connections immediately
Phew... looks like we have plenty of layered problems here:
1) calling "netplan set network.bridges.br54.dhcp4=true" will create an
empty bridge that will never get its DHCP4 configuration, thus will stay
stuck in the "configuring" state of "networkctl". Having empty bridges
is not really a
Thank you, the patch (and PPA build) look good to me overall.
Running the autopkgtests from the PPA build shows that all arches but
"amd64" still fail – with a different error message, though. Do we need
any special triggers for the autopkgtest? Or is this expected behavior?
Please let's clarify
All autopkgtest regressions on Focal/Impish could be resolved by re-
running them with appropriate triggers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966179
Title:
The airplane hotkey does
All autopkgtest regressions on Focal/Impish/Jammy could be resolved by
re-running them with appropriate triggers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967038
Title:
Add mic mute key for
** Changed in: netplan
Status: Confirmed => 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/1771740
Title:
Expose link offload options
To manage notifications about this bug go
Please also confirm that the two following entries, which were
introduced via LP: #1955997 and changed with this MP, are still working
as expected:
evdev:name:Intel HID
events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9MobileWorkstationPC:pvr*
evdev:name:Intel HID
22.04 LTS is now released. Therefore, I uploaded the SRU into the Jammy
queue as well.
** Changed in: systemd (Ubuntu Jammy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, I think we could create a new user for fwupd, similar to how it is
done in systemd-oomd.postinst (https://git.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/systemd/tree/debian/systemd-oomd.postinst?h=ubuntu-
jammy) and then use a "User=fwupd" configuration in fwupd-
refresh.service.
--
You
** Tags added: rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969976
Title:
DynamicUser=1 doesn't get along with services that need dbus-daemon
To manage notifications about this
** Changed in: systemd (Ubuntu Focal)
Status: New => In Progress
** Changed in: systemd (Ubuntu Impish)
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/1966179
** Changed in: systemd (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: systemd (Ubuntu Impish)
Status: New => In Progress
** Changed in: systemd (Ubuntu Focal)
Status: New => In Progress
** Changed in: systemd (Ubuntu Jammy)
Status: Fix Committed =>
Jammy is already fixed via LP: #1955997
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Impish)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received
Thank you for the git MPs! They have been approved and merge (with small
comments, FYI).
I cannot currently upload the Jammy SRU, as Jammy is in Final Freeze
already and IMO this does not really qualify for a 0-day SRU. Please try
to get a statement from the release team (on IRC #ubuntu-release),
Quoting upstream systemd developers
(https://github.com/systemd/systemd/issues/22737#issuecomment-1077682307):
"We essentially traded one problem (lockup when starting services) for another
(the failure described in this commit).
I actually think that the lockup is worse. Here there is a simple
Some work has been done in:
https://github.com/canonical/netplan/pull/271
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967084
Title:
netplan dbus returns "false" in io.netplan.Netplan.Config.Set
This is now in jammy-proposed.
** Changed in: systemd (Ubuntu)
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/1929345
Title:
Pressing calculator key
I still agree that this should be landed as-is (cf. comment #18).
Also, I've just sponsored a new version of systemd for Impish, that contains
this plus additional fixes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: systemd (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
still very unpleasant problem :/// I cant use headphones microphone on
zoom calls, or any other calls. I thought buying bluetooth headphones
would make my life easier... well maybe if I was using windows.
Device 78:5E:A2:6B:02:38 (public)
Name: JBL TUNE230NC TWS
Alias: JBL
*** This bug is a duplicate of bug 1962297 ***
https://bugs.launchpad.net/bugs/1962297
Citing Rahul from the snapcraft forum:
> I moved core20 to candidate channel and now it creates the right netplan with
> nm-devices.
> Thanks for the help. Do you know hen this would be pushed into stable?
Focal looking good as well. I've tested netplan.io
0.104-0ubuntu2~20.04.1 from focal-proposed and attached the autopkgtest
logs to the bug description.
root@ff-nm:/x# apt list *netplan*
Listing... Done
libnetplan-dev/focal-proposed,now 0.104-0ubuntu2~20.04.1 amd64 [installed]
Some additional discussion at https://forum.snapcraft.io/t/creating-
wireguard-connection-on-network-manager-snap/29182/
I cannot understand how it would still create a "tunnels:" stanza on the
latest version of netplan.
But I think I found an explanation now:
The NM snap is not actually using
** Tags added: fr-2124
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962332
Title:
xenial systemd fails to start if cgroup2 is mounted
To manage notifications about this bug go to:
There is now an upstream fix to keep ACD on by default on ipv4ll
addresses, but still honor the user settings if they are set:
https://github.com/systemd/systemd/pull/22824
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was mostly about exposing the offload options in general. But
indeed the tristate should be handled properly.
Let's continue that discussion in LP: #1956264
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for this investigation! This issue has been discussed in multiple
places, like here where a udev rule is recommended:
https://github.com/systemd/systemd/issues/2891
I wonder if we could downgrade the "Requires=sys-subsystem-net-devices-
XXX.device" to a
I've tested netplan.io 0.104-0ubuntu2~21.10.1 from impish-proposed and
attached the autopkgtest logs to the bug description. All looking good!
The additional testing of libnetplan/NetworkManager integration is not
relevant for Impish as it only applies to Focal/Core20.
The regression in
I feel like this special case should be decided and handled by the
release team, not Foundations.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962332
Title:
xenial systemd fails to start if
** Description changed:
[Impact]
This release contains both bug-fixes and new features and we would like to
make sure all of our supported customers have access to those improvements.
The most notable changes (besides usual bug-fixes) incoming in 0.104:
- Enable 'embedded-switch-mode'
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu2
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Lukas Märdian (slyon)
** Changed in: systemd (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubunt
** Also affects: netplan
Importance: Undecided
Status: New
** Changed in: netplan
Importance: Undecided => Wishlist
** Changed in: netplan
Status: New => Triaged
** Tags added: fr-2119
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
monero builds fine nowadays on riscv64
** 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
** Changed in: netplan.io (Ubuntu)
Status: New => Triaged
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848471
Title:
I cannot seem to reproduce this in a clean Bionic environment. Can you
reproduce the issue in a fresh Bionic installation?
It sounds to me like something could be wrong with your local python
environment...
** Changed in: netplan.io (Ubuntu)
Status: New => Incomplete
--
You received
It appears there has been some ABI breakage, similar to LP: #1922898
Newer versions of netplan (starting with 0.104) use a strict version
dependency to upgrade libnetplan and netplan.io at the same time, to
avoid such issues. In addition to being much more careful wrt. ABI
breaking changes!
**
** No longer affects: netplan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922898
Title:
[SRU] SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1922898 ***
https://bugs.launchpad.net/bugs/1922898
** This bug has been marked a duplicate of bug 1922898
[SRU] SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
As there is a workaround available, I'll be lowering the Importance of
this bug. I guess it would still be nice to have an easier way to define
a point-to-point connection.
** Changed in: netplan.io (Ubuntu)
Importance: High => Wishlist
** Changed in: netplan
Importance: High => Wishlist
netplan apply is calling 'systemctl start NetworkManager.service', so
this should be working nowadays.
Please re-open if this is still an issue.
** Changed in: netplan.io (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1949895 ***
https://bugs.launchpad.net/bugs/1949895
** This bug has been marked a duplicate of bug 1949895
"netplan apply --debug" vs "netplan --debug apply"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1951653 ***
https://bugs.launchpad.net/bugs/1951653
** This bug has been marked 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
*** This bug is a duplicate of bug 1664844 ***
https://bugs.launchpad.net/bugs/1664844
** This bug has been marked a duplicate of bug 1664844
No distinction between link-up and link-down interfaces
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The fix was released with netplan v0.103.
** Changed in: netplan
Status: In Progress => Fix Released
** Changed in: netplan.io (Ubuntu Focal)
Status: New => Fix Released
** Changed in: netplan.io (Ubuntu Hirsute)
Status: New => Fix Released
** Changed in: netplan.io
** Changed in: netplan.io (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811802
Title:
Typo in reference example
To manage notifications about this bug
This should be fixed as of v0.104
(https://github.com/canonical/netplan/pull/259)
Please re-open if this is still an issue.
** Changed in: netplan.io (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
There hasn't been a response for a long time, so I'm closing this issue.
Please re-open with the requested information if this is still an issue.
** Changed in: nplan (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1769034 ***
https://bugs.launchpad.net/bugs/1769034
** This bug has been marked a duplicate of bug 1769034
Problems configuring pppoe when using netplan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
The installer bug task seems to be fixed.
I cannot reproduce this with recent versions of netplan (it accepts
quoted and unquoted IPv6 addresses).
Please re-open if this is still an issue.
** Changed in: nplan (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification
This should be fixed as of netplan.io v0.100 (available in Focal+),
using the `hidden` keyword:
https://github.com/canonical/netplan/commit/a28fe6586e30323b5d85484a047af13055b0f43e
** Changed in: nplan (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because
*** This bug is a duplicate of bug 1943120 ***
https://bugs.launchpad.net/bugs/1943120
Netplan recently implemented the ability to pass a "--state" parameter,
which enables to calculate the difference between the old and the new
conf, and allows to delete virtual interfaces that had been
** Changed in: nplan (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736965
Title:
"netplan apply" does not set file mode, umask 077 causes systemd-
I'm closing the Artful and Xenial bug tasks, as those are EOL.
Bash completion is in place nowadays, but it is a bit outdated, so I'm
updating the bug and moving it to the new "netplan.io" project.
The bash completions in ./netplan.completions should be updated.
** Also affects: netplan.io
The situation has improved quite a bit over the years. autopkgtests are
mostly stable nowadays.
This bug report is about Xenial which is EOL, so I'm marking it WONTFIX.
** Changed in: nplan (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member
Marking as WONTFIX as Xenial is EOL
** Changed in: nplan (Ubuntu)
Status: New => Won't Fix
** Changed in: netplan.io (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The configuration in comment #1 is actually the way to do this in
netplan. One could potentially add a "dhcp4-overrides: {...}" stanza, to
make sure the DHCP response does not override the statically configured
routes or nameservers (if need be): https://netplan.io/reference/#dhcp-
overrides
Does
The input validation for "lacp-rate" is still missing and should be
checked for "slow" or "fast" in src/parse.c.
Re-assigning to the netplan.io project as "nplan" is deprecated.
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Also affects: netplan
Moving it over to the netplan.io project, as nplan is deprecated.
Also, I'm marking it as a "Wishlist" item, which could be considered to be
implemented as a new feature.
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
Moving it over to the netplan.io project, as nplan is deprecated.
I think we actually have an upstream way of matching Type=ether nowadays
(as of systemd v245+), so we should reconsider implementing a fix for
this.
Moving it over to the "netplan.io" project, as "nplan" is deprecated.
Anybody, please feel free to submit a pull request at
https://github.com/canonical/netplan to fix this low-hanging fruit.
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nplan
This was enabled in Debian's systemd v250.1-2
https://salsa.debian.org/systemd-team/systemd/-/commit/4a93ec2f56969e11c73ef346a342e7e552faae75
We're shipping the more stable systemd v249 in Ubuntu Jammy LTS, and are
already post feature freeze, so we cannot enable new features anymore.
This will
This has been enabled in Debian's systemd v250 via
https://salsa.debian.org/systemd-
team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8
We're sticking with the more stable systemd v249 for Ubuntu Jammy LTS
and we're already post feature freeze, so we cannot enable those new
features
Thank you for reporting this. I've forwarded it to the upstream
developers, as I think at very least this new behavior should be
documented in
https://systemd.network/systemd.network.html#DuplicateAddressDetection=
https://github.com/systemd/systemd/issues/22763
** Bug watch added:
A fix for this has been landed upstream (v250) for HP Omen 15 and
another fix for Omen 17:
https://github.com/systemd/systemd/commit/6f2353a2ce731afc8622a3d44679abc38105cded
https://github.com/systemd/systemd/commit/70920214b6a1c1825a2724793497e6be2ba3c0fc
It might be worth backporting those
It has recently been picked up by Foundations, and we should have the
capacity to start working on this next week.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958284
Title:
shutdown hangs at
netplan uses the "networkctl reload/reconfigure" commands nowadays,
instead of hard restarting systemd-networkd:
https://github.com/canonical/netplan/pull/200
This change was activated in v0.104 in the Distro, which landed in Jammy
and is currently being SRUed to Focal and Impish (LP: #1964481).
This has been released in 0.102, I forgot to update the status of this
bug report. It also landed in focal-updates.
Please re-open if you still see this issue.
** Changed in: netplan.io (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a
** Description changed:
+ [Impact]
+ This release contains both bug-fixes and new features and we would like to
make sure all of our supported customers have access to those improvements.
+
+ The most notable changes (besides usual bug-fixes) incoming in 0.104:
+ - Enable 'embedded-switch-mode'
Public bug reported:
TBD
** Affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Affects: netplan.io (Ubuntu Focal)
Importance: Undecided
Status: New
** Affects: netplan.io (Ubuntu Impish)
Importance: Undecided
Status: New
** Also
I've prepared a fix/workaround for this issue in netplan:
https://github.com/canonical/netplan/pull/260
** Changed in: netplan.io (Ubuntu)
Assignee: (unassigned) => Lukas Märdian (slyon)
** Changed in: netplan.io (Ubuntu)
Status: Triaged => In Progress
--
You received th
Fixed upstream via
https://github.com/ibm-s390-linux/s390-tools/commit/5e46632767cb95afbf867cded150a4b2326f47f3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907789
Title:
2.35.50 breaks ld
Ubuntu Jammy)
Assignee: (unassigned) => Lukas Märdian (slyon)
** Changed in: systemd (Ubuntu Jammy)
Status: Triaged => 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/1962038
T
** 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
Bugs, which is subscribed to Ubuntu.
** Changed in: nftables (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/1887187
Title:
[MIR] nftables
To manage notifications about this bug go to:
Review for Package: src:nftables
Author: @joalif
Reviewed-by: @slyon
[Summary]
nftables is the future CLI for firewalling which should be available on Ubuntu.
iptables CLI switched to using a nftables backend, but will probably still
exist for a while.
The package is looking good from a MIR
Hi Robie, any update on this?
As Jeremy described earlier, we choose to implement the safe way for the
SRUs by keeping an allow-list of supported devices, instead of switching
over to the upstream solution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: netplan.io (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962095
Title:
netplan apply fails on 22.04 with clean yaml
To manage
Hi Łukasz, thank you for accepting this upload into focal-proposed!
I've tested netplan 0.103-0ubuntu5~20.04.6 and can confirm it fixes the
bug described above. autopkgtest ran successful on all arches and I've
executed the manual testing as described above.
# apt list *netplan*
Listing... Done
mozjs78 now got demoted to universe 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/1962591
Title:
[MIR] mozjs91
To manage notifications about this bug go to:
The package has been promoted to release by @doko on 2022-03-02 14:48:55
CET
** Changed in: mozjs91 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962591
** Description changed:
This is just a version bump based on the same sources that are in main
- already.
+ already. gjs is the only dependency pulling in mozjs, so we should
+ demote mozjs78 and promote mozjs91 instead.
https://bugs.launchpad.net/ubuntu/+source/mozjs38/+bug/1683937
After talking to seb128 and 3v1n0, it turns out we actually did a proper
MIR for mozjs in the past and should consider this as a normal version
bump that doesn't need a full MIR as this is still based on the same
source.
https://bugs.launchpad.net/ubuntu/+source/mozjs38/+bug/1683937
This is related to https://launchpad.net/ubuntu/+source/mozjs78
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962591
Title:
[MIR] mozjs91
To manage notifications about this bug go to:
Public bug reported:
TBD
** Affects: mozjs91 (Ubuntu)
Importance: Undecided
Status: Incomplete
** 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/1962591
Title:
[MIR]
LGTM!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962583
Title:
tpm2-pkcs11: FTBFS with tpm2-tss 3.2.0-ubuntu1
To manage notifications about this bug go to:
** Description changed:
+ [Impact]
+
+ * There's currently a deadlock between PID 1 and dbus-daemon: in some
+ cases dbus-daemon will do NSS lookups (which are blocking) at the same
+ time PID 1 synchronously blocks on some call to dbus-daemon (e.g.
`GetConnectionUnixUser` DBus call). Let's
** Also affects: procps (Ubuntu)
Importance: Undecided
Status: New
** Changed in: procps (Ubuntu Impish)
Status: New => Won't Fix
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This fix is only relevant on core20/core22 (i.e. Focal/Jammy), as this
is the only place where the NetworkManager (snap) is enabled to use the
netplan backend. Therefore I'm marking it WONTFIX on Impish.
** Changed in: netplan.io (Ubuntu Impish)
Status: New => Won't Fix
--
You received
** Description changed:
+ [Impact]
+
I've just learned that systemd is setting kernel.sysrq to 16 in
/usr/lib/sysctl.d/50-default.conf. This is inconsistent with
/etc/sysctl.d/10-magic-sysrq.conf which intentionally sets it to 176 by
default. systemd should drop its setting to defer to
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: systemd (Ubuntu Groovy)
** No longer affects: systemd (Ubuntu Hirsute)
** Also affects: dbus (Ubuntu Jammy)
Importance: High
Status: Incomplete
** Also affects: gnome-shell (Ubuntu
This fix is included in upstream netplan 0.104, so Fix released in Jammy
already.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962297
Title:
[SRU] NetworkManager parser: ip-tunnel connections
Public bug reported:
[Impact]
* NetworkManager snap (using the netplan backend) fails to add "ip-
tunnel" connections.
* ip-tunnel connections are needed in UC20 via the NetworkManager
netplan integration
* This upload includes an upload commit that uses netplan's
"passthrough" mode to
So it seems like this is really related to a stopped (or
hanging/crashed?) systemd-networkd.
In subiquity this seems to be enforced via
https://github.com/canonical/subiquity/commit/41014408143ece5df9ef000d65c23f9307098905
which is in conflict with newer versions of netplan that try to call
** 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/1962038
Title:
wrong sysrq value in
Thank you. I fixed up some file permissions 644 -> 755 that were screwed
up vs the Debian version (probably due to `debdiff` not handling those
properly). Other that that this looks sane to me, builds fine and passes
lintian :-)
--
You received this bug notification because you are a member of
** Also affects: subiquity (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/1962095
Title:
netplan apply fails on 22.04 with clean yaml
To manage
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962095
Title:
netplan apply fails on 22.04 with clean yaml
To manage notifications about this bug go to:
I've analyzed the situation on Jammy, Impish and Focal and got the
following result:
Jammy+Impish:
/usr/lib/sysctl.d/50-default.conf:net.ipv4.conf.default.rp_filter = 2
=> shadowed but equal value
/usr/lib/sysctl.d/50-default.conf:net.ipv4.conf.*.rp_filter = 2
=> shadows default.rp_filter &
301 - 400 of 2500 matches
Mail list logo
