Something kills my screens
up vote
0
down vote
favorite
My screen sessions are getting killed when I log out. How can I prevent this?
I have already set:
KillUserProcesses=no
in /etc/systemd/logind.conf. When I log back in, I get the "wipe" option in screen. This problem is made quite apparent by another bug which forcibly logs me out every time I turn off the monitor.
17.10 systemd background-process
edited Dec 8 '17 at 12:37
Videonauth
23.5k126898
asked Dec 8 '17 at 8:34
Marius Bjørnstad
5517
add a comment |
up vote
0
down vote
favorite
My screen sessions are getting killed when I log out. How can I prevent this?
I have already set:
KillUserProcesses=no
in /etc/systemd/logind.conf. When I log back in, I get the "wipe" option in screen. This problem is made quite apparent by another bug which forcibly logs me out every time I turn off the monitor.
17.10 systemd background-process
edited Dec 8 '17 at 12:37
Videonauth
23.5k126898
asked Dec 8 '17 at 8:34
Marius Bjørnstad
5517
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
My screen sessions are getting killed when I log out. How can I prevent this?
I have already set:
KillUserProcesses=no
in /etc/systemd/logind.conf. When I log back in, I get the "wipe" option in screen. This problem is made quite apparent by another bug which forcibly logs me out every time I turn off the monitor.
17.10 systemd background-process
edited Dec 8 '17 at 12:37
Videonauth
23.5k126898
asked Dec 8 '17 at 8:34
Marius Bjørnstad
5517
My screen sessions are getting killed when I log out. How can I prevent this?
I have already set:
KillUserProcesses=no
in /etc/systemd/logind.conf. When I log back in, I get the "wipe" option in screen. This problem is made quite apparent by another bug which forcibly logs me out every time I turn off the monitor.
17.10 systemd background-process
17.10 systemd background-process
edited Dec 8 '17 at 12:37
Videonauth
23.5k126898
asked Dec 8 '17 at 8:34
Marius Bjørnstad
5517
edited Dec 8 '17 at 12:37
Videonauth
23.5k126898
asked Dec 8 '17 at 8:34
Marius Bjørnstad
5517
edited Dec 8 '17 at 12:37
Videonauth
23.5k126898
edited Dec 8 '17 at 12:37
Videonauth
23.5k126898
edited Dec 8 '17 at 12:37
Videonauth
23.5k126898
23.5k126898
asked Dec 8 '17 at 8:34
Marius Bjørnstad
5517
asked Dec 8 '17 at 8:34
Marius Bjørnstad
5517
asked Dec 8 '17 at 8:34
Marius Bjørnstad
5517
5517
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
I don't know if this works on 17.10 but on 18.04 I had the same issue. It seems to be because of changes on logind cleaning up processes (preventing any user session process persisting). Apparently KillUserProcesses=no is the default in 18.04 (according to the comments in /etc/systemd/logind.conf) so instead I added my user to the KillExcludeUsers list:
KillExcludeUsers=root YOUR_USERNAME
Next I ran the command:
sudo loginctl enable-linger YOUR_USERNAME
and finally rebooted. After that my screen session would persist after a detach.
answered Nov 29 at 14:01
Adam Lyall
261
The second line fixed it for me, thanks! I thinkKillUserProcesses=nodoes the same asKillExcludeUsers=root YOUR_USERNAME, but it's a bit more blunt solution.
– Marius Bjørnstad
Dec 1 at 12:17
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f984332%2fsomething-kills-my-screens%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
I don't know if this works on 17.10 but on 18.04 I had the same issue. It seems to be because of changes on logind cleaning up processes (preventing any user session process persisting). Apparently KillUserProcesses=no is the default in 18.04 (according to the comments in /etc/systemd/logind.conf) so instead I added my user to the KillExcludeUsers list:
KillExcludeUsers=root YOUR_USERNAME
Next I ran the command:
sudo loginctl enable-linger YOUR_USERNAME
and finally rebooted. After that my screen session would persist after a detach.
answered Nov 29 at 14:01
Adam Lyall
261
The second line fixed it for me, thanks! I thinkKillUserProcesses=nodoes the same asKillExcludeUsers=root YOUR_USERNAME, but it's a bit more blunt solution.
– Marius Bjørnstad
Dec 1 at 12:17
add a comment |
up vote
1
down vote
accepted
I don't know if this works on 17.10 but on 18.04 I had the same issue. It seems to be because of changes on logind cleaning up processes (preventing any user session process persisting). Apparently KillUserProcesses=no is the default in 18.04 (according to the comments in /etc/systemd/logind.conf) so instead I added my user to the KillExcludeUsers list:
KillExcludeUsers=root YOUR_USERNAME
Next I ran the command:
sudo loginctl enable-linger YOUR_USERNAME
and finally rebooted. After that my screen session would persist after a detach.
answered Nov 29 at 14:01
Adam Lyall
261
The second line fixed it for me, thanks! I thinkKillUserProcesses=nodoes the same asKillExcludeUsers=root YOUR_USERNAME, but it's a bit more blunt solution.
– Marius Bjørnstad
Dec 1 at 12:17
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
I don't know if this works on 17.10 but on 18.04 I had the same issue. It seems to be because of changes on logind cleaning up processes (preventing any user session process persisting). Apparently KillUserProcesses=no is the default in 18.04 (according to the comments in /etc/systemd/logind.conf) so instead I added my user to the KillExcludeUsers list:
KillExcludeUsers=root YOUR_USERNAME
Next I ran the command:
sudo loginctl enable-linger YOUR_USERNAME
and finally rebooted. After that my screen session would persist after a detach.
answered Nov 29 at 14:01
Adam Lyall
261
I don't know if this works on 17.10 but on 18.04 I had the same issue. It seems to be because of changes on logind cleaning up processes (preventing any user session process persisting). Apparently KillUserProcesses=no is the default in 18.04 (according to the comments in /etc/systemd/logind.conf) so instead I added my user to the KillExcludeUsers list:
KillExcludeUsers=root YOUR_USERNAME
Next I ran the command:
sudo loginctl enable-linger YOUR_USERNAME
and finally rebooted. After that my screen session would persist after a detach.
answered Nov 29 at 14:01
Adam Lyall
261
answered Nov 29 at 14:01
Adam Lyall
261
answered Nov 29 at 14:01
Adam Lyall
261
answered Nov 29 at 14:01
Adam Lyall
261
261
The second line fixed it for me, thanks! I thinkKillUserProcesses=nodoes the same asKillExcludeUsers=root YOUR_USERNAME, but it's a bit more blunt solution.
– Marius Bjørnstad
Dec 1 at 12:17
add a comment |
The second line fixed it for me, thanks! I thinkKillUserProcesses=nodoes the same asKillExcludeUsers=root YOUR_USERNAME, but it's a bit more blunt solution.
– Marius Bjørnstad
Dec 1 at 12:17
The second line fixed it for me, thanks! I think
KillUserProcesses=no does the same as KillExcludeUsers=root YOUR_USERNAME, but it's a bit more blunt solution.– Marius Bjørnstad
Dec 1 at 12:17
The second line fixed it for me, thanks! I think
KillUserProcesses=no does the same as KillExcludeUsers=root YOUR_USERNAME, but it's a bit more blunt solution.– Marius Bjørnstad
Dec 1 at 12:17
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f984332%2fsomething-kills-my-screens%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
