This bug was fixed in the package systemd - 237-3ubuntu10.42
---
systemd (237-3ubuntu10.42) bionic; urgency=medium
[ Dan Streetman ]
*
d/p/lp1860926/0001-networkd-Allow-to-retain-configs-even-if-carrier-is-.patch,
as this is the lowest-numbered bug for this systemd upload, here is the
autopkgtest failure analysis:
linux-aws-edge is failing due to bug 1890178 which is not caused by this
upload, and can be ignored
linux-hwe-5.4 tests appear flaky on all archs, but especially so on
armhf; the repeated
with the proposed version of systemd, i've rebooted a system 100 times
with no issues.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Too late, I am already at 20.04.
--
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/1832754
Title:
"shutdown[1]: Failed to wait for process: Protocol error" at shutdown
or
Hello Tim, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.42 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
As per our discussion, since the changes here are relatively sane and
with a low regression risk, I have accepted this without a clear
reproducer. Please be sure to try and contact someone that has an
affected device/configuration and trying to test it there - if not, your
proposed test of
> So how do you intend to complete this SRU if there is no test case for
verifying?
intermittent issues frequently are not easily reproducable, and
sometimes require specific system configuration that can't be completely
identified and duplicated, even by those experiencing the bug. Expecting
all
> it's unclear what the specific configuration is to be able to
reproduce this, but there are some examples in the upstream bug
So how do you intend to complete this SRU if there is no test case for
verifying?
** Changed in: systemd (Ubuntu Bionic)
Status: In Progress => Incomplete
--
** Description changed:
+ [impact]
+
+ shutdown sometimes fails to unmount some fs, which causes shutdown hang
+
+ [test case]
+
+ it's unclear what the specific configuration is to be able to reproduce
+ this, but there are some examples in the upstream bug
+
+ [regression potential]
+
+ as
Do you have a way to reproduce this? It likely only needs commit
8645ffd12b3cc7b0292acd9e1d691c4fab4cf409 and/or
e783b4902f387640bba12496936d01e967545c3c but without a way to
reproduce/test, it's hard to say if more of the upstream commits are
needed.
** Tags added: ddstreet
** Also affects:
** Changed in: systemd
Status: Unknown => 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/bugs/1832754
Title:
"shutdown[1]: Failed to wait for process:
** Bug watch added: github.com/systemd/systemd/issues #8155
https://github.com/systemd/systemd/issues/8155
** Also affects: systemd via
https://github.com/systemd/systemd/issues/8155
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Upstream discussion points to
https://github.com/systemd/systemd/pull/8429
** Summary changed:
- ubuntu-bug systemd
+ "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or
reboot and hangs.
--
You received this bug notification because you are a member of Ubuntu
Touch
13 matches
Mail list logo
