This bug was fixed in the package systemd - 237-3ubuntu10.22
---
systemd (237-3ubuntu10.22) bionic; urgency=medium
* d/p/resolved-rework-how-we-determine-which-scope-to-send.patch
- fix DNS leakage (LP: 1754671)
*
This bug was fixed in the package systemd - 239-7ubuntu10.14
---
systemd (239-7ubuntu10.14) cosmic; urgency=medium
* d/p/resolved-rework-how-we-determine-which-scope-to-send.patch
- fix DNS leakage (LP: 1754671)
* d/t/boot-and-services:
- skip test_no_failed if gdm failed
This bug was fixed in the package systemd - 240-6ubuntu5.1
---
systemd (240-6ubuntu5.1) disco; urgency=medium
* d/p/ask-password-prevent-buffer-overrow-when-reading-fro.patch:
- prevent buffer overflow when reading keyring (LP: #1814373)
*
This bug was fixed in the package systemd - 240-6ubuntu9
---
systemd (240-6ubuntu9) eoan; urgency=medium
* Fix typpo in storage test.
File: debian/tests/storage
note on the corosync autopkgtest failure in disco; i opened bug 1831492
and the failure can be ignored for this upload.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825997
Title:
boot-smoke fails
autopkgtest failures:
disco:
linux-oracle, linux-snapdragon: tests never passed; ignore
dbus: this appears to be the same issue as is seen for systemd in bug
1829829; i'm re-running the test (again), but if it still doesn't pass I
think we need to ignore it as a failure due to that bug.
autopkgtest failures:
cosmic:
linux-oracle: tests never passed; ignore.
umockdev: I opened bug 1831467, and i'm re-running the test; it's an
intermittent failure so hopefully it will pass the next time, but even
if not i believe we can ignore its failure as it seems to be a test case
problem of
autopkgtest failures:
bionic:
linux-snapdragon, linux-gke-4.15, linux-aws-edge: these have never
passed; ignore.
gvfs (ppc64el and i386): bug 1713098 (failure matches report from that
bug)
systemd (ppc64el): only test failure is due to bug 1821625 (which
requires kernel patch)
systemd (i386):
boot-smoke passed for all releases/archs from this upload
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic verification-needed-disco
** Tags added: verification-done verification-done-bionic
verification-done-cosmic verification-done-disco
--
You
Hello Dan, 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.22 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Dan, or anyone else affected,
Accepted systemd into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Tags removed: ddstreet-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825997
Title:
boot-smoke fails due to running jobs
To manage notifications about this bug go to:
** Changed in: systemd (Ubuntu Eoan)
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/1825997
Title:
boot-smoke fails due to running jobs
To manage
** Description changed:
[impact]
boot-smoke test reboots 5 times and verifies systemd is fully started up
after each boot, including checking if there are any running jobs (with
list-jobs). However, this test makes the assumption that no further
jobs will be started after systemd
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Xenial)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: systemd (Ubuntu Eoan)
Assignee: (unassigned) => Dan Streetman (ddstreet)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825997
Title:
boot-smoke fails due to running jobs
To
** Changed in: systemd (Ubuntu Eoan)
Assignee: Dan Streetman (ddstreet) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825997
Title:
boot-smoke fails due to running jobs
To
** Merge proposal linked:
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/366857
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825997
Title:
boot-smoke fails
** Tags added: ddstreet-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825997
Title:
boot-smoke fails due to running jobs
To manage notifications about this bug go to:
** Description changed:
[impact]
boot-smoke test reboots 5 times and verifies systemd is fully started up
after each boot, including checking if there are any running jobs (with
list-jobs). However, this test makes the assumption that no further
jobs will be started after systemd
** Description changed:
[impact]
boot-smoke test reboots 5 times and verifies systemd is fully started up
after each boot, including checking if there are any running jobs (with
list-jobs). However, this test makes the assumption that no further
jobs will be started after systemd
** Description changed:
[impact]
boot-smoke test reboots 5 times and verifies systemd is fully started up
- after each boot, but only gives 35 seconds for each boot. On loaded
- systems this is too short.
+ after each boot, including checking if there are any running jobs (with
+
22 matches
Mail list logo
