Red Hat Bugzilla – Bug 626131
[abrt] bogofilter-1.2.0-2.fc12: Process /usr/bin/bogofilter was killed by signal 11 (SIGSEGV)
Last modified: 2010-09-11 14:25:19 EDT
abrt version: 1.1.13
Attached file: backtrace
cmdline: bogofilter -I /home/tkoskine/.sylpheed-2.0/imapcache/mail.kapsi.fi/tkoskine/INBOX/97769
comment: I was reading my IMAP inbox using sylpheed when I noticed the bogofilter crash.
reason: Process /usr/bin/bogofilter was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Created an attachment (id=440190)
I informed upstream about the crash: https://sourceforge.net/tracker/?func=detail&atid=499997&aid=3052165&group_id=62265
Please upload the file that cause the SIGSEGV, i.e. the file after the "-I" flag.
Can you duplicate the problem with bogofilter's current release (1.2.2) ?
1.2.2 is available at http://koji.fedoraproject.org/koji/buildinfo?buildID=190626
(In reply to comment #4)
> 1.2.2 is available at
I have been running bogofilter-1.2.2-1.fc13.x86_64 from this url for a few hours
and read+filtered 50-100 emails without crashes.
1.2.0 used to crash pretty much every time when I pressed "Get All" from Sylpheed UI.
So, this bug can be considered as fixed for me.
Upstream co-maintainer writing:
According to the stack trace, it was a crash in Berkeley DB anyways, and that is usually a hint to a database corruption rather than a software bug.
bogoutil --db-verify $HOME/.bogofilter/wordlist.db
can detect some of such corruptions. It is recommended to run bogofilter in transactional mode. For integration by packagers, it might be useful to consider making transactional the only available mode, ./configure --enable transactions, but do note transactional mode requires more files than just the .db file, but also the environment and log files.
Do also note that there have been critical fixes for parser bugs in bogofilter 1.2.1 (older versions missed tokens from messages), and a security fix in bogofilter 1.2.2, see
The upstream is not supporting older versions than the latest release (1.2.2 at the time of this writing), which triggered David's comment #3.
bogofilter-1.2.2-1.fc13 has been submitted as an update for Fedora 13.
bogofilter-1.2.2-1.fc12 has been submitted as an update for Fedora 12.
bogofilter-1.2.2-1.el5 has been submitted as an update for Fedora EPEL 5.
bogofilter-1.2.2-1.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update bogofilter'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/bogofilter-1.2.2-1.el5
bogofilter-1.2.2-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
bogofilter-1.2.2-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
bogofilter-1.2.2-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.