Red Hat Bugzilla – Bug 859211
[abrt] evince-3.4.0-2.fc17: Process /usr/bin/evince was killed by signal 11 (SIGSEGV)
Last modified: 2012-12-11 01:01:53 EST
Description of problem:
I was trying to open djvu file named "Котеров,Костарев - PHP 5.2ed.2009.djvu" and also, another file with name "- PHP 5.2ed.2009.djvu" (this file are from differrent locations — one from my home directory and another from my second HDD).
With 10 other djvu files all is fine.
Version-Release number of selected component:
libreport version: 2.0.13
cmdline: evince '/mnt/bad/tmp/PHP5_2izd_koterov/- PHP 5.2ed.2009.djvu'
Created attachment 615087 [details]
Created attachment 615088 [details]
Created attachment 615089 [details]
Created attachment 615090 [details]
Created attachment 615091 [details]
Created attachment 615092 [details]
Created attachment 615093 [details]
Created attachment 615094 [details]
*** Bug 859213 has been marked as a duplicate of this bug. ***
This looks like a problem in djvulibre. I'm reassigning this.
Can you please attach one of the files that is giving you a problem?
Also, what happens if you open the file with djview4 ?
No problems with djview4. I can attach file but later.
Created attachment 620647 [details]
File that cause a program crash
djvulibre-18.104.22.168-1.fc18 has been submitted as an update for Fedora 18.
djvulibre-22.214.171.124-1.fc17 has been submitted as an update for Fedora 17.
I've updated the djvulibre package to the latest upstream version - please test with these.
However, since djview4 opens these files without issue, I think the bug lies in the way evince is using the library.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing djvulibre-126.96.36.199-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
djvulibre-188.8.131.52-2.fc18 has been submitted as an update for Fedora 18.
djvulibre-184.108.40.206-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.