RE: Reproducing the cygwin X clipboard problems
From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Jon TURNEY Sent: Wednesday, February 25, 2009 2:52 PM I've built a version of 1.5.3-7, with this patch reverted and lots more clipboard debugging added. You can download it from [2] It would be most helpful if you could try this and see if the clipboard problems you are seeing are changed at all. [2] ftp://cygwin.com/pub/cygwinx/XWin.20090225214130.exe.bz2 Both startx and startxwin.bat (i.e. start server menu item), which formerly experienced severe clipboard problems, are now running cleanly! Thanks, Mike -- 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: Reproducing the cygwin X clipboard problems
On Wed, Feb 25, 2009 at 5:51 PM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: I've built a version of 1.5.3-7, with this patch reverted and lots more clipboard debugging added. You can download it from [2] It would be most helpful if you could try this and see if the clipboard problems you are seeing are changed at all. I'm afraid I didn't have the same experience as Mike. I've downloaded and ran your patched XWin. The result was non-deterministic: it typically starts good, but then the problem returns, and may go away and return again, depending on what I do. However, I was never able to replicate. Alas, I currently don't have time to come up with some more coherent observations. I will try it out again during the weekend and report back. --Dan -- 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: Reproducing the cygwin X clipboard problems
Jon TURNEY wrote: Thanks very much for this information on the clipboard problems. I've been able to reproduce something similar to the problems you describe, so I will spend some time trying to fix it. I've looked into this a bit and it seems to me that the patch in [1] can interact badly with other clipboard viewer applications (like clipbrd.exe, VNC viewer, and probably other clipboard helper applications and maybe VMs as well) On my PC, just running the tightvnc viewer and X server and copying something into the X clipboard sends the CPU load to 100% as we seem to be constantly converting the selection onto the windows clipboard and then clearing it. I've built a version of 1.5.3-7, with this patch reverted and lots more clipboard debugging added. You can download it from [2] It would be most helpful if you could try this and see if the clipboard problems you are seeing are changed at all. If the problems still persist, could you please run the X server with the extra parameter '-logverbose 3' and post a relevant section from the log output along with a description of the behaviour. (Note that running with this level of logging will make your log file get very big quite quickly and probably slow down the X server) [1] http://bugs.freedesktop.org/show_bug.cgi?id=5735 [2] ftp://cygwin.com/pub/cygwinx/XWin.20090225214130.exe.bz2 -- 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 problems with xemacs whole-line selection
Normally recent versions of XWin have reliable cut and paste between X and Windows. The application I run under X is xemacs. But I recently noticed that when triple-clicking a line of text in xemacs to select the whole line and put it in the clipboard, I couldn't paste it into Windows. The log file has some messages about UTF8String. Other ways of selecting the same text in xemacs set the Windows clipboard correctly. The text being pasted is just plain ASCII characters. Here is the XWin.log showing a few attempts by me to select some text by triple-clicking in xemacs and paste it into Firefox or Notepad. I also found that for a little while after I'd stopped doing anything XWin was still spewing 'XConvertSelection () failed' messages to its log once or twice a second. But it stopped eventually. Does the following log file have enough information or would you like me to do some more investigation? Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.7.0.0-12 Contact: [EMAIL PROTECTED] XWin was started with the following command line: /usr/X11R6/bin/XWin -clipboard -engine 1 -br ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1200 h 1600 winInitializeDefaultScreens - Returning winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winSetEngine - Using user's preference: 1 winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1194 height: 1547 depth: 32 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (--) Setting autorepeat to delay=250, rate=31 (--) winConfigKeyboard - Layout: 0809 (0809) (--) Using preset keyboard for English (United Kingdom) (809), type 4 Rules = xorg Model = pc105 Layout = gb Variant = (null) Options = (null) Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! winPointerWarpCursor - Discarding first warp: 597 773 winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winProcSetSelectionOwner - Clipboard not yet started, aborting. winProcSetSelectionOwner - Clipboard not yet started, aborting. winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 32, new bpp: 32 winWindowProc - WM_DISPLAYCHANGE - new width: 1200 new height: 1600 winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 32, new bpp: 32 winWindowProc - WM_DISPLAYCHANGE - new width: 1200 new height: 1600 winClipboardWindowProc - WM_DRAWCLIPBOARD - Nested calls detected. Bailing. winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for CompoundText, aborting: 1 winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for UTF8String, aborting: 1 winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for CompoundText, aborting: 1 winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for UTF8String, aborting: 1 winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for CompoundText, aborting: 1 winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for UTF8String, aborting: 1 winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for CompoundText, aborting: 1 winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for UTF8String, aborting: 1 winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for CompoundText, aborting: 1 winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for UTF8String, aborting: 1 winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for CompoundText, aborting: 1 winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for UTF8String, aborting: 1 winProcessXEventsTimeout - Call to select () failed: 0. Bailing. winClipboardFlushXEvents - SelectionNotify -
Re: Clipboard problems with xemacs whole-line selection
Ed Avis writes: Normally recent versions of XWin have reliable cut and paste between X and Windows. The application I run under X is xemacs. But I recently noticed that when triple-clicking a line of text in xemacs to select the whole line and put it in the clipboard, I couldn't paste it into Windows. The log file has some messages about UTF8String. Other ways of selecting the same text in xemacs set the Windows clipboard correctly. The text being pasted is just plain ASCII characters. I just checked and it works fine for me. Here is the XWin.log showing a few attempts by me to select some text by triple-clicking in xemacs and paste it into Firefox or Notepad. I also found that for a little while after I'd stopped doing anything XWin was still spewing 'XConvertSelection () failed' messages to its log once or twice a second. But it stopped eventually. Here is my XWin.log Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.7.0.0-12 Contact: [EMAIL PROTECTED] XWin was started with the following command line: X -ac -nodecoration -rootless -nowinkill -clipboard -fp /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X1 1R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi /,/usr/local/share/emacs/fonts/,/dev/c/WINNT/Fonts/,/usr/local/share/fonts/,/usr/X11R6/lib/X11/fonts/Ethiopic/,/usr/X11R6 /lib/X11/fonts/TTF/,/usr/X11R6/lib/X11/fonts/cyrillic/ ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winSetEngine - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel winFinishScreenInitFB - Masks: 00ff ff00 00ff (--) Setting autorepeat to delay=250, rate=31 (--) winConfigKeyboard - Layout: 0407 (0407) (--) Using preset keyboard for German (Germany) (407), type 4 Rules = xorg Model = pc105 Layout = de Variant = (null) Options = (null) winPointerWarpCursor - Discarding first warp: 512 383 winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. Ed Avis [EMAIL PROTECTED] Ciao Volker
Re: Clipboard problems
Hello. In complement to this problem, I've tried some tests : 1/ I've checked out the cvs tree and compiled a debug version. I've used it but the behaviour was the same and I didn't manage to find how to track the culpid, due to the integration into KDE-Cygwin. I think the problem is strongly related to KDE clipboard management, so I also send this mail to the KDE-cygwin mailing list. 2/ As ever, I've regulary updated my cygwin installation and retried. Until 6.7.0.0-8, there was no change (unless cursor desappearing, temporarily solved with -swcursor). But with 6.7.0.0-9, ther is some evolution : Now, the clipboard works fine as long as I stay into X11 applications, but as soon as I try to use it into Windows applications, XWin freeze, with task manager showing 100% of cpu consumption. The only solution is to kill it manually. How could I help you tracking more efficiently this problem, or even how could I solve it ? Thanks. Gilles Civario Here is the new /tmp/XWin.log Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.7.0.0-9 Contact: [EMAIL PROTECTED] XWin was started with the following command line: /usr/X11R6/bin/XWin :0 -noreset -ac -nowinkill -nodecoration -lesspointer -clipboard -swcursor ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winSetEngine - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel winFinishScreenInitFB - Masks: 00ff ff00 00ff winScreenInit - Using software cursor MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 040C (040c) (--) Using preset keyboard for French (Standard) (40c), type 81 Rules = xorg Model = pc105 Layout = fr Variant = (null) Options = (null) Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! winPointerWarpCursor - Discarding first warp: 640 498 winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. Gilles Civario wrote: Hello. I've got some problems with clipboard integration since XWin version 4.3.0-62 or 4.3.0-64 i think (not 100% sure, but it dates of late march of beginning of april, and i usually update really regularly my installations). I run kde-cygwin.3.1.4 but I don't know if this is relevant; Simply, the trouble I have occures always in this environement, as I've not observed it outside kde (but I've not much tested it). So, my problem it that I can't use Windows clipboard anymore when I've got XWin running!!! I can copy/paste inside X11 applications as normal behavior I can copy from X11 and paste to Windows applications bash-2.05b But I can copy from Windows applications neither to Windows application, nor to X11 ones. And my /tmp/XWin.log looks like : Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.7.0.0-1 Contact: [EMAIL PROTECTED] XWin was started with the following command line: /usr/X11R6/bin/XWin :0 -noreset -ac -nowinkill -nodecoration -lesspointer -clipboard ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winValidateArgs - Returning. (II) XF86Config is not supported. See http://x.cygwin.com/docs/faq/cygwin-xfree-faq.html for more information winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winScreenInit - dwWidth: 1280 dwHeight: 1024 winSetEngine - Multi Window or Rootless = ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winCreateBoundingWindowWindowed - User w: 1280 h: 1024 winCreateBoundingWindowWindowed - Current w: 1280 h: 1024 winAdjustForAutoHide - Original WorkArea: 0 0 996 1280 winAdjustForAutoHide - Adjusted
Clipboard problems
Hello. I've got some problems with clipboard integration since XWin version 4.3.0-62 or 4.3.0-64 i think (not 100% sure, but it dates of late march of beginning of april, and i usually update really regularly my installations). I run kde-cygwin.3.1.4 but I don't know if this is relevant; Simply, the trouble I have occures always in this environement, as I've not observed it outside kde (but I've not much tested it). So, my problem it that I can't use Windows clipboard anymore when I've got XWin running!!! I can copy/paste inside X11 applications as normal behavior I can copy from X11 and paste to Windows applications bash-2.05b But I can copy from Windows applications neither to Windows application, nor to X11 ones. And my /tmp/XWin.log looks like : Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.7.0.0-1 Contact: [EMAIL PROTECTED] XWin was started with the following command line: /usr/X11R6/bin/XWin :0 -noreset -ac -nowinkill -nodecoration -lesspointer -clipboard ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winValidateArgs - Returning. (II) XF86Config is not supported. See http://x.cygwin.com/docs/faq/cygwin-xfree-faq.html for more information winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winScreenInit - dwWidth: 1280 dwHeight: 1024 winSetEngine - Multi Window or Rootless = ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winCreateBoundingWindowWindowed - User w: 1280 h: 1024 winCreateBoundingWindowWindowed - Current w: 1280 h: 1024 winAdjustForAutoHide - Original WorkArea: 0 0 996 1280 winAdjustForAutoHide - Adjusted WorkArea: 0 0 996 1280 winCreateBoundingWindowWindowed - WindowClient w 1280 h 996 r 1280 l 0 b 996 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 996 depth: 32 winAllocateFBShadowGDI - Dibsection width: 1280 height: 996 depth: 32 size image: 5099520 winAllocateFBShadowGDI - Created shadow stride: 1280 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winRandRInit () winCreateDefColormap - Deferring to fbCreateDefColormap () winFinishScreenInitFB - returning winScreenInit - returning InitOutput - Returning. MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 040C (040c) (--) Using preset keyboard for French (Standard) (40c), type 81 Rules = xorg Model = pc105 Layout = fr Variant = (null) Options = (null) Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! winPointerWarpCursor - Discarding first warp: 640 498 winBlockHandler - Releasing pmServerStarted winBlockHandler - pthread_mutex_unlock () returned winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winClipboardWindowProc - WM_DRAWCLIPBOARD - Initializing - Returning. winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) [12000 more idetical lines
Clipboard problems on 4.3.0-47
Thanks, Takuma, the Z-order bug seems to be fixed now. Unfortunately, I am now suddenly having problems with the clipboard integration which I have not had problems with in ages. The bottom of my XWin.log contains the following: winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the di splay. winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the disp lay. winClipboardProc - XOpenDisplay () returned and successfully opened the display. winClipboardWindowProc - WM_DRAWCLIPBOARD - Initializing - Returning. winProcSetSelectionOwner - Clipboard not yet started, aborting. winProcSetSelectionOwner - Clipboard not yet started, aborting. Any thoughts, Harold? - Andy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Takuma Murakami Sent: Tuesday, February 24, 2004 2:27 AM To: [EMAIL PROTECTED] Subject: A windowing bug on manimize/restore I notice a bug on the new windowing code, which resides in release-45 or newer versions of Cygwin/X. To reproduce: 1) Invoke XWin.exe in -multiwindow mode. 2) Open 2 windows (A and B) and make them overlapped. 3) Minimize window A. 4) Minimize window B. 5) Restore window B. Then you will see that the contents of window A are drawn in window B in the overlapped area. I suspect the bug with MSVDM reported by Andrew Braverman may be the same symptom. As a workaround, you can get back the correct Z order by restoring window A (in the above example). I will work to fix the problem as soon as possible. Takuma Murakami
Xwin ... -clipboard problems
I am able to copy between X11 and WinXp when i start xwinclip or Xwin with the clipboard option. Here's the problem I can no longer highlight text in X11 for deletion. Once I highlight the text it is copied to the clipboard and the highlight disappears. How do I resolve this? I'm connecting to an HP-UX machine (11.x).
Re: Xwin ... -clipboard problems
On Thu, Jan 15, 2004 at 03:03:39PM -, Haisam K. Ido wrote: I am able to copy between X11 and WinXp when i start xwinclip or Xwin with the clipboard option. Here's the problem I can no longer highlight text in X11 for deletion. Once I highlight the text it is copied to the clipboard and the highlight disappears. How do I resolve this? That shouldn't happen any more with the latest -40 version, it's fixed on my system anyway. -- Chris Green ([EMAIL PROTECTED])
