Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#14066 - Calendar plasmoid uses 100% CPU
Attached to Project:
Arch Linux
Opened by Zeal (Zeal) - Thursday, 02 April 2009, 08:48 GMT
Last edited by Andrea Scarpino (BaSh) - Tuesday, 14 April 2009, 12:47 GMT
Opened by Zeal (Zeal) - Thursday, 02 April 2009, 08:48 GMT
Last edited by Andrea Scarpino (BaSh) - Tuesday, 14 April 2009, 12:47 GMT
|
DetailsDescription:
Calendar plasmoid uses 100% CPU This is known bug but i tought to add it here too. I got it when i installed KDE 4.2.2 but there are reports of this allso from 4.2.1 on suse distribution. Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: This seems to appear on random for some people but i got it when i updated my KDE from 4.2.1 to 4.2.2 and had calendar plasmoid used on desktop. |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Tuesday, 14 April 2009, 12:47 GMT
Reason for closing: Fixed
Additional comments about closing: patch applied in kdebase-workspace-4.2.2-2
Tuesday, 14 April 2009, 12:47 GMT
Reason for closing: Fixed
Additional comments about closing: patch applied in kdebase-workspace-4.2.2-2
if you dont provide _all_ infos you have found, the developers cannot even imagine what's going wrong.
Simple: If you have more infos, like bugreports or the "other forums" you mentioned here, be sure to INCLUDE that into your bug or no one will be able to reproduce this issue or even find a solution to it...
Telepathy was not invented so far (or did i miss it?), so this is a must ;)
Looks like the fix will be in KDE 4.2.3.