Bug 255437 - Plasma crashes randomly and now repeatedly on login (even after a reboot)
Summary: Plasma crashes randomly and now repeatedly on login (even after a reboot)
Status: RESOLVED NOT A BUG
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 255880 256202 262489 264555 266675 268566 273163 275594 276239 276757 277198 279747 279836 279964 280411 280752 281007 281225 281401 281480 282013 282048 282072 282120 282144 282326 282532 282580 282993 283121 283193 283543 283894 284320 284589 284664 285417 285621 286542 286670 287041 287171 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-10-27 21:36 UTC by sam
Modified: 2012-08-28 02:20 UTC (History)
40 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (5.39 KB, text/plain)
2011-11-21 17:22 UTC, Marcin Gil
Details
New crash information added by DrKonqi (5.13 KB, text/plain)
2012-01-24 18:38 UTC, Tim Henderson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description sam 2010-10-27 21:36:09 UTC
Application: plasma-desktop (0.3)
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-22-generic x86_64
Distribution: Ubuntu 10.10

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

* For this report the specific activity is trying to log-in via NX desktop.

- Unusual behavior I noticed:

* Crash handler immediately opens reporting a crash by plasma-desktop

* There is no taskbar but Alt+F2 opens the run command dialog and it is possible to start konsole

* some apps, ie: emacs, start fine from konsole but many report problems with the ibus-daemon.

* trying to restart the desktop (/usr/bin/plasma-desktop) from konsole returns many error messages about not being able to connect with ibus-daemon and problems with various configuration parameters (see attached crash.txt capture of output from attempt to run plasma-desktop from konsole.)

* Attempting to log into another account on the same workstation via NX works fine - no crash - but I'm not sure where the offending data might be in my main account? Please let me know so that I can delete it.

* will try to append crash reports showing similar crashes that occur when trying to log-in from the local keyboard/screen.

