Am 10.12.2012 00:13, schrieb G. Schlisio:
Am 09.12.2012 18:55, schrieb Leonid Isaev:
On Sat, 08 Dec 2012 21:48:54 +0100
"G. Schlisio" <g.schlisio@xxxxxxxx> wrote:
[...]
how can i get to know, why this is happening, and maybe stop it?
I suspect the issue is in pm-utils' pm-powersave script which
executes "power
saving" hooks, and is in turn being called by upower. But to be sure
we need to
see your pm-utils configuration (in /etc/pm) and and
/etc/Upower/Upower.conf...
/etc/pm/ contains conf.d/, power.d/ (both empty) and sleep.d/
(contains 90alsa, not doing much apart aplay). upower [0] contains a
RunPowersaveCommand=true, does that include APM=1 setting?
what curtis said about expected behavior and default settings, can
those be altered somewhere?
my /usr/lib/systemd/system-sleep/notify-upower.sh contains some call
of upower{,.resuming} via dbus.
what irritates me is that i experience this after last update, and
never before.
[0] my upower.conf:
[UPower]
SleepTimeout=1000
AllowHibernateEncryptedSwap=true
RunPowersaveCommand=true
EnableWattsUpPro=true
PollDockDevices=false
IgnoreLid=false
seems unrelated to suspend, but related to switch between external and
internal power supply. where can i adjust hese settings? may kde
interfere here?
suggestions appreciated.
