----- Original Message ----- > On Mon, Sep 08, 2014 at 08:36:21AM -0500, Michael Catanzaro wrote: > > On Sun, 2014-09-07 at 22:18 -0700, Adam Williamson wrote: > > > > - has tools for setting the system time and timezone, and locale > > > > > > Sure. They're useful. > > > > In GNOME, our settings panels previously only worked on Fedora and > > Debian, with some half-functional code for Arch and openSUSE, because > > each distro handled these differently and required custom code. Now we > > have no special casing for different distros, and it works everywhere > > these D-Bus interfaces are present (including systems without systemd > > that provide it, like Ubuntu). > > Yeah, that was nice, when it worked as we wanted. Unfortunately, with > the latest systemd the NTP service which is enabled/disabled by > timedated is no longer selected from the services installed on the > systemd, but is now hardcoded to the systemd SNTP client (timesyncd). > > That means the NTP status reported in GNOME settings may be incorrect, > enabling/disabling NTP will do nothing if another NTP service is enabled > or timesyncd will be enabled even when our default NTP client > (chronyd) is installed. > > https://bugzilla.redhat.com/show_bug.cgi?id=1136905 > > Upstream is not interesting in having this configurable. Should we be > patching timedated? Or GNOME? FYI, I have no interest in taking a patch to *re-add* special casing for that in GNOME. > > I don't really care where these interfaces live, but they need to exist > > somewhere, and systemd seems like the logical place for them. > > Agreed, the problem is systemd upstream may have a different view on > what exactly the interfaces should do. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
