Application: plasma-desktop (0.4) KDE Platform Version: 4.6.00 (4.6.0) "release 6" Qt Version: 4.7.1 Operating System: Linux 2.6.37.1-1.2-desktop x86_64 Distribution: "openSUSE 11.4 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Trying to add firefox to the daisy launcher - Unusual behavior I noticed: upon minimizing windows to verify it crashes - Custom settings of the application: fade effect glide effect desktop grid custom command f8 The crash can be reproduced every time. -- Backtrace: Application: Plasma Desktop Shell (kdeinit4), signal: Segmentation fault [Current thread is 1 (Thread 0x7f739b116760 (LWP 3298))] Thread 2 (Thread 0x7f7378c44700 (LWP 3347)): #0 0x00007f739880a503 in poll () from /lib64/libc.so.6 #1 0x00007f739567c114 in ?? () from /lib64/libglib-2.0.so.0 #2 0x00007f739567c650 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x00007f7399dfb976 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #4 0x00007f7399dd0052 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #5 0x00007f7399dd0265 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #6 0x00007f7399ce51e4 in QThread::exec() () from /usr/lib64/libQtCore.so.4 #7 0x00007f7399db1968 in ?? () from /usr/lib64/libQtCore.so.4 #8 0x00007f7399ce7a5e in ?? () from /usr/lib64/libQtCore.so.4 #9 0x00007f7399a58a3f in start_thread () from /lib64/libpthread.so.0 #10 0x00007f739881367d in clone () from /lib64/libc.so.6 #11 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f739b116760 (LWP 3298)): [KCrash Handler] #6 0x00007f7399de780e in QObject::installEventFilter(QObject*) () from /usr/lib64/libQtCore.so.4 #7 0x00007f7390bd6411 in Plasma::ToolTipManager::registerWidget(QGraphicsWidget*) () from /usr/lib64/libplasma.so.3 #8 0x00007f7390bd6527 in Plasma::ToolTipManager::setContent(QGraphicsWidget*, Plasma::ToolTipContent const&) () from /usr/lib64/libplasma.so.3 #9 0x00007f7369e640a8 in ?? () from /usr/lib64/kde4/plasma_applet_daisy.so #10 0x00007f7369e64a91 in ?? () from /usr/lib64/kde4/plasma_applet_daisy.so #11 0x00007f7369e67f12 in ?? () from /usr/lib64/kde4/plasma_applet_daisy.so #12 0x00007f7399de5def in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4 #13 0x00007f739aac7f82 in KWindowSystem::activeWindowChanged(unsigned long) () from /usr/lib64/libkdeui.so.5 #14 0x00007f739ac02c7a in ?? () from /usr/lib64/libkdeui.so.5 #15 0x00007f739ab9b50e in KApplication::x11EventFilter(_XEvent*) () from /usr/lib64/libkdeui.so.5 #16 0x00007f738aa18ab7 in ?? () from /usr/lib64/libkdeinit4_plasma-desktop.so #17 0x00007f7398feecc5 in ?? () from /usr/lib64/libQtGui.so.4 #18 0x00007f7398ffcce0 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/libQtGui.so.4 #19 0x00007f73990250f2 in ?? () from /usr/lib64/libQtGui.so.4 #20 0x00007f739567bbd3 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #21 0x00007f739567c3b0 in ?? () from /lib64/libglib-2.0.so.0 #22 0x00007f739567c650 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #23 0x00007f7399dfb91f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #24 0x00007f7399024d8e in ?? () from /usr/lib64/libQtGui.so.4 #25 0x00007f7399dd0052 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #26 0x00007f7399dd0265 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #27 0x00007f7399dd46ab in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #28 0x00007f738aa02da8 in kdemain () from /usr/lib64/libkdeinit4_plasma-desktop.so #29 0x00000000004075e9 in _start () Possible duplicates by query: bug 269473, bug 264553, bug 261040, bug 254412. Reported using DrKonqi
- Does this happen with any other launcher ? - Have you mentioned this to the Daisy widget developers ? (consider that it is an unofficial add-on) Regards
*** This bug has been marked as a duplicate of bug 254412 ***