Yes, I'm sure I'm using kpowersave :) I have a debian-sid with the latest kde. I would not use kpowersave if I had an equivalent tool that allows me to check/switch the cpu-freq from systray. Anyway, I don't think kpowersave issue is relate to suspend one. Why kde cannot suspend?
And why the hal init script is not executed at boot? It is supposed to work with systemd: http://wiki.debian.org/systemd#Debian_packages_with_native_systemd_support >The hal sysv init script has been dropped before the squeeze release and >hal is D-Bus activated now. >Which version of hal do you have? Is this system a mix from old-stable, >stable and unstable? > > You really shouldn't be using hal and kpowersave anymore. kpowersave was > already removed in squeeze and hal is not actively maintained anymore. > Please use the integrated powermanagement in KDE (which is based on upower). > Are you really sure you are using kpowersave? Which KDE version do you use? > > Michael >----Messaggio originale---- >Da: bi...@debian.org >Data: 18/05/2012 2.52 >A: <robert...@libero.it>, <673...@bugs.debian.org> >Ogg: Re: Bug#673192: systemd does not allow suspend to ram > >On 17.05.2012 23:42, robert...@libero.it wrote: >> Dear Tollef, >> >> using 'sudo pm-suspend' the system can suspend to ram and resume back. >> However the standby button of kde doesn't work for some reason, and as a >> consequence also the automatic suspend of power-management. >> >> In addition also kpowersave don't work with systemd; the icon becomes gray >> and no functions are available (e.g. cpu freq. profiles). >> I found that problem was related to hal and by sudoing an '/etc/init.d/hal > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
