Bug 195982 - Task Manager: Iceweasel drag and drop causes crash
Summary: Task Manager: Iceweasel drag and drop causes crash
Status: RESOLVED DUPLICATE of bug 181593
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-11 09:51 UTC by David
Modified: 2009-06-12 14:57 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David 2009-06-11 09:51:12 UTC
Version:            (using KDE 4.2.4)
OS:                Linux
Installed from:    Debian testing/unstable Packages

If I start up a lot of Iceweasel (aka Debian Firefox) sessions, then the Task Manager groups some most of them, and has a few individual sessions in the system tray.

If I then try to drag over one of the individual Iceweasel sessions onto the stack, then the Task Manager crashes.

I did some more testing, and I think that the ungrouped sessions are actually place-holders for Iceweasel sessions that KDE is still trying to start. I think that when you drag one of those onto a group (of actually-running Iceweasel instances), that the Task Manager will crash.
Comment 1 Marco Martin 2009-06-11 12:33:06 UTC
can you reproduce the crash and generate a full backtrace? 
see
http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports
Comment 2 David 2009-06-11 12:53:30 UTC
The crash is easily reproducible on my system, and happens every time. Steps:

1. Start up firefox a lot of times, until the additional sessions take a while to load (so you get extra "placeholder" entries in the task manager).

2. Mouse-drag the placeholder over to the existing group in the Task Tray and release the mouse.

And thanks for the URL, but how do I see the stack trace for the Task Manager? I don't know how to run it separately on the command-line, or if that's even possible.
Comment 3 Dario Andres 2009-06-12 00:25:00 UTC
You need to install the "kdebase-workspace-dbg" package (and may be "kdelibs5-dbg" too), then, when Plasma crashes just click the "Show Details" checkbox in the Crash Handler dialog, and you will get the backtrace. Finally, paste it here inline. Thanks!
Comment 4 David 2009-06-12 11:08:46 UTC
Thanks for the information. Here is the backtrace:

Application: Plasma Workspace (plasma), signal SIGSEGV
[Current thread is 0 (LWP 20877)]

Thread 3 (Thread 0xa85d8b90 (LWP 20880)):
#0  0xb7f93424 in __kernel_vsyscall ()
#1  0xb4fa0fb5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb7ea105d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb67cc822 in QWaitCondition::wait (this=0x8e02628, mutex=0x8e02624, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  0xb524bfd2 in QHostInfoAgent::run (this=0x8e02618) at kernel/qhostinfo.cpp:260
#5  0xb67cb80e in QThreadPrivate::start (arg=0x8e02618) at thread/qthread_unix.cpp:189
#6  0xb4f9d4e5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb7e9221e in clone () from /lib/i686/cmov/libc.so.6

Thread 2 (Thread 0xa79a2b90 (LWP 20881)):
#0  0xb7f93424 in __kernel_vsyscall ()
#1  0xb4fa0fb5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb7ea105d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb67cc822 in QWaitCondition::wait (this=0x8ce4998, mutex=0x8ce4994, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  0xa8882b3a in RenderThread::run (this=0x8ce498c) at ../../../../plasma/wallpapers/image/renderthread.cpp:91
#5  0xb67cb80e in QThreadPrivate::start (arg=0x8ce498c) at thread/qthread_unix.cpp:189
#6  0xb4f9d4e5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb7e9221e in clone () from /lib/i686/cmov/libc.so.6

