From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: Jim Reisert AD1C <jjreisert@alum.mit.edu>
Subject: Re: retry: Problem transfering X11 cut/copy buffer to windows and back
Date: Wed, 11 Sep 2019 17:11:00 -0000 [thread overview]
Message-ID: <d2b98ef1-199d-6999-4696-12fb8cc00732@dronecode.org.uk> (raw)
In-Reply-To: <CAK-n8j5qs15fS-cG3PrcN-ow_Yoykx9y+_8RnaUoQ9HNAQM87A@mail.gmail.com>
On 11/09/2019 00:17, Jim Reisert AD1C wrote:
> I didn't see this message before I posted a separate message. Here is
> my report again.
>
> I am using the latest test X server (1.20.5-3 built 2019-09-06),
> HOWEVER, I have seen this problem again and again for months now.
>
> After I copy/paste enough, either from Xterm to Xterm, or Xterm to
> Windows, eventually it stops working. I can still select text in the
> Xterm, but I'm unable to paste it into windows - nothing happens. My
> fuzzy recollection is that copy/paste from X to X still works, but I
> forgot to test that today.
>
> The only way I have found to fix this is to exit the X server and
> restart it. Simply creating a new Xterm does not fix the problem.
>
> 1. Is there any information I can provide to help debug this problem?
A reliable way of reproducing the problem would be ideal :)
Failing that, the /var/log/xwin/XWin.0.log might be informative.
> 2. Is there a way to reset the X server's (or maybe Windows')
> copy/paste buffer without having to close all my X windows and restart
> the server?
Not really.
You can start the X server with the '-noclipboard' option, and then run
'xwinclip' for clipboard integration (which since it is a separate
process, rather than a thread in the X server, can be killed and restarted).
Ideally you'd then attach gdb to xwinclip if/when it gets stuck to debug
why that's happening. :)
--
Jon Turney
Volunteer Cygwin/X X Server maintainer
--
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
next prev parent reply other threads:[~2019-09-11 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 3:25 L A Walsh
2019-09-07 17:27 ` Jon Turney
2019-09-11 0:03 ` Jim Reisert AD1C
2019-09-11 17:11 ` Jon Turney [this message]
2019-09-11 22:54 ` Jim Reisert AD1C
2019-09-12 3:59 ` bzs
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=d2b98ef1-199d-6999-4696-12fb8cc00732@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=jjreisert@alum.mit.edu \
/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).