[Bug 436076] Re: system clock not adjusted when hardware clock in localtime

2013-11-05 Thread gregrwm
in precise, this causes my cable box to disconnect. the cable modem connects with the time wrong, ntp resets the time, dhclient then fails to renew the lease within the given time, and then Comcast terminates the connection. -- You received this bug notification because you are a member of

[Bug 436076] Re: system clock not adjusted when hardware clock in localtime

2012-05-01 Thread Daniel AƱez Scott
Getting this bug in kubuntu 12.04. My locale is VET, UTC=no in rcS. Also, plymouth blinks so it doesn't get to show the error, but I know it's that one, so I have to boot to recovery mode and run fsck, which messes up the clock in order to adjust it to the present... -- You received this bug

[Bug 436076] Re: system clock not adjusted when hardware clock in localtime

2009-11-20 Thread Richard Ulrich
since upgrading to karmic (release), I get the following very often: /dev/sda1: Superblock last mount time (Thu Sep 24 20:58:00 2009, now = Thu Sep 24 19:59:23 2009) is in the future. /dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options)

[Bug 436076] Re: system clock not adjusted when hardware clock in localtime

2009-09-24 Thread Launchpad Bug Tracker
This bug was fixed in the package util-linux - 2.16-1ubuntu4 --- util-linux (2.16-1ubuntu4) karmic; urgency=low * Removed access checks for hardware clock when called with --systz, since we may not have the rtc device at the point we run hwclock. I believe this is the cause