Bug 180212 - 'Set date and time automatically' setting is not remembered
Summary: 'Set date and time automatically' setting is not remembered
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_clock (show other bugs)
Version: 4.1
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Paul Campbell
URL:
Keywords:
: 209206 299841 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-01-10 04:52 UTC by Syam
Modified: 2012-09-21 01:10 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.8

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Syam 2009-01-10 04:52:01 UTC 
Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    Fedora RPMs

I use Fedora 10 with KDE 4.1.3.
In KDE system settings, the 'Set date and time automatically' option is not remembered. I enable it, click apply, enter root password when prompted and close system settings. Next time I open it, the option is not selected.

I don't even know if updating time from the selected server is even working.

Please see: https://bugzilla.redhat.com/show_bug.cgi?id=478585
Comment 1 Syam 2009-01-22 17:21:55 UTC 
I now have ntpd running (no configuration edited, just started the service as it came with F10). Now when I enable 'Set Date and time automatically' with pool.ntp.org (or any server, for that matter), I get this error message(after the root password): "Unable to contact time server: Public Time Server (pool.ntp.org)."
I'm able to ping pool.ntp.org just fine.
Comment 2 Dario Andres 2009-10-03 22:31:54 UTC 
*** Bug 209206 has been marked as a duplicate of this bug. ***
Comment 3 Burkhard Lück 2011-04-12 17:45:27 UTC 
Kubuntu 10.10:
$ KDE_LANG=en_US systemsettings --version
Qt: 4.7.0
KDE Development Platform: 4.6.2 (4.6.2)
System Settings: 1.0

Setting of the 'Set date and time automatically' option is properly 
remembered here.
Comment 4 Lukáš Tinkl 2012-09-21 01:10:51 UTC 
*** Bug 299841 has been marked as a duplicate of this bug. ***