public inbox for
help / color / mirror / Atom feed
From: Jon TURNEY <>
Subject: Re: X connections reset on PC sleep
Date: Wed, 13 Feb 2013 15:05:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <7BAAEF845FCF42B687F8A3181FD86025@ToshibaLaptop>

On 12/02/2013 03:51, Ray Balogh wrote:
> 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.

I'm afraid that the X protocol doesn't have any way for a running client to
detach and reconnect to a server.  If one end of the connection goes to sleep,
the connection will be broken.

I don't think there's anything particularly cygwin-specific about this X
server behaviour.

It's not clear to me from what you write if the Ubuntu VM is on the same PC as
the cygwin X server.  If so, it might be that there is some kind of problem
with the order in which things are allowed to resume (e.g. the client program
resumes before the virtual networking path to the X server is available, or

You might find using xpra or VNC to connect to an X server running on the VM,
an adequate workaround, as they allow you to disconnect and reconnect.

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)

Volunteer Cygwin/X X Server maintainer

Unsubscribe info:
Problem reports:

  reply	other threads:[~2013-02-13 15:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12  3:51 Ray Balogh
2013-02-13 15:05 ` Jon TURNEY [this message]
2013-02-13 15:37   ` Christopher Faylor
2013-02-13 17:27     ` Ryan Johnson
2013-02-13 17:51       ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).