Bug 967665

This[1] is related commit, to be more precise.

[1] 
http://cgit.freedesktop.org/systemd/systemd/commit/src/timedate/timedated.c?id=7e7d4da22925c329d668334aec3b3e7f21f63bc3

Hmm, not following,. Do you actually have an ntp implementation installed?

(In reply to Lennart Poettering from comment #2)
> Hmm, not following,. Do you actually have an ntp implementation installed?

$ ps ax | grep [c]hrony
19495 ?        S      0:00 /usr/sbin/chronyd -u chrony ;)

http://lists.fedoraproject.org/pipermail/users/2013-May/435891.html

Harald's commit 7e7d4da22925c329d668334aec3b3e7f21f63bc3 
i.e. "timedated: fixed NTP enabled: n/a" 
versus 
systemd-201-2.fc18.7.src.rpm 
i.e. systemd-201/src/timedate/timedated.c 
-build-
# cp systemd-201/.libs/systemd-timedated /usr/lib/systemd/systemd-timedated
$ timedatectl | grep NTP
     NTP enabled: yes
NTP synchronized: yes
$ timedatectl set-ntp off
$ timedatectl | grep NTP
     NTP enabled: no
NTP synchronized: yes
$ systemctl status chronyd
chronyd.service - NTP client/server
   Loaded: loaded (/usr/lib/systemd/system/chronyd.service; disabled)
   Active: inactive (dead)

$ timedatectl set-ntp on
$ systemctl status chronyd
chronyd.service - NTP client/server
   Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled)
   Active: active (running)…

I've noticed this too; the NTP toggle in gnome-control-center is currently broken in F18, though I'm pretty sure it used to work. It's giving the same "Failed to issue method call: No such file or directory" error (when run in terminal with G_MESSAGES_DEBUG=true).

After the recent systemd update, chrony is active and running, and /usr/lib/systemd/ntp-units.d/50-chronyd.list exists (I haven't messed with any defaults), yet:

[michael@victory-road ~]$ gdbus introspect --system --dest org.freedesktop.timedate1 --object-path /org/freedesktop/timedate1
node /org/freedesktop/timedate1 {
  interface org.freedesktop.timedate1 {
    methods:
      SetTime(in  x usec_utc,
              in  b relative,
              in  b user_interaction);
      SetTimezone(in  s timezone,
                  in  b user_interaction);
      SetLocalRTC(in  b local_rtc,
                  in  b fix_system,
                  in  b user_interaction);
      SetNTP(in  b use_ntp,
             in  b user_interaction);
    signals:
    properties:
      readonly s Timezone = 'America/Chicago';
      readonly b LocalRTC = false;
      readonly b CanNTP = false;
      readonly b NTP = false;
  };

CanNTP = false seems bad, and this property didn't exist in F18 until systemd-201, so without actually understanding what's wrong, I blame the update!

poma posted a link above to what he says is the upstream commit which fixes the issue.

poma, are you sure this bug should have been closed? It doesn't seem to be fixed in F18, and I didn't see any requests for additional information.