public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Cc: danilo.turina@alcatel-lucent.com
Subject: Re: Clipboard integration does not work with XDMCP
Date: Sat, 22 Feb 2014 13:36:00 -0000 [thread overview]
Message-ID: <5308A7F3.5050900@dronecode.org.uk> (raw)
In-Reply-To: <530783F6.90209@alcatel-lucent.com>
On 21/02/2014 16:51, Danilo Turina wrote:
> Hello,
> I need to connect from my PC to a Linux machine that runs KDE and I use
> the following command:
>
> XWin -from MY_PC_IP_ADDR -terminate -query LINUX_MACHINE_IP_ADDR
>
> It works well but the clipboard integration that fails.
>
> Notice that:
> 1) XWin alone (i.e. no XDMCP, i.e. local) works nicely with my Windows
> clipboard
> 2) Xming works (almost) fine with XDMCP + clipboard (with the same Linux
> machine)
>
> I gave a look at the XWin log in two cases:
> A) XWin alone
> B) XWin + XDMCP
>
> And the only differences I've found (apart from the different command line
> arguments) is the following lines that were at the end of the log of the XDMCP
> invokation:
>
> winProcEstablishConnection - winInitClipboard returned.
> winClipboardThreadProc - DISPLAY=:0.0
> winClipboardProc - XOpenDisplay () returned and successfully opened the display.
> winClipboardIOErrorHandler!
> winClipboardProc - setjmp returned for IO Error Handler.
> winClipboardProc - trying to restart clipboard thread
> winClipboardThreadProc - DISPLAY=:0.0
> winClipboardProc - XOpenDisplay () returned and successfully opened the display.
> winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT
> message, exiting main loop.
> winClipboardProc - XDestroyWindow succeeded.
Thanks for reporting this problem, and the clear reproduction steps.
The issue here is that the XDMCP login dialog kills all other X clients
(including the clipboard integration client) for security. The clipboard
integration client is supposed to restart and reconnect as necessary, but it
seems this has been broken for a while.
I've has a go at fixing this and uploaded a snapshot at [1]. Perhaps you
could try that and see if it improves things for you?
[1] ftp://cygwin.com/pub/cygwinx/XWin.20140222-git-c14d82e878fc884d.exe.bz2
--
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/
next prev parent reply other threads:[~2014-02-22 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 16:51 Danilo Turina
2014-02-22 13:36 ` Jon TURNEY [this message]
2014-02-23 2:54 ` Claude Sylvain
2014-02-24 8:31 ` Danilo Turina
2014-02-24 8:39 ` Danilo Turina
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5308A7F3.5050900@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-xfree@cygwin.com \
--cc=danilo.turina@alcatel-lucent.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).