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 error - trace owner?
Date: Mon, 03 Nov 2014 11:28:00 -0000	[thread overview]
Message-ID: <545766CE.7040803@dronecode.org.uk> (raw)
In-Reply-To: <CA+2x6-+gT_D8gYdp9rkxYWXRK4bCfrGrsEWwbFOfO68E7sGwsA@mail.gmail.com>

On 31/10/2014 16:20, Nem W Schlecht wrote:
> After a *very* long time of the clipboard working perfectly, it just
> started to stop working on me:
>
> [252960.192] winClipboardFlushXEvents - OpenClipboard () failed:
> 00000005 Owner 0002089e
> [252960.192] winClipboardFlushXEvents - OpenClipboard () failed:
> 00000005 Owner 0002089e
> [253010.517] winWindowProc - WM_DISPLAYCHANGE - new width: 1600 new
> height: 1200 new bpp: 32
> [253380.957] winClipboardFlushXEvents - OpenClipboard () failed:
> 00000005 Owner 0002089e
> [253445.199] winClipboardFlushXEvents - OpenClipboard () failed:
> 00000005 Owner 0002089e
>
> How do I trace the owner HEX code to the program that is causing the
> issue? (Or is the owner X11 here?)

This is a window handle (HWND).  You could find out the corresponding 
window using a tool such as Spy++.

I will improve this so that the window title is reported here as well, 
which would be much better, but that is not quite straightforward.

-- 
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/


      reply	other threads:[~2014-11-03 11:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31 16:20 Nem W Schlecht
2014-11-03 11:28 ` Jon TURNEY [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=545766CE.7040803@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: 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).