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: drstacey@tiscali.co.uk Subject: Re: 64-bit Clipboard troubles Date: Fri, 21 Jun 2013 12:33:00 -0000 [thread overview] Message-ID: <51C44820.4010307@dronecode.org.uk> (raw) In-Reply-To: <51B6479A.5050707@tiscali.co.uk> On 10/06/2013 22:39, David Stacey wrote: > On 10/06/13 14:30, Jon TURNEY wrote: >> On 09/06/2013 19:59, David Stacey wrote: >>> >I am trying to package keepassx for 64-bit Cygwin, and have noticed a >>> >difference between the way the clipboard functions under 32-bit and 64-bit >>> >Cygwin/X. Essentially, keepassx is an encrypted password database that >>> >copies your username and password to the clipboard. Then, you can paste >>> >these into a web site (say) to log in. >>> > >>> >When I run keepassx (both 32-bit and 64-bit builds) using the 32-bit >>> >version of XWin, keepassx copies the username and password to the >>> >clipboard, and these can be pasted into a native Windows web browser (e.g. >>> >Firefox). However, when I run keepassx (again, both 32-bit and 64-bit >>> >builds) using the 64-bit version of XWin, the procedure breaks: I instruct >>> >keepassx to copy to the clipboard, but when I paste in the web browser, no >>> >text is pasted. >> Sorry, integration between the native and X clipboards is broken in 64-bit >> XWin. >> >> Unfortunately, this is rather complex to fix and I haven't found the time to >> do so yet. > > Thank you for your reply. I've sent an RFU for keepassx along with a link to > your reply. If and when you tie the two clipboards together, keepassx should > just start working - there shouldn't be a need to rebuild it, but I'll do that > if necessary. This should be working as of xserver 1.14.1-2. Please test if you can and let me know if there are any problems. On 10/06/2013 14:30, Jon TURNEY wrote: >> I mentioned that my testcase programme doesn't quite work as I intended: >> > writing to the clipboard using Qt4 and reading it back by reading >> > /dev/clipboard fails when using both 32-bit and 64-bit XWin. I don't >> > understand why, but this is probably down to my own limited understanding >> > of the clipboard in X. > Thanks for writing this useful testcase. > > From a brief glance, the test looks well formed, so I'll also try to take a > look at why test 2 always fails, I guess this indicates some bug in the > clipboard integration. Looking again, I think maybe that the problem with test 2 is that it's necessary for Qt's main event loop to be running for pastes from the X clipboard to work. -- 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:[~2013-06-21 12:33 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-09 18:59 David Stacey 2013-06-10 13:30 ` Jon TURNEY 2013-06-10 21:39 ` David Stacey 2013-06-21 12:33 ` Jon TURNEY [this message] 2013-06-21 18:02 ` David Stacey 2013-09-22 2:39 ` Clipboard periodically breaks Matt D. 2013-09-22 3:11 ` Matt D. [not found] ` <524454A6.8030503@dronecode.org.uk> 2013-09-27 0:35 ` Matt D. 2013-10-21 14:46 ` Reinier Post 2013-10-21 22:37 ` Matt D. 2013-11-21 17:51 ` Jon TURNEY
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=51C44820.4010307@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=cygwin-xfree@cygwin.com \ --cc=drstacey@tiscali.co.uk \ /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: linkBe 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).