From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id AF860138206 for ; Wed, 17 Jan 2018 16:23:02 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8F8BEE09B7; Wed, 17 Jan 2018 16:22:54 +0000 (UTC) Received: from mail144c7.megamailservers.com (mail774.megamailservers.com [69.49.98.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2DC75E0977 for ; Wed, 17 Jan 2018 16:22:53 +0000 (UTC) X-Authenticated-User: info.sys-concept.com X-VIP: 69.49.109.100 Received: from [10.0.0.100] ([184.69.242.18]) (authenticated bits=0) by mail144c7.megamailservers.com (8.14.9/8.13.1) with ESMTP id w0HGMpLN025981 for ; Wed, 17 Jan 2018 11:22:53 -0500 Subject: Re: [gentoo-user] gpg2 - error gpg: public key decryption failed: No pinentry To: gentoo-user@lists.gentoo.org References: <7d43ed93-5c66-de97-a892-6e3cd57ddd2a@sys-concept.com> <20180117094650.723c91f6@digimed.co.uk> <080bc2bf-db23-23dd-0477-8fd54bd03542@sys-concept.com> <20180117134656.29f031ca@digimed.co.uk> <98539a20-c63b-20da-b179-bcb8eaed9a05@sys-concept.com> <20180117144827.26dfdc1a@digimed.co.uk> From: thelma@sys-concept.com Message-ID: Date: Wed, 17 Jan 2018 09:22:58 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: <20180117144827.26dfdc1a@digimed.co.uk> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-CTCH-RefID: str=0001.0A020206.5A5F785D.0205,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-CTCH-Score: 0.000 X-CTCH-Rules: X-CTCH-Flags: 0 X-CTCH-ScoreCust: 0.000 X-CSC: 0 X-CHA: v=2.2 cv=aMaAkf1m c=1 sm=1 tr=0 a=u3gW5Uk2xAGXuEgp5FffjQ==:117 a=u3gW5Uk2xAGXuEgp5FffjQ==:17 a=IkcTkHD0fZMA:10 a=046jbqsEAAAA:8 a=YPpUvZMOWTqXoDooaDIA:9 a=QEXdDO2ut3YA:10 a=bGzDz6Hpkc7_N_b525It:22 X-Archives-Salt: c3828205-8b5f-4905-a7ac-a5b0145959aa X-Archives-Hash: f7b55744c7f497f3cde97fca08cef536 On 01/17/2018 07:48 AM, Neil Bothwick wrote: > On Wed, 17 Jan 2018 07:26:28 -0700, thelma@sys-concept.com wrote: > >>> Is pinentry-qt installed and working? >> >> "eix pinentry-qt" is not showing any entry, no such program. >> > Try "which pinentry-qt", it's part of the pinentry package, controlled by > USE. which pinentry-qt /usr/bin/pinentry-qt equery b pinentry-qt * Searching for pinentry-qt ... app-crypt/pinentry-1.0.0-r2 (/usr/bin/pinentry-qt) I re-emerged pinentry but it makes no difference. It might be some glitch with the new profile. On the new system I'm using: default/linux/amd64/17.0/desktop * All my other system are using: default/linux/amd64/13.0/desktop * Joseph