Leave evolution open a while; do some stuff on your computer. Come back a few (minutes, hours) later to see that at some point it got stuck sending/receiving mail.
My results for apt-cache search gnome-keyring:
libgnome-keyring-dev - Development files for GNOME keyring service
libgnome-keyring0 - GObject bindings for PKCS#11
libgnome-keyring1.0-cil - CLI library to access the GNOME Keyring daemon
libgp11-0 - GNOME keyring services library
libgp11-dev - Development files for the PKCS#11 GObject bindings
libpam-gnome-keyring - PAM module to unlock the GNOME keyring upon login
monodoc-gnome-keyring-manual - CLI library to access the GNOME Keyring daemon - manual
network-manager-gnome - network management framework (GNOME frontend)
There is no libgnome-keyring-dbg. I mentioned this because the second and third steps from the top appear to happen there.
Leave evolution open a while; do some stuff on your computer. Come back a few (minutes, hours) later to see that at some point it got stuck sending/receiving mail.
My results for apt-cache search gnome-keyring: keyring- dev - Development files for GNOME keyring service keyring1. 0-cil - CLI library to access the GNOME Keyring daemon gnome-keyring - PAM module to unlock the GNOME keyring upon login gnome-keyring- manual - CLI library to access the GNOME Keyring daemon - manual manager- gnome - network management framework (GNOME frontend)
libgnome-
libgnome-keyring0 - GObject bindings for PKCS#11
libgnome-
libgp11-0 - GNOME keyring services library
libgp11-dev - Development files for the PKCS#11 GObject bindings
libpam-
monodoc-
network-
There is no libgnome- keyring- dbg. I mentioned this because the second and third steps from the top appear to happen there.