X2Go Bug report logs - #1198
Suspend session does not work since update to Fedora 26

version graph

Package: x2goserver; Maintainer for x2goserver is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2goserver is src:x2goserver.

Reported by: chrisgpayne@gmail.com

Date: Thu, 27 Jul 2017 13:20:02 UTC

Severity: normal

Tags: pending

Found in version 4.0.1.20

Fixed in version 4.0.1.21

Done: X2Go Release Manager X2Go Release Manager <git-admin@x2go.org>

Bug is archived. No further changes may be made.

Full log

Message #40 received at 1198@bugs.x2go.org (full text, mbox, reply):

Received: (at 1198) by bugs.x2go.org; 2 Aug 2017 20:29:52 +0000
From unmagoon@gmail.com  Wed Aug  2 22:29:46 2017
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=-1.0 required=3.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,FREEMAIL_REPLY,RCVD_IN_DNSWL_NONE,
	URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.1
Received: from localhost (localhost [127.0.0.1])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 0CDE35DACC
	for <1198@bugs.x2go.org>; Wed,  2 Aug 2017 22:29:46 +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 iGxQ9ffqYK0F for <1198@bugs.x2go.org>;
	Wed,  2 Aug 2017 22:29:16 +0200 (CEST)
Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 117C65DA4A
	for <1198@bugs.x2go.org>; Wed,  2 Aug 2017 22:29:16 +0200 (CEST)
Received: by mail-wm0-x243.google.com with SMTP id r77so295693wmd.2
        for <1198@bugs.x2go.org>; Wed, 02 Aug 2017 13:29:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=subject:to:references:from:message-id:date:user-agent:mime-version
         :in-reply-to:content-language:content-transfer-encoding;
        bh=fqqsJkPqHaNSBF64WxRIxUvj5gdLFP2ADpYibIBLcaY=;
        b=vGnxSXHfxS6hEOLcTADU4TCTUckDUDXiN8dgZpuW3Dkdw3M/sTmT6yQNctmIAvb7zY
         U3OzpwqOO11i418P6Q5w+abiwysZrA4yXvpLlZIOVuvR/LqI/QD6XsYZOQj5NLkX1tCe
         C4fW0OuspIPSWhCGL7TkWo4XsQbtjPxkBHidpqCaV9T4WxNlajqmymC1+RKZfeVnMefe
         BMVf1yqD26afTfKH+ZtoylBidv77D8xclUiMFKJpQUkBlnSJj1KYwMqVu/dn9C4oa39M
         pYHEiTI9QpmVY1oBiJl/YE01tQVYe2DVrrXTu5CCBl4RsZ8n5c9tfFEhw3ja1VJsikwP
         b+7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:subject:to:references:from:message-id:date
         :user-agent:mime-version:in-reply-to:content-language
         :content-transfer-encoding;
        bh=fqqsJkPqHaNSBF64WxRIxUvj5gdLFP2ADpYibIBLcaY=;
        b=oR92i77SX5i2a5AO+AQTPB+vEV531L7BBnH2Sp7axBdD05D2WpUrhhPyrHW2mtgMjM
         Ji0GNFqqZV3LIQK3m+G7XyqqZFWJNFVPR6GNikUtxlLU+0Yk96qBX1ejZh+Ob3/9d5r1
         9grYW3t12d7aciYZv4UgOXZ7X14KFfgXfEItUT6lSLlvAzCvNslZRttCeCiiWIVOi690
         l1KLKV9jyIDB88SuSV/lV+nyWYHxf4REliGnGFJK9BW24JwPxzEQaLVpWn6Ciq0q3+9D
         0lnxDmqQfwkW9uBOjQvQL1VV4GNxm/5Fq/jOxy5HOh97Re2tUdXg33XCdAG3jNXmLkAG
         8Kuw==
X-Gm-Message-State: AIVw110y4b9+WIsW2AYVNaWDwJKOKbDwYOKm7lGaFKK/ULd9WvQNzLvE
	g/lEeJhc0HqfIgfyD8o=
X-Received: by 10.28.99.137 with SMTP id x131mr4855922wmb.125.1501705228966;
        Wed, 02 Aug 2017 13:20:28 -0700 (PDT)
Received: from ?IPv6:2001:41d0:1:e6cc::1000? ([2001:41d0:1:e6cc::1000])
        by smtp.gmail.com with ESMTPSA id k46sm191510wre.1.2017.08.02.13.20.27
        for <1198@bugs.x2go.org>
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Wed, 02 Aug 2017 13:20:28 -0700 (PDT)
Subject: Re: [X2Go-Dev] Bug#1198: Bug#1198: Suspend session does not work
 since update to Fedora 26
To: 1198@bugs.x2go.org
References: <CALhpf6R4eBzJLsGb5wnoA_gbXhvPx4Q9js-8hjYchoUf6wHLnQ@mail.gmail.com>
 <9d7a82e6-5618-c6a6-bc9d-a2accd675607@baur-itcs.de>
 <CALhpf6Q2wKG-yjhCA7bJw1Qt-Myd+UpNBeL2pkW8nYW_5UX7tg@mail.gmail.com>
 <247b55bd-ae44-bece-2036-26adb05157b5@baur-itcs.de>
 <CALhpf6TEz3NVwu7JmvZDD4dg-XwAaTp2D_vocmAyRKUBizNkPA@mail.gmail.com>
 <628a4129-9fa0-8756-79ca-481bb4e27098@baur-itcs.de>
 <CALhpf6Qxio6nrnakP+OV5V9CyNMZRgRDwp2FmYTQrhaA+3vHhA@mail.gmail.com>
From: "U. M. Goon" <unmagoon@gmail.com>
Message-ID: <d30bbd33-43d9-6fd7-3bdb-38d9a4c32c6d@gmail.com>
Date: Wed, 2 Aug 2017 22:20:27 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CALhpf6Qxio6nrnakP+OV5V9CyNMZRgRDwp2FmYTQrhaA+3vHhA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit

Hi Chris,

if you're looking for things to try please enable lingering via

# loginctl enable-linger cpayne2go

because it appears even with this flag explicitly set user-sessions can 
still get killed. You can also check if that is even the problem by 
keeping open a separate SSH session while suspend/resuming or looking at 
your journal (user service getting killed). The same problem appeared on 
Arch a few weeks ago.

Also if anyone knows how the KillUserProcesses flag can get ignored, 
please let me know.

Best,
U.G.

On 08/02/2017 06:20 PM, 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 <mailto:chrisgpayne@gmail.com>
> 
> On Fri, Jul 28, 2017 at 3:14 PM, Stefan Baur <X2Go-ML-1@baur-itcs.de 
> <mailto: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 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
> 
> 
> 
> 
> _______________________________________________
> x2go-dev mailing list
> x2go-dev@lists.x2go.org
> https://lists.x2go.org/listinfo/x2go-dev
>

Send a report that this bug log contains spam.

X2Go Developers <owner@bugs.x2go.org>. Last modified: Fri May 3 05:33:27 2024; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.