<p>That sounds more like an input systems failure that took down evolution. Funky chipset sends spurious signal through dbus that isn't trapped and discarded properly.</p>
<p>On Aug 28, 2010 9:52 AM, "Richard Faulkner" <<a href="mailto:rfaulkner@34thprs.org">rfaulkner@34thprs.org</a>> wrote:<br type="attribution">> In an earlier posting I sought suggestions for a replacement for<br>
> Evolution 2.28.3 but have yet to explore those and make any changes.<br>> With that said I'm still running into periodic crashes of Evolution with<br>> the last one moments ago. The symptoms have me curious and I wanted to<br>
> see if anyone had some input as to what happened...<br>> <br>> I am running Fedora 12 (2.6.32.19-163.fc12.i686) on Asus A8N w/AMD X2<br>> (Manchester)/2GB and XFX 6800GS GPU's.<br>> <br>> I was doing a reply-all and editing the "Cc:" addresses when the crash<br>
> happened. Evolution goes "dark" and I loose all mouse input. I<br>> couldn't click on a single thing and get a response anywhere on the<br>> desktop. Noting that Eyes 2.28.0 was still running I knew the system<br>
> was still running but I had lost the mouse as well as Evolution.<br>> Keyboard input was still good so I did a force quit to Evolution and all<br>> was well.<br>> <br>> My question to those who are most learned in such things...why did a<br>
> crash in Evolution trash all mouse input to the system outside of<br>> Evolution? Could this have been a failure in the mouse input or a<br>> combined failure in Evolution and mouse? Inquiring minds want to<br>
> know...<br>> <br>> Rich in Lilburn<br></p>