Bug 669352 - [abrt] bogofilter-1.2.2-1.fc14: _dl_fini: Process /usr/bin/bogofilter was killed by signal 11 (SIGSEGV)
Summary: [abrt] bogofilter-1.2.2-1.fc14: _dl_fini: Process /usr/bin/bogofilter was kil...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: bogofilter
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Adrian Reber
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f9cd5c96b8d47d3d713648d9461...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-13 13:10 UTC by Peter Janes
Modified: 2012-03-27 15:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-27 15:34:58 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (15.85 KB, text/plain)
2011-01-13 13:10 UTC, Peter Janes
no flags Details

Description Peter Janes 2011-01-13 13:10:12 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: bogofilter -p -u -e
component: bogofilter
crash_function: _dl_fini
executable: /usr/bin/bogofilter
kernel: 2.6.35.10-74.fc14.x86_64
package: bogofilter-1.2.2-1.fc14
rating: 4
reason: Process /usr/bin/bogofilter was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1294912025
uid: 500

How to reproduce
-----
1. bogofilter running under procmail; was processing a short non-spam message generated by cron
2.
3.

Comment 1 Peter Janes 2011-01-13 13:10:14 UTC
Created attachment 473311 [details]
File: backtrace

Comment 2 Peter Janes 2011-02-21 21:52:18 UTC
Package: bogofilter-1.2.2-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. bogofilter running under procmail; was processing a short non-spam message generated by cron
2.
3.

Comment 3 Adrian Reber 2012-03-27 14:01:38 UTC
Can you run: bogoutil --db-verify $HOME/.bogofilter/wordlist.db

to see if there is a database corruption.

Comment 4 Peter Janes 2012-03-27 15:34:58 UTC
I don't have the wordlist.db file any more (the report was submitted over a year ago), and can't recall what I did, if anything, to resolve the issue.


Note You need to log in before you can comment on or make changes to this bug.