Hide Forgot
abrt 1.1.1 detected a crash. architecture: i686 cmdline: /usr/bin/python /usr/bin/sb_filter.py component: spambayes executable: /usr/bin/sb_filter.py kernel: 2.6.33.5-124.fc13.i686.PAE package: spambayes-1.0.4-9.fc12 reason: hammie.py:37:_scoremsg:AttributeError: 'NoneType' object has no attribute 'spamprob' release: Fedora release 13 (Goddard) backtrace ----- hammie.py:37:_scoremsg:AttributeError: 'NoneType' object has no attribute 'spamprob' Traceback (most recent call last): File "/usr/bin/sb_filter.py", line 257, in <module> main() File "/usr/bin/sb_filter.py", line 248, in main action(msg) File "/usr/bin/sb_filter.py", line 180, in filter return self.h.filter(msg) File "/usr/lib/python2.6/site-packages/spambayes/hammie.py", line 108, in filter prob, clues = self._scoremsg(msg, True) File "/usr/lib/python2.6/site-packages/spambayes/hammie.py", line 37, in _scoremsg return self.bayes.spamprob(tokenize(msg), evidence) AttributeError: 'NoneType' object has no attribute 'spamprob' Local variables in innermost frame: msg: <email.message.Message instance at 0x9e5ed6c> self: <spambayes.hammie.Hammie instance at 0x9e5efcc> evidence: True comment ----- The problem seems to be eliminated by doing the following initialization. Perhaps this should be added to the RPM %install procedures for kdepim or spambayes? /usr/bin/sb_filter.py -d $HOME/.hammiedb -n How to reproduce ----- 1.Start Kontact or Kmail when you have new (unread) messages. 2.Spambayes apparently tries to run but dies. 3.The issue is probably for people upgrading to Fedora 13 from pervious version. They need to initialize their spambayes database manually. Perhaps this should be added to the RPM %install procedures for kdepim or spambayes?
Created attachment 429852 [details] File: backtrace
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.