Bug 223987 - Task manager crashes in RC1 when closing windows from a froup
Summary: Task manager crashes in RC1 when closing windows from a froup
Status: RESOLVED DUPLICATE of bug 219664
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:
Depends on:
Blocks:
 
Reported: 2010-01-24 02:23 UTC by iferca
Modified: 2010-01-24 09:26 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description iferca 2010-01-24 02:23:11 UTC
Application: plasma-desktop (0.3)
KDE Platform Version: 4.3.90 (KDE 4.3.90 (KDE 4.4 RC1))
Qt Version: 4.6.0
Operating System: Linux 2.6.31-18-generic i686
Distribution: Ubuntu 9.10

-- Information about the crash:
I can repeat this crash every time in RC (4.3.90).
Open a firefox windows, open download and any other window from firefox (downthemall?), open more windows to cause the firefox windows get grouped. Then just select one window from the group ant close... should crash.

The crash can be reproduced every time.

 -- Backtrace:
Application: Plasma Workspace (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0xb782d700 (LWP 1602))]

Thread 2 (Thread 0xab69db70 (LWP 1603)):
#0  0x00ac2422 in __kernel_vsyscall ()
#1  0x00a82e15 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0x00e82307 in QWaitConditionPrivate::wait (this=0x8991228, mutex=0x8991224, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#3  QWaitCondition::wait (this=0x8991228, mutex=0x8991224, time=4294967295) at thread/qwaitcondition_unix.cpp:159
#4  0x025ab102 in QHostInfoAgent::run (this=0x8991218) at kernel/qhostinfo.cpp:252
#5  0x00e813ae in QThreadPrivate::start (arg=0x8991218) at thread/qthread_unix.cpp:244
#6  0x00a7e80e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0x03a2e8de in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb782d700 (LWP 1602)):
[KCrash Handler]
#6  QGraphicsScenePrivate::processDirtyItemsRecursive (this=0x81f2f78, item=0x8ef1708, dirtyAncestorContainsChildren=false, parentOpacity=1) at graphicsview/qgraphicsscene.cpp:4895
#7  0x0665eeed in QGraphicsScenePrivate::_q_processDirtyItems (this=0x81f2f78) at graphicsview/qgraphicsscene.cpp:466
#8  0x0665f4f6 in QGraphicsScene::qt_metacall (this=0x8240530, _c=QMetaObject::InvokeMetaMethod, _id=14, _a=0x8f3c1a8) at .moc/release-shared/moc_qgraphicsscene.cpp:130
#9  0x0230b20a in Plasma::Corona::qt_metacall (this=0x8240530, _c=QMetaObject::InvokeMetaMethod, _id=18, _a=0x8f3c1a8) at ./corona.moc:107
#10 0x0166efaa in DesktopCorona::qt_metacall (this=0x8240530, _c=QMetaObject::InvokeMetaMethod, _id=18, _a=0x8f3c1a8) at ./desktopcorona.moc:78
#11 0x00f8811a in QMetaObject::metacall (object=0x8240530, cl=QMetaObject::InvokeMetaMethod, idx=18, argv=0x8f3c1a8) at kernel/qmetaobject.cpp:237
#12 0x00f92856 in QMetaCallEvent::placeMetaCall (this=0x92bd928, object=0x8240530) at kernel/qobject.cpp:574
#13 0x00f938ae in QObject::event (this=0x8240530, e=0x92bd928) at kernel/qobject.cpp:1260
#14 0x0665b1c4 in QGraphicsScene::event (this=0x8240530, event=0x92bd928) at graphicsview/qgraphicsscene.cpp:3450
#15 0x05fb619c in QApplicationPrivate::notify_helper (this=0x8168118, receiver=0x8240530, e=0x92bd928) at kernel/qapplication.cpp:4242
#16 0x05fbcdf7 in QApplication::notify (this=0x8161a30, receiver=0x8240530, e=0x92bd928) at kernel/qapplication.cpp:3661
#17 0x0080e67a in KApplication::notify (this=0x8161a30, receiver=0x8240530, event=0x92bd928) at ../../kdeui/kernel/kapplication.cpp:302
#18 0x00f82eab in QCoreApplication::notifyInternal (this=0x8161a30, receiver=0x8240530, event=0x92bd928) at kernel/qcoreapplication.cpp:704
#19 0x00f858e3 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x81198a8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#20 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x81198a8) at kernel/qcoreapplication.cpp:1345
#21 0x00f85a4d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1238
#22 0x00faf0df in QCoreApplication::sendPostedEvents (s=0x816a2b0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#23 postEventSourceDispatch (s=0x816a2b0) at kernel/qeventdispatcher_glib.cpp:276
#24 0x01a39e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#25 0x01a3d730 in ?? () from /lib/libglib-2.0.so.0
#26 0x01a3d863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#27 0x00faebd5 in QEventDispatcherGlib::processEvents (this=0x81673f0, flags=...) at kernel/qeventdispatcher_glib.cpp:407
#28 0x06073b75 in QGuiEventDispatcherGlib::processEvents (this=0x81673f0, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#29 0x00f814c9 in QEventLoop::processEvents (this=0xbfd94bf4, flags=) at kernel/qeventloop.cpp:149
#30 0x00f8191a in QEventLoop::exec (this=0xbfd94bf4, flags=...) at kernel/qeventloop.cpp:201
#31 0x00f85b0f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#32 0x05fb6237 in QApplication::exec () at kernel/qapplication.cpp:3570
#33 0x01676c7e in kdemain (argc=1, argv=0x8159300) at ../../../../plasma/desktop/shell/main.cpp:112
#34 0x0804dff7 in launch (argc=<value optimized out>, _name=<value optimized out>, args=<value optimized out>, cwd=0x0, envc=0, envs=0x814d5a8 "", reset_env=false, tty=0x0, avoid_loops=false, 
    startup_id_str=0x8051429 "0") at ../../kinit/kinit.cpp:706
#35 0x0804ec15 in handle_launcher_request (sock=<value optimized out>, who=<value optimized out>) at ../../kinit/kinit.cpp:1198
#36 0x0804f08c in handle_requests (waitForPid=<value optimized out>) at ../../kinit/kinit.cpp:1391
#37 0x0804fe27 in main (argc=4, argv=0xbfd956a4, envp=0xbfd956b8) at ../../kinit/kinit.cpp:1830

Possible duplicates by query: bug 223904, bug 223703, bug 223534, bug 223399, bug 223327.

Reported using DrKonqi
Comment 1 Beat Wolf 2010-01-24 09:26:50 UTC

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