Bug 223399 - plasma crash last action: in kontact switch from akregator to kmail check for mail
Summary: plasma crash last action: in kontact switch from akregator to kmail check for...
Status: RESOLVED DUPLICATE of bug 210146
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-19 13:18 UTC by Florian Reinhard
Modified: 2010-01-19 13:47 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 Florian Reinhard 2010-01-19 13:18:34 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-17-generic i686
Distribution: Ubuntu 9.10

-- Information about the crash:
Last thing i did was switching in kontact from akregator to kmail and then checked for new mail.

Found one might-be-dup. Backtrace looks similar, but since the linenumbers differ i'm not sure if this is really a duplicate.

 -- Backtrace:
Application: Plasma-Arbeitsfläche (plasma-desktop), signal: Segmentation fault
[Current thread is 1 (Thread 0xb7815710 (LWP 15775))]

Thread 2 (Thread 0xac51fb70 (LWP 15786)):
#0  0x009ba422 in __kernel_vsyscall ()
#1  0x004efe15 in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:122
#2  0x00b3e87d in __pthread_cond_wait (cond=0x97667c0, mutex=0x97667a8) at forward.c:139
#3  0x01383307 in QWaitConditionPrivate::wait (this=0x97729c8, mutex=0x97729c4, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (this=0x97729c8, mutex=0x97729c4, time=4294967295) at thread/qwaitcondition_unix.cpp:159
#5  0x02668102 in QHostInfoAgent::run (this=0x97729b8) at kernel/qhostinfo.cpp:252
#6  0x013823ae in QThreadPrivate::start (arg=0x97729b8) at thread/qthread_unix.cpp:244
#7  0x004eb80e in start_thread (arg=0xac51fb70) at pthread_create.c:300
#8  0x00b318de in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb7815710 (LWP 15775)):
[KCrash Handler]
#6  QGraphicsScenePrivate::processDirtyItemsRecursive (this=0x92a6c48, item=0x95f54e0, dirtyAncestorContainsChildren=false, parentOpacity=1) at graphicsview/qgraphicsscene.cpp:4895
#7  0x0558aeed in QGraphicsScenePrivate::_q_processDirtyItems (this=0x92a6c48) at graphicsview/qgraphicsscene.cpp:466
#8  0x0558b4f6 in QGraphicsScene::qt_metacall (this=0x939ec60, _c=QMetaObject::InvokeMetaMethod, _id=14, _a=0x9b0a688) at .moc/release-shared/moc_qgraphicsscene.cpp:130
#9  0x001dd20a in Plasma::Corona::qt_metacall (this=0x939ec60, _c=QMetaObject::InvokeMetaMethod, _id=18, _a=0x9b0a688) at ./corona.moc:107
#10 0x00544faa in DesktopCorona::qt_metacall (this=0x939ec60, _c=QMetaObject::InvokeMetaMethod, _id=18, _a=0x9b0a688) at ./desktopcorona.moc:78
#11 0x0148911a in QMetaObject::metacall (object=0x939ec60, cl=QMetaObject::InvokeMetaMethod, idx=18, argv=0x9b0a688) at kernel/qmetaobject.cpp:237
#12 0x01493856 in QMetaCallEvent::placeMetaCall (this=0x9ab9bc0, object=0x939ec60) at kernel/qobject.cpp:574
#13 0x014948ae in QObject::event (this=0x939ec60, e=0x9ab9bc0) at kernel/qobject.cpp:1260
#14 0x055871c4 in QGraphicsScene::event (this=0x939ec60, event=0x9ab9bc0) at graphicsview/qgraphicsscene.cpp:3450
#15 0x04ee219c in QApplicationPrivate::notify_helper (this=0x92ad490, receiver=0x939ec60, e=0x9ab9bc0) at kernel/qapplication.cpp:4242
#16 0x04ee8df7 in QApplication::notify (this=0x92a0f18, receiver=0x939ec60, e=0x9ab9bc0) at kernel/qapplication.cpp:3661
#17 0x0114567a in KApplication::notify (this=0x92a0f18, receiver=0x939ec60, event=0x9ab9bc0) at ../../kdeui/kernel/kapplication.cpp:302
#18 0x01483eab in QCoreApplication::notifyInternal (this=0x92a0f18, receiver=0x939ec60, event=0x9ab9bc0) at kernel/qcoreapplication.cpp:704
#19 0x014868e3 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x928b518) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#20 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x928b518) at kernel/qcoreapplication.cpp:1345
#21 0x01486a4d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1238
#22 0x014b00df in QCoreApplication::sendPostedEvents (s=0x92af720) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#23 postEventSourceDispatch (s=0x92af720) at kernel/qeventdispatcher_glib.cpp:276
#24 0x07b38e88 in g_main_dispatch (context=0x92af698) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:1960
#25 IA__g_main_context_dispatch (context=0x92af698) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2513
#26 0x07b3c730 in g_main_context_iterate (context=0x92af698, block=<value optimized out>, dispatch=1, self=0x92ac4a0) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2591
#27 0x07b3c863 in IA__g_main_context_iteration (context=0x92af698, may_block=1) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2654
#28 0x014afbd5 in QEventDispatcherGlib::processEvents (this=0x92ad0b0, flags=...) at kernel/qeventdispatcher_glib.cpp:407
#29 0x04f9fb75 in QGuiEventDispatcherGlib::processEvents (this=0x92ad0b0, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#30 0x014824c9 in QEventLoop::processEvents (this=0xbfa468f4, flags=) at kernel/qeventloop.cpp:149
#31 0x0148291a in QEventLoop::exec (this=0xbfa468f4, flags=...) at kernel/qeventloop.cpp:201
#32 0x01486b0f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#33 0x04ee2237 in QApplication::exec () at kernel/qapplication.cpp:3570
#34 0x0054cc7e in kdemain (argc=1, argv=0xbfa46af4) at ../../../../plasma/desktop/shell/main.cpp:112
#35 0x080485cb in main (argc=1, argv=0xbfa46af4) at plasma-desktop_dummy.cpp:3

This bug may be a duplicate of or related to bug 210146.

Possible duplicates by query: bug 223327, bug 223230, bug 223189, bug 223169, bug 223132.

Reported using DrKonqi
Comment 1 Dario Andres 2010-01-19 13:47:11 UTC
Indeed, this is bug 210146.

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