Description of problem: 1, Download http://www-m9.ma.tum.de/foswiki/pub/SS2013/ATGT/ex01.pdf 2, Open the file 3, Print the file Version-Release number of selected component: evince-3.6.1-2.fc18 Additional info: backtrace_rating: 4 cmdline: evince /var/tmp/ex01.pdf crash_function: strlen executable: /usr/bin/evince kernel: 3.8.8-202.fc18.x86_64 uid: 1000 ureports_counter: 7 Truncated backtrace: Thread no. 1 (10 frames) #0 strlen at ../sysdeps/x86_64/strlen.S:31 #1 write_used_glyphs at cairo-type1-subset.c:1147 #2 cairo_type1_font_subset_for_each_glyph at cairo-type1-subset.c:1229 #3 cairo_type1_font_subset_write_private_dict at cairo-type1-subset.c:1480 #4 cairo_type1_font_subset_write at cairo-type1-subset.c:1587 #5 cairo_type1_font_subset_generate at cairo-type1-subset.c:1659 #6 _cairo_type1_subset_init at cairo-type1-subset.c:1724 #8 _cairo_pdf_surface_emit_type1_font_subset at cairo-pdf-surface.c:5039 #9 _cairo_pdf_surface_emit_unscaled_font_subset at cairo-pdf-surface.c:5566 #10 _cairo_sub_font_collect at cairo-scaled-font-subsets.c:746
Created attachment 740254 [details] File: backtrace
Created attachment 740255 [details] File: core_backtrace
Created attachment 740256 [details] File: dso_list
Created attachment 740257 [details] File: environ
Created attachment 740258 [details] File: limits
Created attachment 740259 [details] File: maps
Created attachment 740260 [details] File: open_fds
Created attachment 740261 [details] File: proc_pid_status
Created attachment 740262 [details] File: var_log_messages
Created attachment 740263 [details] File: xsession_errors
Just trying to print, and evince crashes... reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: evince '/home/helene/T\xc3\xa9l\xc3\xa9chargements/O.J. 12 juin 2013.pdf' crash_function: strlen executable: /usr/bin/evince kernel: 3.9.4-200.fc18.x86_64 package: evince-3.6.1-2.fc18 reason: Process /usr/bin/evince was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000 xsession_errors:
Created attachment 778507 [details] A naive fix After segfaults in inkscape and rsvg-convert with the same backtrace, I located the problem in cairo. This fixed both cases. I filled bug 67324 in freedesktop.org's bugzilla. Regards.
Hi Salvador, thank you for the fix! I'm reassigning this to cairo (see http://cgit.freedesktop.org/cairo/commit/?id=274863be08f6c8df6d411df9db725d34f7fbabea). Regards Marek
*** Bug 913571 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.