Stefan- I did some digging and found this change entry for Fedora: https://fedoraproject.org/wiki/Changes/KillUserProcesses_by_default so it appears your gut feeling was correct, it is a change in Fedora defaults. This does not explain why manually setting it back does not preserve the session, I will continue to investigate. Thanks. Chris chrisgpayne@gmail.com On Wed, Aug 2, 2017 at 10:20 AM, Chris Payne wrote: > Hi Stefan- > > I could not find a window to reboot my main workstation, so I setup x2go > between a couple a laptops at home and can reproduce this. I set these > parameters (added my user as well to the Exclude list) > > [root@Spotted-Ray ~]# grep -ri kill /etc/systemd/ > /etc/systemd/logind.conf:KillUserProcesses=no > /etc/systemd/logind.conf:#KillOnlyUsers= > /etc/systemd/logind.conf:KillExcludeUsers=root cpayne2go > [root@Spotted-Ray ~]# > > but I still get the same response even after rebooting with these in place. > > Not sure what else to try, thanks again. > > Chris > chrisgpayne@gmail.com > > On Fri, Jul 28, 2017 at 3:14 PM, Stefan Baur > wrote: > >> Am 28.07.2017 um 22:14 schrieb Chris Payne: >> >> > I uncommented the line, restarted the login service >> > >> > systemctl status systemd-logind.service >> > >> > and I get the same response from a suspend. Does it require a reboot or >> > a different restart? >> >> That's a good question. If you can reboot the system without much >> hassle, it would probably be the quickest way to find out if that >> setting makes a difference for you. >> If rebooting is not an option, I hope someone more knowledgeable about >> systemd comes along and has an answer for you. >> >> Kind Regards, >> Stefan Baur >> >> -- >> BAUR-ITCS UG (haftungsbeschränkt) >> Geschäftsführer: Stefan Baur >> Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 >> Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 >> >> >