Running kded modules on non-KDE desktops

David Jarvie djarvie at
Thu Jan 21 17:05:52 GMT 2010

On Thu, January 21, 2010 1:12 pm, dantti85-dev at wrote:
> Not sure if someone already answered for this
> but this sounds like it should use DBus activate
> to start kded if the ktimezoned interface is not available,
> pretty simple patch btw

Thiago did answer - kded modules are supposed to be run automatically by
kdelibs. It works for me on Gnome, but it didn't work for a user for some
reason. I'm still trying to find out what his configuration was exactly.

>> Enviadas: Sábado, 9 de Janeiro de 2010 19:47:45
>> Assunto: Running kded modules on non-KDE desktops
>> Applications which use time zone data get the data by calling
>> KSystemTimeZones::local(), which in turn gets the system time zone from
>> the kded
>> module ktimezoned. This mechanism avoids the system time zone being read
>> separately by each application - reading it can be time consuming, so
>> fetching
>> it once only is desirable.
>> This works in the KDE desktop, but when a KDE application is run under
>> another
>> desktop environment, ktimezoned isn't running and therefore the system
>> time zone
>> returned by kdelibs is always the default, UTC. Is there any way for
>> ktimezoned
>> to be activated automatically by kdelibs when it is required? If not, it
>> is
>> probably necessary for KSystemTimeZones to read the system time zone
>> itself when
>> it is not available from ktimezoned.
>> --
>> David Jarvie.

David Jarvie.
KDE developer.
KAlarm author -

More information about the kde-core-devel mailing list