<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.28.1">
</HEAD>
<BODY>
There seems to be a set of very irritating regressions in Karmic (well, gnome 2.28.0) regarding session idling or power management inhibition. Core software such as eog and totem seem to break it. In the case at hand, your screen will never blank, never lock, and your IM will never be set to away (and never autosuspend either). There may be other broken software in different ways (Transmission? Browsers? Haven't tested).<BR>
<BR>
I filed a bug report in launchpad, <A HREF="https://bugs.launchpad.net/eog/+bug/448438">https://bugs.launchpad.net/eog/+bug/448438</A> with 3 companions bug reports upstream in totem, eog and gnome-screensaver. Upstream eog and gnome-screensaver have not yet replied.<BR>
<BR>
I consider these regressions to be particularly bad from the desktop/laptop user point of view. I feel a bit hopeless as I am not one to code patches for such things, and I don't know if there's anything else I should do other than wait and hope for a miraculous fix (since we are what, 2 days from release now?).<BR>
<BR>
And to be honest, I'm a bit baffled that core gnome apps can let "crap" like this slip through... I mean, there was roughly a whole year of transitional period to get this right, since the "gnome-power-manager inhibition is transferred to gnome-session" switch was announced a long time ago, and gnome-power-manager proxied the behavior for the 2.26 series and (as planned) deprecated that API in 2.28 (so apps must only interface with gnome-session... or gnome-screensaver, it seems). <BR>
<BR>
Proper session management is critical in<BR>
- The computer's power management routines to work properly<BR>
- The "presence" to work properly for instant messaging (and a ton of other stuff)<BR>
<BR>
Is there hope for this to be fixed in karmic?
</BODY>
</HTML>