public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Linda Walsh <cygwin@tlinx.org>
To: cygwin-xfree <cygwin-xfree@cygwin.com>
Subject: Re: X still crashing, but interesting log messages... different config vals needed?
Date: Sun, 26 Feb 2012 16:24:00 -0000 [thread overview]
Message-ID: <4F4A5CB8.2040806@tlinx.org> (raw)
In-Reply-To: <4F38508C.4060805@tlinx.org>
On Feb 12, 2012, Linda Walsh wrote:
> Jon TURNEY wrote:
>>
>>> [ 14334.463] SocketUNIXAccept: accept() failed
>>
>> This log looks normal apart from this line.
>>
>> I don't think this is a new warning, and wasn't in the previous log you
>> posted, so it's hard to see how this could be directly related to the
>> problem.
----
You mean you think it IS a new warning. Since I upgraded
the Xserver the week before that last, I haven't been able to
get *any* local 'X' programs to connect.
Oddly enough, remote programs do connect.
But I also can easily create a multi-gig /var/log file in a few hours,
as that message repeats multiple times/second.
FWIW, dbus always hangs now, (presumably it tries to connect to the X server),
when I start a local terminal session, but one started on a remote system, seems
to work, as I have it spawn in my .bashrc. Had to write some
timeout code... so haven't forgotten about it... just been swamped by other
probs...(so what else is new...)...
-l
--
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/
prev parent reply other threads:[~2012-02-26 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-11 4:20 Linda Walsh
2012-02-12 19:52 ` Jon TURNEY
2012-02-12 23:52 ` Linda Walsh
2012-02-13 22:00 ` Jon TURNEY
2012-02-26 20:56 ` Linda Walsh
2012-02-26 16:24 ` Linda Walsh [this message]
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=4F4A5CB8.2040806@tlinx.org \
--to=cygwin@tlinx.org \
--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).