Red Hat Bugzilla – Bug 1281859
[abrt] pyzor: codecs.py:319:decode:UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe3 in position 2790: invalid continuation byte
Last modified: 2016-12-20 10:50:11 EST
Description of problem:
filtring emails on evolution
Version-Release number of selected component:
cmdline: /usr/bin/python3 /usr/bin/pyzor check
runlevel: N 5
#1 decode in /usr/lib64/python3.4/codecs.py:319
#2 parse in /usr/lib64/python3.4/email/parser.py:54
#3 message_from_file in /usr/lib64/python3.4/email/__init__.py:56
#4 _get_input_msg in /usr/bin/pyzor:174
#5 check in /usr/bin/pyzor:237
#6 main in /usr/bin/pyzor:152
#7 <module> in /usr/bin/pyzor:408
Created attachment 1093717 [details]
Created attachment 1093718 [details]
This appears to be the same issue already reported upstream at: https://github.com/SpamExperts/pyzor/issues/38
If you could possibly obtain the message which caused this problem, I'm sure upstream would love to see it. There might be enough in the backtrace, though; I'll have to take a hard look at it.
Created attachment 1095581 [details]
the message that was request
here it is , the message that make this fail .
Thanks! Upstream was looking for an example, so this should help narrow things down. I have passed it up to the developers, and there's a chance I might be able to fix it myself.
*** Bug 1297247 has been marked as a duplicate of this bug. ***
still the almost one year later ...
Yes, upstream appears to be completely dead. I suppose I should just have the software removed from the distribution entirely.
I removed pyzor  and evolution is working in same way, detect well spam etc, and stopped to crash (I recently had some crashes but abrt doesn't le me report), so recently pyzor seems also make evolution crash .
So I support you in remove pyzor from the distribution.
 dnf remove "pyzor*"
Sorry I spoke to soon evolution just crash again, abrt says:
The process had locked memory which usually indicates efforts to protect sensitive data (passwords) from being written to disk.
In order to avoid sensitive information leakages, ABRT will not allow you to report this problem to bug tracking tools
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora 'version'
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.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 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, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
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.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.