DMARC-Filter:	OpenDMARC Filter v1.4.2 delorie.com 57CN14Ms1768700
Authentication-Results:	delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results:	delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter:	OpenDKIM Filter v2.11.0 delorie.com 57CN14Ms1768700
Authentication-Results:	delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=bjX2vuEV
X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 660633858C2C
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1755039662;
	bh=TL4qHErw5cZ0xDD6+rBtwd6Cq2iEMtYYF4BgJsw1+OM=;
	h=Date:Subject:To:List-Id:List-Unsubscribe:List-Archive:List-Post:
	List-Help:List-Subscribe:From:Reply-To:From;
	b=bjX2vuEVRwOJDUW5SvPzh3lYxXPSiU7trdai11woAJsuV9seD7OsM8qMilJOfwpZ+
	Bm6T/uJiUYdC+CGGoCdPu34f3T6C4BqLIU2Y0eGUKzAlBUmFwe7SXyHcQbZH9PbR2a
	rR5h5Z8iOLhYezOdn3SiT1hifCStzErm+0Rh1RKg=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org 0C5EC3858D37
ARC-Filter:	OpenARC Filter v1.0.0 sourceware.org 0C5EC3858D37
ARC-Seal:	i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1755039638; cv=none;
	b=k+4yOXqRjaZDZt2ROi3QO3z+pfguEyipAq75hBmtE2sS6R8Jv7xhgrx7qoDM548SegZOipFvSZqgsUfNy6mlzM3iXYqW4MAM2N7/UtS1cQ4tkqr3E6hhONDvjg/xIrCLoj5JeeDkrUGJq5N6HqtlrDMtpPc0WeSAYQHsmSvitkw=
ARC-Message-Signature:	i=1; a=rsa-sha256; d=sourceware.org; s=key;
	t=1755039638; c=relaxed/simple;
	bh=gQT32ykxCY5cLVQm0wY+JsPuEv3bE4yk4Vorb6nTYq8=;
	h=DKIM-Signature:Message-ID:Date:MIME-Version:From:Subject:To;
	b=TfsYHBwMXWs4I3p8nB+u3OJ0bWOpzfwc/TIIDVeJ9QAbUVO3Ha43qhBxLQy8hodgcxorhAfnFemyG1CMlT+TkEg3plLo+CnX8kIvi06yJzSIFA0tFbAWylXR1ba0WZa4PTNVOEPCDLDLZMeTOKFolCAdySJgYxssYRSK3BNprbI=
ARC-Authentication-Results:	i=1; server2.sourceware.org
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 0C5EC3858D37
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20230601; t=1755039637; x=1755644437;
	h=content-transfer-encoding:content-language:to:subject:from
	:user-agent:mime-version:date:message-id:x-gm-message-state:from:to
	:cc:subject:date:message-id:reply-to;
	bh=HYE3IiRekzOali9oMvTVQSWSyF6l1e+2rQU+Omav7Lg=;
	b=sEruTbyadOgyDVv2aj8uKqNd/HsgWJyMwau0G4os1TwP2AZubdGB7UCcyD1732vYFk
	rpP+71RwArVbRgkKgseMAxtN/7Eaxuh5EYnpUCD+7yOINvqbvY3Uu8N4L8DGND8xYQaK
	LCbGlAtbCcRmMGgrY5JGjNHfMX5K8yftmnIAr3ovMLYNPP3uUQWZdWSgkChXbMkkm7fC
	qhfQm6f60aCVGpprgKLDOClW3QYzXaymeO5a184J2JzqvvJVrR50eIr/Lo/biwb1DQfI
	XJhlEQZ39vr90u4h7mHUR0ENv2ygfrBVZ6WrpsFXszBNuWIYr7tKr17oHo6cic1B3Zki
	OTrA==
X-Gm-Message-State:	AOJu0YweWmLBSZCsUplHuF5HR5eec9hcen0yGjqnVrrQIpW0/h5DsfWN
	zvK2faWtIGVp0S5IESZZ7Ie3pId2ohnOT0CxSOMEdn8WICGJOGQ+7eJ0Ck6C8A==
X-Gm-Gg:	ASbGncufsL5U6hhCB6g8sNmjhhLwMLHsy+DfxOlPPN3FhRFeKlzvRS4U+OPbND+aqBR
	GArM9Or75PsEBOeAmi5svwd6/CHqrF6bpN9s4elsIJg68H9gxUMmszQeEEFG/sas//CboF3vySx
	OEOb/bgLuLRyP4A/WmcVokzpS4TdcYKV73CBC6KnL9M4kzoUp14TYcNDc6CpDr2xoe5y50sKf/3
	FI2TCRJyochY1lcp/3nohLQDo+9jyQQ+5bQ/fbmc7x50P5LFvkMbotbCc4Gmf4XDxfjqWr3HvZr
	5ZXIHupMHlsiT/OWV1q6bRw01nrVedqvX/KNuHd0SmlpHwyzaeRdxrRyKg1E1n5e97z0keay/CC
	861h5dmLx9Iekv9wyJVzQKrTTx5PsCLn3EQjg3JLKPugj38fGihTgHDKzHRBNqJ/uPEnM6e4RDo
	y5glLy6WyF1DuJXw==
