From teranders@gmail.com Sat Jan 17 13:44:51 2015 Received: (at 743) by bugs.x2go.org; 17 Jan 2015 12:44:53 +0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on ymir.das-netzwerkteam.de X-Spam-Level: X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50,FREEMAIL_FROM, T_DKIM_INVALID autolearn=ham version=3.3.2 Received: from mail-la0-f41.google.com (mail-la0-f41.google.com [209.85.215.41]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 0169B5DEA3 for <743@bugs.x2go.org>; Sat, 17 Jan 2015 13:44:51 +0100 (CET) Received: by mail-la0-f41.google.com with SMTP id hv19so22735922lab.0 for <743@bugs.x2go.org>; Sat, 17 Jan 2015 04:44:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:user-agent:in-reply-to:references :mime-version:content-transfer-encoding:content-type; bh=t6KpI01a2oRC1Vo70M1TIHnWJpqzWSgUwDOssj2lmPw=; b=HhjHdeFyGTEw9bCYTgmjVFTIYN7ePNdOR9FMPQycVpGK2nH4XlR3eyVvQdSs4MW6Sw Oat2lspNrT71lymxL9fSIAoJzknbvxs2dkeQHxC3XdBoADCU3GxVOzcaJ5V7+hOWS2jq 4MBgtwNsI7KHlFnCjwvUwY8x79jTA3EWbol55eWsepLruNPYxiFyb8cLYxTzjjFgovSm pEtxrRNsAWhz/NOW19t5uxP1XQBBJG3fBVFHMv8veNJqOVrWxGDfPDb73pSEyiY3i3Fb aSdiLDoW6U5ZrhmtO1CSkwD3vfB59RGoUQAeLAMVc04dbpUryFU5xUbAi4Jt27W128Nj aV/Q== X-Received: by 10.153.7.100 with SMTP id db4mr20478429lad.79.1421498690339; Sat, 17 Jan 2015 04:44:50 -0800 (PST) Received: from tan-latitude-e6410.localnet (17.141-0-116.customer.lyse.net. [141.0.116.17]) by mx.google.com with ESMTPSA id db7sm1612752lad.16.2015.01.17.04.44.48 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 17 Jan 2015 04:44:49 -0800 (PST) From: Terje Andersen To: x2go-dev@lists.x2go.org, 743@bugs.x2go.org Subject: Re: [X2Go-Dev] Bug#743: Hangup issues when server unavailable Date: Sat, 17 Jan 2015 13:44:47 +0100 Message-ID: <2110705.PADhevySuk@tan-latitude-e6410> User-Agent: KMail/4.13.3 (Linux/3.13.0-44-generic; KDE/4.13.3; x86_64; ; ) In-Reply-To: <54B6FEF9.7060602@apl.washington.edu> References: <54B6FEF9.7060602@apl.washington.edu> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Onsdag 14. januar 2015 15.42.49 skrev Peter Brodsky: > package: x2goclient > severity: wishlist > > If I mistakenly try to open a session to a (linux) server which is not > powered up, the (Windows) client simply sits and tries. There's no way to > cancel. Clicking on the small round on/off button in the session window > (the rectangular one that lands in the left/blue area) does not take. I > simply have to wait until it times out. Could this not be dealt with more > actively? Obviously this is a "don't do that" kind of thing, but it does > happen. I've come across this myself and what I do to work around this is to quit the x2goclient. Either just closing it, or right-click and choose 'quit'. This seems to close down all the components and it's faster to just start another instance after quitting it than to wait until it times out. Regards, Terje