public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: "cygwin at sipxx.com" <cygwin@sipxx.com>
To: cygwin-xfree@cygwin.com
Subject: Re: XWin.exe: _XSERVTransSocketUNIXAccept: accept() failed
Date: Fri, 17 Feb 2012 04:14:00 -0000 [thread overview]
Message-ID: <4F3DD449.6070604@sipxx.com> (raw)
In-Reply-To: <B0F186A62859414E85548AC90F735EE006A9C8D0C7@xch-ksc-04.boeing.ksc.nasa.gov>
Just a brief comment:
I have observed the same problem after an update within the last week or
so, but the previously running version was several months old, so I
don't know which release caused this originally.
In my case, the X server simply dies after perhaps a minute. I was able
to start the server manually though without the problem, bypassing all
startup scripts and the 'run' utility, but haven't had time to
investigate further.
Bonggren, Jeffrey L wrote:
> Hello,
>
> I have recently noticed that XWin.exe is spinning and maxing out a CPU core. I checked the log and saw that it is spamming it with "_XSERVTransSocketUNIXAccept: accept() failed" messages at a rate of about one per millisecond. This is generating a very large log file!
>
> X seems to be behaving normally in spite of this. I typically run only xterm and nedit (many instances) locally.
>
> I have verified that the Windows firewall has a blanket allow rule for XWin.exe.
>
> I can't place the exact update that caused this problem, but I believe it was not having this issue in December 2011. I am never more than a week behind on updating cygwin. I tried falling back to the previous 1.11.4-2 version of xorg-server, but it failed to start. Perhaps a version conflict with some of the other updated packages?
>
> I am attaching my cygcheck (redacted), startxwin.bat and XWin.0.log (truncated!) files.
>
> Thank you,
>
> Jeff
>
>
> ------------------------------------------------------------------------
>
> --
> 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/
--
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/
next prev parent reply other threads:[~2012-02-17 4:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 16:39 Bonggren, Jeffrey L
2012-02-17 4:14 ` cygwin at sipxx.com [this message]
2012-02-17 18:56 ` Jon TURNEY
2012-02-18 16:10 ` Jon TURNEY
2012-02-21 13:38 Kiehl, Horst
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F3DD449.6070604@sipxx.com \
--to=cygwin@sipxx.com \
--cc=cygwin-xfree@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).