Hello, I am using openSUSE Tumbleweed 20240421 . I have noticed a log entry concerning 'plymouth.start.service' systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed. - Examining the service file shown below: cat plymouth-start.service [Unit] Description=Show Plymouth Boot Screen DefaultDependencies=no Wants=systemd-ask-password-plymouth.path systemd-vconsole-setup.service After=systemd-vconsole-setup.service systemd-udev-trigger.service systemd-udevd.service Before=systemd-ask-password-plymouth.service ConditionKernelCommandLine=!plymouth.enable=0 ConditionVirtualization=!container [Service] ExecStart=/usr/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session ExecStartPost=-/usr/bin/plymouth show-splash Type=forking RemainAfterExit=yes KillMode=none SendSIGKILL=no - Should I file a bug report about this this? There is a previous Bugzilla report filed on 11-06-21 https://bugzilla.opensuse.org/show_bug.cgi?id=1192412 and it has not yet been resolved upstream. What type of KillMode do you recommend for use with this this particular service? "mixed" and "control-group" options are shown above. Are there more options than those available for this situation? Could this be a reason/reasons why sometimes when the machine is shutdown the verbose shutdown messages hang for approximately one minute and 30 seconds? Displaying the following message > A stop job is running for User Manager for UID 1000 ...... -Regards