Re: Clipboard interaction issues - breaks after awhile

Re: Clipboard interaction issues - breaks after awhile

[mathog]

Today I ran into an interesting variant of this.

1.  putty   ssh -X session from XP to a remote Centos 6.5 system.
2.  on the remote system: xterm &
3.  copy a line of text on remote system
4.  paste it into a roundcube "compose" window on XP system.  The 
browser is
Seamonkey 2.29.

It works fine for a while and then the _browser_ locks.  It is 
definitely an X11
issue because this unlocked the browser: exit all xterms, exit the putty 
session, kill
the X11 server.  The browser didn't unlock until the last step.

This lock up happened twice within half an hour.  Now I can't reproduce 
it.

That is the only system I have used recently that uses xterm instead of 
uxterm.

The clipboard problems I have seen previously were all in the other 
direction, where clip going into an X11 application would fail.

Unfortunately I didn't save the X server log file.  Which, brings up 
another point.
The X11 server is started by clicking on "start_server.bat" which 
contains:

@echo off
set CYGXTOP=%~dp0
C:
chdir "%CYGXTOP%\bin"
start Xwin :0 -multiwindow

It always overwrites the Xwin.0.log file when it starts.  Is there some 
change we could make to this .bat script that would cause it to at least 
save one previous version?

Regards,

David Mathog
mathog@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech

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

Re: Clipboard interaction issues - breaks after awhile

[Jon TURNEY]

On 03/10/2014 21:02, mathog wrote:
> Today I ran into an interesting variant of this.
>
> 1.  putty   ssh -X session from XP to a remote Centos 6.5 system.
> 2.  on the remote system: xterm &
> 3.  copy a line of text on remote system
> 4.  paste it into a roundcube "compose" window on XP system.  The
> browser is Seamonkey 2.29.
>
> It works fine for a while and then the _browser_ locks.  It is
> definitely an X11
> issue because this unlocked the browser: exit all xterms, exit the putty
> session, kill
> the X11 server.  The browser didn't unlock until the last step.
>
> This lock up happened twice within half an hour.  Now I can't reproduce it.

There is supposed to be a 1 second timeout to ensure that we always 
respond to the Windows application in a timely fashion.

(The issue here is that Windows clipboard pastes are synchronous (when 
the Windows application calls GetClipboardData(), it sends a 
WM_RENDERFORMAT to the clipboard owner, and blocks until that returns), 
but the X11 clipboard render is asynchronous (since we send a 
XConvertSelection() request to the clipboard owner and wait for a 
SelectionNotify event))

I've looked at this code again, and can't see anything wrong with they 
way this timeout is implemented.

So, I'm afraid there's not a lot I can do without a repeatable 
reproduction or a log file.

> That is the only system I have used recently that uses xterm instead of
> uxterm.
>
> The clipboard problems I have seen previously were all in the other
> direction, where clip going into an X11 application would fail.
>
> Unfortunately I didn't save the X server log file.  Which, brings up
> another point.
> The X11 server is started by clicking on "start_server.bat" which contains:
>
> @echo off
> set CYGXTOP=%~dp0
> C:
> chdir "%CYGXTOP%\bin"
> start Xwin :0 -multiwindow
>
> It always overwrites the Xwin.0.log file when it starts.  Is there some
> change we could make to this .bat script that would cause it to at least
> save one previous version?

I guess you could add to the above something like:

move C:\cygwin\var\log\XWin.0.log C:\cygwin\var\log\XWin.0.log.old

but yes, there is actually some code in the server to do that, but it's 
not turned on in XWin for unknown reasons...

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

Re: Clipboard interaction issues - breaks after awhile

[mathog]

On 07-Oct-2014 06:14, Jon TURNEY wrote:
>> It always overwrites the Xwin.0.log file when it starts.  Is there 
>> some
>> change we could make to this .bat script that would cause it to at 
>> least
>> save one previous version?
> 
> I guess you could add to the above something like:
> 
> move C:\cygwin\var\log\XWin.0.log C:\cygwin\var\log\XWin.0.log.old
> 
> but yes, there is actually some code in the server to do that, but
> it's not turned on in XWin for unknown reasons...

Good idea.  Changed it to the following and tested. It keeps the last 
two versions.

======================after this line
@echo off
set CYGXTOP=%~dp0

C:
chdir "%CYGXTOP%\var\log\xwin"
move XWin.0.log.1 XWin.0.log.2
move XWin.0.log XWin.0.log.1
chdir "%CYGXTOP%\bin"

start Xwin :0 -multiwindow
======================before this line

Regards,

David Mathog
mathog@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech

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

Clipboard interaction issues - breaks after awhile

[Nem W Schlecht]

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?

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

Re: Clipboard interaction issues - breaks after awhile

[mathog]

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?

Look in the X11 server log file for error messages after you experience 
a
failed paste.

I see something like that inside nedit.

    http://www.cygwin.com/ml/cygwin-xfree/2013-06/msg00000.html

The crash problem in that post was resolved with a later version of the 
X11 server, but
the paste and window degradation problems are still around.