* Plasma will also crash after leaving the desktop alone for a few days (while remotely accessing virtual PC's running on it.)

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma Workspace (plasma-desktop), signal: Aborted
[Current thread is 1 (Thread 0x7f0922828780 (LWP 8029))]

Thread 3 (Thread 0x7f08fe90c710 (LWP 8035)):
#0  0x00007f09221391d3 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f0916b8e009 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007f0916b8e45c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007f091f13e1e6 in QEventDispatcherGlib::processEvents (this=0x3156360, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:417
#4  0x00007f091f110a02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007f091f110dec in QEventLoop::exec (this=0x7f08fe90bd90, flags=) at kernel/qeventloop.cpp:201
#6  0x00007f091f01b2fd in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#7  0x00007f091f0f05f8 in QInotifyFileSystemWatcherEngine::run (this=0x3183d60) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f091f01e27e in QThreadPrivate::start (arg=0x3183d60) at thread/qthread_unix.cpp:266
#9  0x00007f091ed93971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#10 0x00007f092214591d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f08f7bdc710 (LWP 8082)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:212
#1  0x00007f091f01eda2 in wait (this=<value optimized out>, mutex=0x35110a0, time=30000) at thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x35110a0, time=30000) at thread/qwaitcondition_unix.cpp:160
#3  0x00007f091f013da2 in QThreadPoolThread::run (this=0x34a83b0) at concurrent/qthreadpool.cpp:140
#4  0x00007f091f01e27e in QThreadPrivate::start (arg=0x34a83b0) at thread/qthread_unix.cpp:266
#5  0x00007f091ed93971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#6  0x00007f092214591d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f0922828780 (LWP 8029)):
[KCrash Handler]
#6  0x00007f0922092ba5 in raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007f09220966b0 in abort () at abort.c:92
#8  0x00007f091de596bd in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6
#9  0x00007f091de57906 in ?? () from /usr/lib/libstdc++.so.6
#10 0x00007f091de57933 in std::terminate() () from /usr/lib/libstdc++.so.6
#11 0x00007f091de57a86 in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#12 0x00007f091f110f3d in QEventLoop::exec (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventloop.cpp:214
#13 0x00007f091f114ebb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#14 0x00007f092241ca56 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_plasma-desktop.so
#15 0x00007f092207dd8e in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff12698488) at libc-start.c:226
#16 0x0000000000400669 in _start ()

Possible duplicates by query: bug 255434, bug 255429, bug 255399, bug 255393, bug 255391.

Reported using DrKonqi
Comment 1 Dario Andres 2011-01-01 18:06:37 UTC
[Comment from a bug triager]
- Which plasmoids do you have in your system ? Any third-party one ?
That kind of error is likely to be caused by some kind of third-party components/plasmoids loaded in Plasma.

Regards
Comment 2 Aaron J. Seigo 2011-11-20 20:18:21 UTC
*** Bug 286542 has been marked as a duplicate of this bug. ***
Comment 3 Beat Wolf 2011-11-20 21:58:43 UTC
*** Bug 287041 has been marked as a duplicate of this bug. ***
Comment 4 Beat Wolf 2011-11-20 21:59:05 UTC
*** Bug 286670 has been marked as a duplicate of this bug. ***
Comment 5 Beat Wolf 2011-11-20 21:59:11 UTC
*** Bug 285621 has been marked as a duplicate of this bug. ***
Comment 6 Beat Wolf 2011-11-20 21:59:27 UTC
*** Bug 285417 has been marked as a duplicate of this bug. ***
Comment 7 Beat Wolf 2011-11-20 21:59:43 UTC
*** Bug 284664 has been marked as a duplicate of this bug. ***
Comment 8 Beat Wolf 2011-11-20 21:59:54 UTC
*** Bug 284589 has been marked as a duplicate of this bug. ***
Comment 9 Beat Wolf 2011-11-20 22:00:06 UTC
*** Bug 284320 has been marked as a duplicate of this bug. ***
Comment 10 Beat Wolf 2011-11-20 22:00:18 UTC
*** Bug 283894 has been marked as a duplicate of this bug. ***
Comment 11 Beat Wolf 2011-11-20 22:00:24 UTC
*** Bug 283543 has been marked as a duplicate of this bug. ***
Comment 12 Beat Wolf 2011-11-20 22:00:32 UTC
*** Bug 283193 has been marked as a duplicate of this bug. ***
Comment 13 Beat Wolf 2011-11-20 22:00:38 UTC
*** Bug 282993 has been marked as a duplicate of this bug. ***
Comment 14 Beat Wolf 2011-11-20 22:00:59 UTC
*** Bug 282532 has been marked as a duplicate of this bug. ***
Comment 15 Beat Wolf 2011-11-20 22:01:14 UTC
*** Bug 282326 has been marked as a duplicate of this bug. ***
Comment 16 Beat Wolf 2011-11-20 22:01:22 UTC
*** Bug 282144 has been marked as a duplicate of this bug. ***
Comment 17 Beat Wolf 2011-11-20 22:01:50 UTC
*** Bug 282072 has been marked as a duplicate of this bug. ***
Comment 18 Beat Wolf 2011-11-20 22:02:01 UTC
*** Bug 282048 has been marked as a duplicate of this bug. ***
Comment 19 Beat Wolf 2011-11-20 22:02:06 UTC
*** Bug 281480 has been marked as a duplicate of this bug. ***
Comment 20 Beat Wolf 2011-11-20 22:02:12 UTC
*** Bug 281401 has been marked as a duplicate of this bug. ***
Comment 21 Beat Wolf 2011-11-20 22:02:21 UTC
*** Bug 281225 has been marked as a duplicate of this bug. ***
Comment 22 Beat Wolf 2011-11-20 22:02:44 UTC
*** Bug 281007 has been marked as a duplicate of this bug. ***
Comment 23 Beat Wolf 2011-11-20 22:03:11 UTC
*** Bug 280752 has been marked as a duplicate of this bug. ***
Comment 24 Beat Wolf 2011-11-20 22:03:30 UTC
*** Bug 280411 has been marked as a duplicate of this bug. ***
Comment 25 Beat Wolf 2011-11-20 22:03:47 UTC
*** Bug 279964 has been marked as a duplicate of this bug. ***
Comment 26 Beat Wolf 2011-11-20 22:03:52 UTC
*** Bug 279836 has been marked as a duplicate of this bug. ***
Comment 27 Beat Wolf 2011-11-20 22:03:59 UTC
*** Bug 277198 has been marked as a duplicate of this bug. ***
Comment 28 Beat Wolf 2011-11-20 22:04:06 UTC
*** Bug 276757 has been marked as a duplicate of this bug. ***
Comment 29 Beat Wolf 2011-11-20 22:04:11 UTC
*** Bug 276239 has been marked as a duplicate of this bug. ***
Comment 30 Beat Wolf 2011-11-20 22:04:27 UTC
*** Bug 275594 has been marked as a duplicate of this bug. ***
Comment 31 Beat Wolf 2011-11-20 22:04:34 UTC
*** Bug 273163 has been marked as a duplicate of this bug. ***
Comment 32 Beat Wolf 2011-11-20 22:05:47 UTC
*** Bug 268566 has been marked as a duplicate of this bug. ***
Comment 33 Beat Wolf 2011-11-20 22:06:11 UTC
*** Bug 266675 has been marked as a duplicate of this bug. ***
Comment 34 Beat Wolf 2011-11-20 22:06:24 UTC
*** Bug 262489 has been marked as a duplicate of this bug. ***
Comment 35 Beat Wolf 2011-11-20 22:06:31 UTC
*** Bug 255880 has been marked as a duplicate of this bug. ***
Comment 36 Ilia K. 2011-11-21 08:28:48 UTC
Wow, 35 plasma crash reports for an exception thrown by a wild applet.
IIRC there was a discussion a while ago, whether to make each applet a separate process (gnome does this?) or a part of a plasma process. This bug report looks like a big argument in favor of the multi-process approach.
Comment 37 Dominik Steenken 2011-11-21 08:53:22 UTC
... Are you telling me that so far, any random applet crashing can bring down all of plasma... ? o-O
Comment 38 Aaron J. Seigo 2011-11-21 09:14:02 UTC
*** Bug 256202 has been marked as a duplicate of this bug. ***
Comment 39 Aaron J. Seigo 2011-11-21 09:14:08 UTC
*** Bug 264555 has been marked as a duplicate of this bug. ***
Comment 40 Aaron J. Seigo 2011-11-21 09:16:39 UTC
*** Bug 283121 has been marked as a duplicate of this bug. ***
Comment 41 Aaron J. Seigo 2011-11-21 09:17:03 UTC
*** Bug 282580 has been marked as a duplicate of this bug. ***
Comment 42 Aaron J. Seigo 2011-11-21 09:17:15 UTC
*** Bug 282120 has been marked as a duplicate of this bug. ***
Comment 43 Aaron J. Seigo 2011-11-21 09:17:42 UTC
*** Bug 282013 has been marked as a duplicate of this bug. ***
Comment 44 Aaron J. Seigo 2011-11-21 09:18:40 UTC
*** Bug 279747 has been marked as a duplicate of this bug. ***
Comment 45 Aaron J. Seigo 2011-11-21 09:25:22 UTC
so .. while there are numerous duplicates marked here, they are not, indeed all duplicates. what each of these crashes is is this: a single add-on (usually a plasmoid, and usually one not provided by upstream KDE) is causing an error inside an event handler which results in an exception being thrown.

many times third party plasmoids downloaded from kde-apps.org or elswhere are implicated; sometimes it's only after an upgrade (implying that some third party plasmoids are likely linking to libraries that are not ABI stable; we know this happens and it causes no end of grief for their users); sometimes it is the network manager stack.

in any case, none of these reports gives us something that we can identify or, if the general source of the problem is identifiable, it's not something we (upstream) can fix.

as for the comments on in-process vs out-of-process, i invite you to read the code so as to understand what is going on and why it is that way. then, if you have any informed and implementable solution ("make the out of process" does not count as it does include the all important "how") bring it to the dev list. otherwise, none of us have time for the peanut gallery sharing opinions that are based on supposition and nothing else.
Comment 46 Dominik Steenken 2011-11-21 09:40:16 UTC
While i understand where you're coming from, i think you should also appreciate that it is pretty frustrating for users who experience random crashes (from their perspective) out of nowhere when "not our problem" is the response they get from community support whereever they turn.

Even if i knew which plasmoid is causing the problem i doubt very much that i would get much heelp from its original developer.

I don't have the time or or energy to look through code i know nothing about so i will accept your explanation that insulating plasma from exceptions thrown by plasmoids is non-trivial. The explanation would have been enough though - there is no need for snarky comments.
Comment 47 Beat Wolf 2011-11-21 15:20:47 UTC
*** Bug 287171 has been marked as a duplicate of this bug. ***
Comment 48 sam 2011-11-21 16:32:47 UTC
Hi Folks, 

Let's review quickly:

* major failure - desktop crashes and is not usable

* the only error message provided is the crash reporting tool (hence all the reports.)

* dev team evaluation: bug in third party modules can bring down the desktop

Conclusion:

* As there will always be bugs in third party modules we can conclude that reports will continue to flood into the bug tracker.

Of course, if the desktop code could be modified, somehow, to emit a warning about the third-party module that caused the problem:

* users would disable the offending module
* bug reports would be filed against that module instead of against the desktop.

So I suggest you change the resolution to LATER and think about how it might be possible to catch the error so that the necessary warning can be produced. It might be possible to include such a feature in a future release of the desktop.

Thanks again for your excellent service!

Take care,
Ttys,
Sam.
Comment 49 Marcin Gil 2011-11-21 17:22:38 UTC
Created attachment 65913 [details]
New crash information added by DrKonqi

plasma-desktop (0.4) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4

- What I was doing when the application crashed:

Logged in.
Applets: Message indicator, dropbox, kontact (kmail + akregator), choqok, Kopete, nepomuk, volume, devices, akonadi tray, bluetooth, printer, network mgmt, korganizer daemon.

-- Backtrace (Reduced):
#6  0x00007fdadcd243a5 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007fdadcd27b0b in __GI_abort () at abort.c:92
[...]
#12 0x00007fdad9f8a02e in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#13 0x00007fdad9f8e789 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#14 0x00007fdadd0ce1a3 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_plasma-desktop.so
Comment 50 Tim Henderson 2012-01-24 18:38:40 UTC
Created attachment 68146 [details]
New crash information added by DrKonqi

plasma-desktop (0.4) on KDE Platform 4.7.3 (4.7.3) using Qt 4.7.4

- What I was doing when the application crashed:

I opened Korganizer for the first time and tried to associate some remote iCal calendars. This is when the crashing started.

- Unusual behavior I noticed:

There is no automatic restart. It has to be restarted manually. I may be related to Akonadi

-- Backtrace (Reduced):
#8  0x00007f6ab271fd7d in __gnu_cxx::__verbose_terminate_handler () at ../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95
#9  0x00007f6ab271df26 in __cxxabiv1::__terminate (handler=<optimized out>) at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:40
#10 0x00007f6ab271df53 in std::terminate () at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:50
#11 0x00007f6ab271e096 in __cxxabiv1::__cxa_rethrow () at ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:116
#12 0x00007f6ab37b602e in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
Comment 51 schneiderpj63366 2012-08-28 02:20:32 UTC
Application: Plasma Desktop Shell (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f1a3c20b760 (LWP 4723))]

