*** This bug is a duplicate of bug 36815 ***
https://bugs.launchpad.net/bugs/36815
Thank you for reporting back.
I'm marking it as duplicate of bug 36815.
** Changed in: acpi-support (Ubuntu)
Status: Incomplete => Invalid
** This bug has been marked a duplicate of bug 36815
hwclock
I don't think this is (was?) the same problem. This one was caused by
the installer leaving an /etc/adjtime with "UTC" even if local time was
chosen and/or that resume.sh did not help by appending --localtime or
--utc.
--
clock is wrong after resume when hardware clock is set to localtime
https:/
Now looking at your patch in bug #193842 it seems to fix this anyway,
since it calls /etc/init.d/hwclock.sh which I believe adds --utc or
--localtime (instead of the old resume.sh which called /sbin/hwclock
directly.
--
clock is wrong after resume when hardware clock is set to localtime
https://b
Is this the same as bug 36815? If so, you might want to try the proposed fix
there (or tell me how it needs to be improved).
Thank you.
** Changed in: acpi-support (Ubuntu)
Importance: Low => Medium
Assignee: (unassigned) => Daniel Hahler (blueyed)
Status: Confirmed => Incomplete