I hardly ever do a copy/paste from an X11 app to windows app or vice 
versa, so
no idea if the nedit issue is related to what you are seeing.

Regards,

David Mathog
mathog@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech

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

Re: Clipboard interaction issues - breaks after awhile

[Nem W Schlecht]

[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]

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 <mathog@caltech.edu> 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?
>
>
> Look in the X11 server log file for error messages after you experience a
> failed paste.
>
> I see something like that inside nedit.
>
>    http://www.cygwin.com/ml/cygwin-xfree/2013-06/msg00000.html
>
> The crash problem in that post was resolved with a later version of the X11
> server, but
> the paste and window degradation problems are still around.
>
> I hardly ever do a copy/paste from an X11 app to windows app or vice versa,
> so
> no idea if the nedit issue is related to what you are seeing.
>
> Regards,
>
> David Mathog
> mathog@caltech.edu
> Manager, Sequence Analysis Facility, Biology Division, Caltech
>
> --
> 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/
>



-- 
Nem W Schlecht

[-- Attachment #2: XWin.0.log --]
[-- Type: application/octet-stream, Size: 16126 bytes --]

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.16.0.0
OS: CYGWIN_NT-6.1 HOSTNAME 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64
OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (Win64)
Package: version 1.16.0-1 built 2014-08-16

XWin was started with the following command line:

X :0 -multiwindow 

ddxProcessArgument - Initializing default screens
winInitializeScreenDefaults - primary monitor w 1600 h 1200
winInitializeScreenDefaults - native DPI x 96 y 96
[305963.996] (II) xorg.conf is not supported
[305963.996] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
[305963.996] LoadPreferences: /home/username/.XWinrc not found
[305963.996] LoadPreferences: Loading /etc/X11/system.XWinrc
[305963.996] LoadPreferences: Done parsing the configuration file...
[305964.074] winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL
[305964.074] winDetectSupportedEngines - Returning, supported engines 00000015
[305964.074] winSetEngine - Multi Window or Rootless => ShadowGDI
[305964.074] winScreenInit - Using Windows display depth of 16 bits per pixel
[305964.090] winAllocateFBShadowGDI - Creating DIB with width: 1600 height: 1200 depth: 16
[305964.090] winFinishScreenInitFB - Masks: 0000f800 000007e0 0000001f
[305964.090] winInitVisualsShadowGDI - Masks 0000f800 000007e0 0000001f BPRGB 6 d 16 bpp 16
[305964.090] winInitMultiWindowWM - Calling pthread_mutex_lock ()
[305964.090] winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
[305964.090] MIT-SHM extension disabled due to lack of kernel support
[305964.090] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel
[305964.105] glWinSelectGLimplementation: Loaded 'cygnativeGLthunk.dll'
[305964.214] GL_VERSION:     1.1.0
[305964.214] GL_VENDOR:      Microsoft Corporation
[305964.214] GL_RENDERER:    GDI Generic
[305964.214] wglwrap: Can't resolve "wglGetExtensionsStringARB"
[305964.214] (EE) AIGLX: Won't use generic native renderer as it is not accelerated
[305964.370] glWinSelectGLimplementation: Loaded 'cygGL-1.dll'
[305965.041] (II) AIGLX: enabled GLX_EXT_texture_from_pixmap
[305965.041] (II) AIGLX: Loaded and initialized swrast
[305965.041] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[305965.275] winPointerWarpCursor - Discarding first warp: 800 600
[305965.275] (--) 3 mouse buttons found
[305965.291] (--) Setting autorepeat to delay=500, rate=31
[305965.291] (--) Windows keyboard layout: "00010409" (00010409) "United States-Dvorak", type 4
[305965.291] (--) Found matching XKB configuration "English (USA,Dvorak)"
[305965.291] (--) Model = "pc105" Layout = "dvorak" Variant = "none" Options = "none"
[305965.291] Rules = "base" Model = "pc105" Layout = "dvorak" Variant = "none" Options = "none"
[305965.338] winBlockHandler - pthread_mutex_unlock()
[305965.338] winInitMultiWindowWM - pthread_mutex_lock () returned.
[305965.338] winInitMultiWindowWM - pthread_mutex_unlock () returned.
[305965.338] winMultiWindowXMsgProc - pthread_mutex_lock () returned.
[305965.338] winInitMultiWindowWM - DISPLAY=:0.0
[305965.338] winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
[305965.338] winMultiWindowXMsgProc - DISPLAY=:0.0
[305965.338] winProcEstablishConnection - winInitClipboard returned.
[305965.338] winClipboardThreadProc - DISPLAY=:0.0
[305965.338] winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display.
[305965.338] winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display.
[305965.338] winClipboardProc - XOpenDisplay () returned and successfully opened the display.
[305966.570] executing 'nxterm -ls -u8', pid 13456
[305988.660] winClipboardFlushXEvents - SelectionNotify - X*TextPropertyToTextList list_return is NULL.
[340104.940] winWindowProc - WM_DISPLAYCHANGE - new width: 1280 new height: 800 new bpp: 32
[340104.940] winWindowProc - Performance may be non-optimal after change in depth
[340104.940] winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 800 depth: 16
[340104.940] winAllocateFBShadowGDI - Shadow blit failure
 The handle is invalid.
[348302.933] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348302.933] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348303.011] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348303.011] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348303.120] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348303.120] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348303.213] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348303.213] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348303.323] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348303.323] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348303.416] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348303.416] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348303.510] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348303.510] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348303.619] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348303.619] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348303.713] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348303.713] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348303.822] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348303.822] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348303.915] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348303.915] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348304.009] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348304.009] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348304.118] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348304.118] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348304.212] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348304.212] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348304.321] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348304.321] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348304.415] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348304.415] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348304.508] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348304.508] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348304.617] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348304.617] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348304.711] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348304.711] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348304.820] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348304.820] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348304.914] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348304.914] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348305.007] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348305.007] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348305.117] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348305.117] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348305.210] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348305.210] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348305.319] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348305.319] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348305.413] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348305.413] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348305.522] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348305.522] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348305.616] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348305.616] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348305.709] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348305.709] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348305.819] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348305.819] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348305.912] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348305.912] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348306.021] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348306.021] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348306.115] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348306.115] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348306.209] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348306.209] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348306.318] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348306.318] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348306.411] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348306.411] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348306.521] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348306.521] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348306.614] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348306.614] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348306.723] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348306.723] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348306.817] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348306.817] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348306.911] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348306.911] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348307.020] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348307.020] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348307.113] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348307.113] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348307.223] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348307.223] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348307.316] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348307.316] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348307.410] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348307.410] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348307.519] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348307.519] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348307.613] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348307.613] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348307.722] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348307.722] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348307.815] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348307.815] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348307.925] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348307.925] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348308.018] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348308.018] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348308.112] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348308.112] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348308.221] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348308.221] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348308.315] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348308.315] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348308.424] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348308.424] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348308.517] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348308.517] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348308.611] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348308.611] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348308.720] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348308.720] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348308.814] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348308.814] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[348308.923] winClipboardFlushXEvents - SelectionNotify - Conversion to format 242 refused.
[348308.923] winClipboardWindowProc - timed out waiting for WIN_XEVENTS_NOTIFY_TARGETS
[367770.157] winWindowProc - WM_DISPLAYCHANGE - new width: 1280 new height: 800 new bpp: 32
[367770.157] winWindowProc - Performance may be non-optimal after change in depth
[367837.035] winWindowProc - WM_DISPLAYCHANGE - new width: 1280 new height: 800 new bpp: 32
[367837.035] winWindowProc - Performance may be non-optimal after change in depth
[369986.089] winWindowProc - WM_DISPLAYCHANGE - new width: 1600 new height: 1200 new bpp: 32
[369986.089] winWindowProc - Performance may be non-optimal after change in depth
[369986.089] winAllocateFBShadowGDI - Creating DIB with width: 4100 height: 1440 depth: 16
[433623.779] winClipboardFlushXEvents - SelectionRequest - OpenClipboard () failed: 00000005
[433623.779] winClipboardFlushXEvents - SelectionRequest - OpenClipboard () failed: 00000005
[433623.795] winClipboardFlushXEvents - SelectionRequest - OpenClipboard () failed: 00000005
[434526.698] winClipboardFlushXEvents - OpenClipboard () failed: 00000005
[434528.024] winClipboardFlushXEvents - OpenClipboard () failed: 00000005