Thread 4 (Thread 0x7f1a16856700 (LWP 4753)):
#0  0x00007f1a39889ff3 in poll () from /lib64/libc.so.6
#1  0x00007f1a3667dae8 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f1a3667dfa9 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f1a3ae9b586 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#4  0x00007f1a3ae6fa32 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#5  0x00007f1a3ae6fc2f in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#6  0x00007f1a3ad875df in QThread::exec() () from /usr/lib64/libQtCore.so.4
#7  0x00007f1a3ae52aff in ?? () from /usr/lib64/libQtCore.so.4
#8  0x00007f1a3ad8a025 in ?? () from /usr/lib64/libQtCore.so.4
#9  0x00007f1a2beb6b74 in ?? () from /usr/X11R6/lib64/libGL.so.1
#10 0x00007f1a3aaf9f05 in start_thread () from /lib64/libpthread.so.0
#11 0x00007f1a3989310d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f1a0ffff700 (LWP 4761)):
#0  0x00007f1a39889ff3 in poll () from /lib64/libc.so.6
#1  0x00007f1a3667dae8 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f1a3667dfa9 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f1a3ae9b586 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#4  0x00007f1a3ae6fa32 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#5  0x00007f1a3ae6fc2f in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#6  0x00007f1a3ad875df in QThread::exec() () from /usr/lib64/libQtCore.so.4
#7  0x00007f1a3ae52aff in ?? () from /usr/lib64/libQtCore.so.4
#8  0x00007f1a3ad8a025 in ?? () from /usr/lib64/libQtCore.so.4
#9  0x00007f1a2beb6b74 in ?? () from /usr/X11R6/lib64/libGL.so.1
#10 0x00007f1a3aaf9f05 in start_thread () from /lib64/libpthread.so.0
#11 0x00007f1a3989310d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f1a0e79b700 (LWP 4763)):
#0  0x00007f1a39889ff3 in poll () from /lib64/libc.so.6
#1  0x00007f1a3667dae8 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f1a3667dfa9 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f1a3ae9b586 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#4  0x00007f1a3ae6fa32 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#5  0x00007f1a3ae6fc2f in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#6  0x00007f1a3ad875df in QThread::exec() () from /usr/lib64/libQtCore.so.4
#7  0x00007f1a3ae52aff in ?? () from /usr/lib64/libQtCore.so.4
#8  0x00007f1a3ad8a025 in ?? () from /usr/lib64/libQtCore.so.4
#9  0x00007f1a2beb6b74 in ?? () from /usr/X11R6/lib64/libGL.so.1
#10 0x00007f1a3aaf9f05 in start_thread () from /lib64/libpthread.so.0
#11 0x00007f1a3989310d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f1a3c20b760 (LWP 4723)):
[KCrash Handler]
#6  0x00007f1a3adce6e7 in QString::operator=(QString const&) () from /usr/lib64/libQtCore.so.4
#7  0x00007f1a1e18b36a in ?? () from /usr/lib64/kde4/plasma_applet_worldclock.so
#8  0x00007f1a318e0ac5 in ?? () from /usr/lib64/libplasma.so.3
#9  0x00007f1a318f5032 in ?? () from /usr/lib64/libplasma.so.3
#10 0x00007f1a318f5d04 in Plasma::Corona::loadLayout(QString const&) () from /usr/lib64/libplasma.so.3
#11 0x00007f1a318f5dcc in Plasma::Corona::initializeLayout(QString const&) () from /usr/lib64/libplasma.so.3
#12 0x00007f1a27c55cdb in ?? () from /usr/lib64/libkdeinit4_plasma-desktop.so
#13 0x00007f1a27c55ffa in ?? () from /usr/lib64/libkdeinit4_plasma-desktop.so
#14 0x00007f1a27c577d2 in ?? () from /usr/lib64/libkdeinit4_plasma-desktop.so
#15 0x00007f1a3ae8715a in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#16 0x00007f1a3a026b04 in QApplication::event(QEvent*) () from /usr/lib64/libQtGui.so.4
#17 0x00007f1a3a022c34 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#18 0x00007f1a3a027ac1 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#19 0x00007f1a3bc02e36 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#20 0x00007f1a3ae7082c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#21 0x00007f1a3ae73c08 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#22 0x00007f1a3ae9b0c3 in ?? () from /usr/lib64/libQtCore.so.4
#23 0x00007f1a3667d5dd in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#24 0x00007f1a3667ddd8 in ?? () from /usr/lib64/libglib-2.0.so.0
#25 0x00007f1a3667dfa9 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#26 0x00007f1a3ae9b51f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#27 0x00007f1a3a0c5f9e in ?? () from /usr/lib64/libQtGui.so.4
#28 0x00007f1a3ae6fa32 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#29 0x00007f1a3ae6fc2f in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#30 0x00007f1a3ae73df7 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#31 0x00007f1a27c3c773 in kdemain () from /usr/lib64/libkdeinit4_plasma-desktop.so
#32 0x0000000000408897 in _start ()