public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk> To: cygwin-xfree@cygwin.com Cc: nem@emptec.com Subject: Re: Clipboard interaction issues - breaks after awhile Date: Fri, 19 Sep 2014 13:46:00 -0000 [thread overview] Message-ID: <541C33A4.3060708@dronecode.org.uk> (raw) In-Reply-To: <CA+2x6-K4ag2umBKsfp3pP4G3e97+2FNW5y4pFUtnVGVnt3mpJA@mail.gmail.com> On 10/09/2014 18:57, Nem W Schlecht wrote: > That 'nedit' thread looks pretty old. Cut/Paste was working perfectly > for me pre-1.16.0-1. I've decided to downgrade, as I was having zero > issues with 1.15.1-4. > > I can see I'm getting winClipboardFlushXEvents errors in my XWin.0.log > file (attached). First, multiple time out events after trying > "Conversion to format 242 refused." and then later OpenClipboard () > failed: 00000005 errors. > > On Wed, Sep 10, 2014 at 12:17 PM, mathog wrote: >> On 10-Sep-2014 09:33, Nem W Schlecht wrote: >>> >>> After the latest update to xorg-server (1.16.0-1), I've been having >>> issues with clipboard interaction between my xterm windows and Windows >>> apps. Bi-directional copy/paste works initially, but at some unknown >>> point stops working. Anybody else seeing this as well? What can I do >>> to help debug this issue? Thanks for reporting this problem, and the log file. Unfortunately, I can't reproduce this problem. > winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused. > winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS I think the log timestamps indicate this occurs approximately 9 hours after the server was started. I guess that that format 242 is 'TARGETS' (The value of the atom will vary depending on circumstances. You could check with 'xlsatoms | grep 242'), in which case this means that something went wrong when asking the X client what conversion formats are supported for the selection, which is odd. I also notice an 'nxterm' process is started. Is this a wrapper for xterm, or some other terminal program? But are these errors actually correlated with your problem? About a day later we have: > winClipboardFlushXEvents - SelectionRequest - OpenClipboard () failed: 00000005 00000005 is 'access denied', which typically means that the X server can't take ownership of the clipboard, because some other Windows program isn't letting go of it. On 10/09/2014 22:23, Nem W Schlecht wrote: > Hmm.. I might have to reboot. I went back to 1.15.1-4 and everything > was fine, but now its not working again and same errors as before. :( There should be no clipboard-related changes between 1.15.1-4 and 1.16.0-1, so perhaps something else changing is the cause of this problem? -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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:[~2014-09-19 13:46 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-09-10 16:33 Nem W Schlecht 2014-09-10 17:17 ` mathog 2014-09-10 17:57 ` Nem W Schlecht 2014-09-10 18:34 ` mathog 2014-09-10 21:23 ` Nem W Schlecht 2014-09-19 13:46 ` Jon TURNEY [this message] 2014-09-19 13:53 ` Nem W Schlecht 2014-09-26 14:45 ` Jon TURNEY 2014-10-03 20:02 mathog 2014-10-07 13:14 ` Jon TURNEY 2014-10-07 16:25 ` mathog
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=541C33A4.3060708@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=cygwin-xfree@cygwin.com \ --cc=nem@emptec.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: linkBe 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).