Very Computer

I have recently started having trouble displaying images in kmail.
After starting kmail konqueror will not start until after a reboot.

I have traced it to a process called "kded".  If I kill kded
everything works just fine.  My question is:

What the heck is kded and how do I stop it from starting in the first place?

Dan Simpson, alle 15:59, sabato 28 giugno 2003, ha scritto:

Quote:> I have traced it to a process called "kded".  If I kill kded
> everything works just fine.  My question is:

I don't know what is kded, but now all my troubles have gone! Thanks for the
suggestion!
Roberto

"man kded" doesn't help?

(i find that there is something plainly wrong in the way kde (or
 gnome, for what is worth) is being deployed... no man pages, no info
 files, some spare htlm pages that add so little to inspection of
 menus, to me using kde sometimes resembles using

--
termy prende per fatica, attento.                     -- PLS, in IFQ

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

kded is the 'small kde daemon'

It has lots of uses, including watching the filesystem and triggering
updates of things that need updating.  This may include menu updates,
settings changes that need to be propagated, and updating views in
konqueror file manager views and file open/save dialogs.

Turning it off is probably a bad idea.  If it's running slow, you should
look at your system performance, in particular hard drive speeds, using
or not using FAM or dnotify (both of which on some systems vastly speed
up such file system watching, and on others trigger bugs that make
things very slow indeed.)

Regards,
- --
Lauri Watts
KDE Documentation: http://i18n.kde.org/doc/
KDE on FreeBSD: http://freebsd.kde.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)

iD8DBQE/ACeE/gUyA7PWnacRAjH6AJ9tZHXqz5VV0bwh2sBsXbkYbx43egCgi3XQ
OFf5GCnvrUXPVJB/c/Dzj4A=
=vhaK
-----END PGP SIGNATURE-----

I had a run-in with FAM on my RH72 installation. For some reason (with
no preceeding system mods), it suddenly started using vast amounts of
CPU and would hang the system on startup, preventing X from starting.
Killing the FAM process would allow things to progress, but it would do
it again next go-round. I disabled FAM startup with no apparent
side-effects, but it may have just been that I didn't use whatever FAM
"fed".

YMMV.

--

-- Len Philpot                          ><>  --

unless you consider this:

No manual entry for kded

To be help, No it didn't.