Re: Clipboard interaction issues - breaks after awhile

[Nem W Schlecht <nem@emptec.com>]

Thanks so much for getting back to me, Jon.

"nxterm" is "Nem's Xterm" - I've just recompiled xterm with some minor
configuration differences.

I backed out to 1.15.1-4 and rebooted and since then I have *not* had
the issue, so I'm wondering if the reboot is needed for some reason.
I'll be upgrading to 1.16.0-2 today and will reboot and test.

Like you mention, I assume its one of my *Windows* apps that is really
the cause of the issue.  Not sure which one, though, if that's the
case.  If it comes back up again, I'll shoot out another note to the
list.


On Fri, Sep 19, 2014 at 8:46 AM, Jon TURNEY <jon.turney@dronecode.org.uk> wrote:
> 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



-- 
Nem W Schlecht

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