X-Google-Smtp-Source:	AGHT+IGhy9VsThqrhqmXtlqp9LzpFbOHnvsWZfClnFPfteSv5wKrSuK/iIfQzaQIiJ6ClynJ7NC52g==
X-Received:	by 2002:a05:6214:21a8:b0:707:72aa:fa17 with SMTP id
	6a1803df08f44-709e8829a62mr11555696d6.11.1755039634588;
	Tue, 12 Aug 2025 16:00:34 -0700 (PDT)
Message-ID:	<b51fb2c5-50a4-4de2-af36-8d32570806ff@gmail.com>
Date:	Tue, 12 Aug 2025 19:00:34 -0400
MIME-Version:	1.0
User-Agent:	Mozilla Thunderbird
Subject:	gpg: can't connect to the gpg-agent: IPC connect call failed
To:	Cygin Mailing List <cygwin AT cygwin DOT com>
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.30
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Frank Eskesen via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Frank Eskesen <fn DOT eskesen AT gmail DOT com>
Sender:	"Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 57CN14Ms1768700

Hi Cygwin,

I have a problem. I'm running Windows 10 Cygwin and hadn't updated 
Cygwin since July 16. I updated Windows 10 on 8/7 installing KB5064838 
(.NET 8.9.19 Update for x64 Client.) I have two Windows 11 machines, and 
a virtual Windows 10 machine last updated 7/15.

None of the other machines have this problem. All machines copy the 
~/.gnupg file. They also each have a copy of an encrypted password file. 
One of the Windows 11 machines is new. I've been building it and am now 
configuring it.

The new Windows 11 machine had a problem I was able to fix. I caused 
this problem by using gpg before copying the .gnupg directory, so the 
directory was created with a common.conf file containing "use-keyboxd". 
When copying the .gnupg directory I kept existing files, so that 
configuration directive caused gpg  to ignore secret keys. Removing that 
file fixed the problem on that machine.

Then I went back to the Windows 10 machine updated with KB5064838. Now, 
with no significant changes other than KB5064838, gpg fails as follows:
(This runs inside a script)
```
+ gpg -vv --output home --decrypt home.gpg
gpg: enabled compatibility flags:
# off=0 ctb=85 tag=1 hlen=3 plen=268
:pubkey enc packet: version 3, algo 1, keyid 05916FDA5225F00E
         data: [2047 bits]
gpg: public key is 05916FDA5225F00E
# off=271 ctb=d4 tag=20 hlen=2 plen=0 partial new-ctb
:aead encrypted packet: cipher=9 aead=2 cb=16
         length: unknown
gpg: using subkey 05916FDA5225F00E instead of primary key 0D4A2C912C5594AD
gpg: encrypted with rsa2048 key, ID 05916FDA5225F00E, created 2025-04-11
       "***** ******* <*********@gmail.com>"
gpg: using pgp trust model
gpg: key 568B3948A0D16ADB: accepted as trusted key
gpg: key 0D4A2C912C5594AD: accepted as trusted key
gpg: no running gpg-agent - starting '/usr/bin/gpg-agent'
gpg: waiting for the agent to come up ... (8s)
gpg: waiting for the agent to come up ... (7s)
gpg: waiting for the agent to come up ... (6s)
gpg: waiting for the agent to come up ... (5s)
gpg: waiting for the agent to come up ... (4s)
gpg: waiting for the agent to come up ... (3s)
gpg: waiting for the agent to come up ... (2s)
gpg: waiting for the agent to come up ... (1s)
gpg: can't connect to the gpg-agent: IPC connect call failed
gpg: no running gpg-agent - starting '/usr/bin/gpg-agent'
gpg: waiting for the agent to come up ... (8s)
: (Repeated)
gpg: keydb_search failed: No agent running
gpg: public key decryption failed: No secret key
gpg: decryption failed: No secret key
+ rc=2
+ [[ 2 != 0 ]]
+ rm home
+ echo 'ERROR: Decryption failure 2.'
ERROR: Decryption failure 2.
+ echo 'No file changed.'
No file changed.
+ exit 1
```
The agent actually starts and gpg-agent.exe shows up in process list 
(three times.) After the script ends gpg-agent.exe (apparently times out 
and) terminates.

I have since fully updated Cygwin and Windows 10 (applying today's 
update) but the problem still recurs. I'm not going to update the 
virtual Windows 10 machine.

I tried uninstall the update, but the recovery environment didn't think 
I had Administrator privileges (probably because I only log in with a 
local account) and system restore could only get me back as far as 
August 9th.

My working theory is that KB5064838 causes this problem. I don't know 
enough about IPC or Cygwin internals to have confidence in the theory, 
though.

Thanks,
F. Eskesen

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -