Bug 1931682 - KillMode=none still set in /usr/lib/systemd/system/plymouth-start.service
Summary: KillMode=none still set in /usr/lib/systemd/system/plymouth-start.service
Keywords:
Status: CLOSED DUPLICATE of bug 1896929
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-22 23:13 UTC by John Dodson
Modified: 2021-02-23 21:34 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-02-23 21:34:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.