There appears to have been some progress on this bug. powersaved now
responds to Fn+F4. It seems to get the event from HAL (when I stop hal,
powersaved no longer responds). Wow, is the future really here?? No,
things are still badly broken:
- Fn+F4 suspends to disk, not ram.
- Fn+F12 does noth
On Wed, 9 Apr 2008, Michael Biebl wrote:
> Sven-Haegar Koch schrieb:
> > Package: powersaved
> > Version: 0.15.20-2
> > Severity: normal
> >
> >
> > Until the powersaved update of today pressing Fn+F4 on my Thinkpad T60
> > started suspend to ram, which worked without problems.
> >
> > Now when
Sven-Haegar Koch schrieb:
> Package: powersaved
> Version: 0.15.20-2
> Severity: normal
>
>
> Until the powersaved update of today pressing Fn+F4 on my Thinkpad T60
> started suspend to ram, which worked without problems.
>
> Now when pressing it I only get some logs from acpid into syslog, noth
Package: powersaved
Version: 0.15.20-2
Severity: normal
Until the powersaved update of today pressing Fn+F4 on my Thinkpad T60
started suspend to ram, which worked without problems.
Now when pressing it I only get some logs from acpid into syslog, nothing
from powersaved anymore:
(/etc/powersave
4 matches
Mail list logo
