Running kded modules on non-KDE desktops

Thiago Macieira thiago at
Sun Jan 10 09:07:15 GMT 2010

Em Sábado 9. Janeiro 2010, às 22.47.45, David Jarvie escreveu:
> 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.

I thought kdelibs started kdeinit4, klauncher and kded when necessary.

That isn't happening?

Thiago Macieira - thiago (AT) - thiago (AT)
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <>

More information about the kde-core-devel mailing list