This bug was fixed in the package powernap - 2.13-0ubuntu1
---------------
powernap (2.13-0ubuntu1) oneiric; urgency=low
[ Dustin Kirkland ]
* sbin/powernapd:
- make sure that powerwake-now works, even if a system has gone into
powersave mode by other means (erhm, gnome-power-settings, erhm)
* actions/01cpu_online:
- drop the nasty sleep 10 hack around gnome-settings-daemon bugginess;
doesn't seem to be a problem at this point in Oneiric; If this bug
shows back up, we need to solve it in a better way
* actions/video:
- drop incorrect inline docs
* config:
- now that the default is powersave mode, adjust the absent time and
grace period; it takes fractions of a second to go in and out of
powersave mode
* actions/00flag, debian/powernap.upstart, sbin/powernapd: LP: #829618
- use a flag in shared memory that notes the powersave status of the
system
- set/remove that flag in the 00flag script in the pm-utils suite
- set/remove/query that same flag in powernapd itself
* debian/control: LP: #637635
- depend on anacron, to better handle server cronjobs on systems that
might have been asleep
* powernap/monitors/InputMonitor.py: LP: #826278
- test device path existence before opening, fixes nasty crash
-- Andres Rodriguez <andres...@ubuntu.com> Tue, 09 Aug 2011 15:28:38 -0400
** Changed in: powernap (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/637635
Title:
please make powernap depend on/recommend anacron
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powernap/+bug/637635/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
