Really still clipboard deadlock with 4.3.0-50

[Harold L Hunt II]

Ed,

Okay, I have another idea about how to fix this, or at least how to work 
around it.  The following information helps:

 > winProcSetSelectionOwner - OpenClipboard () failed: 00000000
 > winProcSetSelectionOwner - OpenClipboard () failed: 00000000
 > winProcSetSelectionOwner - OpenClipboard () failed: 00000000

It seems that whatever X11 application that we are requesting text from 
is not fulfilling that request, which means that we never write to the 
clipboard like we are supposed to (which causes the other Win32 
application to close the clipboard).

I'll try to come up with a way to detect when this is happening and just 
write some bogus text to the clipboard to fulfill our obligation.

Of course, I reserve the right to change my mind later when I have had 
more time to think about this.  :)

Harold