Bug 293417 - Crash during spam filter operation
Summary: Crash during spam filter operation
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.7
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2012-02-06 06:34 UTC by musa_karolia
Modified: 2018-10-27 04:00 UTC (History)
0 users

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 musa_karolia 2012-02-06 06:34:04 UTC
Application: kmail (4.7.3)
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-16-generic x86_64
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:

Bogofilter is working well to identify spam but the filter is failing to move the spam to my spam folder.
The directory defined for mail in Akonadi only had 'cur', 'new', & 'tmp' directories.
I followed advice to archive the 'local folder' & sub-folders. Then  extract archive in the directory defined  in Akonadi.
On restart of kmail it crashed
from here:
http://forum.kde.org/viewtopic.php?f=20&t=97744&p=207482#p207619

hope this helps.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
[Current thread is 1 (Thread 0x7ff6f310e7a0 (LWP 10626))]

Thread 4 (Thread 0x7ff6c5ea9700 (LWP 10630)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007ff6e53dfc2c in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007ff6e53dfd59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007ff6ee036efc in start_thread (arg=0x7ff6c5ea9700) at pthread_create.c:304
#4  0x00007ff6f049089d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7ff6c5590700 (LWP 10631)):
#0  0x00007ff6e8ece058 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007ff6e8ecedfd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ff6e8ecf429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ff6f0e02f3e in QEventDispatcherGlib::processEvents (this=0xe0fdf0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007ff6f0dd6cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007ff6f0dd6ef7 in QEventLoop::exec (this=0x7ff6c558fde0, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007ff6f0cee27f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498
#7  0x00007ff6f0cf0d05 in QThreadPrivate::start (arg=0xd81070) at thread/qthread_unix.cpp:331
#8  0x00007ff6ee036efc in start_thread (arg=0x7ff6c5590700) at pthread_create.c:304
#9  0x00007ff6f049089d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7ff67da08700 (LWP 10634)):
#0  0x00007ff6f0484773 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007ff6e8ecef68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ff6e8ecf429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ff6f0e02f3e in QEventDispatcherGlib::processEvents (this=0x14d4840, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007ff6f0dd6cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007ff6f0dd6ef7 in QEventLoop::exec (this=0x7ff67da07db0, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007ff6f0cee27f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498
#7  0x00007ff6f0db9cbf in QInotifyFileSystemWatcherEngine::run (this=0x14d3c40) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007ff6f0cf0d05 in QThreadPrivate::start (arg=0x14d3c40) at thread/qthread_unix.cpp:331
#9  0x00007ff6ee036efc in start_thread (arg=0x7ff67da08700) at pthread_create.c:304
#10 0x00007ff6f049089d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7ff6f310e7a0 (LWP 10626)):
[KCrash Handler]
#6  0x00007ff6f03e53a5 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007ff6f03e8b0b in __GI_abort () at abort.c:92
#8  0x00007ff6f0a1fd7d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007ff6f0a1df26 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007ff6f0a1df53 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x00007ff6f0a1e096 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x00007ff6f0dd702e in QEventLoop::exec (this=<optimized out>, flags=<optimized out>) at kernel/qeventloop.cpp:214
#13 0x00007ff6f0ddb789 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#14 0x0000000000402bd3 in main (argc=<optimized out>, argv=<optimized out>) at ../../kmail/main.cpp:145

Possible duplicates by query: bug 293255, bug 292903, bug 292249, bug 292027, bug 292022.

Reported using DrKonqi
Comment 1 Jekyll Wu 2013-09-30 14:08:26 UTC
Unfortunately, the backtrace doesn't contain much helpful information due to uncaught exception (not your fault). 

If you can reproduce the crash every time,  please follow the guide[1] and try to run it under gdb to get a better backtrace.  

[1] http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_when_an_uncaught_exception_is_causing_a_crash
Comment 2 Andrew Crouthamel 2018-09-25 03:34:55 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-10-27 04:00:25 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!