abrt version: 1.1.13
cmdline: python /usr/share/recoll/filters/rclchm
comment: Run recoll indexing (manual and via cron)
reason: HTMLParser.py:115:error:HTMLParseError: EOF in middle of construct, at line 273, column 13
release: Fedora release 13 (Goddard)
HTMLParser.py:115:error:HTMLParseError: EOF in middle of construct, at line 273, column 13
Traceback (most recent call last):
File "/usr/share/recoll/filters/rclchm", line 150, in <module>
File "/usr/share/recoll/filters/rclexecm.py", line 116, in mainloop
File "/usr/share/recoll/filters/rclexecm.py", line 84, in processmessage
if not processor.openfile(params):
File "/usr/share/recoll/filters/rclchm", line 134, in openfile
File "/usr/lib64/python2.6/HTMLParser.py", line 112, in close
File "/usr/lib64/python2.6/HTMLParser.py", line 164, in goahead
self.error("EOF in middle of construct")
File "/usr/lib64/python2.6/HTMLParser.py", line 115, in error
raise HTMLParseError(message, self.getpos())
HTMLParseError: EOF in middle of construct, at line 273, column 13
Local variables in innermost frame:
message: 'EOF in middle of construct'
self: <__main__.ChmTopicsParser instance at 0x1ff8cf8>
How to reproduce
1. this happens when recollindex is run
2. I think it happens when it treis to index chm files
3. as far as I can tell all chms are affected as the only information I can find about chms is in the filename
Created attachment 462567 [details]
OS Release: Fedora release 14 (Laughlin)
How to reproduce
1. Recoll index update is run via anacron
2. Crashes happen - apparently when recoll tries to index chm files (although I do not know how to verify that).
Thanks for your report.
recoll-1.14.4-1.fc14 has been submitted as an update for Fedora 14.
recoll-1.14.4-1.fc13 has been submitted as an update for Fedora 13.
recoll-1.14.4-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
recoll-1.14.4-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
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:
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.