Bug 282326

Summary:	Plasma crashes after boot
Product:	[Unmaintained] plasma4	Reporter:	Richard Homonnai <Chain>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	asraniel
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Richard Homonnai 2011-09-19 08:36:54 UTC

Application: plasma-desktop (0.4)
KDE Platform Version: 4.7.1 (4.7.1)
Qt Version: 4.7.2
Operating System: Linux 2.6.39-gentoo-r3-richIx61t x86_64
Distribution: "Gentoo Base System release 2.0.3"

-- Information about the crash:
- What I was doing when the application crashed:

Nothing, but I guess, that Akonadi has it's fingers in there, as I can read the following in the logs:

chain@richIx61t ~ $ plasma-desktop(3098)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 
QGridLayoutEngine::addItem: Cell (1, 1) already taken
QGraphicsLinearLayout::itemAt: invalid index 6
plasma-desktop(3098)/libakonadi Akonadi::EntityTreeModelPrivate::fetchJobDone: Job error:  "Unbekanntes Fehler. (Cannot select this collection)" 

plasma-desktop(3098)/libakonadi Akonadi::MonitorPrivate::slotStatisticsChangedFinished: Error on fetching collection statistics:  "No status for this folder" 
Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

terminate called after throwing an instance of 'Akonadi::PayloadException'
  what():  Akonadi::PayloadException: No payload set
KCrash: Attempting to start /usr/bin/plasma-desktop from kdeinit
sock_file=/home/chain/.kde4/socket-richIx61t/kdeinit4__0
KCrash: Application 'plasma-desktop' crashing...
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit                                                                                                         
sock_file=/home/chain/.kde4/socket-richIx61t/kdeinit4__0

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma-Desktop-Umgebung (plasma-desktop), signal: Aborted
[Current thread is 1 (Thread 0x7f0d43245780 (LWP 3098))]

Thread 5 (Thread 0x7f0d22963700 (LWP 3099)):
#0  0x00007f0d42954263 in poll () from /lib64/libc.so.6
#1  0x00007f0d3730afb9 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f0d3730b40c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f0d3fa36dc6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#4  0x00007f0d3fa099e2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#5  0x00007f0d3fa09dc4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#6  0x00007f0d3f91648d in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4
#7  0x00007f0d3f9e9a08 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#8  0x00007f0d3f9194b5 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#9  0x00007f0d3f686c1a in start_thread () from /lib64/libpthread.so.0
#10 0x00007f0d4295ceed in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f0d1eafc700 (LWP 3102)):
#0  0x00007f0d3f68b8eb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f0d3f919ff1 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/qt4/libQtCore.so.4
#2  0x00007f0d3f90dbf1 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#3  0x00007f0d3f9194b5 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#4  0x00007f0d3f686c1a in start_thread () from /lib64/libpthread.so.0
#5  0x00007f0d4295ceed in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f0d1d45e700 (LWP 3103)):
#0  0x00007f0d3f68b8eb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f0d3f919ff1 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/qt4/libQtCore.so.4
#2  0x00007f0d3f90dbf1 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#3  0x00007f0d3f9194b5 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#4  0x00007f0d3f686c1a in start_thread () from /lib64/libpthread.so.0
#5  0x00007f0d4295ceed in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f0d1cc5d700 (LWP 3104)):
#0  0x00007f0d3f68b8eb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f0d3f919ff1 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/qt4/libQtCore.so.4
#2  0x00007f0d3f90dbf1 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#3  0x00007f0d3f9194b5 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#4  0x00007f0d3f686c1a in start_thread () from /lib64/libpthread.so.0
#5  0x00007f0d4295ceed in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f0d43245780 (LWP 3098)):
[KCrash Handler]
#6  0x00007f0d428bd355 in raise () from /lib64/libc.so.6
#7  0x00007f0d428be5ef in abort () from /lib64/libc.so.6
#8  0x00007f0d3e783d95 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/libstdc++.so.6
#9  0x00007f0d3e7821c6 in ?? () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/libstdc++.so.6
#10 0x00007f0d3e7821f3 in std::terminate() () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/libstdc++.so.6
#11 0x00007f0d3e782275 in __cxa_rethrow () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/libstdc++.so.6
#12 0x00007f0d3fa09f13 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#13 0x00007f0d3fa0de3b in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4
#14 0x00007f0d42e48643 in kdemain () from /usr/lib64/libkdeinit4_plasma-desktop.so
#15 0x00007f0d428a9d2d in __libc_start_main () from /lib64/libc.so.6
#16 0x00000000004007b9 in _start ()

Possible duplicates by query: bug 282322, bug 282321, bug 282308, bug 282306, bug 282291.

Reported using DrKonqi

Comment 1 Richard Homonnai 2011-10-11 08:29:15 UTC

I found out what's causing this. It's also related to the bug where nepomuk_calendar_feeder eats all CPU.

In short, it is related to the calendars on pagancalendar.co.uk.

Adding one of those immediately lets Akonadi go crazy (I think it refreshes over and over again!) and at some time (a few seconds later) Plasma crashes.

One of those calendars is:

http://pagancalendar.co.uk/pagancalendarcouk2.php?cal=MoonPhase

I had this one because of the moon phases, and it caused all the problems I reported. Now that I am not using it, all problems are gone. Still, I think, this should be fixed :)

Comment 2 Beat Wolf 2011-11-20 22:01:14 UTC


*** This bug has been marked as a duplicate of bug 255437 ***