Hey

Today I upgraded to kde 4.2.2 and suddenly plasma is canstantly using a lot of system resources. I restarted the computer to see if that made any difference, but it didn't. Even with no apps running and only one plasmoid on the desktop (not including the panel thingys) it still eats resources. Is this a known bug? What can I do to fix this?

System:
Kubuntu Intrepid
Nvidia 8500GT with 180.44 drivers

Thanks in advance.

If you disable that only plasmoid what happens?
I updated to 4.2.2 yesterday on my openSUSE 11.1 and plasma use less than 1% of my resources so, no, it is not a known bug.
Maybe during update the plasmarc and/or plasma-appletsrc went wrong. If nothing else work, try deleting/renaming those files (they are in ~/.kde4/share/config/ or ~/.kde/share/config/, depending on your distro).

Ok, so I removed the only plasmoid, which was the calendar-plasmoid, and plasma stopped hogging resources completely. I thought it was kind of strange and added other plasmoids to the desktop just to see what happened. The result was that no other plasmoid had any visible effect on resource usage. However, when I add the calendar plasmoid again it goes up to 40-60% usage again.

Conclusion is that there's something fishy with the calendar-plasmoid and kde 4.2.2.

mintlars wrote:Conclusion is that there's something fishy with the calendar-plasmoid and kde 4.2.2.

Is that the standard calendar like the one that appears when you click on the clock? If it's something you downloaded from someplace else and compiled, try recompiling and reinstalling.

Alec wrote:Is that the standard calendar like the one that appears when you click on the clock? If it's something you downloaded from someplace else and compiled, try recompiling and reinstalling.

It's the standard one, so no compiling to blame there.

I also had this calender bug after upgrade to 4.2.2. . It used 60-90 % of CPU usage. Removed the calender and everything works fine again.

It's a bug, then.

You should file a bug report.

Alec wrote:It's a bug, then.

You should file a bug report.

Done. Link to bugreport