From chrisgpayne@gmail.com Thu Aug 3 22:35:50 2017 Received: (at 1198) by bugs.x2go.org; 3 Aug 2017 20:35:59 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on ymir.das-netzwerkteam.de X-Spam-Level: X-Spam-Status: No, score=-2.0 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_BLOCKED, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.1 Received: from localhost (localhost [127.0.0.1]) by ymir.das-netzwerkteam.de (Postfix) with ESMTP id A7D525DA80 for <1198@bugs.x2go.org>; Thu, 3 Aug 2017 22:35:50 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at ymir.das-netzwerkteam.de Received: from ymir.das-netzwerkteam.de ([127.0.0.1]) by localhost (ymir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LZxSa6uMluxs for <1198@bugs.x2go.org>; Thu, 3 Aug 2017 22:35:29 +0200 (CEST) Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id EDA455DA4A for <1198@bugs.x2go.org>; Thu, 3 Aug 2017 22:35:28 +0200 (CEST) Received: by mail-qk0-x230.google.com with SMTP id d136so14541897qkg.3 for <1198@bugs.x2go.org>; Thu, 03 Aug 2017 13:35:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc; bh=OVyXgl05GOk8mVJlYRUYhyhGR8M3JKvKfXQljFeB050=; b=F0nJYzzlWzWFPE+lAWenEqS/RFwK3jHFnge2uVZMlbUZpodw84cmJEQ+9TougXGBjA bdCeUP9/m095frt9eLIg/jAP8zXaeb5s93sonhVV+uKD9fjyYz3Hpar+qADRWHNsF/gl d5fGG0zi7sCQWUO6hMKB1P0u1mUmSvg+E8fMyHh8M6K3g7it7rj6mczZNXajgCjWndbg zkL4gMZbfi6GTUnjOHymsncDvAmEPn23FEKHb/CODN5dbo0vf4YDp7GoxhxhwxWdEV/T 0lu4DDs0vQbKxE/AoWlaSjxSLxL3WWDnhfCMFTuoqvFEO1BI9mt88sQ5ww77Rv3PULeO tPeQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=OVyXgl05GOk8mVJlYRUYhyhGR8M3JKvKfXQljFeB050=; b=ewewJOu9hcgmJUrvzbpiIOFi+Neh5vl/caFPMhAwfR3n1q2msCWLouYayRDGVbA0Cp 6WgLRx3P6yZTR+umjgsIfrYx409u6ES/9nqizxYuLT629bf5+QTsgZPV575lbbniVPoo FKH/0Fy4KC2OGhxmlRQRcWj52t1mVzBDaTiwVRbPbSg43Ew1ly/1PzseYfrJCgKyqWPu 9UjTkweQRTS+ahRKndXRF/PC5qDeI19tgsN0OMPM/0c95M3xaAcwF4MftuyLsxAhVpOV ibheCZRwcoeE7nP0aqoqY6XuPEo/kSou+/zTyx1Y3Sf4v/JNixbCU7nWmaUKxOJeiZua ltwg== X-Gm-Message-State: AHYfb5iLNjKfSZ6fExRp5VnhMDLdBOnmowUeg5bclF5YtyOcpwd3ZNy8 a58mtJKtvyaBBe7NtNFnaE9hyHS/IQ== X-Received: by 10.55.26.14 with SMTP id a14mr153976qka.4.1501792527743; Thu, 03 Aug 2017 13:35:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.28.6 with HTTP; Thu, 3 Aug 2017 13:35:07 -0700 (PDT) Reply-To: chrisgpayne@gmail.com In-Reply-To: References: <9d7a82e6-5618-c6a6-bc9d-a2accd675607@baur-itcs.de> <247b55bd-ae44-bece-2036-26adb05157b5@baur-itcs.de> <628a4129-9fa0-8756-79ca-481bb4e27098@baur-itcs.de> From: Chris Payne Date: Thu, 3 Aug 2017 14:35:07 -0600 Message-ID: Subject: Re: [X2Go-Dev] Bug#1198: Suspend session does not work since update to Fedora 26 To: Stefan Baur Cc: 1198@bugs.x2go.org Content-Type: multipart/alternative; boundary="001a11471d90248b400555df52df" --001a11471d90248b400555df52df Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=3Dno > /etc/systemd/logind.conf:#KillOnlyUsers=3D > /etc/systemd/logind.conf:KillExcludeUsers=3Droot cpayne2go > [root@Spotted-Ray ~]# > > but I still get the same response even after rebooting with these in plac= e. > > 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 o= r >> > 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=C3=A4nkt) >> Gesch=C3=A4ftsf=C3=BChrer: Stefan Baur >> Eichen=C3=A4ckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 >> Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 >> >> > --001a11471d90248b400555df52df Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Stefan-

I did some digging and found th= is change entry for Fedora:


so it appears your gut feeling was correct, it is a change in Fedora def= aults. This does not explain why manually setting it back does not preserve= the session, I will continue to investigate.

Thanks.



On Wed, Aug 2, 2017 at 10:20 AM, Chris Payne= <chrisgpayne@gmail.com> wrote:
Hi Stefan-

I could n= ot find a window to reboot my main workstation, so I setup x2go between a c= ouple a laptops at home and can reproduce this. I set these parameters (add= ed my user as well to the Exclude list)

[root@Spotted-Ray ~]# grep -= ri kill /etc/systemd/
/etc/systemd/logind.conf:KillUserProcesses=3D= no
/etc/systemd/logind.conf:#KillOnlyUsers=3D
/etc/systemd/login= d.conf:KillExcludeUsers=3Droot 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.
<= div class=3D"gmail_extra">

On Fri, Jul 28, 2017 at 3:14 PM, Stefan Baur= <X2Go-ML-1@baur-itcs.de> 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 o= r
> a different restart?

That's a good question.=C2=A0 If you can reboot the system witho= ut 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=C3=A4nkt)
Gesch=C3=A4ftsf=C3=BChrer: Stefan Baur
Eichen=C3=A4ckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364
Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243



--001a11471d90248b400555df52df--