Btw, I'm on linux because I can control the system at each level, if I wanted a dumb (and locked) ready-to-use system I'd go on a mac.
I use to perform some heavy calculation sometimes that raise the system temperature. Then I have to limit the frequency in order to avoid overheating. In addition I don't see why I have to open the systemsettings just to switch powersaving profile. The fact that there is nothing like kpowersave in kde4 is a severe regression, imho. On ven 18 mag 2012, robert...@libero.it wrote: > Dear Michael, > > just to check I removed the /etc/init.d/hal script and rebooted; the > system still refuses to suspend even if kpowersave is not loaded > > Can you tell me what I should do to make kde suspend work? > All the packages are updated to the latest sid. > > Thank you, > > Roberto > > > Btw, I don't say this as someone helping with systemd, but as the > > maintainer of hal (and its successors) and the previous maintainer of > > kpowersave. > > > > You really should upgrade. > > The integrated powermanagement application in KDE4 is really good and > > the ondemand cpufreq scheduler is so good nowadays that you shouldn't > > need to fiddle with the cpu frequencies anymore. > > > > Michael > > On ven 18 mag 2012, you wrote: > > On 18.05.2012 17:58, Michael Biebl wrote: > > > The problem is, that kpowersave is buggy. It should trigger hal via > > > D-Bus activation, which it doesn't do. That means, hal is not > > > started and so kpowersave doesn't allow you to suspend. > > > That and the fact that kpowersave is not supported anymore. > > > kpowersave was removed from the archive for a reason. > > > If you insist on keeping using hal, you need to create corresponding > > > start symlinks in multi-user.target.wants yourself. > > > This is not something we support any longer. > > > > > > Closing this bug report. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
