Re: Clipboard problems

[Gilles Civario <gilles dot civario at cea dot fr>]

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: cygwin-xfree@cygwin.com

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 00000007
winSetEngine - Using Shadow DirectDraw NonLocking
winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel
winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
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: "0000040C" (0000040c)
(--) 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: cygwin-xfree@cygwin.com
>
> 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 00000007
> 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: 00ff0000 0000ff00 000000ff
> winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff 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: "0000040C" (0000040c)
> (--) 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!!!! after 5 minutes running]
>
> One tail -f on the log file show that the first occurence of the Error line
> appears when i firts try to select something in a windows application with
> a Control-C. After this, the line continually apears and the log fiel 
> grows.
>
> Any idea ?
>
> Regards.
>
> Gilles.


--
 Gilles Civario - CS SI / CEA DSI
  tel: 33 (0)4 38 78 67 61
  fax: 33 (0)4 38 78 51 81
  mailto:gilles.civario@cea.fr

 Equipe Support Calcul
  mailto:equipe-support@www-ccrt.ccc.cea.fr