Red Hat Bugzilla – Bug 1058503
[abrt] mate-document-viewer: active_edges(): atril killed by SIGSEGV
Last modified: 2015-06-29 10:48:22 EDT
Description of problem:
I downloaded a PDF user manual for a power washer and the software crashed upon opening it.
Version-Release number of selected component:
cmdline: atril /run/user/1000/midori/BTA-5246119-000-00.pdf
runlevel: N 5
Thread no. 1 (10 frames)
#0 active_edges at cairo-polygon-intersect.c:1235
#1 intersection_sweep at cairo-polygon-intersect.c:1271
#2 _cairo_polygon_intersect at cairo-polygon-intersect.c:1466
#3 clip_and_composite_polygon at cairo-spans-compositor.c:946
#4 _cairo_spans_compositor_stroke at cairo-spans-compositor.c:1083
#5 _cairo_compositor_stroke at cairo-compositor.c:157
#7 _cairo_image_surface_stroke at cairo-image-surface.c:964
#8 _cairo_surface_stroke at cairo-surface.c:2260
#9 _cairo_gstate_stroke at cairo-gstate.c:1194
#11 _cairo_default_context_stroke at cairo-default-context.c:1010
Created attachment 856273 [details]
Created attachment 856274 [details]
Created attachment 856275 [details]
Created attachment 856276 [details]
Created attachment 856277 [details]
Created attachment 856278 [details]
Created attachment 856279 [details]
Created attachment 856280 [details]
Created attachment 856281 [details]
Created attachment 856282 [details]
Created attachment 856283 [details]
Can you attach the culpit file?
How did you open it?
From inside caja?
Created attachment 856826 [details]
PDF file causing crash - Karcher-K5-540.PDF
I have attached file. I launched it from within the Midori browser. I also got the same results when just opening the file from within caja.
(In reply to Wolfgang Ulbrich from comment #12)
> Can you attach the culpit file?
> How did you open it?
> From inside caja?
OK, i can confirm the crash with atril, but it crashed also evince.
With acrobat reader himself i can open the document on fedora without any problem.
So i quess it's a prob with poppler libary, both atril and evince use poppler to display pdf's.
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.