After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 784514 - gnome-keyring-daemon not correctly launched on user login ?
gnome-keyring-daemon not correctly launched on user login ?
Status: RESOLVED OBSOLETE
Product: gnome-keyring
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-07-04 12:54 UTC by Coeur Noir
Modified: 2021-06-18 18:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Coeur Noir 2017-07-04 12:54:05 UTC
Hi,

not sure if it's the right place…

Seems like gnome-keyring-daemon is no longer correctly launched with user login :

https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825

https://askubuntu.com/questions/898694/gnome-keyring-daemon-not-starting-up-properly

https://forum.ubuntu-fr.org/viewtopic.php?id=2011625

As you may see it happens for many people on different systems :

ubuntu 16.04, manjaro

and has side-effects on many app's chromium/chrome, evolution, gnome-terminal, gnome-screenshot, deja-dup/duplicity…
Comment 1 Coeur Noir 2017-07-09 14:52:19 UTC
To illustrate some side effects :

coeurnoir@Asgard:~$ deja-dup --backup

** (deja-dup:2774): WARNING **: AssistantOperation.vala:732: Erreur lors de l'appel de StartServiceByName pour org.freedesktop.secrets : GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.secrets': timed out

coeurnoir@Asgard:~$ chromium-browser
Using PPAPI flash.
 --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so --ppapi-flash-version=
Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[2522:2557:0709/160712.624017:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-112809610336884273312
[1:14:0709/160714.099842:ERROR:adm_helpers.cc(62)] Failed to query stereo recording.
[2522:2568:0709/160715.080299:ERROR:gcm_store_impl.cc(929)] Failed to restore security token.
[2522:2522:0709/161045.983720:ERROR:data_type_manager_impl.cc(36)] Bookmarks cryptographer error was encountered: 
[2522:2522:0709/161045.983734:ERROR:data_type_manager_impl.cc(36)] Preferences cryptographer error was encountered: 
[2522:2522:0709/161045.983737:ERROR:data_type_manager_impl.cc(36)] Passwords cryptographer error was encountered: 
[2522:2522:0709/161045.983756:ERROR:data_type_manager_impl.cc(36)] Autofill Profiles cryptographer error was encountered: 
[2522:2522:0709/161045.983774:ERROR:data_type_manager_impl.cc(36)] Autofill cryptographer error was encountered: 
[2522:2522:0709/161045.983777:ERROR:data_type_manager_impl.cc(36)] Autofill Wallet Metadata cryptographer error was encountered: 
[2522:2522:0709/161045.983779:ERROR:data_type_manager_impl.cc(36)] Themes cryptographer error was encountered: 
[2522:2522:0709/161045.983781:ERROR:data_type_manager_impl.cc(36)] Typed URLs cryptographer error was encountered: 
[2522:2522:0709/161045.983784:ERROR:data_type_manager_impl.cc(36)] Extensions cryptographer error was encountered: 
[2522:2522:0709/161045.983786:ERROR:data_type_manager_impl.cc(36)] Search Engines cryptographer error was encountered: 
[2522:2522:0709/161045.983788:ERROR:data_type_manager_impl.cc(36)] Sessions cryptographer error was encountered: 
[2522:2522:0709/161045.983791:ERROR:data_type_manager_impl.cc(36)] Apps cryptographer error was encountered: 
[2522:2522:0709/161045.983793:ERROR:data_type_manager_impl.cc(36)] App settings cryptographer error was encountered: 
[2522:2522:0709/161045.983806:ERROR:data_type_manager_impl.cc(36)] Extension settings cryptographer error was encountered: 
[2522:2522:0709/161045.983809:ERROR:data_type_manager_impl.cc(36)] Dictionary cryptographer error was encountered: 
[2522:2522:0709/161045.983812:ERROR:data_type_manager_impl.cc(36)] Favicon Images cryptographer error was encountered: 
[2522:2522:0709/161045.983815:ERROR:data_type_manager_impl.cc(36)] Favicon Tracking cryptographer error was encountered: 
[2522:2562:0709/161046.299893:ERROR:mcs_client.cc(705)] Failed to log in to GCM, resetting connection.
coeurnoir@Asgard:~$
Comment 2 Coeur Noir 2017-07-15 17:47:43 UTC
Seems to be solved through :

sudo apt-get remove --purge dbus-user-session

as read here :

https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/comments/62
Comment 3 Stephen M 2018-03-09 16:43:40 UTC
Problem occurs even if dbus-user-session was never installed.

Also, if dbus-user-session hangs Gnome Keyring, doesn't that mean there is something wrong with Gnome Keyring.  Software as important and relied on as heavily as Gnome Keyring needs to be robust enough to not cause problems for other software because of one or two bad actors.

I've had problems off and on over the years with Gnome Keyring, to the point it is getting a negative reputation.
Comment 4 André Klapper 2021-06-18 10:41:24 UTC
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.