Bug 210764 - kmail crash when filtering imap account
Summary: kmail crash when filtering imap account
Status: RESOLVED DUPLICATE of bug 169048
Alias: None
Product: kontact
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-10-16 09:25 UTC by Thierry Chich
Modified: 2009-10-17 21:59 UTC (History)
1 user (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 Thierry Chich 2009-10-16 09:25:22 UTC
Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.28-11-generic i686
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
I just have had a new rule in order to filter my email.  For this rule, on the email matching this rule, there is a crash when I apply filters manually.  Kmail don't crash on other rules.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 0 (LWP 7065)]

Thread 2 (Thread 0xaae32b90 (LWP 7073)):
#0  0xb7fa4430 in __kernel_vsyscall ()
#1  0xb50cd0e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb59462ed in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb5b2a172 in QWaitCondition::wait (this=0x9dd2790, mutex=0x977bfd0, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  0xb0b2a148 in ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned (this=0x9dd2778, th=0xa4d78d0) at /build/buildd/kde4libs-4.3.2/threadweaver/Weaver/WeaverImpl.cpp:365
#5  0xb0b2ceec in ThreadWeaver::WorkingHardState::waitForAvailableJob (this=0x9dd1488, th=0xa4d78d0) at /build/buildd/kde4libs-4.3.2/threadweaver/Weaver/WorkingHardState.cpp:80
#6  0xb0b28d2b in ThreadWeaver::WeaverImpl::waitForAvailableJob (this=0x9dd2778, th=0xa4d78d0) at /build/buildd/kde4libs-4.3.2/threadweaver/Weaver/WeaverImpl.cpp:356
#7  0xb0b2cfea in ThreadWeaver::WorkingHardState::applyForWork (this=0x9dd1488, th=0xa4d78d0) at /build/buildd/kde4libs-4.3.2/threadweaver/Weaver/WorkingHardState.cpp:71
#8  0xb0b2a6d3 in ThreadWeaver::WeaverImpl::applyForWork (this=0x9dd2778, th=0xa4d78d0, previous=0x9b47130) at /build/buildd/kde4libs-4.3.2/threadweaver/Weaver/WeaverImpl.cpp:351
#9  0xb0b2afbe in ThreadWeaver::ThreadRunHelper::run (this=0xaae32330, parent=0x9dd2778, th=0xa4d78d0) at /build/buildd/kde4libs-4.3.2/threadweaver/Weaver/Thread.cpp:87
#10 0xb0b2b5fb in ThreadWeaver::Thread::run (this=0xa4d78d0) at /build/buildd/kde4libs-4.3.2/threadweaver/Weaver/Thread.cpp:142
#11 0xb5b29132 in QThreadPrivate::start (arg=0xa4d78d0) at thread/qthread_unix.cpp:188
#12 0xb50c94ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#13 0xb593749e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb4837700 (LWP 7065)):
[KCrash Handler]
#6  0xb0e3ddcc in KMail::ActionScheduler::actionMessage (this=0xa83c5a8, res=KMFilterAction::GoOn) at /build/buildd/kdepim-4.3.2/kmail/actionscheduler.cpp:675
#7  0xb0e3edbe in KMail::ActionScheduler::filterMessage (this=0xa83c5a8) at /build/buildd/kdepim-4.3.2/kmail/actionscheduler.cpp:648
#8  0xb0e3f03d in KMail::ActionScheduler::qt_metacall (this=0xa83c5a8, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0xbffc1f08)
    at /build/buildd/kdepim-4.3.2/obj-i486-linux-gnu/kmail/actionscheduler.moc:124
#9  0xb5c331b8 in QMetaObject::activate (sender=0xa820a68, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#10 0xb5c33e42 in QMetaObject::activate (sender=0xa820a68, m=0xb5d10904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#11 0xb5c6f687 in QTimer::timeout (this=0xa820a68) at .moc/release-shared/moc_qtimer.cpp:128
#12 0xb5c395ce in QTimer::timerEvent (this=0xa820a68, e=0xbffc238c) at kernel/qtimer.cpp:261
#13 0xb5c2e16f in QObject::event (this=0xa820a68, e=0xbffc238c) at kernel/qobject.cpp:1075
#14 0xb60e1d3c in QApplicationPrivate::notify_helper (this=0x95f4290, receiver=0xa820a68, e=0xbffc238c) at kernel/qapplication.cpp:4056
#15 0xb60ea03e in QApplication::notify (this=0xbffc2638, receiver=0xa820a68, e=0xbffc238c) at kernel/qapplication.cpp:3603
#16 0xb6cdb49d in KApplication::notify (this=0xbffc2638, receiver=0xa820a68, event=0xbffc238c) at /build/buildd/kde4libs-4.3.2/kdeui/kernel/kapplication.cpp:302
#17 0xb5c1dbcb in QCoreApplication::notifyInternal (this=0xbffc2638, receiver=0xa820a68, event=0xbffc238c) at kernel/qcoreapplication.cpp:610
#18 0xb5c4cd51 in QTimerInfoList::activateTimers (this=0x95ea684) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#19 0xb5c493a0 in timerSourceDispatch (source=0x95ea650) at kernel/qeventdispatcher_glib.cpp:165
#20 0xb4ceeb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#21 0xb4cf20eb in ?? () from /usr/lib/libglib-2.0.so.0
#22 0xb4cf2268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#23 0xb5c492f8 in QEventDispatcherGlib::processEvents (this=0x95c3028, flags={i = -1073994488}) at kernel/qeventdispatcher_glib.cpp:327
#24 0xb6183a75 in QGuiEventDispatcherGlib::processEvents (this=0x95c3028, flags={i = -1073994440}) at kernel/qguieventdispatcher_glib.cpp:202
#25 0xb5c1c1fa in QEventLoop::processEvents (this=0xbffc25b0, flags={i = -1073994376}) at kernel/qeventloop.cpp:149
#26 0xb5c1c642 in QEventLoop::exec (this=0xbffc25b0, flags={i = -1073994312}) at kernel/qeventloop.cpp:201
#27 0xb5c1eae9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#28 0xb60e1bb7 in QApplication::exec () at kernel/qapplication.cpp:3525
#29 0x0804bfef in main (argc=1, argv=0xbffc2934) at /build/buildd/kdepim-4.3.2/kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 Thierry Chich 2009-10-16 09:43:25 UTC
I know a little more about the context. When I have added my new filter, i have created one with the right-click on the message. But after that, I have copied the sender and add it to an another already existant rule.
An incomplete rule was then staying at the begining of the list of rules.
Comment 2 Dario Andres 2009-10-17 21:59:53 UTC
Merging with bug 169048. Thanks

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