Red Hat Bugzilla – Bug 984277
[abrt] unrtf-0.21.2-1.fc19: word_print_core: Process /usr/bin/unrtf was killed by signal 11 (SIGSEGV)
Last modified: 2015-02-17 11:08:55 EST
Description of problem:
1) start recoll in any desktop
2) update index from the menu
Version-Release number of selected component:
cmdline: unrtf --nopict --html /home/mark/Dropbox/personal/sermons3/ushaw4.rtf
runlevel: N 5
Thread no. 1 (2 frames)
#0 word_print_core at convert.c:3467
#3 word_print at convert.c:3676
Created attachment 773285 [details]
Created attachment 773286 [details]
Created attachment 773287 [details]
Created attachment 773288 [details]
Created attachment 773289 [details]
Created attachment 773290 [details]
Created attachment 773291 [details]
Created attachment 773292 [details]
Created attachment 773293 [details]
Created attachment 773294 [details]
recoll desktop search began indexing the harddrive at boot up using unrtf to extract text from word documents (perhaps corrupted ones) and crashed
cmdline: unrtf --nopict --html /home/hobs/files_recovered/from_photorec/recup_dir.87/f101495104.rtf
reason: Process /usr/bin/unrtf was killed by signal 11 (SIGSEGV)
runlevel: N 5
The unrtf package should really be updated to at least 0.21.3, there were major changes and cleanups in this version.
In any case, the problem input file should be tested against 0.21.3 or newer.
Hi Mark, mind testing against 0.21.9? I've submitted it for testing today, and it should be signed and pushed out to the updates-testing mirrors soon.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.