Bug 209733 - powerdevil tries to enforce settings on inactive display
Summary: powerdevil tries to enforce settings on inactive display
Status: RESOLVED NOT A BUG
Alias: None
Product: solid
Classification: Unmaintained
Component: powermanagement-daemon (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Dario Freddi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-07 12:13 UTC by Michi
Modified: 2010-11-09 20:43 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michi 2009-10-07 12:13:38 UTC
Version:            (using KDE 4.3.1)
OS:                Linux
Installed from:    SuSE RPMs

Hi,

I've realized that powerdevil must be trying to enforce powersave settings even when the user session doesn't run on the active display, i.e. when I am logged in as a different user on let's say vt8. After some time the "inactive" X server occupies one core of my cpu; I reckon that it tries to put the display into standby.

bye M;chi
Comment 1 Dario Freddi 2009-12-01 17:09:49 UTC
PowerDevil should actually support this if you have consolekit enabled (I believe I backported the change to 4.3.2), can you please test if, with ck enabled, you are still able to reproduce the issue?
Comment 2 Michi 2009-12-06 10:09:25 UTC
(In reply to comment #1)
> PowerDevil should actually support this if you have consolekit enabled (I
> believe I backported the change to 4.3.2), can you please test if, with ck
> enabled, you are still able to reproduce the issue?

consolekit has always been enabled, however something might be wrong there, because soundcard switching doesn't work either.

In the meantime I've switched to 4.3.80 (opensuse) and found something else. In the inactive session I have a profile that defines a timeout for suspending the computer. When I get back to that inactive session after the specified timeout the computer immediately runs into suspend.
What happens as well is that after a consolekit sessions is reactivated the default profile is being applied rather than the one that had been defined before.