[-- Attachment #3: Type: text/plain, Size: 223 bytes --]

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

Re: Clipboard interaction issues - breaks after awhile

[mathog]

On 10-Sep-2014 10:57, Nem W Schlecht wrote:
> That 'nedit' thread looks pretty old.

Sadly, yes.  Fixing it seems to be nobody's priority.

Regards,

David Mathog
mathog@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech

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

Re: Clipboard interaction issues - breaks after awhile

[Nem W Schlecht]

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

On Wed, Sep 10, 2014 at 1:34 PM, mathog <mathog@caltech.edu> wrote:
> On 10-Sep-2014 10:57, Nem W Schlecht wrote:
>>
>> That 'nedit' thread looks pretty old.
>
>
> Sadly, yes.  Fixing it seems to be nobody's priority.
>
>
> Regards,
>
> David Mathog
> mathog@caltech.edu
> Manager, Sequence Analysis Facility, Biology Division, Caltech
>
> --
> 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/
>



-- 
Nem W Schlecht                   nem@emptec.com
Empyreal Technologies    http://www.emptec.com/
 "Perl did the magic.  I just waved the wand."

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

Re: Clipboard interaction issues - breaks after awhile

[Jon TURNEY]

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/

Re: Clipboard interaction issues - breaks after awhile

[Nem W Schlecht]

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/

Re: Clipboard interaction issues - breaks after awhile

[Jon TURNEY]

On 19/09/2014 14:53, Nem W Schlecht wrote:
> 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.

Thanks. I would appreciate any help you can give in tracking down the 
cause of this problem.

I plan to add a bit more logging in the next release which should help 
identify the Windows application which own the clipboard when 
OpenClipboard() is failing.

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