Thank you, Milan. It's a directly installed account. gnome-keyring-daemon was present, but restarting did cure it. I've had other problems with Evolution and gnome-keyring-daemon, though, usually cured by killing and restarting the relevant processes. So perhaps it's related to those. Annoying, but so far not a deal-breaker! Merphik On Tue, 2022-01-11 at 14:45 +0100, Milan Crha via evolution-list wrote: > On Tue, 2022-01-11 at 08:38 -0500, Merphik via evolution-list wrote: > > Error message is "Failed to connect account “[account name]”: > > Thereported error was “Failed to authenticate: The name :1.22 was > > notprovided by any .service files”." > > Hi,the error means that a DBus service named ":1.22" > disappeared and theDBus does not know how to restart it. By any > chance, is your accountconfigured in the GNOME Online Accounts or any > similar service, aka outof the Evolution itself? The error sometimes > shows up when thegoa-daemon process vanishes. Similarly when gnome- > keyring-daemonvanishes, which can influence also accounts configured > directly in theEvolution. > Usually a machine restart helps to start the services in a > properorder. Bye, Milan > _______________________________________________evolution-list mailing > listevolution-l...@gnome.org > To change your list options or unsubscribe, visit ... > https://mail.gnome.org/mailman/listinfo/evolution-list
_______________________________________________ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
