Logs tell us that there is indeed a cross problem with SCIM :
> Oct 24 16:06:08 phloston gnome-keyring-daemon[11908]: couldn't parse dialog response from ask tool: Le fichier de clés contient la ligne « /usr/bin/scim » qui n'est ni une paire de valeurs de clé, ni un groupe, ni un commentaire
[translated : The keyring file contains "/usr/bin/scim" which is neither a key-pair, a group or a commentary.]
After a bit of launchpad digging, it may be similar to bug #276159 as the debug output off a manual launch of gnome-keyring-manager or seahorse gives the same output on startup :
>fs@phloston:~$ seahorse
>** Message: init gpgme version 1.1.6
>/usr/bin/scim
>The messenger is now down
Logs tell us that there is indeed a cross problem with SCIM :
> Oct 24 16:06:08 phloston gnome-keyring- daemon[ 11908]: couldn't parse dialog response from ask tool: Le fichier de clés contient la ligne « /usr/bin/scim » qui n'est ni une paire de valeurs de clé, ni un groupe, ni un commentaire
[translated : The keyring file contains "/usr/bin/scim" which is neither a key-pair, a group or a commentary.]
After a bit of launchpad digging, it may be similar to bug #276159 as the debug output off a manual launch of gnome-keyring- manager or seahorse gives the same output on startup :
>fs@phloston:~$ seahorse
>** Message: init gpgme version 1.1.6
>/usr/bin/scim
>The messenger is now down