This is a tracking bug for Change: KillUserProcesses=yes by default
For more details, see: https://fedoraproject.org//wiki/Changes/KillUserProcesses_by_default
Set the default policy to terminate processes in session scope when the user logs out. Specifically, systemd-logind's KillUserProcesses setting, which currently is set to "no" to override the upstream default, will be removed to follow the upstream default of "yes".
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.
On 2016-July-26, we have reached Fedora 25 Change Checkpoint: Completion deadline (testable).
At this point, all accepted changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be enabled at Change Completion deadline as well.
Change tracking bug should be set to the MODIFIED state to indicate it achieved completeness.
Incomplete and non testable Changes will be reported to FESCo on 2016-July-29 meeting.
Systemd-231 was compiled in rawhide today, with the first bit of implementation for this change: logging of left-over processes killed with SIGKILL/SIGABRT at notice level.
I'm still working on the other parts.
Deferred to F26 https://fedorahosted.org/fesco/ticket/1606#comment:6
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
According to the Fedora 29 schedule, today is the deadline for changes to be in a testable state. If your change is ready to be tested, please set the status to ON_QA. A list of incomplete changes will be sent to FESCo tomorrow for evaluation. If you know your change will not be ready for Fedora 29, you can set the version to rawhide and notify bcotton.
Closing this bug as the Change has not been implemented or resubmitted for Fedora 30.
Should we reopen this? People are complaining about KDE Plasma sessions:
I am no longer in Fedora PgM position. Changing the request to Ben.
(In reply to Andrey from comment #9)
> Should we reopen this? People are complaining about KDE Plasma sessions:
No, the change was abandoned so it's not appropriate to reopen the tracking bug. If someone wants to bring this back up, they need to submit a new change proposal.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days