[e-users] E17 and inhibiting autosuspend

[Ross Vandegrift]

Hi everyone,

When I am logged in via E17, my workstation autosuspends even when an
app (brasero, transmission, etc) has requested that suspend be
inhibited. When I am logged in via Gnome, this works as expected.

I cannot for the life of me figure out what is busted here, though I
have the following hint. This inhibiting happens via a dbus call, and
under E17, I see the following errors:

(gnome-settings-daemon:12215): power-plugin-WARNING **: IsInhibited
failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.gnome.SessionManager was not provided by any .service files

I am running Enlightenment using the shipped Xsession file. I have
enabled Apps -> Desktop Environments -> Start GNOME services on login.
I have disabled Look -> Applications -> Enable Settings Daemon.

Any hints?

Ross

[Carsten Haitzler]

On Sat, 10 Mar 2012 10:09:23 -0500 Ross Vandegrift <ro...@kallisti.us> said:

and what is doing the auto-suspend. e has only 1 autosuspend feature - to
suspend if screensaver kicks in. it has never been on by default, so unless you
enabled it, it's not e suspending. (e has no inhibit thing for that). all those
apps DEPEND on gnome power manager and its dbus api - which of course is a
gnome thing, not e.

--
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler) ras...@rasterman.com

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
enlightenment-users mailing list
enlighten...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

[Ross Vandegrift]

On Sun, 2012-03-11 at 09:20 +0900, Carsten Haitzler wrote:
> and what is doing the auto-suspend. e has only 1 autosuspend feature - to
> suspend if screensaver kicks in. it has never been on by default, so unless you
> enabled it, it's not e suspending. (e has no inhibit thing for that). all those
> apps DEPEND on gnome power manager and its dbus api - which of course is a
> gnome thing, not e.

Hmmm, looks like the trigger is E's DPMS Standby timer, but that E is
not ultimately to blame. When X's DPMS standby timeout hits, something
forces the whole machine to suspend instead of the monitor.

I think it works under Gnome and not E because whatever the session
manager stuff is, its preventing gnome power manager from taking control
under E.

I'll have to see if I can figure out why on earth X thinks suspending
the box is the right thing to do when asked to put the display into
standby mode.

Ross

[Ross Vandegrift]

On Sun, 2012-03-11 at 13:26 -0400, Ross Vandegrift wrote:
> Hmmm, looks like the trigger is E's DPMS Standby timer, but that E is
> not ultimately to blame. When X's DPMS standby timeout hits, something
> forces the whole machine to suspend instead of the monitor.

*bangs head on desk*

Screen -> Screen Saver -> Suspend on blank means "Suspend the whole
shebang", not "Suspend the display".

Well I feel stupid!

Ross

[Carsten Haitzler]

On Sun, 11 Mar 2012 13:51:58 -0400 Ross Vandegrift <ro...@kallisti.us> said:

> On Sun, 2012-03-11 at 13:26 -0400, Ross Vandegrift wrote:
> > Hmmm, looks like the trigger is E's DPMS Standby timer, but that E is

> > not ultimately to blame. When X's DPMS statndby timeout hits, something

> > forces the whole machine to suspend instead of the monitor.
>
> *bangs head on desk*
>
> Screen -> Screen Saver -> Suspend on blank means "Suspend the whole
> shebang", not "Suspend the display".

that is... why i mentioned "unless you enabled it" :)