Thread 1 (Thread 0xb3cbe730 (LWP 20877)):
[KCrash Handler]
#6  0xa8719022 in WindowTaskItem::setAdditionalMimeData (this=0x98a0cf0, mimeData=0x98a0130) at ../../../../plasma/applets/tasks/windowtaskitem.cpp:298
#7  0xa8722898 in AbstractTaskItem::mouseMoveEvent (this=0x98a0cf0, event=0xbfeaf8f0) at ../../../../plasma/applets/tasks/abstracttaskitem.cpp:287
#8  0xb71a01c0 in QGraphicsItem::sceneEvent (this=0x98a0cf8, event=0xbfeaf8f0) at graphicsview/qgraphicsitem.cpp:5005
#9  0xb71f055f in QGraphicsWidget::sceneEvent (this=0x98a0cf0, event=0xbfeaf8f0) at graphicsview/qgraphicswidget.cpp:1110
#10 0xb71c57fc in QGraphicsScenePrivate::sendEvent (this=0x8a3fb48, item=0x98a0cf8, event=0xbfeaf8f0) at graphicsview/qgraphicsscene.cpp:1159
#11 0xb71c6e62 in QGraphicsScenePrivate::sendMouseEvent (this=0x8a3fb48, mouseEvent=0xbfeaf8f0) at graphicsview/qgraphicsscene.cpp:1230
#12 0xb71d161d in QGraphicsScene::mouseMoveEvent (this=0x8a39830, mouseEvent=0xbfeaf8f0) at graphicsview/qgraphicsscene.cpp:4424
#13 0xb71d317a in QGraphicsScene::event (this=0x8a39830, event=0xbfeaf8f0) at graphicsview/qgraphicsscene.cpp:3807
#14 0xb6b6b7bc in QApplicationPrivate::notify_helper (this=0x89bc7d8, receiver=0x8a39830, e=0xbfeaf8f0) at kernel/qapplication.cpp:4057
#15 0xb6b73ace in QApplication::notify (this=0x89bf8a0, receiver=0x8a39830, e=0xbfeaf8f0) at kernel/qapplication.cpp:3604
#16 0xb78125ed in KApplication::notify (this=0x89bf8a0, receiver=0x8a39830, event=0xbfeaf8f0) at ../../kdeui/kernel/kapplication.cpp:307
#17 0xb68bea2b in QCoreApplication::notifyInternal (this=0x89bf8a0, receiver=0x8a39830, event=0xbfeaf8f0) at kernel/qcoreapplication.cpp:610
#18 0xb71e1488 in QGraphicsViewPrivate::mouseMoveEventHandler (this=0x8e3bf68, event=0xbfeb002c) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#19 0xb71e4c43 in QGraphicsView::mouseMoveEvent (this=0x8e3bba8, event=0xbfeb002c) at graphicsview/qgraphicsview.cpp:3299
#20 0xb6bc221d in QWidget::event (this=0x8e3bba8, event=0xbfeb002c) at kernel/qwidget.cpp:7506
#21 0xb6f9c3e3 in QFrame::event (this=0x8e3bba8, e=0xbfeb002c) at widgets/qframe.cpp:559
#22 0xb703c39f in QAbstractScrollArea::viewportEvent (this=0x8e3bba8, e=0x0) at widgets/qabstractscrollarea.cpp:962
#23 0xb71e5682 in QGraphicsView::viewportEvent (this=0x8e3bba8, event=0xbfeb002c) at graphicsview/qgraphicsview.cpp:2897
#24 0xb703e9a5 in QAbstractScrollAreaFilter::eventFilter (this=0x8e47fc8, o=0x8e480a0, e=0xbfeb002c) at widgets/qabstractscrollarea_p.h:100
#25 0xb68bdc4a in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=0x89bc7d8, receiver=0x8e480a0, event=0xbfeb002c) at kernel/qcoreapplication.cpp:726
#26 0xb6b6b79a in QApplicationPrivate::notify_helper (this=0x89bc7d8, receiver=0x8e480a0, e=0xbfeb002c) at kernel/qapplication.cpp:4053
#27 0xb6b74441 in QApplication::notify (this=0x89bf8a0, receiver=0x8e480a0, e=0xbfeb002c) at kernel/qapplication.cpp:3759
#28 0xb78125ed in KApplication::notify (this=0x89bf8a0, receiver=0x8e480a0, event=0xbfeb002c) at ../../kdeui/kernel/kapplication.cpp:307
#29 0xb68bea2b in QCoreApplication::notifyInternal (this=0x89bf8a0, receiver=0x8e480a0, event=0xbfeb002c) at kernel/qcoreapplication.cpp:610
#30 0xb6b734ae in QApplicationPrivate::sendMouseEvent (receiver=0x8e480a0, event=0xbfeb002c, alienWidget=0x8e480a0, nativeWidget=0x8e3bba8, buttonDown=0xb74189e0, lastMouseReceiver=@0xb74189e4)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216
#31 0xb6be2dc5 in QETWidget::translateMouseEvent (this=0x8e3bba8, event=0xbfeb15dc) at kernel/qapplication_x11.cpp:4448
#32 0xb6be2266 in QApplication::x11ProcessEvent (this=0x89bf8a0, event=0xbfeb15dc) at kernel/qapplication_x11.cpp:3444
#33 0xb6c0c9a2 in x11EventSourceDispatch (s=0x89be880, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#34 0xb4fea848 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#35 0xb4fedd73 in ?? () from /usr/lib/libglib-2.0.so.0
#36 0x089be800 in ?? ()
#37 0x00000000 in ?? ()
Comment 5 Dario Andres 2009-06-12 14:57:38 UTC
Thanks!

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