This bug was fixed in the package acpi-support - 0.106
---
acpi-support (0.106) hardy; urgency=low
* Cherrypicked bugfix patches from Launchpad (LP: #193842)
* lib/state-funcs: make wireless led work with asus-laptop (the new module);
patch from Nicolò Chieffo (LP: #189889)
** Changed in: acpi-support (Ubuntu)
Assignee: Daniel Hahler (blueyed) = (unassigned)
Status: In Progress = Triaged
** Description changed:
/etc/init.d/hwclock.sh should be called before hibernation and when the
computer wakes up again, otherwise changes to the system clock are
@Daniel:
I couldn't test the whole package because i'm on Gutsy and Gutsy misses the
dependecy package x11-xserver-utils.
But i tested the /etc/acpi/suspend.d/88-time.sh extracted from your package.
Works as expected!
[EMAIL PROTECTED]:/etc/acpi/resume.d# date; hwclock --show
Don Mär 6
Use case (happened here right now):
Clock is off by X minutes for some reason. The running ntpd will reset it to
the correct time after several minutes.
Then you suspend your laptop, resume it, clock is off by X minutes again.
--
hwclock.sh should be called before/after hibernate
The patch for this is attached to bug 193842.
You can get a test package for acpi-support from my PPA at
https://launchpad.net/~blueyed/+archive?field.name_filter=acpi-support
(0.106blueyedppa5 or later)
--
hwclock.sh should be called before/after hibernate
https://bugs.launchpad.net/bugs/36815
** Description changed:
/etc/init.d/hwclock.sh should be called before hibernation and when the
- computer wakes up again, otherwise changes to the system lock are lost.
+ computer wakes up again, otherwise changes to the system clock are lost.
--
hwclock.sh should be called before/after
** Changed in: acpi-support (Ubuntu)
Assignee: (unassigned) = Daniel Hahler (blueyed)
Status: Confirmed = In Progress
--
hwclock.sh should be called before/after hibernate
https://bugs.launchpad.net/bugs/36815
You received this bug notification because you are a member of Ubuntu
I was affected by this bug when daylight saving transition happened last
week. Although I tried to update the clock it manually over and over
again, it was reset everytime I suspended the computer (I usually never
shut it off completely).
Stopping and starting hwclock.sh did the trick so I'm
Use case: clock set to local time (dual boot with Windows). A daylight
savings transition happens, but the clock is not written out to
hardware. Computer is suspended, and when resumed the timezone is
correct, but the time has reverted to the time before the transition.
There are some relevant
