Application that crashed: plasma-desktop Version of the application: 0.3 KDE Version: 4.3.00 (KDE 4.3.0) "release 158" Qt Version: 4.5.2 Operating System: Linux 2.6.27.29-0.1-default i686 What I was doing when the application crashed: Removed Tasks widget from panel, added STasks, worked fine. Removed STasks, dragged Fancy tasks to panel, placeholder appeared and plasma crashed. Worked fine afterwards. -- Backtrace: Application: Plasma Workspace (kdeinit4), signal: Segmentation fault [Current thread is 1 (Thread 0xb5e5b700 (LWP 6088))] Thread 2 (Thread 0xa6912b90 (LWP 6093)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb7cdfc35 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb7d3f582 in QWaitCondition::wait (this=0x8b2f3d8, mutex=0x8b2f3d4, time=4294967295) at thread/qwaitcondition_unix.cpp:87 #3 0xb75b4ad2 in QHostInfoAgent::run (this=0x8b2f3c8) at kernel/qhostinfo.cpp:260 #4 0xb7d3e572 in QThreadPrivate::start (arg=0x8b2f3c8) at thread/qthread_unix.cpp:188 #5 0xb7cdc1b5 in start_thread () from /lib/libpthread.so.0 #6 0xb65233be in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb5e5b700 (LWP 6088)): [KCrash Handler] #6 0xb7d390a9 in QMutex::lock (this=0x80532f0) at thread/qmutex.cpp:152 #7 0xb7e32e17 in QCoreApplication::postEvent (receiver=0x8ad41f0, event=0x97c96f8, priority=0) at kernel/qcoreapplication.cpp:1020 #8 0xb7e330dc in QCoreApplication::postEvent (receiver=0x8ad41f0, event=0x97c96f8) at kernel/qcoreapplication.cpp:973 #9 0xb7e429c7 in QObject::deleteLater (this=0x8ad41f0) at kernel/qobject.cpp:2019 #10 0xb6885099 in QX11Data::xdndHandleFinished (this=0x80c7400, xe=0xbfe8dddc, passive=false) at kernel/qdnd_x11.cpp:1244 #11 0xb685e332 in QApplication::x11ClientMessage (this=0x80bdf18, w=0x9709bb8, event=0xbfe8dddc, passive_only=240) at kernel/qapplication_x11.cpp:3124 #12 0xb6870cc2 in QApplication::x11ProcessEvent (this=0x80bdf18, event=0xbfe8dddc) at kernel/qapplication_x11.cpp:3675 #13 0xb689b5ea in x11EventSourceDispatch (s=0x80c6758, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #14 0xb63a09c8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #15 0xb63a4083 in ?? () from /usr/lib/libglib-2.0.so.0 #16 0xb63a4241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #17 0xb7e5e8d8 in QEventDispatcherGlib::processEvents (this=0x80c3b98, flags={i = -1075257448}) at kernel/qeventdispatcher_glib.cpp:327 #18 0xb689ace5 in QGuiEventDispatcherGlib::processEvents (this=0x80c3b98, flags={i = -1075257400}) at kernel/qguieventdispatcher_glib.cpp:202 #19 0xb7e3178a in QEventLoop::processEvents (this=0xbfe8e040, flags={i = -1075257336}) at kernel/qeventloop.cpp:149 #20 0xb7e31bd2 in QEventLoop::exec (this=0xbfe8e040, flags={i = -1075257272}) at kernel/qeventloop.cpp:201 #21 0xb7e34079 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #22 0xb67fa677 in QApplication::exec () at kernel/qapplication.cpp:3525 #23 0xb3826b30 in kdemain (argc=1, argv=0x80a6740) at /usr/src/debug/kdebase-workspace-4.3.0/plasma/shells/desktop/main.cpp:50 #24 0x0804e505 in launch (argc=1, _name=0x80a6694 "/usr/bin/plasma-desktop", args=0x80a66ac "", cwd=0x0, envc=0, envs=0x80a66b0 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x805163d "0") at /usr/src/debug/kdelibs-4.3.0/kinit/kinit.cpp:705 #25 0x0804ecdd in handle_launcher_request (sock=8, who=<value optimized out>) at /usr/src/debug/kdelibs-4.3.0/kinit/kinit.cpp:1197 #26 0x0804f173 in handle_requests (waitForPid=0) at /usr/src/debug/kdelibs-4.3.0/kinit/kinit.cpp:1390 #27 0x0804feb2 in main (argc=4, argv=0xbfe8ea34, envp=0xbfe8ea48) at /usr/src/debug/kdelibs-4.3.0/kinit/kinit.cpp:1825 This bug may be a duplicate of or related to bug 182511 Reported using DrKonqi
does it happen every time you drag the fancy tasks widget to the panel? or was this just a semi-random event? the backtrace itself never leaves Qt.
It worked fine after plasma restarted, so I don't think it is specific to the fancy tasks widget. I see that there are similar bugs filed for other widgets, e.g. bug 182511 (even though the crash itself is different, the 'what i was doing' is the same.) It has happened to me before with other ones in the 4.2 devel series (can't remember exactly which ones, sorry), but not every time, so i would call it a semi-random event.
Merging with bug 192000. Thanks *** This bug has been marked as a duplicate of bug 192000 ***