Ubuntu
systemd package

  1. Bug #1908067
  2. Comment #0

Comment 0 for bug 1908067

Revision history for this message
Dan Streetman (ddstreet) wrote :

[impact]

systemd-fsckd test fails on groovy because plymouth-start service is active

[test case]

check autopkgtest logs of systemd-fsckd test case on groovy

[regression potential]

incorrectly passed, or failed, systemd-fsckd test

[scope]

this is needed only for groovy.

the plymouth-start.service did not include RemainAfterExit=true before groovy, so the service is expected to be inactive when checked by the test before groovy. this is already fixed in hirsute, and this is just a backport of that fix to groovy.