From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: cygwin@cygwin.com
Subject: Re: Xorg server 1.7.1 spontaneously exiting with clipboard message
Date: Mon, 27 Apr 2015 16:45:00 -0000 [thread overview]
Message-ID: <CAK-n8j7xvST3nEvnRzy-vFK5ufkLdj3UXosaF+AwcXGmEGihmw@mail.gmail.com> (raw)
In-Reply-To: <CAK-n8j73Kh1zk-oc+H=D+_Wf-tGHHb4x+38qkwkzBjnkQZZ+Ag@mail.gmail.com>
Just to try to close this:
I have not seen my X server exit with a Clipboard Error in at least a
couple of weeks. I can't say what was causing the problem. My
working theory was that somehow TeamViewer (remote control software)
was causing the problem. However, I have been doing extensive remote
access the last week and have not had a single X server crash!
I did make a few changes after the crashes became more frequent:
1. I had originally some problems with ~/.startxwinrc, and had copied
the default from \etc\X11\xinit\startxwinrc in order to keep the extra
window from popping up when X server was started. I have since been
able to reduce ~/.startxwinrc to simply:
sleep infinity
For some reason, at home I additionally have to explicitly call "xrdb"
in my ~/.startxwinrc, but not at work. I do not know why, or what's
different.
2. I have been using the 2.x beta releases of the Cygwin library. In
the process, I have removed my local /etc/passwd and /etc/groups
files, letting Cygwin get the info from Windows directly.
I can't say whether either of these two actions has stopped the
crashes. But they have stopped.
--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2015-04-27 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 1:13 Jim Reisert AD1C
2015-03-10 13:11 ` Jon TURNEY
2015-03-17 16:16 ` Jim Reisert AD1C
2015-03-19 14:53 ` Jon TURNEY
2015-03-19 17:27 ` Jim Reisert AD1C
2015-04-27 16:45 ` Jim Reisert AD1C [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=CAK-n8j7xvST3nEvnRzy-vFK5ufkLdj3UXosaF+AwcXGmEGihmw@mail.gmail.com \
--to=jjreisert@alum.mit.edu \
--cc=cygwin@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).