I file an issue against gnome-control-center even if I'm not confident that the component is the right one. But if I access a resource with Nautilus, I'm also able to save the password. What happens: If I go to Settings -> Sharing -> Screen Sharing, Select Require a password radio button, start to write a password A window asking for a password appears. This windows states that "Authentication required. The password you use to log in to your computer no longer matches that of your login keyring." I don't know what password to use. If I hit cancel, and try to add a character to the Screen Sharing password, such window reappears. In the logs I can see: Sep 15 16:38:41 fedora gnome-control-c[2578]: Failed to store VNC password: Cannot create an item in a locked collection Another similar problem is. Settings -> Online Accounts -> Nextcloud Insert the server address, the username and the password, then click on Connect. Such window asking for a password appears. If you hit cancel, then the Nextcloud account was successfully created, but obviously Credentials have expired. This is the log Sep 15 16:41:33 fedora goa-daemon[1825]: secret_password_store_sync() failed: Cannot create an item in a locked collection Sep 15 16:41:35 fedora goa-daemon[1825]: secret_password_lookup_sync() returned NULL Sep 15 16:41:35 fedora goa-daemon[1825]: /org/gnome/OnlineAccounts/Accounts/account_1631716887_1: Setting AttentionNeeded to TRUE because EnsureCredentials() failed with: No credentials found in the keyring (goa-error-quark, 4) Sep 15 16:41:35 fedora gnome-calendar[2485]: source_credentials_required_cb: Failed to authenticate 'user': Failed to lookup credentials: Failed to get password from GOA: No credentials found in the keyring
mmmh Could it be related to gnome keyring? Sep 15 18:16:03 fedora gdm-password][6598]: gkr-pam: the password for the login keyring was invalid. Indeed, if using seahorse I delete the Login keyring and I create the "login" one, the aforementioned problems have gone.
mmmh it seems that the problem affects only the user created during GNOME initial setup. Indeed if I create a new user, it works normally.
I had to face this issue once while configuring google account on fedora 35 4 days back. It did not bother me after that.
Proposed as a Blocker for 35-final by Fedora user alciregi using the blocker tracking app because: Default_application_functionality: system settings "All applications that can be launched using the standard graphical mechanism after a default installation of Fedora Workstation on the x86_64 architecture must start successfully and withstand a basic functionality test."
Since this happens only with the first user created during GNOME Initial Setup, could it be related to this bug? BZ#2003778
> If I go to Settings -> Sharing -> Screen Sharing, Select Require a password radio button, start to write a password > A window asking for a password appears. This windows states that "Authentication required. The password you use to log in to your computer no longer matches that of your login keyring." I can confirm this exactly on a completely fresh installation. Providing your user password only says "password invalid". After installing Seahorse, I see the default "Login" keyring locked, and can't be unlocked, because it asks for a password and your user password doesn't unlock it. Clearly, the keyring was created with some invalid password, which doesn't match the password you selected in gnome-initial-setup. The keyring itself works (tested), just the default keyring password was created incorrectly. And it turn this "breaks" all apps which use the keyring. Reassigning to gnome-initial-setup.
Are you sure this isn't another case of bug #1997310 and bug #2003778? I think this is expected to be broken if D-Bus isn't working.
Definitely not, it's still happening with today's compose. Of course every app that uses the keyring is affected. Likely the same underlying cause as bug #2005625.
Discussed during the 2021-09-20 blocker review meeting: [0] The decision to classify this bug as an "AcceptedBlocker (Final)" was made as it violates the following criterion: "All applications that can be launched using the standard graphical mechanism after a default installation of Fedora Workstation on the x86_64 architecture must start successfully and withstand a basic functionality test." We believe this has the same cause as 2005625, but there's no harm in accepting it separately in case it doesn't. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-09-20/f35-blocker-review.2021-09-20-16.00.txt
Root cause is here: https://bugzilla.redhat.com/show_bug.cgi?id=2005625#c16
I confirmed this is the same as 2005625 in testing. *** This bug has been marked as a duplicate of bug 2005625 ***
This comment was flagged a spam, view the edit history to see the original text if required.