Bug 217758 - Clicked on 'This is not a SPAM' button, Kmail crashed
Summary: Clicked on 'This is not a SPAM' button, Kmail crashed
Status: RESOLVED DUPLICATE of bug 163071
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-07 20:21 UTC by Greg
Modified: 2009-12-10 17:32 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 Greg 2009-12-07 20:21:27 UTC
Application that crashed: kmail
Version of the application: 1.12.4
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.3
Operating System: Linux 2.6.31-ARCH x86_64

What I was doing when the application crashed:
I was trying to mark a message as 'not SPAM', Kmail crashed immediately. It happened again, after I restarted Kmail and tried to do the same thing

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fc0a3ecc760 (LWP 4177))]

Thread 2 (Thread 0x7fc08ac06710 (LWP 4181)):
#0  0x00007fc0a08ae3e9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1  0x00007fc0a218abd2 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#2  0x00007fc0a2180d32 in ?? () from /usr/lib/libQtCore.so.4
#3  0x00007fc0a2189ba5 in ?? () from /usr/lib/libQtCore.so.4
#4  0x00007fc0a08a981a in start_thread () from /lib/libpthread.so.0
#5  0x00007fc0a0de38cd in clone () from /lib/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fc0a3ecc760 (LWP 4177)):
[KCrash Handler]
#5  0x00007fc0a2c826a0 in KMail::FolderJob::msgList() const () from /usr/lib/libkmailprivate.so.4
#6  0x00007fc0a2b2a633 in KMAcctImap::ignoreJobsForMessage(KMMessage*) () from /usr/lib/libkmailprivate.so.4
#7  0x00007fc0a2c43037 in KMCommand::transferSelectedMsgs() () from /usr/lib/libkmailprivate.so.4
#8  0x00007fc0a2c4353f in KMCommand::slotStart() () from /usr/lib/libkmailprivate.so.4
#9  0x00007fc0a2c34326 in KMCommand::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkmailprivate.so.4
#10 0x00007fc0a2283d3c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#11 0x00007fc0a2288d7f in ?? () from /usr/lib/libQtCore.so.4
#12 0x00007fc0a227dce3 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#13 0x00007fc0a172007c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#14 0x00007fc0a172734e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#15 0x00007fc0a39108f6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#16 0x00007fc0a226ebfc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#17 0x00007fc0a229a3e2 in ?? () from /usr/lib/libQtCore.so.4
#18 0x00007fc0a22973f8 in ?? () from /usr/lib/libQtCore.so.4
#19 0x00007fc0992c91fe in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#20 0x00007fc0992ccbb8 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#21 0x00007fc0992ccce0 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#22 0x00007fc0a2297123 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#23 0x00007fc0a17b314e in ?? () from /usr/lib/libQtGui.so.4
#24 0x00007fc0a226d532 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#25 0x00007fc0a226d904 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#26 0x00007fc0a226fab9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#27 0x0000000000402f89 in _start ()

Reported using DrKonqi
Comment 1 Nicolas L. 2009-12-08 16:53:44 UTC
please install the debug packages from your distribution and paste a new crashlog
Comment 2 Dario Andres 2009-12-10 17:32:24 UTC
This is related to bug 163071 and to some of its duplicates. Thanks

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