From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Unable to open the clipboard
Date: Mon, 3 Jan 2022 18:47:37 +0100 [thread overview]
Message-ID: <e64ecb1d-8f74-6e5a-e506-55bbeac010a5@gmail.com> (raw)
In-Reply-To: <9e6144ac-9a33-fa10-d634-11ceb5154346@cornell.edu>
On 03.01.2022 16:59, Ken Brown wrote:
> On 1/3/2022 9:34 AM, Marco Atzeri wrote:
>> Hi Guys,
>>
>> I noticed, from time to time, that on recent Cygwin
>>
>> $ uname -svr
>> CYGWIN_NT-10.0 3.3.3(0.341/5/3) 2021-12-03 16:35
>>
>> there seems to be a "failed race (?)" using the clipboard
>>
>> $ putclip < Announce_geos
>> Unable to open the clipboard
>
> Hi Marco,
>
> There was a clipboard bug that Takashi fixed in commit 69ed8ca20. I
> don't know if it's the same issue that you're seeing. The fix will
> appear in Cygwin 3.3.4, or you could try the latest snapshot.
>
> Ken
>
The last snapshot that includes that and another one still has the issue
$ uname -svr
CYGWIN_NT-10.0 3.4.0s(0.341/5/3) 2021-12-13 12:59
and it seems I am able to hit multiple failures in a row
very easily
$ putclip < COPYING
$ putclip < COPYING
Unable to open the clipboard
$ putclip < COPYING
Unable to open the clipboard
$ putclip < COPYING
$ putclip < COPYING
Unable to open the clipboard
$ putclip < COPYING
Unable to open the clipboard
$ putclip < COPYING
Unable to open the clipboard
$ putclip < COPYING
Unable to open the clipboard
$ putclip < COPYING
Regards
Marco
next prev parent reply other threads:[~2022-01-03 17:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 14:34 Marco Atzeri
2022-01-03 15:59 ` Ken Brown
2022-01-03 17:47 ` Marco Atzeri [this message]
2022-01-04 0:25 ` Mark Geisert
2022-01-04 2:23 ` Marco Atzeri
2022-01-04 5:12 ` Mark Geisert
2022-01-04 5:15 ` Mark Geisert
2022-01-04 18:08 ` Marco Atzeri
2022-01-06 9:29 ` Marco Atzeri
2022-01-07 3:32 ` Mark Geisert
2022-01-10 6:44 ` Mark Geisert
2022-01-10 7:02 ` Marco Atzeri
2022-01-22 8:35 ` Mark Geisert
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=e64ecb1d-8f74-6e5a-e506-55bbeac010a5@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.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).