I put my laptop into sleep by just closing the lid and sometimes after wake up the clock shows wrong time and date which results into web sites not loading until I change it back and then I also lose logins to my previously logged in websites and have to re-enter the logins.

I don’t have dual boot so it’s not Windows messing with the Linux time issue I was able to find.

I use automatic time and date with my time zone selected. Not sure what I should do about this.

I’ve tried to enable RTC in local time zone but that made things even worse so I disabled it again.

  • yesman@lemmy.world
    link
    fedilink
    arrow-up
    13
    arrow-down
    1
    ·
    9 months ago

    A common cause for time issues through power states is a dead CMOS battery.

    • WereCat@lemmy.worldOP
      link
      fedilink
      arrow-up
      2
      ·
      9 months ago

      It’s a new laptop. Just released like 2 months ago so I doubt CMOS battery is an issue

        • FBJimmy
          link
          fedilink
          English
          arrow-up
          3
          ·
          9 months ago

          Yep, especially surface mount lithium batteries - they’re very sensitive to the solder reflow profile being juuuust right

  • Bitrot@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    10
    ·
    edit-2
    9 months ago

    timedatectl will tell you if your system time matches the rtc time on your motherboard. Could be the rtc is wrong (or failed) and the system is updating via ntp.

    hwclock -w can write the current system time to the rtc. If the battery is dead it wouldn’t help.

    • WereCat@lemmy.worldOP
      link
      fedilink
      arrow-up
      3
      ·
      9 months ago

      I just got home. You’re right that it’s using NTP. I went into BIOS and checked system time and it was 1h behind so I corrected it. timedatectl shows that system clock sync is OFF so I used hwclock --systohc command to sync with system clock and will see if that causes any issues. If it wont work then I’ll try to just stick with your way of doing it. But thanks for letting me know about the hwclock command.