plymouth does not remain stopped with v245, takes over tty1

[mbiebl]

systemd version the issue has been seen with

v245

Used distribution

Debian sid

After the upgrade from v244.3 to v245 I noticed, that plymouth is no longer stopped during boot.
tty1 continues to show the plymouth boot splash even after the system has booted fully.

The following is strange:

# dpkg -L plymouth | grep quit
/lib/systemd/system/plymouth-quit-wait.service
/lib/systemd/system/plymouth-quit.service
/lib/systemd/system/multi-user.target.wants/plymouth-quit-wait.service
/lib/systemd/system/multi-user.target.wants/plymouth-quit.service

# systemctl status plymouth-quit.service 
● plymouth-quit.service - Terminate Plymouth Boot Screen
     Loaded: loaded (/lib/systemd/system/plymouth-quit.service; static; vendor preset: enabled)
     Active: inactive (dead)

# systemctl status plymouth-start.service 
● plymouth-start.service - Show Plymouth Boot Screen
     Loaded: loaded (/lib/systemd/system/plymouth-start.service; static; vendor preset: enabled)
     Active: active (running) since Thu 2020-03-12 00:06:30 CET; 7min ago
    Process: 778 ExecStart=/usr/sbin/plymouthd --mode=boot --pid-file=/var/run/plymouth/pid --attach-to-session (code=exited, status=0/SUCCESS)
    Process: 781 ExecStartPost=/usr/bin/plymouth show-splash (code=exited, status=0/SUCCESS)
   Main PID: 780 (plymouthd)
      Tasks: 1 (limit: 19006)
     Memory: 41.3M
     CGroup: /system.slice/plymouth-start.service
             └─780 @usr/sbin/plymouthd --mode=boot --pid-file=/var/run/plymouth/pid --attach-to-session

Mär 12 00:06:30 pluto systemd[1]: Starting Show Plymouth Boot Screen...
Mär 12 00:06:30 pluto systemd[1]: Started Show Plymouth Boot Screen.

[mbiebl]

(tested with lightdm and sddm)

[mbiebl]

Seems to be caused by commit 097537f

[bigon]

I think it's somehow worse, updating fro 244 to 245 in debian just now, without even rebooting, plymouth was restarted at once

[keszybz]

Yes, this is well known, and plymouth needs an update to add RemainAfterExit=yes as discussed in https://bugzilla.redhat.com/show_bug.cgi?id=1807771. Distributions should not push systemd-245 without taking care of that.

[mbiebl]

I don't think it's ok to close this.

[keszybz]

Well, what exactly do you expect us to do here? Plymouth maintainers are in contact and a fix has been agreed.

[mbiebl]

This is a significant change in behaviour. The communication regarding this change is non-existent.
Apparently it also affects other services besides plymouth.
We shouldn't just frivolously break users systems and hope downstreams mop up for us.
We should be more careful not to break systems.

[mbiebl]

What should we do: revert, find affected software, fix them, make releases for them, then reapply the change in systemd.

[mbiebl]

That this breakage was known makes this even worse, tbh.

[mbiebl]

If this issue was known: why was this not communicated much more prominently, e.g. in the release notes with a big fat warning?