Binary package hint: gnome-keyring
This is similar to bug #316070, but can get worked around:
$ eval $(gnome-keyring-daemon) bash: syntax error near unexpected token `('
$ gnome-keyring-daemon ** (process:9543): DEBUG: cleanup_session_keyring(): File name: /home/user/.gnome2/keyrings/session.keyring ** (process:9543): DEBUG: cleanup_session_keyring(): Cannot stat /home/user/.gnome2/keyrings/session.keyring, aborting GNOME_KEYRING_CONTROL=/tmp/keyring-NzuxUn SSH_AUTH_SOCK=/tmp/keyring-NzuxUn/ssh GNOME_KEYRING_PID=9544
WORKAROUND: eval $(gnome-keyring-daemon | grep -v DEBUG`)
I'm using this in ~/.kde/env/start-custom.sh and it's the second time that gkd caused KDE to start.
I'll forward this to the Gnome bugtracker.
Binary package hint: gnome-keyring
This is similar to bug #316070, but can get worked around:
$ eval $(gnome- keyring- daemon)
bash: syntax error near unexpected token `('
$ gnome-keyring- daemon session_ keyring( ): File name: /home/user/ .gnome2/ keyrings/ session. keyring session_ keyring( ): Cannot stat /home/user/ .gnome2/ keyrings/ session. keyring, aborting CONTROL= /tmp/keyring- NzuxUn SOCK=/tmp/ keyring- NzuxUn/ ssh PID=9544
** (process:9543): DEBUG: cleanup_
** (process:9543): DEBUG: cleanup_
GNOME_KEYRING_
SSH_AUTH_
GNOME_KEYRING_
WORKAROUND: keyring- daemon | grep -v DEBUG`)
eval $(gnome-
I'm using this in ~/.kde/ env/start- custom. sh and it's the second time that gkd caused KDE to start.
I'll forward this to the Gnome bugtracker.