Bug 957009

Summary: [abrt] evince-3.6.1-2.fc18: strlen: Process /usr/bin/evince was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: s.sickert
Component: cairoAssignee: Benjamin Otte <otte>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: mkasik, otte, sog, udo.rader
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:ae41143724d8a38b7420eef2cded5da4e0a47fc8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 21:05:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
File: xsession_errors
none
A naive fix none

Description s.sickert 2013-04-26 07:55:47 UTC
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

Comment 1 s.sickert 2013-04-26 07:55:51 UTC
Created attachment 740254 [details]
File: backtrace

Comment 2 s.sickert 2013-04-26 07:55:56 UTC
Created attachment 740255 [details]
File: core_backtrace

Comment 3 s.sickert 2013-04-26 07:55:59 UTC
Created attachment 740256 [details]
File: dso_list

Comment 4 s.sickert 2013-04-26 07:56:04 UTC
Created attachment 740257 [details]
File: environ

Comment 5 s.sickert 2013-04-26 07:56:07 UTC
Created attachment 740258 [details]
File: limits

Comment 6 s.sickert 2013-04-26 07:56:09 UTC
Created attachment 740259 [details]
File: maps

Comment 7 s.sickert 2013-04-26 07:56:13 UTC
Created attachment 740260 [details]
File: open_fds

Comment 8 s.sickert 2013-04-26 07:56:16 UTC
Created attachment 740261 [details]
File: proc_pid_status

Comment 9 s.sickert 2013-04-26 07:56:19 UTC
Created attachment 740262 [details]
File: var_log_messages

Comment 10 s.sickert 2013-04-26 07:56:21 UTC
Created attachment 740263 [details]
File: xsession_errors

Comment 11 Max DW 2013-05-29 14:28:38 UTC
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:

Comment 12 Salvador Ortiz 2013-07-25 20:25:10 UTC
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.

Comment 13 Marek Kašík 2013-10-25 09:50:00 UTC
Hi Salvador,

thank you for the fix! I'm reassigning this to cairo (see http://cgit.freedesktop.org/cairo/commit/?id=274863be08f6c8df6d411df9db725d34f7fbabea).

Regards

Marek

Comment 14 Marek Kašík 2013-10-25 09:54:46 UTC
*** Bug 913571 has been marked as a duplicate of this bug. ***

Comment 15 Fedora End Of Life 2013-12-21 13:15:22 UTC
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.

Comment 16 Fedora End Of Life 2014-02-05 21:05:54 UTC
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.