GNOME Bugzilla – Bug 771818
Can't sign in to accounts. Online accounts says that credentials have expired
Last modified: 2021-06-18 10:41:13 UTC
On some boots of my Fedora 25 Workstation my online accounts doesn't get signed in (Google and imap/smtp accounts). It says that "credentials have expired". But when I use the sign in button and then I sign in to the account nothing changes, so I can't use the accounts (for example mails). This problem persists through the whole session (or boot, I'm not sure). I have to restart (sometimes few times in the row) and it starts to work. Versions: gnome-shell-3.21.92-1.fc25.x86_64 control-center-3.20.1-1.fc25.x86_64 I'll attach the screenshot and journal.
Created attachment 336063 [details] Screenshot of control center with expired credentials
Created attachment 336064 [details] output of journal -b 0 -a
It's yet another problem with gnome-keyring not registering itself soon enough.
(In reply to Bastien Nocera from comment #3) > It's yet another problem with gnome-keyring not registering itself soon > enough. Correct. The following log entries point towards this: pschindl goa-daemon[2451]: Remote error from secret service: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.18 was not provided by any .service files pschindl goa-daemon[2451]: secret_password_lookup_sync() failed: The name :1.18 was not provided by any .service files pschindl goa-daemon[2451]: Remote error from secret service: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.18 was not provided by any .service files pschindl goa-daemon[2451]: secret_password_lookup_sync() failed: The name :1.18 was not provided by any .service files pschindl goa-daemon[2451]: Remote error from secret service: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.18 was not provided by any .service files pschindl goa-daemon[2451]: secret_password_lookup_sync() failed: The name :1.18 was not provided by any .service files
Tentatively re-assigning to gnome-keyring.
Is there a temporary workaround? Could we kill GOA and let it re-spawn? Or...?
I've been experiencing this on GNOME 3.22 on Fedora 25 (64-bit) as well. I'd also appreciate a workaround, if anyone can think of one, while we figure out how to actually fix the problem.
I have experienced this problem as well, also on Gnome 3.22 & Fedora 25. For me, it only happens whenever I log out & log back in, or when waking up from hibernation (but not when waking up from sleep).
For the problem of it happening after logging out and back in again, I solved it by, upon the X server ending, killing all of the user session daemons that might be causing the problem. Specifically, since I'm using SDDM, I edited /etc/sddm/Xstop to run the following command: killall -9 -u user dbus-daemon gnome-keyring-daemon evolution-source-registry \ evolution-calendar-factory-subprocess evolution-addressbook-factory \ evolution-addressbook-factory-subprocess at-spi2-registryd \ at-spi-bus-launcher I haven't narrowed down exactly which of the lingering processes is causing the problem.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/ Thank you for your understanding and your help.