From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18982 invoked by alias); 22 Apr 2014 16:58:16 -0000 Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com Received: (qmail 18865 invoked by uid 89); 22 Apr 2014 16:58:15 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 X-HELO: smtpout19.bt.lon5.cpcloud.co.uk Received: from smtpout19.bt.lon5.cpcloud.co.uk (HELO smtpout19.bt.lon5.cpcloud.co.uk) (65.20.0.139) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 22 Apr 2014 16:58:14 +0000 X-CTCH-RefID: str=0001.0A090202.53569FA3.0036,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0 X-Junkmail-Premium-Raw: score=8/97,refid=2.7.2:2014.4.21.191820:17:8.317,ip=,rules=__MOZILLA_MSGID, __HAS_MSGID, __SANE_MSGID, __HAS_FROM, __HAS_REPLYTO, __USER_AGENT, __MOZILLA_USER_AGENT, __MIME_VERSION, __TO_MALFORMED_2, __TO_NO_NAME, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __IN_REP_TO, __CT, __CT_TEXT_PLAIN, __CTE, __CP_NOT_1, __SUBJ_ALPHA_NEGATE, __FORWARDED_MSG, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_2000_2999, __MIME_TEXT_ONLY, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, REPLYTO_FROM_DIFF_ADDY, BODY_SIZE_7000_LESS, NO_URI_FOUND X-CTCH-Spam: Unknown Received: from [192.168.1.72] (86.164.67.104) by smtpout19.bt.lon5.cpcloud.co.uk (8.6.100.99.10223) (authenticated as jonturney@btinternet.com) id 534DAD88006BE0BC; Tue, 22 Apr 2014 17:58:11 +0100 Message-ID: <53569FB3.9070803@dronecode.org.uk> Date: Tue, 22 Apr 2014 16:58:00 -0000 From: Jon TURNEY Reply-To: cygwin-xfree User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: cygwin-xfree@cygwin.com CC: arnaud.caubel@lsce.ipsl.fr Subject: Re: windows 7 cygwin/XWin session dies References: <53563DC6.8030402@lsce.ipsl.fr> In-Reply-To: <53563DC6.8030402@lsce.ipsl.fr> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SW-Source: 2014-04/txt/msg00005.txt.bz2 On 22/04/2014 11:00, Arnaud Caubel wrote: > I run my cygwin/XWin.exe session on Windows 7 Professional and this session > dies when I iconify it during some time (let'say 20 min). > I think the problem is not to iconify it but more to not do anything. > It is very uncomfortable because I have to relaunch it every time I do > something else (emails, internet,...) more than about 20 minutes... > I do not understand why the X session crashes... > Could anyone help me ? > > It seems there is something with : "XDM: Alive response indicates session > dead, declaring session dead" but I do not know which parameter I have to > change to modify this behaviour... > Release: 1.9.2.0 (10902000) > Build Date: 2010-11-03 This is quite an old version. While I am not aware of any fixes in this area, you might like to try with the current version. > [ 6240.102] XDM: Alive response indicates session dead, declaring session dead This means "I sent an XDMCP keepalive for the current session to the XDM server, but it's response said that the session wasn't alive." One question I have is if your machine running XWin is idle, and going into a sleep state before this problem occurs? If that is the case, that may be the problem, as XDM will, by default, periodically test if it can contact the display and declare the session dead if that fails. If your display manager is XDM, that can be turned off by setting the DisplayManager.DISPLAY.pingInterval resource to 0. Other display managers may have similar settings. Alternatively, you could arrange for sleeping to be suspended while the X server is running (It seems on Win7 or later you can use powercfg -requestsoverride to prevent sleep while a specified program is running, or there are several simple utilities available which prevent suspend while they are running) If that is not the case, the XDM logs on the XDM host might be informative, if you have access to them. Failing that, you could use wireshark or similar to monitor the XDMCP protocol interactions. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/