public inbox for
 help / color / mirror / Atom feed
From: Jim Reisert AD1C <>
To: Jon Turney <>
Cc: The Cygwin Mailing List <>
Subject: Re: retry: Problem transfering X11 cut/copy buffer to windows and back
Date: Wed, 11 Sep 2019 22:54:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Sep 11, 2019 at 8:52 AM Jon Turney wrote:

> > 1.  Is there any information I can provide to help debug this problem?
> A reliable way of reproducing the problem would be ideal :)

I wish!

> 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. :)

The next time I'm doing an activity which is likely to hit this, I'll
see what I can get.

Jim Reisert AD1C, <>,

Problem reports:
Unsubscribe info:

  reply	other threads:[~2019-09-11 22:46 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
2019-09-11 22:54       ` Jim Reisert AD1C [this message]
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:

* 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).