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
Created attachment 949877 [details] File: backtrace
Created attachment 949878 [details] File: cgroup
Created attachment 949879 [details] File: core_backtrace
Created attachment 949880 [details] File: dso_list
Created attachment 949881 [details] File: environ
Created attachment 949882 [details] File: exploitable
Created attachment 949883 [details] File: limits
Created attachment 949884 [details] File: maps
Created attachment 949885 [details] File: open_fds
Created attachment 949886 [details] File: proc_pid_status
Created attachment 949887 [details] File: var_log_messages
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
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.
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.