Bug 2063508

Summary:	authentication recquired The password you use does not match
Product:	[Fedora] Fedora	Reporter:	jpbn <jjb>
Component:	geary	Assignee:	Thomas Moschny <thomas.moschny>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	36	CC:	epel-packagers-sig, michel, thomas.moschny
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-25 19:05:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description jpbn 2022-03-13 09:56:38 UTC

Description of problem:
Keyring is locked. (in Passwords and Keys, Seahorse)
try to solve error message "authentication required, the password you use to log in to your computer no longer match that of your login keyring"
The known password is not accepted.

Version-Release number of selected component (if applicable):


How reproducible:
try to Get Geary (email program) at work.
At login to the computer the password is working all right.

Steps to Reproduce:
1. 
2.
3.

Actual results:

cannot authenticate password.
Expected results:

no question of authentication
Additional info:
do not know how to solve this problem.

Comment 1 jpbn 2022-03-14 06:37:24 UTC

The Geary is the cause of the error message, no other apps do trigger the error. 
The error message opens when I insert a password for the email provider.

Comment 2 Sergio Basto 2022-03-18 01:48:00 UTC

anyway  "that of your login keyring" is not about keyrings-filesystem ,

keyrings-filesystem    is only used by 
arch-install-scripts 
archlinux-keyring  
debian-keyring  
ubu-keyring

Comment 3 jpbn 2022-03-18 06:28:16 UTC

I did send a copy of this bug report to Geary https://gitlab.gnome.org/GNOME/geary/-/issues

Comment 4 Ben Cotton 2023-04-25 16:55:18 UTC

This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Ludek Smid 2023-05-25 19:05:16 UTC

Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.