Bug 288065

Summary:	plasma-desktop uses 100% CPU after Boot for about 2min, related with calendar: Plasma crash when changed by external program
Product:	[Unmaintained] plasma4	Reporter:	it
Component:	widget-clock	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	asraniel, boboudrescu, jlayt, matija, notmart
Priority:	NOR
Version:	4.7.3
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description it 2011-12-02 15:20:54 UTC

Version: unspecified (using KDE 4.7.3)
OS: Linux

After booting the panel doesn't react for about 2 minutes (just after everything got loadet in it).
I can start any programs though with alt+F2.
htop tells me that plasma-desktop is using 100% CPU.

After the 2mins I get my messages telling that Nepumuk ain't running (I disabled that). The CPU goes down then and everything is all right.

Now I figured out, that if I diasble to show my appointments in the calendar of the system clock the problem is fixed for me.
But if I have them activated they are actually shown after the panel is finally reacting again.

I have one more problem with the calendar which is related (which ist actuelly the reason why I got to the point to turn off the calendar in the system clock):

I sync my ical file with unison between desktop and netbook. Each time the file is synced plasma crashes, leaving the running applications an X untouched. Just the panel and the wallpaper is gone, not coming back by itself, not asking to report the crash.
This also only happens if the calendar is shown in the system clock.
My calendar works fine in Kontact though. It just keeps forgetting that I activated it, also forgetting the color I assigned to it.

Reproducible: Always

Steps to Reproduce:
Replace the ical file that is set up in akonadi (copy a different one over the existing one) (To crash plasma)

I guess to reproduce the panel-hang you would need my ical file!?

Actual Results:
Panel and Wallpaper gone, programs still running, alt+F2 still works, no error message.

Expected Results:
Keep runnung ;-)

Same Problem in KDE 4.7.2

Comment 1 Beat Wolf 2011-12-02 18:18:23 UTC

This might be an akonadi issue and not a plasma one.

Comment 2 Bogdan Udrescu 2011-12-02 22:55:37 UTC

Can you post a backtrace of the crash ? It may be very helpful for the devs.

Comment 3 Aaron J. Seigo 2011-12-03 13:01:37 UTC

this is like to do with the startup code in the calendar DataEngine in void CalendarEngine::initAkonadiCalendar() 

CC'ing John Layt as he's been doing work in that area, and maybe he will have a good idea of who to poke on this one.

Comment 4 Marco Martin 2011-12-03 18:35:21 UTC

also, please include a detailed backtrace for the crash (would be better having the crash as a separate report, even)

Comment 5 it 2011-12-14 19:42:13 UTC

Hi,
as I wrote above there is no Window coming up asking to create a backtrace.

I have been trying now for quite a while to create one manually (following the tutorial) but as soon as I connect to plasma-desktop with
sudo gdb plasma-desktop 1851
the desktop won't react at all any more. It doesn't even crash.

Just as I disconnect again it continues running.

Any other idea how I can provide a backtrace?

Comment 6 Matija Šuklje 2012-09-20 22:14:13 UTC

I was having a similar issue and don’t get the crashes since 4.8.5. Can you re-test it?

Comment 7 Myriam Schweingruber 2012-10-01 12:06:54 UTC

I can't reproduce this either with KDE 4.9.1, closing for now. Please feel free to reopen if you can still reproduce this with KDE 4.9.1 or later.