>> > 1. Is there any damage in startkde of running
>> kdetcompmgr as a background
>> > task?
>>
>> Yes
>>
>> >
>> > 2. What process started in startkde is launching
>> kconf_update?
>>
>> Don't know
>>
>> >
>> > 3. Why is kconf_update being launched?
>>
>> To regenerate a configuration file index IIRC
>>
>> >
>> > 4. Is there a way to prevent kconf_update from
>> running?
>>
>> Not a good idea
>>
>> Sorry!
>
> Looks like kded might be causing this. There is a setting in KControl KDE
> Performance to disable system configuration startup checks. Possibly that
> can be enabled to stop kconf_update.
>
> Darrell

I would suggest filing a bug report on this.  Mark the priority to minor,
as this seems to only affect a small number of systems that have a
third-party binary blob installed.

We will need a stack trace from gdb attached to the bug report.  Best way
to do that is:
1.) Wait for the process to hang
2.) Switch to another console and find the PID of the hung process
3.) Start gdb with 'gdb'
4.) Issue these commands to gdb:
 a.) attach <PID you found above>
 b.) bt

gdb should now spit out a backtrace that can be attached to the bug
report.  You will of course need the debugging symbols installed for the
backtrace to be of any use. ;-)

Tim