From owner-freebsd-questions@freebsd.org Fri Sep 24 12:11:18 2021 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 36E2E66C72E for ; Fri, 24 Sep 2021 12:11:18 +0000 (UTC) (envelope-from doralitze@chaotikum.org) Received: from mail.chaotikum.net (magrathea.chaotikum.net [138.201.66.177]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4HG9qT1PLjz4lr7 for ; Fri, 24 Sep 2021 12:11:17 +0000 (UTC) (envelope-from doralitze@chaotikum.org) Received: from [IPv6:2003:e7:bf14:1600:ed36:31f3:7cef:d95a] (p200300e7bf141600ed3631f37cefd95a.dip0.t-ipconnect.de [IPv6:2003:e7:bf14:1600:ed36:31f3:7cef:d95a]) by mail.chaotikum.net (Postfix) with ESMTPSA id BC9C815402AA for ; Fri, 24 Sep 2021 14:11:02 +0200 (CEST) Subject: Re: Gnome-keyring not unlocking From: Leon Dietrich To: freebsd-questions@freebsd.org References: Message-ID: Date: Fri, 24 Sep 2021 14:11:02 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 4HG9qT1PLjz4lr7 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of doralitze@chaotikum.org designates 138.201.66.177 as permitted sender) smtp.mailfrom=doralitze@chaotikum.org X-Spamd-Result: default: False [-3.30 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:138.201.66.177]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; ARC_NA(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_NA(0.00)[chaotikum.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:138.201.0.0/16, country:DE]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-questions] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2021 12:11:18 -0000 Hi, I found a work around for this matter and like to share it in case someone else might run into this issue. > I recently switched from running i3 on Xorg to running sway (Wayland) As it turns out gnome-keyring uses pinentry-gnome to ask for a passphrase and will output no error message if it fails to do so. pinentry-gnome does not seam to work with sway at the moment and will silently fail when trying to unlock the key ring. A work around would be to either disable the passphrase of the key ring entirely using Xorg again (make sure your passwords are protected in another way like for example full disk encryption) or use a PAM enabled login manager *that does not switch dbus sessions* to have the key ring being unlocked prior to starting sway. I hope someone will consider these information's useful.