Bug 268464 - IMAP Filerting
Summary: IMAP Filerting
Status: RESOLVED DUPLICATE of bug 169048
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.4.10
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-14 14:59 UTC by Chris
Modified: 2011-03-14 15:07 UTC (History)
0 users

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 2011-03-14 14:59:43 UTC
Application: kontact (4.4.10)
KDE Platform Version: 4.5.5 (KDE 4.5.5) "release 1"
Qt Version: 4.7.2
Operating System: Linux 2.6.34.7-0.7-desktop x86_64
Distribution: "openSUSE 11.3 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: So the filtering issue may be two part.  I received one crash (which out of frustration I did not report, sorry) where I was filtering a group of 13 emails manually.  I had highlighted 13 new emails and pressed ctrl-J and received the crash.  

I then restarted Kontact and this time filtered individual emails.  I realized too late that I had pressed ctrl-J on an email that had no filter associated with it. . . and received this crash.

So does the filtering of IMAP emails depend on whether or not there is a specific filter established?  Why would this be?  Wouldn't or shouldn't filtering not be dependent on a filter set up for a specific set of criteria?  The filter should be applied and if the email does not meet the criteria the process should move on, not crash.

This crashing usually occurs at the start of a day (time of day is not important).  It is when Kontact/Kmail is first started.  There are several crashes and then everything seems to settle down . . . for a while.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  KMail::ActionScheduler::actionMessage (this=0x1209880, res=<value optimized out>) at /usr/src/debug/kdepim-4.4.10/kmail/actionscheduler.cpp:675
#7  0x00007f43fc43e6a5 in KMail::ActionScheduler::filterMessage (this=0x1209880) at /usr/src/debug/kdepim-4.4.10/kmail/actionscheduler.cpp:648
#8  0x00007f43fc43ea54 in KMail::ActionScheduler::qt_metacall (this=0x1209880, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7fff245434e0)
    at /usr/src/debug/kdepim-4.4.10/build/kmail/actionscheduler.moc:130
#9  0x00007f4415fb888f in QMetaObject::activate (sender=0x15ce530, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3278
#10 0x00007f4415fb7239 in QObject::event (this=0x15ce530, e=<value optimized out>) at kernel/qobject.cpp:1181
#11 0x00007f441535e114 in QApplicationPrivate::notify_helper (this=0x6419a0, receiver=0x15ce530, e=0x7fff24543c80) at kernel/qapplication.cpp:4462
#12 0x00007f44153666aa in QApplication::notify (this=<value optimized out>, receiver=0x15ce530, e=0x7fff24543c80) at kernel/qapplication.cpp:4341
#13 0x00007f44168e6876 in KApplication::notify (this=0x7fff24544040, receiver=0x15ce530, event=0x7fff24543c80) at /usr/src/debug/kdelibs-4.5.5/kdeui/kernel/kapplication.cpp:310
#14 0x00007f4415fa363c in QCoreApplication::notifyInternal (this=0x7fff24544040, receiver=0x15ce530, event=0x7fff24543c80) at kernel/qcoreapplication.cpp:731
#15 0x00007f4415fd0ee8 in sendEvent (this=0x640350) at kernel/qcoreapplication.h:215
#16 QTimerInfoList::activateTimers (this=0x640350) at kernel/qeventdispatcher_unix.cpp:619
#17 0x00007f4415fcdc58 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#18 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#19 0x00007f440d672a93 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#20 0x00007f440d673270 in ?? () from /usr/lib64/libglib-2.0.so.0
#21 0x00007f440d673510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#22 0x00007f4415fce30f in QEventDispatcherGlib::processEvents (this=0x6132c0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#23 0x00007f4415403b8e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#24 0x00007f4415fa2a72 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#25 0x00007f4415fa2c85 in QEventLoop::exec (this=0x7fff24543f90, flags=...) at kernel/qeventloop.cpp:201
#26 0x00007f4415fa70eb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#27 0x000000000040417e in _start ()

Possible duplicates by query: bug 268232, bug 268226, bug 268222, bug 268153, bug 268152.

Reported using DrKonqi
Comment 1 Christophe Marin 2011-03-14 15:07:57 UTC

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