From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21398 invoked by alias); 12 Feb 2013 03:51:51 -0000 Received: (qmail 21378 invoked by uid 22791); 12 Feb 2013 03:51:50 -0000 X-SWARE-Spam-Status: No, hits=1.0 required=5.0 tests=AWL,BAYES_50,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-ve0-f194.google.com (HELO mail-ve0-f194.google.com) (209.85.128.194) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 12 Feb 2013 03:51:46 +0000 Received: by mail-ve0-f194.google.com with SMTP id 14so1394600vea.5 for ; Mon, 11 Feb 2013 19:51:45 -0800 (PST) X-Received: by 10.220.219.80 with SMTP id ht16mr21651284vcb.30.1360641105516; Mon, 11 Feb 2013 19:51:45 -0800 (PST) Received: from ToshibaLaptop (pool-100-0-26-106.bstnma.fios.verizon.net. [100.0.26.106]) by mx.google.com with ESMTPS id p20sm63187889vdj.6.2013.02.11.19.51.44 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 11 Feb 2013 19:51:44 -0800 (PST) Message-ID: <7BAAEF845FCF42B687F8A3181FD86025@ToshibaLaptop> From: "Ray Balogh" To: Subject: X connections reset on PC sleep Date: Tue, 12 Feb 2013 03:51:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original Content-Transfer-Encoding: 8bit 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 X-SW-Source: 2013-02/txt/msg00018.txt.bz2 Sorry, I’m sure this is a known issue, but I can’t seem to locate any description of the problem in the FAQ, docs, or mailing list archives. The problem is that when my PC sleeps, my X connections get reset with xterm: fatal IO error 104 (Connection reset by peer) or KillClient on X server “somehost:0” although the Cygwin/X server (Ver. 1.13.1) is still running. I’ve enabled logging, but I don’t see anything at all in the log file. Is there some configuration to stop Cygwin/X from doing this? It’s extremely inconvenient to have to recreate all my windows if I happen to step away from the system for a while. I’m running the X clients under a Ubuntu VM (VMware Player), in case that is significant. Thanks in advance for your advice! Ray -- 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/