https://bugzilla.novell.com/show_bug.cgi?id=893427 https://bugzilla.novell.com/show_bug.cgi?id=893427#c2 ill lume changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|illumilore@gmail.com | --- Comment #2 from ill lume 2014-08-30 17:44:34 UTC --- I have the timezone set to denver. I also run windows, which also resets the clock, but this time change happens between reboots of opensuse only. And since opensuse can't set the time from a timeserver properly, I can also see the time slowly drift behind actual time. ie. the minute is now 42, but opensuse's clock is still at 40. $ ll /etc/localtime lrwxrwxrwx 1 root root 36 Aug 25 14:56 /etc/localtime -> ../usr/share/zoneinfo/America/Denver $ ntpq -pn ntpq: read: Connection refused $ hwclock hwclock: Cannot access the Hardware Clock via any known method. hwclock: Use the --debug option to see the details of our search for an access method. $ hwclock -w hwclock: Sorry, only the superuser can change the Hardware Clock. $ sudo hwclock -w The time doesn't change after sudo hwclock -w -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=893427 https://bugzilla.novell.com/show_bug.cgi?id=893427#c4 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #4 from Dr. Werner Fink 2014-09-01 07:30:52 UTC --- (In reply to comment #3) This is wrong! This has nothing todo with boot.hwclock. The configuration of the system is broken. Also I guess that the CMOS clock is running in local time and not as strongly recommended in UTC. Compare with https://en.opensuse.org/index.php?title=SDB:Configuring_the_clock -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=893427 https://bugzilla.novell.com/show_bug.cgi?id=893427#c6 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO CC| |systemd-maintainers@suse.de Component|Basesystem |Installation InfoProvider| |illumilore@gmail.com AssignedTo|systemd-maintainers@suse.de |yast2-maintainers@suse.de QAContact|qa-bugs@suse.de |jsrain@suse.com --- Comment #6 from Dr. Werner Fink 2014-09-02 07:24:44 UTC --- All test systems work and may private systems at home work flawless. Even if I break the common standard and choose localtime for CMOS clock for testing. Do you have read https://en.opensuse.org/index.php?title=SDB:Configuring_the_clock that is do you have checked if the clock in CMOS is in UTC to allow the kernel to hold its system clock in UTC aka network time? If not it is up on you to check this in e.g. YaST which will then trigger that the kernel will be enabled in the initrd to correct its clock back to UTC. To avoid this frangible workaround simply avoid localtime in CMOS clock and choose the international time standard UTC. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=893427 https://bugzilla.novell.com/show_bug.cgi?id=893427#c Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |mvidner@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=893427 Peter Varkoly changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |INVALID --- Comment #8 from Peter Varkoly --- (In reply to ill lume from comment #7)

I read the info in that link and it was unhelpful. I went into yast system config and then clicked on date and time and clicked change from there clicked synch with ntp and chose a new server and checked the boxes and told it to run now and on boot from the configure button there. It seems to not be resetting on reboot, so something was broken with the configuration.

I still think it might be a bug that it broke in the first place, and there is some weirdness in yast ntp configuration in that it reset my choice from sync with ntp server to manually after clicking cancel then going back.

I can only repeate what Werner Fink said: "The configuration of the system is broken. Also I guess that the CMOS clock is running in local time and not as strongly recommended in UTC." -- You are receiving this mail because: You are on the CC list for the bug.