Bug 183668

Does this still happen for 2.13.93?

Yes, still seeing this with 2.13.93-4. It *seems* to happen more after a resume
from suspend.

The very strange part is that it seems to be blanking roughly every 5 minutes,
yet I don't have a 5 minute timeout configured anywhere.

What about gnome-screensaver-properties?

When it blanks the screen, what does cat /var/log/messages | grep gnome-power
display?

Nothing from g-p-m. This does appear to be gnome-screensaver.

*** Bug 186314 has been marked as a duplicate of this bug. ***

ignore the MODIFIED status change, i've got too many browser tabs open

I can confirm this with 2.14.0-1. Happens with both swsusp and suspend2 code.

Do you guys reckon it is worth referencing:

http://bugzilla.gnome.org/show_bug.cgi?id=335831

Looks like a slightly different issue, but related nontheless.

This is actually upstream at:

http://bugzilla.gnome.org/show_bug.cgi?id=332576

I put an untested patch on the upstream report that I'm building into rawhide now.  

Would you guys mind testing it tomorrow after the sync?

As long as it runs on FC5 (I hope Rawhide didn't go to far yet with changes), it
should be OK.

Installed gnome-screensaver-2.14.0-4 from Rawhide on FC5. I'll be testing this
today and tomorrow.

I'll push it into updates-testing, too (for those who run FC-5 and don't want to
use the rawhide package)

Seems it was pushed into plain updates too.

Anyhow - it fixes the problem for me. Great work!

Plain updates has an older version (and its changelog doesn't show the change
either).

Yeah, seems I accidentally lied about that one... It had in deed not been fixed
in updates. Updated to updates-testing, and now it seems to work better though.

However, there's still one bug: when resuming from suspend, if the time in
suspend has been longer than the screensaver interval, the screensaver is on
when leaving suspend. Which is kind of weird - the desktop should start up
directly. Perhaps that's a different bug though.

Actually, I think that's a desired feature. I definitely want the screensaver to
kick in and lock the desktop if the machine has been suspended for more than
screensaver interval.

In other words, if you walk away from your system and are relying on screensaver
to lock it (which is admittedly only a low level, limited time protection
measure against someone with physical access to your box), it shouldn't matter
if you left the system on or suspended. It should still get locked after exactly
the same amount of time of inactivity.

Well, pressing the power button does in my book count as interacting with the
computer, and hence - a key-press event should be sent to the screensaver
turning it off.

HOWEVER: if the screen is actually locked, that same key press event should show
the unlock screen.

Am I not right?

Yeah, maybe. Then again, maybe not - if "interacting with the computer" is
defined as touching one of the input devices defined in X ;-)

The new RPM appears to be good. I had no screen locking happening while working
on the system after resume.

gnome-screensaver-2.14.0-1.fc5.1 has been pushed for fc5, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.

This bug should be closed. Not a problem any more.

Sweet, thanks.