When I start my first KDE session after a reboot, I get a message to the effect that I should turn on kpowersaved. But in fact it was already turned on: suillus:~ # /usr/sbin/rcpowersaved start daemon already running done Anyone know why I'm getting this message? Paul
On Thursday, May 11, 2006 @ 12:32 PM, Paul W. Abrahams wrote:
When I start my first KDE session after a reboot, I get a message to the effect that I should turn on kpowersaved. But in fact it was already turned on:
suillus:~ # /usr/sbin/rcpowersaved start daemon already running done
Anyone know why I'm getting this message?
Paul
Kpowersaved is a separate app from the powersave daemon. I personally turned off the powersave daemon and uninstalled kpowersave, so I can't look at my own configuration to give you any more detail. However, it sounds like you somehow need to enable kpowersave. Maybe it's also a daemon. You might check to see if there is a kpowersave daemon in rulevel editor. Greg Wallace
Paul W. Abrahams a écrit :
When I start my first KDE session after a reboot, I get a message to the effect that I should turn on kpowersaved. But in fact it was already turned on:
suillus:~ # /usr/sbin/rcpowersaved start daemon already running done
Anyone know why I'm getting this message?
Paul
Hello, I happened to get this problem on one computer and to solve it. For that computer it came from the fact that the "run parallel" option was enabled at boot, so that kde started while boot scripts were still running. And kpowersave started before the powersave daemon. I disabled "run parallel" and everything was OK. Michel.
On Thursday 11 May 2006 2:45 pm, Catimimi wrote:
I happened to get this problem on one computer and to solve it. For that computer it came from the fact that the "run parallel" option was enabled at boot, so that kde started while boot scripts were still running. And kpowersave started before the powersave daemon.
I disabled "run parallel" and everything was OK.
Thanks to your suggestion, I found "run parallel" within the system configuration variables (available through Yast) and have disabled it. But that seems like overkill. Apparently the related software isn't good enough at detecting which tasks really can be run in parallel. A better solution would be to force synchronization of the offending tasks. But I'm wondering how to achieve that. Paul
On Thursday 11 May 2006 2:45 pm, Catimimi wrote:
Paul W. Abrahams a écrit :
When I start my first KDE session after a reboot, I get a message to the effect that I should turn on kpowersaved. But in fact it was already turned on:
suillus:~ # /usr/sbin/rcpowersaved start daemon already running done
Anyone know why I'm getting this message?
Paul
Hello,
I happened to get this problem on one computer and to solve it. For that computer it came from the fact that the "run parallel" option was enabled at boot, so that kde started while boot scripts were still running. And kpowersave started before the powersave daemon.
I disabled "run parallel" and everything was OK.
I also disabled "run parallel" and it did not help. Paul
participants (4)
-
Catimimi -
Greg Wallace -
Paul Abrahams -
Paul W. Abrahams