<br><br><div class="gmail_quote">On Sun, Jun 20, 2010 at 5:34 PM, Patrick O'Callaghan <span dir="ltr"><<a href="mailto:pocallaghan@gmail.com">pocallaghan@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Sun, 2010-06-20 at 17:04 -0400, Gregory Woodbury wrote:<br>
> It's not a kernel crash, It's an X server crash/hang. It depends on an<br>
> interaction between gnoe-screensaver modules, the gnome-power manager<br>
> and<br>
> the X server. The workaround is to select a screensaver module that<br>
> doesn't<br>
> crash/hang and leave it alone.<br>
<br>
</div>I'm not using Gnome and have no processes called gnome*.<br></blockquote><div class="im">then its in the power-management functions, I would guess.<br>The workaround would be the same, find a screensaver that doesn't crash and don't randomize.<br>
<br>
> I have not exhaustively tested all the screensaver modules but have<br>
> found<br>
> two that definitely elicit the bad behaviours on my x86_64 box. (I've<br>
> not<br>
> had the problem on i686 boxes.)<br>
><br>
> "Ant Inspect" will crash the X server, showing a gdm-greeter when<br>
> waking up<br>
> the monitor.<br>
> "Apple II" will hang the X server, requiring a ssh into the box and a<br>
> manual<br>
> kill -9 of the X server to recover without a reboot.<br>
><br>
> I have filed a bugzilla report (BZ #606136) and invite y'all to add<br>
> comments thereunto.<br>
<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
The BZ number is wrong. Please revise. </blockquote><div> Not wrong - looking at it in another tab right now.<br></div><div> </div><div><a href="https://bugzilla.redhat.com/show_bug.cgi?id=606136">https://bugzilla.redhat.com/show_bug.cgi?id=606136</a> <br>
</div><br></div>