Bug 127419 - kontact crashes when starting kmail
Summary: kontact crashes when starting kmail
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.9.1
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-16 09:37 UTC by Willi Richert
Modified: 2010-04-06 00:27 UTC (History)
2 users (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 Willi Richert 2006-05-16 09:37:26 UTC
Version:           1.9.1 (using KDE 3.5.2-3.0.fc3.kde, Fedora Core release 3 (Heidelberg))
Compiler:          gcc version 3.4.4 20050721 (Red Hat 3.4.4-2)
OS:                Linux (i686) release 2.6.12-1.1381_FC3

Using host libthread_db library "/lib/tls/libthread_db.so.1".
`shared object read from target memory' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1227942208 (LWP 12235)]
[New Thread -1273594960 (LWP 12251)]
[Thread debugging using libthread_db enabled]
[New Thread -1227942208 (LWP 12235)]
[New Thread -1273594960 (LWP 12251)]
[New Thread -1263105104 (LWP 12250)]
[New Thread -1252615248 (LWP 12249)]
[New Thread -1242125392 (LWP 12248)]
[Thread debugging using libthread_db enabled]
[New Thread -1227942208 (LWP 12235)]
[New Thread -1273594960 (LWP 12251)]
[KCrash handler]
#6  0xb6592ffe in KMMsgIndex::continueCreation ()
   from /usr/lib/libkmailprivate.so
#7  0xb65932a9 in KMMsgIndex::qt_invoke () from /usr/lib/libkmailprivate.so
#8  0x06e8e17e in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#9  0x071c361d in QSignal::signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#10 0x06ea6ded in QSignal::activate () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#11 0x06eadfbf in QSingleShotTimer::event ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#12 0x06e2e949 in QApplication::internalNotify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#13 0x06e2eada in QApplication::notify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#14 0xb7293d02 in KApplication::notify () from /usr/lib/libkdecore.so.4
#15 0x06e22d1b in QEventLoop::activateTimers ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#16 0x06ddd4ee in QEventLoop::processEvents ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#17 0x06e43f65 in QEventLoop::enterLoop ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#18 0x06e43ebe in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#19 0x06e2db4b in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#20 0x08061006 in ?? ()
#21 0xbff0dfb0 in ?? ()
#22 0x00000001 in ?? ()
#23 0x00000001 in ?? ()
#24 0x00000000 in ?? ()
Comment 1 michael 2009-07-01 18:53:56 UTC
Not sure if I should add my experience to this bug, or another but I had a crash while composing a message.  However, the crash handler would not allow me to copy the backtrace information.
Comment 2 Björn Ruberg 2009-12-26 00:26:37 UTC
Please report if you are still experiencing this issue
Comment 3 Björn Ruberg 2010-04-06 00:27:04 UTC
No report. Closing old KDE 3 crash