<div class="gmail_quote">On Mon, Jun 2, 2008 at 11:37 AM, David L <<a href="mailto:idht4n@gmail.com">idht4n@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I just had a new record of 3 bugs biting me within 30 seconds. evolution crashed as I was typing an address into the CC field. I restarted evolution and it asked if I wanted to recover a lost message. When I clicked recover, X windows crashed and dropped me to the console. The console was sluggish because a process named console-kit was sucking 99.9% of the CPU.</blockquote><div> Same exact thing happened to me again. Evolution crashes. Restarting evolution causes a window with "recover" & "ignore" options. Clicking on "ignore" crashed X, which didn't restart... it dropped to a console login. console-kit used all of the CPU until I killed it. starting X from the console caused KDE to start instead of gnome that is my default (as set from the GUI login screen) desktop. KDE took several minutes to get to a point where I could interact with it in any way. I count 5 bugs in rapid succession: 1) evolution crashed (bugzilla 450017) 2) X crashed (bugzilla 449460)<a href="https://bugzilla.redhat.com/show_bug.cgi?id=449460"> </a>3) X didn't restart 4) console-kit sucked CPU 5) KDE started instead of gnome It happened another time when I clicked on a GTK button in a different application. It gets hard to report a bug when the procedure to reproduce it involves causing 2-4 other bugs first! Arg. I'm back in f8 for a while. :( </div></div>