Bug 1931682

Summary: KillMode=none still set in /usr/lib/systemd/system/plymouth-start.service
Product: [Fedora] Fedora Reporter: John Dodson <jwadodson>
Component: plymouthAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 33CC: gnome-sig, hdegoede, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-23 21:34:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description John Dodson 2021-02-22 23:13:24 UTC
Description of problem:

Error is logged...
/usr/lib/systemd/system/plymouth-start.service:15: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.: 1 Time(s)

Version-Release number of selected component (if applicable):

plymouth.x86_64                        0.9.4-16.20200325gite31c81f.fc33

How reproducible:

Every boot.

Steps to Reproduce:
1. Boot
2. See journal log or logwatch
3.

Actual results:

/usr/lib/systemd/system/plymouth-start.service:15: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.: 1 Time(s)

Expected results:

No error.

Additional info:

This was noted in, https://bugzilla.redhat.com/show_bug.cgi?id=1807771
but still seemingly not fixed.

Comment 1 Hans de Goede 2021-02-23 21:34:23 UTC

*** This bug has been marked as a duplicate of bug 1896929 ***