Bug 182853

Summary: Crash on some click in the message list
Product: [Unmaintained] kmail Reporter: RenĂ© Krell <renda.krell>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra
Priority: NOR    
Version: 1.11.0   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description René Krell 2009-02-02 12:36:49 UTC
Version:           1.11.0 (using 4.2.00 (KDE 4.2.0) "release 83.1", KDE:KDE4:Factory:Desktop / openSUSE_11.1)
Compiler:          gcc
OS:                Linux (i686) release 2.6.27.7-9-default

There was a crash when I clicked in the message list of KMail (within Kontact). I'm not sure where I clicked, whether on a header or a message. I was using the "Activity by date, threaded" layout.

Backtrace:

Application: Kontact (kontact), signal SIGSEGV
[?1034h[Thread debugging using libthread_db enabled]
0xb59d454c in nanosleep () from /lib/libc.so.6
[Current thread is 1 (Thread 0xb4965920 (LWP 4579))]

Thread 1 (Thread 0xb4965920 (LWP 4579)):
[KCrash Handler]
#5  0xb112e3d0 in KMReaderWin::parseMsg (this=0x86506b0, aMsg=0x9d717f8) at /usr/src/debug/kdepim-4.2.0/kmail/kmreaderwin.cpp:1628
#6  0xb111f568 in KMReaderWin::displayMessage (this=0x86506b0) at /usr/src/debug/kdepim-4.2.0/kmail/kmreaderwin.cpp:1555
#7  0xb111f780 in KMReaderWin::updateReaderWin (this=0x86506b0) at /usr/src/debug/kdepim-4.2.0/kmail/kmreaderwin.cpp:1495
#8  0xb112dbf0 in KMReaderWin::qt_metacall (this=0x86506b0, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfdf71f8) at /usr/src/debug/kdepim-4.2.0/build/kmail/kmreaderwin.moc:164
#9  0xb675c580 in QMetaObject::activate (sender=0x8650700, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3031
#10 0xb675d302 in QMetaObject::activate (sender=0x8650700, m=0xb682f904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3101
#11 0xb67977f7 in QTimer::timeout (this=0x8650700) at .moc/release-shared/moc_qtimer.cpp:126
#12 0xb6762f9e in QTimer::timerEvent (this=0x8650700, e=0xbfdf76b0) at kernel/qtimer.cpp:257
#13 0xb675704f in QObject::event (this=0x8650700, e=0xbfdf76b0) at kernel/qobject.cpp:1120
#14 0xb5cdd8fc in QApplicationPrivate::notify_helper (this=0x8077c30, receiver=0x8650700, e=0xbfdf76b0) at kernel/qapplication.cpp:3803
#15 0xb5ce575e in QApplication::notify (this=0xbfdf7988, receiver=0x8650700, e=0xbfdf76b0) at kernel/qapplication.cpp:3393
#16 0xb6ce791d in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#17 0xb6747961 in QCoreApplication::notifyInternal (this=0xbfdf7988, receiver=0x8650700, event=0xbfdf76b0) at kernel/qcoreapplication.cpp:587
#18 0xb6775b86 in QTimerInfoList::activateTimers (this=0x8067f6c) at kernel/qcoreapplication.h:209
#19 0xb6772060 in timerSourceDispatch (source=0x8067f38) at kernel/qeventdispatcher_glib.cpp:160
#20 0xb50f29a8 in IA__g_main_context_dispatch (context=0x8079730) at gmain.c:2144
#21 0xb50f6063 in g_main_context_iterate (context=0x8079730, block=1, dispatch=1, self=0x806c5d8) at gmain.c:2778
#22 0xb50f6221 in IA__g_main_context_iteration (context=0x8079730, may_block=1) at gmain.c:2841
#23 0xb6771fb8 in QEventDispatcherGlib::processEvents (this=0x8066f60, flags={i = -1075873704}) at kernel/qeventdispatcher_glib.cpp:319
#24 0xb5d767c5 in QGuiEventDispatcherGlib::processEvents (this=0x8066f60, flags={i = -1075873656}) at kernel/qguieventdispatcher_glib.cpp:198
#25 0xb674601a in QEventLoop::processEvents (this=0xbfdf7900, flags={i = -1075873592}) at kernel/qeventloop.cpp:143
#26 0xb67461da in QEventLoop::exec (this=0xbfdf7900, flags={i = -1075873528}) at kernel/qeventloop.cpp:194
#27 0xb6748895 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#28 0xb5cdd777 in QApplication::exec () at kernel/qapplication.cpp:3331
#29 0x0804bf8f in main (argc=1, argv=0xbfdf7c84) at /usr/src/debug/kdepim-4.2.0/kontact/src/main.cpp:218
Comment 1 Dario Andres 2009-02-03 13:52:35 UTC

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