Bug 1156054

Summary: [abrt] evince: append_escaped_text(): evince killed by SIGSEGV
Product: [Fedora] Fedora Reporter: h2obrain
Component: evinceAssignee: Marek Kašík <mkasik>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: bugs.michael, mkasik
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/0bc8f1094b181db97a12aee90052029d949b99e9
Whiteboard: abrt_hash:e8165860fc2cd04a9bc27a3661a98d86c1d79938
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 04:28:24 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: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description h2obrain 2014-10-23 13:32:15 UTC 
Description of problem:
Search something

It seems when I type too slow, the search function crashes evince when it has found too many entries.
Eg. search for PE3 in a STM32 chip datasheet works, typing PE and wait crashes evince

Version-Release number of selected component:
evince-3.14.1-1.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        evince '/media/Laserdrive/Public/Oliver/LC3 Data/MCU/STM32F427xx_429xx - Datasheet.pdf'
crash_function: append_escaped_text
executable:     /usr/bin/evince
kernel:         3.17.1-302.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (8 frames)
 #0 append_escaped_text at gmarkup.c:2163
 #1 g_markup_escape_text at gmarkup.c:2239
 #2 g_markup_vprintf_escaped at gmarkup.c:2492
 #3 g_markup_printf_escaped at gmarkup.c:2551
 #4 get_surrounding_text_markup at ev-find-sidebar.c:381
 #5 process_matches_idle at ev-find-sidebar.c:512
 #9 g_main_context_iteration at gmain.c:3842
 #10 g_application_run at gapplication.c:2282

Potential duplicate: bug 916466
Comment 1 h2obrain 2014-10-23 13:32:18 UTC 
Created attachment 949877 [details]
File: backtrace
Comment 2 h2obrain 2014-10-23 13:32:19 UTC 
Created attachment 949878 [details]
File: cgroup
Comment 3 h2obrain 2014-10-23 13:32:20 UTC 
Created attachment 949879 [details]
File: core_backtrace
Comment 4 h2obrain 2014-10-23 13:32:21 UTC 
Created attachment 949880 [details]
File: dso_list
Comment 5 h2obrain 2014-10-23 13:32:22 UTC 
Created attachment 949881 [details]
File: environ
Comment 6 h2obrain 2014-10-23 13:32:23 UTC 
Created attachment 949882 [details]
File: exploitable
Comment 7 h2obrain 2014-10-23 13:32:24 UTC 
Created attachment 949883 [details]
File: limits
Comment 8 h2obrain 2014-10-23 13:32:26 UTC 
Created attachment 949884 [details]
File: maps
Comment 9 h2obrain 2014-10-23 13:32:27 UTC 
Created attachment 949885 [details]
File: open_fds
Comment 10 h2obrain 2014-10-23 13:32:28 UTC 
Created attachment 949886 [details]
File: proc_pid_status
Comment 11 h2obrain 2014-10-23 13:32:29 UTC 
Created attachment 949887 [details]
File: var_log_messages
Comment 12 Michael Schwendt 2014-11-10 17:00:49 UTC 
Another user experienced a similar problem:

I deleted and entered a different word ("250") in the search box. ABRT refuses to use generate a backtrace:
Retrace server is unable to process package 'evince-3.14.1-3.fc21.x86_64'.

reporter:       libreport-2.3.0
backtrace_rating: 3
cmdline:        evince /home/ms20/tmp/ringsumuns_ruu_2009_15.pdf
crash_function: append_escaped_text
executable:     /usr/bin/evince
kernel:         3.17.2-300.fc21.x86_64
package:        evince-3.14.1-3.fc21
reason:         evince killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 13 Fedora End Of Life 2015-11-04 14:54:47 UTC 
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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'
of '21'.

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 21 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.
Comment 14 Fedora End Of Life 2015-12-02 04:28:27 UTC 
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.