[Bug 262538] New: KMail crashes when pressing reply button while opening new folder

Wonko wonko at wonkology.org
Sat Jan 8 15:38:23 GMT 2011


https://bugs.kde.org/show_bug.cgi?id=262538

           Summary: KMail crashes when pressing reply button while opening
                    new folder
           Product: kontact
           Version: unspecified
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kdepim-bugs at kde.org
        ReportedBy: wonko at wonkology.org


Application: kontact (4.4.9)
KDE Platform Version: 4.5.4 (KDE 4.5.4) (Compiled from sources)
Qt Version: 4.7.1
Operating System: Linux 2.6.36-ck-r3 x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
When pressing the 'Reply' button while changing into another folder (before a
new mail message is selected), KMail crashes instantly.

This happens every time. Steps to reproduce:
1. select any message, so the 'Reply' button is sensitive
2. select another mail folder (no matter if local or IMAP)
3. press 'Reply' quickly
4. kmail crashes

Actually, it was kontact that crashed, did not try standalone kmail.

Drkonqui  found no usable backtrace when the first crash happened, but now it
did.
In case you guys cannot reproduce this, I can compile kmail with debug output.

There are LOTS of duplicates suggested by drkonqui, but most are about deleting
messages. Maybe the general problem ist that things are being initated while no
message is selected, be it because the folder is being changed, or a message
was deleted, or whatever.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0x00007fc0b0e19373 in KMCommand::slotStart() () from
/usr/lib/libkmailprivate.so.4
#7  0x00007fc0b0e2400e in KMCommand::qt_metacall(QMetaObject::Call, int,
void**) () from /usr/lib/libkmailprivate.so.4
#8  0x00007fc0c96e2982 in QObject::event(QEvent*) () from
/usr/lib64/qt4/libQtCore.so.4
#9  0x00007fc0c9bc8be4 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/qt4/libQtGui.so.4
#10 0x00007fc0c9bcd62a in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/qt4/libQtGui.so.4
#11 0x00007fc0cad54e46 in KApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkdeui.so.5
#12 0x00007fc0c96ceac3 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib64/qt4/libQtCore.so.4
#13 0x00007fc0c96d220c in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib64/qt4/libQtCore.so.4
#14 0x00007fc0c96f8f03 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /usr/lib64/qt4/libQtCore.so.4
#15 0x00007fc0c21dabd2 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#16 0x00007fc0c21db380 in g_main_context_iterate.clone.5 () from
/usr/lib/libglib-2.0.so.0
#17 0x00007fc0c21db61d in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#18 0x00007fc0c96f908f in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib64/qt4/libQtCore.so.4
#19 0x00007fc0c9c6c57e in
QGuiEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
() from /usr/lib64/qt4/libQtGui.so.4
#20 0x00007fc0c96cded2 in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/qt4/libQtCore.so.4
#21 0x00007fc0c96ce114 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/qt4/libQtCore.so.4
#22 0x00007fc0c96d24b3 in QCoreApplication::exec() () from
/usr/lib64/qt4/libQtCore.so.4
#23 0x000000000040446e in main ()

Possible duplicates by query: bug 262472, bug 262442, bug 262334, bug 261750,
bug 259621.

Reported using DrKonqi

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Kdepim-bugs mailing list