Bug 162347 - Crash in updateMessageActions() after trying to send message
Summary: Crash in updateMessageActions() after trying to send message
Status: RESOLVED DUPLICATE of bug 171491
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-20 10:42 UTC by chris newton
Modified: 2008-11-19 15:08 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 chris newton 2008-05-20 10:42:02 UTC
Version:            (using KDE 4.0.4)
Installed from:    Ubuntu Packages
OS:                Linux

Every time I press ctrl+enter from the open composer window Kontact crashes.
this part of the readout I get after the crash:


[Thread debugging using libthread_db enabled]
[New Thread 0x7f4fc064e6f0 (LWP 5066)]
[New Thread 0x42d77950 (LWP 5070)]
[New Thread 0x42576950 (LWP 5069)]
[New Thread 0x41d75950 (LWP 5068)]
[New Thread 0x41574950 (LWP 5067)]
)
[KCrash handler]
#5  0x00007f4fb13dbfec in KMHeaders::selectedSernums ()
   from /usr/lib/libkmailprivate.so
#6  0x00007f4fb15709ac in KMMainWidget::updateMessageActions ()
   from /usr/lib/libkmailprivate.so
#7  0x00007f4fb157e2db in KMMainWidget::qt_invoke ()
   from /usr/lib/libkmailprivate.so
#8  0x00007f4fba93dfd0 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#9  0x00007f4fba93eb4e in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#10 0x00007f4fbacb8496 in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#11 0x00007f4fba963d83 in QTimer::event () from /usr/lib/libqt-mt.so.3
#12 0x00007f4fba8d633a in QApplication::internalNotify ()
   from /usr/lib/libqt-mt.so.3
#13 0x00007f4fba8d8093 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#14 0x00007f4fbc00c40d in KApplication::notify ()
   from /usr/lib/libkdecore.so.4
#15 0x00007f4fba86720e in QApplication::sendEvent ()
   from /usr/lib/libqt-mt.so.3
#16 0x00007f4fba8c9abc in QEventLoop::activateTimers ()
   from /usr/lib/libqt-mt.so.3
#17 0x00007f4fba87c107 in QEventLoop::processEvents ()
   from /usr/lib/libqt-mt.so.3
#18 0x00007f4fba8f05bf in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#19 0x00007f4fba8f02ab in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#20 0x00007f4fba8d7e00 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#21 0x0000000000419299 in ?? ()
#22 0x00007f4fb71031c4 in __libc_start_main () from /lib/libc.so.6
#23 0x0000000000418a59 in ?? ()
#24 0x00007fffc86810d8 in ?? ()
#25 0x0000000000000000 in ?? ()
Comment 1 Oliver Putz 2008-10-19 20:31:38 UTC
Backtrace looks similar to the one in bug #171491. The same problem / bug?
Comment 2 Christophe Marin 2008-11-19 15:08:16 UTC

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