Bug 21890 - Automatic time synchronization fails when using drakconf
Summary: Automatic time synchronization fails when using drakconf
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-18 02:28 CEST by Jack M
Modified: 2017-10-30 06:53 CET (History)
2 users (show)

See Also:
Source RPM: drakxtools
CVE:
Status comment:


Attachments

Description Jack M 2017-10-18 02:28:11 CEST
Description of problem:

While synchronizing the time through drakconf (mageia control center), selecting the "enable network time protocol" (Mageia Control Center > System > Manage Date and Time) seems to have no effect other than immediately synchronizing the time. This has to be done every single time, it doesn't happen automatically when the machine is booted. I am not sure this is by design since this used to happen automatically in mga5.

This happens on both cauldron and on mageia 6(not upgraded, fresh install).
Cauldron is lxde, mga6 is plasma.

How reproducible:

Every time.

Steps to Reproduce:

1) drakconf
2) System > Manage Data and Time
3) Set 'Enable Network Time Protocol'
4) Redo the above, the option 'Enable Network Time Protocol' has to be enabled again.
Comment 1 Marja Van Waes 2017-10-18 22:51:29 CEST
See also bug 17091

CC: (none) => marja11
Source RPM: (none) => drakxtools
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=17091
Assignee: bugsquad => mageiatools

Comment 2 Nicolas Lécureuil 2017-10-28 21:47:52 CEST
i can reproduce this.

CC: (none) => mageia

Comment 3 Jack M 2017-10-30 06:53:51 CET
So, I am not sure if there were any changes made, but the time is now synchronising automatically upon boot, but, there is still no tick mark against Enable NTP option in MCC. Would be nice if we knew if it was enabled or disabled.

Note You need to log in before you can comment on or make changes to this bug.