FWIW you can test this out by adding a drop-in config:
$ cat > /etc/systemd/system/cloud-init.service.d/10-after-systemd-resolved.conf
<< EOF
[Service]
After=systemd-resolved.service
EOF
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
Released => In Progress
** Changed in: systemd (Ubuntu Jammy)
Status: Fix Committed => In Progress
** Changed in: systemd (Ubuntu Kinetic)
Status: Fix Committed => In Progress
** Changed in: systemd (Ubuntu Jammy)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
*
** Description changed:
[Impact]
On systems with mellanox NICs, udev's NIC renaming races with the mlx5_core
driver's own configuration of subordinate interfaces. When the kernel wins this
race, the device cannot be renamed as udev has attempted, and this causes
systemd-network-online.targe
Thanks for preparing this patch, Serge. I have converted it into a git
commit and will make sure it is in the next upload of systemd. I will
also forward this to Debian, since this is something they will want too.
** Changed in: systemd (Ubuntu)
Status: New => Triaged
--
You received this
** Changed in: systemd (Ubuntu Focal)
Assignee: Mustafa Kemal Gilor (mustafakemalgilor) => Nick Rosbrook (enr0n)
--
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/2002
** Changed in: systemd (Ubuntu Focal)
Status: Incomplete => 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 20.04 disa
** Changed in: dpkg (Ubuntu)
Status: Triaged => Fix Released
** Changed in: dpkg (Ubuntu Kinetic)
Status: Triaged => 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.l
I missed this my first time looking at the code, but the specific
filename is logged at the debug level. So you can at least do:
$ SYSTEMD_LOG_LEVEL=debug systemd-cryptenroll --tpm2-device=list
libtss2-esys.so.0 is not installed: libtss2-esys.so.0: cannot open shared
object file: No such file or
>From what I can tell, this patch is present in Jammy and newer, but not
Focal.
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Focal)
Status: New => Triag
** Tags removed: verification-needed-jammy verification-needed-kinetic
** Tags added: verification-done-jammy verification-done-kinetic
--
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.
I re-confirmed the fix using systemd 249.11-0ubuntu3.9 from jammy-
proposed:
$ apt-cache policy systemd
systemd:
Installed: 249.11-0ubuntu3.9
Candidate: 249.11-0ubuntu3.9
Version table:
*** 249.11-0ubuntu3.9 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
I have re-confirmed the fix using systemd 249.11-0ubuntu3.9 from jammy-
proposed:
root@jammy:~# apt-cache policy systemd
systemd:
Installed: 249.11-0ubuntu3.9
Candidate: 249.11-0ubuntu3.9
Version table:
*** 249.11-0ubuntu3.9 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/ma
I have re-confirmed the fix using systemd 251.4-1ubuntu7.3 from kinetic-
proposed:
root@kinetic:~# apt-cache policy systemd
systemd:
Installed: 251.4-1ubuntu7.3
Candidate: 251.4-1ubuntu7.3
Version table:
*** 251.4-1ubuntu7.3 500
500 http://archive.ubuntu.com/ubuntu kinetic-proposed/
I have prepared the fix for this in git because I have more context from
other discussions, but can you please add a bit more detail here? E.g.
at least provide the stack trace you have observed which suggests the
above patch is correct?
--
You received this bug notification because you are a mem
** Tags removed: systemd-sru-next
--
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/2025382
Title:
22.04 DHCPv6 IPv6 broken (at least on Oracle OCI)
Status in systemd packag
** Tags added: foundations-todo
--
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/1837227
Title:
systemd mount units fail during boot, while file system is correctly
mounte
** Description changed:
+ [Impact]
+
+ In the latest Ubuntu 23.10 cloud images we are seeing unexpected UDP
+ listening port 5353.
+
+ By default and by policy, aside from port 22 there should be no other
+ open ports on Ubuntu cloud images. Listening port 5353 is a regression.
+
+ [Test Plan]
** Changed in: systemd (Ubuntu Mantic)
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.
https://bugs.launchpad.net/bugs/2038894
Title:
Ubuntu 23.10 cloud images unex
o this
bug which was uploaded in 1:23.10.11.
** Changed in: ubuntu-release-upgrader (Ubuntu Mantic)
Status: Fix Committed => In Progress
** Changed in: ubuntu-release-upgrader (Ubuntu Mantic)
Assignee: Gunnar Hjalmarsson (gunnarhj) => Nick Rosbrook (enr0n)
--
You received this
We do not do these kinds of updates in stable releases - just bug fixes
etc. We will have systemd > v254 in 24.04.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Chris, Andreas, SRU team - In short, I think this should be released to
-updates, yes. From looking through the various comments I have observed
the same that either (a) a user is not testing with -proposed, or (b)
they are in a slightly different situation (but see the timeout
nonetheless, hence f
Since you say this happens from a shell too, please provide the output
of the following:
SYSTEMD_LOG_LEVEL=debug /usr/lib/systemd/systemd-networkd-wait-online
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
T
Please provide debug-level logs from systemd-resolved.service from a
time where this issue is observed. You can enable debug-level logging
like this:
$ mkdir -p /etc/systemd/system/systemd-resolved.service.d/
$ cat > /etc/systemd/system/systemd-resolved.service.d/debug.conf << EOF
[Service]
Enviro
** Changed in: systemd (Ubuntu)
Status: Invalid => Incomplete
--
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/2040051
Title:
systemd-networkd-wait-online terminates
** 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/2039743
Title:
Intermittent DHCP startup
** Description changed:
+ [Impact]
+
+ Using systemd-resolved to resolve a hostname which has more than 8 CNAME
+ redirects will fail because of the hard-coded limit. While this case is
+ somewhat rare, the original reporter demonstrated a real-world scenario
+ where this happened (although that
The test case with removing kexec-tools before rebooting works for me.
But I can only reproduce the issue by doing that. Can you share more
about your setup so we can understand why exactly you hit this?
I think that having this fallback makes sense, and is fine for an SRU,
but it would be good to
** Changed in: systemd (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.
https://bugs.launchpad.net/bugs/2038897
Title:
systemd-resolved: not all records flushed when
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
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/1791102
Title:
udev postinst fails because kvm group already
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: systemd (Ubuntu Jammy)
Importance: Undecided => Low
--
I confirmed this issue on 22.04 using the reproducer in the original
description. I agree that [1] looks like the appropriate upstream bug.
In fact, we currently skip a test in Jammy's autopkgtest due to this
issue [2]. Unfortunately, the fix doesn't apply to v249.11 without [3],
and I'm not sure t
Because upgrades are not enabled yet for mantic -> noble, we still
cannot explicitly verify the XDG_SESSION_TYPE fix for mantic. However,
(a) since this exact patch was verified for lunar -> mantic, (b) this
patch relates to upgrading *from* mantic rather than *to* mantic, and
(c) we do not want to
** Changed in: systemd (Ubuntu Noble)
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/2038894
Title:
Ubuntu 23.10 cloud images unexpecte
The autopkgtest failures were resolved with retries.
--
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/2038894
Title:
Ubuntu 23.10 cloud images unexpected UDP listening port
I have verified the fix using systemd-resolved 253.5-1ubuntu6.1 from
mantic-proposed:
root@mantic:~# apt policy systemd-resolved
systemd-resolved:
Installed: 253.5-1ubuntu6.1
Candidate: 253.5-1ubuntu6.1
Version table:
*** 253.5-1ubuntu6.1 500
500 http://security.ubuntu.com/ubuntu ma
cgroupsv2 has been the default for a few releases now, so it's odd that
you are running cgroupsv1. Can you share /proc/cmdline? I haven't looked
close enough to see if this would actually cause this error, but since
this error seems odd as it is, I wouldn't be surprised.
--
You received this bug
** Description changed:
+ [Impact]
+
+ The armhf autopkgtest fails for focal and ultimately leads to less test
+ coverage because other packages now won't block on these failures, and
+ may not notice new regressions.
+
+ [Test Plan]
+
+ The test-execute test within root-unittests should pass.
This is fixed by upstream commit [1], which is included in v251 and
newer. The reason this is not needed in Jammy (v249) is because we
already have a patch [2] that causes this test case to be skipped on
arhmf.
[1]
https://github.com/systemd/systemd/commit/646cba5c4208c28c56dbe52d676ab1a176c69b7f
** Description changed:
[Impact]
When working with ubuntu core or ubuntu core desktop, neither
*/etc/default/locale* nor */etc/default/keyboard* are modifiable, so
it's not possible to set the global keyboard or the global language.
This is required to allow to set the GDM language, a
** Also affects: systemd (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Lunar)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu Mantic)
Status: New
** Also affects: systemd-hwe (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd-hwe (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Mantic)
do
** Changed in: systemd-hwe (Ubuntu Jammy)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: systemd-hwe (Ubuntu Lunar)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: systemd-hwe (Ubuntu Mantic)
Assignee: (unassigned) => Nick Rosbrook (enr0n
Lukas - upstream is actually broken in v253 until v253.6, and the reason
it appears "OK" in v253.5 (which we have in Mantic) is that [1]
introduces a bug upstream that makes systemd-networkd-wait-online behave
similarly to Ubuntu's patched systemd-networkd-wait-online prior to
systemd 249.11-0ubunt
*** This bug is a duplicate of bug 2045621 ***
https://bugs.launchpad.net/bugs/2045621
It seems bug (bug 2045621) has been opened which is proposing the same
thing. That one has the SRU info required, so let's carry on there
instead.
** This bug has been marked a duplicate of bug 2045621
I
For Jammy, Lunar, and Mantic, the correct fix is to add these rules in a
90-ubuntu-autosuspend.hwdb file in systemd-hwe.
** Changed in: systemd (Ubuntu Jammy)
Status: Confirmed => Won't Fix
** Changed in: systemd (Ubuntu Lunar)
Status: Confirmed => Won't Fix
** Changed in: systemd
This symlink looks correct to me. If you are still having an issue,
please provide a specific example and instructions on how to reproduce
it in another bug report.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member
As Yu said on the upstream bug, this is the expected default behavior
for systemd-networkd-wait-online. You can make it more tailored to your
use case, e.g. by writing an override like this:
# /etc/systemd/system/systemd-networkd-wait-online.service.d/override.conf
[Service]
ExecStart=
ExecStart=/
Yes, I am aware of the path. This is what I see on a fresh jammy
install:
nr@clean-jammy-amd64:~$ readlink /etc/resolv.conf
../run/systemd/resolve/stub-resolv.conf
nr@clean-jammy-amd64:~$ nslookup google.com
Server: 127.0.0.53
Address:127.0.0.53#53
Non-authoritative answer:
Name:
If you have a bunch of unmanaged interfaces, then you should use a drop-
in configuration to pass the --any flag to systemd-networkd-wait-online:
cat > /etc/systemd/system/systemd-networkd-wait-online.service.d/any.conf << EOF
[Service]
ExecStart=
ExecStart=/lib/systemd/systemd-networkd-wait-onlin
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/2046356
Title:
Update URL for Support information in MOTD message
Status in base-files pa
signee: (unassigned) => Nick Rosbrook (enr0n)
** Tags added: foundations-todo
--
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/2046459
Title:
systemd-gpt-auto-generator is omit
-credential.service/start finished, result=failed
Dec 14 19:24:24 noble systemd[1]: Failed to start exec-set-credential.service -
Test for SetCredential=.
Dec 14 19:24:24 noble systemd[1]: exec-set-credential.service: Unit entered
failed state.
Dec 14 19:24:24 noble systemd[1]: exec-set-credential.ser
ce: Changed start-post -> dead
2159s Spawning process to nuke
'/tmp/systemd-private-450e0b7e943048c0b7ce141f3516b98a-exec-basic.service-tbQx7j'
2159s Successfully forked off intermediary '(sd-rmrf)' as PID 1678.
2159s Spawning process to nuke
'/var/tmp/systemd-private-45
rivatemounts-no.service: can_unshare=no: exit status
1, expected 0
(test-execute-without-unshare) terminated by signal ABRT.
Assertion 'r >= 0' failed at src/test/test-execute.c:1330, function
prepare_ns(). Aborting.
** Affects: systemd (Ubuntu)
Importance: High
Assignee: N
-root) terminated by signal ABRT.
Assertion 'r >= 0' failed at src/test/test-execute.c:1330, function
prepare_ns(). Aborting.
** Affects: systemd (Ubuntu)
Importance: High
Assignee: Nick Rosbrook (enr0n)
Status: New
** Changed in: systemd (Ubuntu)
Importanc
* Affects: systemd (Ubuntu)
Importance: High
Assignee: Nick Rosbrook (enr0n)
Status: New
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because
I believe this thread from systemd-devel answers your questsion:
https://lists.freedesktop.org/archives/systemd-
devel/2023-November/049675.html.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
This is the apparmor denial:
audit: type=1400 audit(1704299091.131:665): apparmor="DENIED"
operation="mount" class="mount" info="failed flags match" error=-13
profile="lxd-noble_" name="/dev/shm/"
pid=71828 comm="(sd-mkdcreds)" flags="ro, nosuid, nodev, noexec,
remount, bind"
which corresponds to
** Changed in: systemd (Ubuntu)
Status: Triaged => 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/2046459
Title:
systemd-gpt-auto-generator is omitted
I think the setting you are looking for is ExternalSizeMax=[1]. The
ProcessSizeMax=[2] seems to clarify this as well:
"The maximum size in bytes of a core which will be processed. Core dumps
exceeding this size may be stored, but the stack trace will not be
generated."
[1]
https://www.freedeskto
It seems that the apparmor_parser in core22 does not understand the
nosymfollow mount option:
$ lxc config set systemd-lxc raw.apparmor "mount
options=(ro,remount,bind,nosuid,noexec,nodev,nosymfollow) /dev/shm,"
Error: Parse AppArmor profile: Failed to run: apparmor_parser -QWL
/var/snap/lxd/com
I have created a PR with LXD to at least get feedback:
https://github.com/canonical/lxd/pull/12698.
--
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/2046486
Title:
units wit
The problem here is that the AppArmor policy prevents the private mount
namespace from being setup, but systemd continues on after:
Jan 04 21:10:39 noble (sh)[565]: Applying namespace mount on
/run/systemd/mount-rootfs/sys
Jan 04 21:10:39 noble (sh)[565]: Mounting sysfs (sysfs) on
/run/systemd/n
I have uploaded this change for jammy and mantic, and it is already in
systemd in noble-proposed. Given lunar is EOL on January 25, I think we
can skip lunar, so I marked that won't fix.
** Changed in: systemd-hwe (Ubuntu Lunar)
Status: Confirmed => Won't Fix
** Changed in: systemd-hwe (Ub
The issue with this is that during the test setup, adding the dummy-
test-ns interface to the test-execute-netns network namespace fails with
EPERM, but this return code is not checked at all:
...
/* Create dummy network interface for testing PrivateNetwork=yes */
have_net_dummy =
https://github.com/systemd/systemd/pull/30854
** Changed in: systemd (Ubuntu)
Status: New => Triaged
--
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/2046498
Title:
I have verified the fix using systemd 245.4-4ubuntu3.23 from focal-
proposed.
On the host, I have a Focal container, and killed the existing DNS
servers:
nr@clean-jammy-amd64:~$ lxc list
+---+-+--+--+---+---+
| NAME | S
The autopkgtest for systemd 245.4-4ubuntu3.23 on armhf passed, which
verifies this fix: https://autopkgtest.ubuntu.com/results/autopkgtest-
focal/focal/armhf/s/systemd/20240110_171824_cbc46@/log.gz.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done ver
The "Fix Committed" status means that I have uploaded the change (to
noble-proposed), but it is not available in the release yet. "Fix
Released" means the change is actually available in the specified
release.
I have not staged the change for Mantic, but I have added a bug task for
it.
** Also af
Thanks for the verification, Dan!
--
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/1969365
Title:
focal: backport kexec fallback patch
Status in systemd package in Ubuntu:
** Tags removed: foundations-todo
** Tags added: systemd-sru-next
--
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/2046459
Title:
systemd-gpt-auto-generator is omitted since
I think this test will just need to remain skipped. Since systemd gets
-EPERM when trying to mount the private sysfs, it just takes some
fallback code and re-uses the existing sysfs, which means that dummy-
test-exec will still be accessible through sysfs. I can't currently
think of a good way to g
This is shipped in the systemd-boot-efi package. Please install that.
** Changed in: systemd (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.
https://bugs.launchpad.net
I think this is actually due to the recent AppArmor change too; exec-
basic.service has PrivateTmp=yes which implies PrivateUsers=yes for user
managers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https:
Looking at the attached screenshot, it covers everything in the test
plan above.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
emd package in Ubuntu:
Incomplete
Bug description:
Hi,
I create this bug issue following an advice from Nick Rosbrook in this
bug : https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2043234
May be it's a F5 VPN. I haven't found such a bug anywhere.
I have an issue when co
** Tags added: systemd-sru-next
--
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/2037667
Title:
Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
tunnels
St
** Description changed:
+ [Impact]
+
+ The systemd shutdown sequence does not honor systemd-system.conf
+ settings when waiting for remaining processes. This means that, for
+ example, if a systemd service specifies KillMode=process and a process
+ remaining from that service does not properly ha
I tested the -proposed packages on focal (tested apport
2.20.11-0ubuntu27.22) and impish (tested apport 2.20.11-0ubuntu71.1)
using the test plan above. In both cases, the fix worked as expected.
** Tags removed: verification-needed-focal verification-needed-impish
** Tags added: verification-done-
I tested systemd 245.4-4ubuntu3.16 from focal-proposed using the test
plan above. I observed that the loop-ignore-sigterm.service processes
were killed after ~20s on shutdown, which is what I configured in
/etc/systemd/system.conf.
** Tags removed: verification-needed-focal
** Tags added: verifica
These errors appear to be coming from the udev rules in
/lib/udev/rules.d/66-snapd-autoimport.rules. I also see the errors on my
system, but I have not experienced any other problems as a result.
Jimmy or Jiwei, can you please tell us how you came across these logs?
What other problem(s) did you e
I tested systemd 248.3-1ubuntu8.4 from impish-proposed to verify the
fix:
$ systemctl --version
systemd 248 (248.3-1ubuntu8.4)
+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL
+ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP
-LIBFDISK +PCRE2 -P
After speaking with snapd folks, it was determined that these udev rules
should not be triggered on desktop or server (and in fact, should be
limited to removable media). The proper solution here is to improve the
snapd auto-import udev rules.
Given that, we do not need to make any changes to syst
In the near term, we could consider tweaking the systemd-oomd defaults
in Ubuntu. According to the commit that added systemd-oomd in Jammy [1],
the current config is based on Fedora's. This includes using the default
value of SwapUsedLimit=90% [2]. However, Fedora has more swap space by
default: a
Public bug reported:
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.
During setup for tests-in-lxd, an attempt is made to purge snapd, but
this fails:
[ ... ]
Purging configurati
** Patch added: "systemd-lp-1967576.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1967576/+attachment/5575869/+files/systemd-lp-1967576.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in U
The autopkgtest regressions blocking systemd 245.4-4ubuntu3.16 in focal-
proposed have been resolved. The regressions appear to have been related
to recent autopkgtest infrastructure issues, and retrying the tests
resolved the issues.
--
You received this bug notification because you are a member
The autopkgtest regressions blocking systemd 245.4-4ubuntu3.16 in focal-
proposed have been resolved. The regressions appear to have been related
to recent autopkgtest infrastructure issues, and retrying the tests
resolved the issues.
--
You received this bug notification because you are a member
The autopkgtest regressions blocking systemd 245.4-4ubuntu3.16 in focal-
proposed have been resolved. The regressions appear to have been related
to recent autopkgtest infrastructure issues, and retrying the tests
resolved the issues.
--
You received this bug notification because you are a member
The autopkgtest regressions blocking systemd 245.4-4ubuntu3.16 in focal-
proposed have been resolved. The regressions appear to have been related
to recent autopkgtest infrastructure issues, and retrying the tests
resolved the issues.
--
You received this bug notification because you are a member
** Changed in: systemd (Ubuntu Jammy)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
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/1966381
Title:
systemd-oomd
I tested apport 2.20.11-0ubuntu27.23 from focal-proposed using the test
plan above to confirm the fix.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
The autopkgtest regressions blocking systemd 248.3-1ubuntu8.5 in impish-
proposed have been resolved. The regressions were caused either by (1)
network/infrastructure issues and succeeded on retry, or by (2)
unrelated snapd regressions. The systemd 248.3-1ubuntu8.5 upload added
an autopkgtest chang
The autopkgtest regressions blocking systemd 248.3-1ubuntu8.5 in impish-
proposed have been resolved. The regressions were caused either by (1)
network/infrastructure issues and succeeded on retry, or by (2)
unrelated snapd regressions. The systemd 248.3-1ubuntu8.5 upload added
an autopkgtest chang
The autopkgtest regressions blocking systemd 248.3-1ubuntu8.5 in impish-
proposed have been resolved. The regressions were caused either by (1)
network/infrastructure issues and succeeded on retry, or by (2)
unrelated snapd regressions. The systemd 248.3-1ubuntu8.5 upload added
an autopkgtest chang
The autopkgtest regressions blocking systemd 248.3-1ubuntu8.5 in impish-
proposed have been resolved. The regressions were caused either by (1)
network/infrastructure issues and succeeded on retry, or by (2)
unrelated snapd regressions.
This change is verified by the fact that the systemd tests-in
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1955997
Title:
The airplane hotkey has no function on
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1958284
Title:
shutdown hangs at "Waiting for process:
I tested systemd 245.4-4ubuntu3.16 from focal-proposed using the test
plan above to confirm this fix.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
T
** 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/1926860
Title:
XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04
Status i
301 - 400 of 901 matches
Mail list logo
