Evolution lockup

[Steve]

---- Jonathan Underwood <jonathan.underwood at gmail.com> wrote: 
> 2008/6/2 Steve <zephod at cfl.rr.com>:
> > Every time I try to compose a new message in Evolution, it locks up. I have to force quit to kill it and then restart it. Whenever this happens I get the following message in /var/log/messages:
> >
> > gnome-keyring-daemon[2851]: couldn't write 139 bytes to client : Broken pipe
> > gnome-keyring-daemon[2851]: couldn't read 4 bytes from client
> >
> > Anyone else having this problem?
> >
> > # rpm -qa | grep evolution
> > evolution-data-server-2.22.1-2.fc9.x86_64
> > evolution-data-server-2.22.1-2.fc9.i386
> > evolution-data-server-debuginfo-2.22.1-2.fc9.x86_64
> > evolution-data-server-devel-2.22.1-2.fc9.i386
> > evolution-data-server-doc-2.22.1-2.fc9.x86_64
> > evolution-2.22.1-2.fc9.i386
> > evolution-webcal-2.21.92-1.fc9.x86_64
> > evolution-data-server-devel-2.22.1-2.fc9.x86_64
> > evolution-webcal-debuginfo-2.21.92-1.fc9.x86_64
> > evolution-2.22.1-2.fc9.x86_64
> > evolution-spamassassin-2.22.1-2.fc9.x86_64
> > evolution-debuginfo-2.22.1-2.fc9.x86_64
> > evolution-conduits-2.22.1-2.fc9.x86_64
> > evolution-exchange-2.22.1-1.fc9.x86_64
> > evolution-bogofilter-2.22.1-2.fc9.x86_64
> >
> > # rpm -qa | grep keyring
> > gnome-python2-gnomekeyring-2.22.0-2.fc9.x86_64
> > gnome-keyring-2.22.1-1.fc9.x86_64
> > gnome-keyring-devel-2.22.1-1.fc9.x86_64
> > gnome-keyring-pam-2.22.1-1.fc9.x86_64
> > gnome-keyring-2.22.1-1.fc9.i386
> 
> Yes I see exactly the same thing with these versions (all updates
> including testing):
> rpm -qa | grep evolution
> evolution-data-server-2.22.2-1.fc9.x86_64
> evolution-webcal-2.21.92-1.fc9.x86_64
> evolution-2.22.2-1.fc9.x86_64
> evolution-exchange-2.22.2-1.fc9.x86_64
> # rpm -qa | grep keyring
> gnome-keyring-manager-2.20.0-2.fc9.x86_64
> gnome-keyring-pam-2.22.1-1.fc9.x86_64
> gnome-python2-gnomekeyring-2.22.0-2.fc9.x86_64
> gnome-keyring-2.22.1-1.fc9.x86_64
> 
> In /var/log/messages:
> Jun  4 10:14:31 localhost gnome-keyring-daemon[2910]: couldn't read 4
> bytes from client:
> 
> repeated many times.

OK, I'll file a bug assuming there isn't one already filed. This problem make Evolution unusable.

Steve