Version: (using Devel) Installed from: Compiled sources For quite a while now (I think since 4.3 beta2) kconf_update needs 100% CPU each time it is executed... not sure what else i can provide to help out with this issue... this happens on a 64bit arch linux system with kernel 2.6.30...
confirmed on my arch-linux with kde 4.2.95
arch linux with kde 4.3 rc1 confirmed, too.
try to delete kconf_updaterc or to run kconf_update...
(In reply to comment #3) > try to delete kconf_updaterc or to run kconf_update... no effect
(In reply to comment #4) > (In reply to comment #3) > > try to delete kconf_updaterc or to run kconf_update... > > no effect same here. I'm on arch linux x64. this problem started with 4.2.95
i just upgraded to rc2 and removed my kconf_updaterc, then ran kconf_update. upon restart, the cpu usage seems to be cured!
I'm on Archlinux x86_64 with kdemod rc2, removing kconf_updaterc doesn't solve the problem.
I can confirm this issue, Arch Linux x86_64 with packages from kde-unstable repo.
Anyone not on Arch getting this?
(In reply to comment #7) > I'm on Archlinux x86_64 with kdemod rc2, removing kconf_updaterc doesn't solve > the problem. I believe you have to remove ~/.kde4(or .kdemod4)/share/config/kconf_updaterc, then from the command line type: "kconf_update." It took a few seconds. I don't remember if i had to run it as sudo, but it fixed the problem for me. Anyone confirm?
I can confirm on my arch
I forgot to mention: (as root) type into command line "killall kconf_update" before performing the kconf_updaterc removal and kconf_update. (In reply to comment #10) > (In reply to comment #7) > > I'm on Archlinux x86_64 with kdemod rc2, removing kconf_updaterc doesn't solve > > the problem. > > I believe you have to remove ~/.kde4(or .kdemod4)/share/config/kconf_updaterc, > then from the command line type: "kconf_update." It took a few seconds. I > don't remember if i had to run it as sudo, but it fixed the problem for me. > > Anyone confirm?
I can confirm this on Arch Linux. But please note that this kconf_update which makes trouble risides at /opt/kde/bin/, coming from the package kdelibs3, not kdelibs. There is not any problem with /usr/lib/kde4/libexec/kconf_update, which comes from the package kdelibs. Though most of us use KDE 4, the package kdelibs3 is installed as dependency when we install KDE 3 applications, a typical example, Konversation. Therefore I guess it is a bug of KDE 3 instead of KDE 4.
I confirm on archlinux with kde 4.3 rc3 During the login the application kbuildcoca get the 100% of the cpu. And after killing kbuildcoca, kconf_update starts whit the 100% of the CPU and don't stop.
I confirm on archlinux x86 kernel 2.6.30 with no kde4 installed. I just installed kdelibs (version 4.2.4-4) and kdelibs3 (version 3.5.10-4) to run a few kde packages. After removing ~/.kde4/share/config/kconf_updaterc it took almost no time to run kconf_update.
*** This bug has been confirmed by popular vote. ***
I confirm this bug also on kde 4.3.0 on archlinux x86_64.
Right, this seems to be a problem of the kdelibs3 package, when I remove it on my arch system, it is working fine again.
Hi, other Arch user for here. In my case, kconf_update only eat 50% of cpu, all of the time. I can confirm this: removing kdelibs3 package solve the problem.
Confirm with arch and KDE 4.3.00 It's taking up 100% of one cpu core (In reply to comment #19) > In my case, kconf_update only eat 50% of cpu, all of the time. I suppose you also have a dual-core cpu?
I have disabled kconf_update in kdelibs3 by adding the following to /opt/kde/share/config/kconf_updaterc updateInfoAdded=false autoUpdateDisabled=true
The problem is persisting also with kde 4.3.4. And I've not installed kdelibs3.
What is the status of this bug? Does it still happen with a recent KDE version, such as 4.6.5 or 4.7.x? Please add a comment.
If you can provide the information requested in comment #23, please add it.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!