I have verified the fix using systemd 249.11-0ubuntu3.11 from jammy-
proposed:
Creating a fresh container:
nr@six:~$ lxc launch ubuntu-daily:jammy jammy
Creating jammy
Starting jammy
nr@six:~$ lxc exec jammy bash
Within the container, after enabling -proposed:
** Description changed:
[NOTE]
If you are running a desktop system and you see this issue, you should
run:
$ systemctl disable --now systemd-networkd.service
This will disable systemd-networkd and associated units, including
systemd-networkd-wait-online.service.
** Description changed:
[Impact]
- When all interfaces "not required for online", e.g. when they are marked
- "optional: true" in netplan, systemd-networkd-wait-online will timeout.
- Or, in other words, systemd-networkd-wait-online will timeout even
- though all interfaces are ignored,
This behavior is not present in Mantic, so nothing to do there. I have
staged fixes for Jammy and Lunar.
** Changed in: systemd (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: systemd (Ubuntu Lunar)
Status: Triaged => In Progress
** Changed in: systemd (Ubuntu)
** Tags removed: rls-mm-incoming
** Tags added: foundations-todo
** Tags added: rls-mm-incoming
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) =
Dave - yeah that's the expect outcome with this patch.
--
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/2036358
Title:
systemd wait-online now times out after jammy and
** Also affects: linux (Ubuntu)
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/2038433
Title:
systemd autopkgtest regression
Werner - it sounds like you might have been having a different issue.
Without the debug level output from systemd-networkd-wait-online, it's
hard to tell what caused the timeout. Glad you have a workaround,
though.
--
You received this bug notification because you are a member of Ubuntu
Touch
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Tags added: foundations-todo
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received th
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]
** 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
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
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
** 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 tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2030684
Title:
tzname[1] empty after tzset() with env TZ="UTC"
I have verified the fix using systemd-container 249.11-0ubuntu3.10 from
jammy-proposed:
nr@clean-jammy-amd64:~$ apt-cache policy systemd-container
systemd-container:
Installed: 249.11-0ubuntu3.10
Candidate: 249.11-0ubuntu3.10
Version table:
*** 249.11-0ubuntu3.10 500
500
I have verified the fix using systemd 249.11-0ubuntu3.10 from jammy-
proposed:
1. Verified that boot-and-services is passing on all arches for
249.11-0ubuntu3.10: https://autopkgtest.ubuntu.com/packages/systemd.
2. Manual test:
root@jammy:~# systemd-detect-virt
lxc
root@jammy:~# apt-cache
I verified the fix using systemd-container 249.11-0ubuntu3.10 from
jammy-proposed:
nr@clean-jammy-amd64:~$ apt-cache policy systemd-container
systemd-container:
Installed: 249.11-0ubuntu3.10
Candidate: 249.11-0ubuntu3.10
Version table:
*** 249.11-0ubuntu3.10 500
500
This was indeed fixed in v253.6, so let's cherry pick the patch.
https://github.com/systemd/systemd-
stable/commit/f29f0877c5abfd03060838d1812ea6fdff3b0b37
** Changed in: systemd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Hi Pirouette,
Can you show the output of `oomctl` and `free -h` on your system?
FWIW, at the time of writing this systemd 249.11-0ubuntu3 is still in
jammy-proposed, so is only available on systems with the -proposed
archive enabled.
--
You received this bug notification because you are a
** Package changed: ubuntu-release-upgrader (Ubuntu) => software-
properties (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1973779
Title:
Could not
I think there are actually two similar bugs here. The first I think is
caused by [1], which I have confirmed is present in impish, but not
focal or jammy. This can be demonstrated by the following:
$ resolvectl dns eth0 8.8.8.8 8.8.4.4 1.1.1.1
$ resolvectl dns eth0
Link 110 (eth0): 8.8.8.8
This was a deliberate change in systemd [1] to address the kernel's
bind/unbind uevent issue [2]. In short, it is an intentional change in
udev's behavior, and unfortunately breaks the assumptions that your
custom udev rules rely on.
[1]
** Tags added: 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/1981042
Title:
/etc/localtime symlink not correctly handled when using
You may have already seen this based on your workaround, but I think
this is the same issue discussed in [1]. If so, it sounds like this may
need to be fixed in the kernel?
[1] https://github.com/systemd/systemd/issues/18333
** Bug watch added: github.com/systemd/systemd/issues #18333
I believe the commit you referenced has been in jammy since
249.9-0ubuntu1.
Can you please attach some journalctl output from a boot that
demonstrates this issue?
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
> This is also occuring on Ubuntu Server on VPS.
Did you install/enable systemd-oomd manually? AFAIK, systemd-oomd is not
enabled by default on server. Or is something else killing your
programs?
> swap file is far from full.
If it is systemd-oomd, do you have logs from this (journalctl -u
** Tags added: rls-ff-incoming 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/1978079
Title:
EFI pstore not cleared on boot
Status in systemd package in
I think I misunderstood the first time I looked at the upstream issue.
We have the commit that reverts the regressing commit, but not the
follow-on patch (which was not backported to the v259-stable branch).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** 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/1981622
Title:
mtd device must be supplied (device name is empty)
Status in systemd package
This issue is fixed in Jammy, but not earlier LTS releases.
--
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/1928733
Title:
Starting systemd Network Service fails with
> But there is another fix around this issue
(https://github.com/systemd/systemd/pull/20214) which is released in
systemd 250.
Taking a closer look, this was actually backported to 249.4 [1] and is
present in Jammy, so this appears to be a similar but different issue.
[1]
That would be helpful. You can turn on debug-level logging for systemd-
resolved by running `systemctl edit systemd-resolved`, and add the
following line to the [Service] section:
Environment=SYSTEMD_LOG_LEVEL
Then `systemctl restart systemd-resolved`. When you have some debug logs
from an
If you have not already, I would suggest opening a new upstream issue.
After a quick look through https://github.com/systemd/systemd/issues, it
seems there have been many closely related DNSSEC issues, so it is not
obvious to me if there is a patch for your issue.
--
You received this bug
** Changed in: systemd (Ubuntu Jammy)
Status: New => 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/1981431
Title:
systemd-resolved: DNSSEC validation
Richard - I edited my above comment to clarify. That workaround is not
an attempt to fix boot on any systems.
To anyone that is experiencing boot issues, please open a separate bug
with your journal logs and dmesg logs. The "mtd device must be supplied
(device name is empty)" error is not the
Whoops, edited my comment above to fix that.
--
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/1981431
Title:
systemd-resolved: DNSSEC validation failed: incompatible-server
** 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/1981431
Title:
systemd-resolved: DNSSEC validation failed: incompatible-server
Status in
** Description changed:
[WORKAROUND]
This will NOT fix a system that is not booting, because the "mtd device
must be supplied (device name is empty)" message is not the cause of
failed boots. This work around is only for those who are annoyed by the
error message, but are otherwise
** Description changed:
+ [Impact]
+
+ Users who wish to configure additional addresses on lo may inadvertently
+ remove the 127.0.0.1/8 address from the interface. And, because this
+ only happens on the second invocation of `netplan apply`, it can create
+ confusing breakages for users.
** Description changed:
+ [WORKAROUND]
+
+ This will NOT fix a system that is not booting, because the "mtd device
+ must be supplied (device name is empty)" message is not the cause of
+ failed boots. This work around is only for those who are annoyed by the
+ error message, but are otherwise
** Description changed:
+ [Impact]
+
+ Networking components such as VPNs that rely on systemd-resolved's API
+ to configure search domains may inadvertently leave the network
+ configuration in a bad state. This is a result of a broken systemd-
+ resolved API.
+
+ [Test Plan]
+ * On a jammy
Hi,
This is in fact caused by the recent systemd SRU, which includes a patch
to systemd-pstore.service [1]. The issue appears to be quite benign, but
if anyone has experienced side effects as a result of this change
(besides the dmesg error), please let us know.
In the mean time, you can work
Are you referring to https://ubuntuforums.org/showthread.php?t=2476796?
If not, please share the links you are referring to.
It seems unlikely to me that failing to load `mtdpstore` is the problem
preventing boot. Note that systemd-pstore.service only starts if
`/sys/fs/pstore` is not empty, i.e.
The workaround prevents systemd-pstore.service from trying to load the
mtdpstore module, but it will still try to load several others which
should allow systemd-pstore to function normally.
If you have not experienced any adverse side effects, you can also
safely ignore the log message.
--
You
** Tags added: rls-ff-incoming 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/1959475
Title:
"machinectl shell" connections immediately terminated
Status
** 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/1969375
Title:
systemd-cryptenroll does not support TPM2 devices
Status in systemd package
Hi Johannes,
> Rebooting a week later after living on standby, I am screwed again.
Can you please explain what problems you experienced as a result of this
bug? My previous understanding was that there was no real effect, and
just a failed udev rule (which should not be running anyways) and
** Description changed:
+ [Impact]
+
+ This bug can cause systemd timers to lock up systems using the
+ Europe/Dublin timezone if certain OnCalendar values are used. If the
+ timer is enabled at boot, this bug prevents the system from booting. If
+ the timer is started later, systemd becomes
** Description changed:
+ [Impact]
+
+ This bug prevents users on Impish and newer from connecting to Focal
+ systemd containers using `machinectl shell`. This limits users ability
+ to manage containers spawned with systemd-nspawn.
+
+ [Test Plan]
+
+ On a Jammy host, do the following:
+
+ *
** Package changed: systemd (Ubuntu) => libfido2 (Ubuntu)
--
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/1983784
Title:
LUKS-encrypted partition is not automatically
Hi Mike,
Do you have a test case that can demonstrate/reproduce this issue?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Bill - Can you please provide more detailed logs from a failed boot
(i.e. complete journalctl output from the failed .mount units)?
** Package changed: btrfs-progs (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Public bug reported:
[Impact]
We plan to SRU src:systemd-hwe to Jammy[1] to provide an easier way to
SRU HWE hwdb rules to Ubuntu. The src:systemd-hwe package contains a
test script[2] to ensure that no redundant hwdb rules are added to the
package, i.e. rules that are already present in
It looks like jokroepke created an upstream issue:
https://github.com/systemd/systemd/issues/24098.
** Bug watch added: github.com/systemd/systemd/issues #24098
https://github.com/systemd/systemd/issues/24098
--
You received this bug notification because you are a member of Ubuntu
Touch
The fix for kinetic is included in 251.4-1ubuntu1, and the patch is
staged in git for the next jammy SRU.
** Changed in: systemd (Ubuntu Kinetic)
Status: In Progress => Fix Released
** Changed in: systemd (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug
This was covered in the 251.2-2ubuntu1 release in kinetic, but the
changelog did not reference the bug number to indicate this.
** Changed in: systemd (Ubuntu Kinetic)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
[Impact]
With systemd 249.11-0ubuntu3.5 in jammy-proposed, which enables systemd-
repart, the TEST-58-REPART fails on ppc64el:
https://autopkgtest.ubuntu.com/results/autopkgtest-
jammy/jammy/ppc64el/s/systemd/20220906_165335_6dd88@/log.gz.
This is due to a missing commit
That is expected for the stub resovler. Can you please post the full
output of the command?
$ resolvectl status
--
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/1988010
The autopkgtest regressions were all resolved with retries.
I verified this fix as well, using the test plan above to create a focal
container with -proposed enabled:
nr@clean-jammy-amd64:~$ lsb_release -cs
jammy
nr@clean-jammy-amd64:~$ sudo machinectl shell test-container
Connected to machine
On focal, the autopkgtest regressions were all resolved with retries. I
verified this fix for focal using LXD container:
root@focal:~# apt-cache policy systemd
systemd:
Installed: 245.4-4ubuntu3.18
Candidate: 245.4-4ubuntu3.18
Version table:
*** 245.4-4ubuntu3.18 500
500
lid
** Changed in: ubuntu-docker-images
Status: New => Invalid
** Changed in: systemd (Ubuntu)
Status: New => Fix Committed
** Changed in: systemd (Ubuntu)
Status: Fix Committed => In Progress
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick
Josh - Before applying your workaround, you can see which DNS servers
systemd-resolved is using by running:
$ resolvectl status
What does that show you for DNS servers? Your servers, or something else
entirely?
--
You received this bug notification because you are a member of Ubuntu
Touch
For the systemd-networkd case, can you set `SYSTEMD_LOG_LEVEL=debug` on
systemd-networkd.service to see if it yields useful information?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
: foundations-todo
** Changed in: ubiquity (Ubuntu Kinetic)
Assignee: Nick Rosbrook (enr0n) => (unassigned)
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Kinetic)
Status: New => Fix Released
** Changed in: ubiquity (
Murmel - What release of Ubuntu are you running? This has only been
fixed on Kinetic, not 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/1977630
Title:
machinectl
I think at the very least we would need to see journal output from that
time (at least until it crashes that is), and dmesg output from around
that time.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
This makes me think pid1 is dead, since the notification socket is
apparently down. Can you please try booting with these options appended
to the kernel command line?
systemd.log_level=debug systemd.log_target=console console=ttyS0,38400
console=tty1
Hopefully that will give us more information
Upstream has encountered this issue on their CI as well:
https://github.com/systemd/systemd/issues/25091.
** Bug watch added: github.com/systemd/systemd/issues #25091
https://github.com/systemd/systemd/issues/25091
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
+ [Impact]
+
+ Users with /etc/ssh/sshd_config's that contain ListenAddress entries
+ with the port specified will not be migrated to socket-activated ssh
+ correctly, or may be migrated when they should not be (e.g. if
+ ListenAddress, with a port number, is specified
** Also affects: openssh (Ubuntu Kinetic)
Importance: Critical
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1993478
Title:
package
** Patch added: "openssh_9.0p1-1ubuntu8.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1993478/+attachment/5627076/+files/openssh_9.0p1-1ubuntu8.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Description changed:
+ [NOTE FOR SRU TEAM]
+
+ I would prefer that vorlon review the attached patch before the upload
+ is accepted. I will remove this note when that has happened.
+
[Impact]
Users with /etc/ssh/sshd_config's that contain ListenAddress entries
with the port
Fixed upstream: https://github.com/systemd/systemd/pull/25172.
--
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/1995048
Title:
reboot reboots system when --poweroff is
Looking at the upstream code, the --poweroff option is intentionally
ignored when reboot is invoked [1]. The man page should be fixed to
document this exception.
[1]
https://github.com/systemd/systemd/commit/a042efad57741e90ee78b69c57310858295bf3fc
** Changed in: systemd (Ubuntu)
Status:
Sorry, I wrote my comment in a confusing way. No additional patch was
needed in Kinetic for this issue. However, the fix has not been released
for Jammy yet, but a patch has been provided that will be included in
the next systemd SRU.
--
You received this bug notification because you are a
This patch has not been brought into the Ubuntu packaging yet, so the
status should remained "Triaged" for now.
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Onuh and David - Please share the output from the following commands:
$ apt-cache policy systemd
$ systemctl list-dependencies systemd-pstore.service
$ systemctl list-dependencies --reverse modprobe@mtdpstore.service
$ systemd-analyze unit-files systemd-pstore.service
--
You received this bug
Public bug reported:
In Kinetic, TEST-36-NUMAPOLICY from upstream-2 fails very frequently on
ppc64el. See for example:
https://autopkgtest.ubuntu.com/results/autopkgtest-
kinetic/kinetic/ppc64el/s/systemd/20220908_195425_da51e@/log.gz, and the
full kinetic ppc64el history:
There is a pkgconfig file shipped with udev itself, which just contains
the definition of udev_dir. This is unrelated to the udev development
package (libudev-dev). For development purposes, you should be using
libudev, e.g. `pkg-config --libs libudev`.
The rest sounds related to your build
I have verified this fix using systemd 249.11-0ubuntu3.6 from jammy-
proposed:
nr@clean-jammy-amd64:~$ apt-cache policy systemd
systemd:
Installed: 249.11-0ubuntu3.6
Candidate: 249.11-0ubuntu3.6
Version table:
*** 249.11-0ubuntu3.6 500
500 http://archive.ubuntu.com/ubuntu
I have verified this fix using systemd 249.11-0ubuntu3.6 from jammy-
proposed:
nr@clean-jammy-amd64:~$ apt-cache policy systemd
systemd:
Installed: 249.11-0ubuntu3.6
Candidate: 249.11-0ubuntu3.6
Version table:
*** 249.11-0ubuntu3.6 500
500 http://archive.ubuntu.com/ubuntu
I have verified this fix using systemd 249.11-0ubuntu3.6 from jammy-
proposed:
nr@six:~$ apt-cache policy systemd
systemd:
Installed: 249.11-0ubuntu3.6
Candidate: 249.11-0ubuntu3.6
Version table:
*** 249.11-0ubuntu3.6 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main
I have verified the fix on jammy using systemd 249.11-0ubuntu3.6 from
jammy-proposed:
root@jammy:~# apt-cache policy systemd
systemd:
Installed: 249.11-0ubuntu3.6
Candidate: 249.11-0ubuntu3.6
Version table:
*** 249.11-0ubuntu3.6 500
500 http://archive.ubuntu.com/ubuntu
I have verified the fix using udev 249.11-0ubuntu3.6 from jammy-
proposed:
nr@clean-jammy-amd64:~$ apt-cache policy udev
udev:
Installed: 249.11-0ubuntu3.6
Candidate: 249.11-0ubuntu3.6
Version table:
*** 249.11-0ubuntu3.6 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main
I have verified that systemd-repart is available in jammy-proposed, and
that the upgrade path to kinetic works as expected:
root@jammy:~# apt-cache policy systemd-repart
systemd-repart:
Installed: 249.11-0ubuntu3.6
Candidate: 249.11-0ubuntu3.6
Version table:
*** 249.11-0ubuntu3.6 500
** Description changed:
[Impact]
With systemd 249.11-0ubuntu3.5 in jammy-proposed, which enables systemd-
repart, the TEST-58-REPART fails on ppc64el:
https://autopkgtest.ubuntu.com/results/autopkgtest-
jammy/jammy/ppc64el/s/systemd/20220906_165335_6dd88@/log.gz.
- This is due to
The focal autopkgtest regressions were all resolved by 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/1978079
Title:
EFI pstore not cleared on boot
Status in
The autopkgtest regressions were resolved by retries.
I have verified this fix on focal using the test plan above:
nr@clean-focal-amd64:~$ apt-cache policy systemd
systemd:
Installed: 245.4-4ubuntu3.18
Candidate: 245.4-4ubuntu3.18
Version table:
*** 245.4-4ubuntu3.18 500
500
** 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/1988657
Title:
VLAN gets IP address assignment from parent
> systemd-udevd[455717]: ethtool: autonegotiation is unset or enabled,
the speed and duplex are not writable.
This is not an error, but an informational message. This just means that
speed and duplex settings are read-only because autonegotiation is
enabled. Please see [1] for more detail.
Can
Onuh - are you running with -proposed enabled? This update hasn't been
released yet.
--
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
I'm not sure I understand the problem you are experiencing. Can you
please expand on what you are trying to do, and what unexpected behavior
you are seeing?
Ideally, if you could provide steps to reproduce the problem, we can
better investigate the issue.
** Changed in: systemd (Ubuntu)
> Eh? That isn't at all what the patch does...
Before the patch, the `getenv("TERM")` call would not happen; now it
does.
While fixing path_compare() may be a better long-term solution, I think
the existing patch is appropriate for this bug/SRU.
--
You received this bug notification because
Er, I see the problem in my description now. It's been a while since I
looked at this patch. In any case, the patch is still appropriate.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: systemd (Ubuntu Focal)
Status: Triaged => Fix Committed
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Description changed:
[Impact]
This bug prevents users on Impish and newer from connecting to Focal
systemd containers using `machinectl shell`. This limits users ability
to manage containers spawned with systemd-nspawn.
[Test Plan]
On a Jammy host, do the following:
*
** Tags added: foundations-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1988819
Title:
When apt keeps back packages due to phased updates, it should say so
*** This bug is a duplicate of bug 1967576 ***
https://bugs.launchpad.net/bugs/1967576
This was fixed in bug 1967576, so I am marking this a duplicate of that.
** This bug has been marked a duplicate of bug 1967576
systemd: autopkgtest: tests-in-lxd fails because of remaining snap .mount
This does not look like a systemd bug, so I am re-assigning to linux.
But, this sounds similar to your issue:
https://forums.developer.nvidia.com/t/nvidia-probe-of-00-0-failed-
with-error-1/199301, based on looking at your attached CurrentDmesg.txt.
** Package changed: systemd (Ubuntu) =>
101 - 200 of 823 matches
Mail list logo
