New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
systemctl isolate causes forced logout #1969
Comments
|
Probably all slices should be /me is affected too. |
|
@poettering? would it be correct to ignore all slices on isolate? they are second to actual units, after all. We could also make them stopped-when-unneeded. |
|
Same reports here http://bugzilla.opensuse.org/show_bug.cgi?id=966535 ... |
Fixes: systemd#1969 (cherry picked from commit 1b4cd0c) [fbui: fix for boo#966535]
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805442
Say you are logged in to the console, "systemctl isolate multi-user.target" will kick you out of your session and you are back to the login prompt. This should not happen, since getty@.service has IgnoreOnIsolate=yes.
This is a regression that afaics was introduced in v227 by commit 8c8da0e.
v228 had a followup fix in 4178002 but that is unfortunately not sufficient. So both v227 and v228 show this behaviour.
The text was updated successfully, but these errors were encountered: