>> >> > 1. Is there any damage >> in startkde of running >> >> kdetcompmgr as a background >> >> > task? >> >> > >> >> > 2. What process started in startkde is >> launching >> >> kconf_update? >> >> > >> >> > 3. Why is kconf_update being launched? >> >> > >> >> > 4. Is there a way to prevent kconf_update >> from >> >> running? >> >> > >> >> >> >> What version of the nVidia drivers does Slackware >> install? >> >> >> >> The issue occurs within a very low level section >> of code, >> >> and I have not >> >> seen it on my Ubuntu systems in ages, thus I >> suspect it may >> >> be a known >> >> issue with older versions of the nVidia driver. >> > >> > Slackware does not install any Nvidia packages. They >> are left to the users >> > to build and install. >> > >> > I am using 195.36.31 and have been for a long time. >> That is what I'm using >> > on 3.5.10 too, where I don't see this behavior. >> > >> > Is changing the Nvidia package the answer? Many people >> are going to be >> > attracted to TDE because of the potential to run on >> older hardware. If >> > those people have older Nvidia cards they will be >> using legacy drivers. >> > >> >> I don't know. This particular bug would require a LOT >> of time to >> troubleshoot and I don't have that much time to offer for >> free at this >> point. >> >> If anyone else wants to take a stab at it feel free! > > Let's not focus yet on the bowels of the kdeinit code. Let's focus on the > four questions I posed: > > 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! Tim