Bug 142815 - Modification of date and time disabled after enabling NTP and removing ntpdate
Summary: Modification of date and time disabled after enabling NTP and removing ntpdate
Status: RESOLVED FIXED
Alias: None
Product: kcontrol
Classification: Miscellaneous
Component: kcmclock (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Paul Campbell
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-11 03:24 UTC by Philippe Cloutier
Modified: 2012-12-07 04:09 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe Cloutier 2007-03-11 03:24:45 UTC 
Version:            (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages
OS:                Linux

This is a corner case kcmclock bug.
If ntpdate is installed, one can check the NTP checkbox at the top of the dialog. After doing that, ntpdate can be removed.
After that, kcmclock even in administrator mode will only allow to change the timezone. Modification of date and time will be disabled. But the NTP checkbox will no longer be shown. This is possible because KDE stores

[NTP]
enabled=true

in /root/.kde/share/config/kcmclockrc.

I see two possible fixes: 
get rid of that configuration in kcmclockrc, using a non-KDE setting instead. No idea how feasible that is.
if ntpdate is not installed, let the administrator disable NTP or disable it automagically

Thanks to Modestas Vainius from Debian Qt/KDE team for diagnosing the problem.
Comment 1 Harald Sitter 2010-04-07 00:20:28 UTC 
Nowadays when ntpdate gets removed after initial config, the widget for configuring the NTP stuff will still be enabled and all, but the applying will consequently fail.

I hope this is enough a fix :)
Comment 2 Philippe Cloutier 2010-04-08 00:28:03 UTC 
Harald, since which versions does your description apply to? I'm getting the same behavior as in KDE 3 in KDE 4.3.4.
Comment 3 Philippe Cloutier 2012-12-07 04:09:44 UTC 
The new form taken by this bug was reported in #311286.