public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Unable to open the clipboard
Date: Tue, 4 Jan 2022 03:23:56 +0100	[thread overview]
Message-ID: <0e94e79a-d827-e67f-6e3f-c866c1b84c77@gmail.com> (raw)
In-Reply-To: <804ad578-4cbb-c4b4-f0ae-1717fb4b4af9@maxrnd.com>

On 04.01.2022 01:25, Mark Geisert wrote:
> Hi Marco,
> 
> 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
>>
>> $ putclip < Announce_geos
>>
>>
>> Usually never happend two time in the row and it is a relative
>> rare event. But I never had such issue in the past.
>>
>> It is not caused by computer load, probably arised in
>> the 3.3.x times but I could be wrong.
> 
> I'm assuming 64-bit Cygwin.  What is your cygutils version please?
> 
> ..mark
> 

Hi Mark,
I see in both versions 32 and 64

Windows 10 version 21H1 build 19043.1415

$ cygcheck -c cygutils
Cygwin Package Information
Package              Version        Status
cygutils             1.4.16-7       OK

Regards
Marco

  reply	other threads:[~2022-01-04  2:24 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
2022-01-04  0:25 ` Mark Geisert
2022-01-04  2:23   ` Marco Atzeri [this message]
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=0e94e79a-d827-e67f-6e3f-c866c1b84c77@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).