[Bug 50598] Wine Clipboard not always shared across to X11

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50598

--- Comment #5 from Pau Coma Ramirez <paucoma at gmail.com> ---
I followed through some more code and performed some more tests attempting to
trace where it is getting hanged and found the following:
X11DRV_SelectionRequest(..) OK log gets called , KO log not

X11DRV_SelectionRequest(..) is called in `dlls/winex11.drv/event.c`

https://source.winehq.org/git/wine.git/blob/HEAD:/dlls/winex11.drv/event.c#l107
107 static x11drv_event_handler handlers[MAX_EVENT_HANDLERS] =
108 {
 ...
139     X11DRV_SelectionRequest,  /* 30 SelectionRequest */

217 void X11DRV_register_event_handler( int type, x11drv_event_handler handler,
const char *name )

X11DRV_register_event_handler(..) OK log gets called , KO log not

380 static inline BOOL call_event_handler( Display *display, XEvent *event )

call_event_handler(..) OK log gets called , KO log also but never for
`event->type "SelectionRequest"` in KO log

Lets see who calls `X11DRV_register_event_handler`

https://source.winehq.org/git/wine.git/blob/HEAD:/dlls/winex11.drv/clipboard.c#l1973
1977 static void xfixes_init(void)

xfixes_init(void) OK log gets called , KO log not

xfixes_init() called by clipboard_thread( ..)

2029 static DWORD WINAPI clipboard_thread( void *arg )

clipboard_thread(..)  OK log gets called , KO log not

Clipboard_thread created in 
2157 void X11DRV_InitClipboard(void)

X11DRV_InitClipboard(void) called in X11DRV_CreateWindow(..)

https://source.winehq.org/git/wine.git/blob/HEAD:/dlls/winex11.drv/window.c#l1884
1866 BOOL CDECL X11DRV_CreateWindow( HWND hwnd )
1867 {
1868     if (hwnd == GetDesktopWindow())
1869     {
...
1884         X11DRV_InitClipboard();

I am suspecting that GetDesktopWindow may be a point of interest...
found in 
https://source.winehq.org/git/wine.git/blob/HEAD:/dlls/user32/win.c#l2063

GetDesktopWindow gets called in OK not in KO

This seems to be as far as I can go due to the lack of trace/debug messages...

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.