I just ran a clean install of 12.10 on my sys76 laptop.

Time and date reads: 19:36 31 december 1969, even though it is: 13:29 07 november 2012.

I have it set for my location and it won't change manually, even tried in the command line with tz.

I think it is messing up the security certificates over the Internet cause I cannot change PPA over command line and going to Launchpad brings up the certificates page in Firefox.

Is this some known bug or is there a fix for it?

  • 1
    Dude... your computer is fine - it is 1969. Woodstock is apparently going to be pretty good this year... – GrayedFox Mar 5 at 1:24

Try:

sudo ntpdate ntp.ubuntu.com

Yes it would certainly mess with the SSL certs because they would be future-dated.

It doubt it's a bug in Ubuntu, your CMOS clock in the BIOS must have been set to that somehow.

  • 18 Apr 15:06:04 ntpdate[29230]: no server suitable for synchronization found – vipin8169 Apr 18 '16 at 10:36
  • after installing >> sudo apt-get install ntp>> 18 Apr 15:07:03 ntpdate[30070]: the NTP socket is in use, exiting – vipin8169 Apr 18 '16 at 10:37
  • That's fine for a one-off fix, but you'll still have system drift and get off again. You really want to install ntp to get the ntpd deamon running (At that point ntpdate will then give the error "the NTP socket is in use, exiting" which is what you want, because ntpd is taking care of keeping the clock in sync) – Randall Oct 28 '16 at 14:46

Just install ntp server:

sudo apt-get install ntp

It will automatically keep your clock synchronized.

  • This fixed the problem for me on Ubuntu 13.10. No idea why. (Problem was that the clock was off by one hour after daylight saving time/summer time took effect.) – Carl Apr 2 '14 at 8:40
  • I installed ntp however my time is still ahead by 5 minutes. How long does it take to update the time or do I need to run any command after? Thanks – Mo. Jul 12 '15 at 4:56
  • Mine took a few minutes to run, then it finally set the clock correctly – Sam Barnum Aug 2 '17 at 15:08

After installing 12.10 I had the same problem as well. Somehow the new installation set the BIOS clock to the year 2070 !! After this, Ubuntu wasn't able to set a different date both by ntp, manually, even using the date command.

Setting the right date in the BIOS settings solved the problem.

Install ntp and ntpdate executing the following commands-

sudo apt-get install ntp
sudo apt-get install ntpdate

Then, execute

sudo ntpdate ntp.ubuntu.com

This works for me.

  • 10
    Pretty sure that if you do it in that order, that ntpdate will give the error "the NTP socket is in use, exiting" because the ntp package should have started ntpd which grabs the socket. – Randall Oct 28 '16 at 14:48
  • Don't you only need ntp? – Gabriel Fair Apr 20 at 16:39
  • @Randall is correct, however it still updates the time. Don't know if there are any other side effects though. – JBaczuk Jun 15 at 15:58

Your Answer

 

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.