Red Hat Bugzilla – Bug 1252537
[abrt] bluefish: _gtk_search_engine_finished(): bluefish killed by SIGSEGV
Last modified: 2016-07-19 13:28:40 EDT
Description of problem:
Inside Open dialogue I tried to search for .bashrc file in ~ directory. When I started typing .bashrc, the editor crashed.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 _gtk_search_engine_finished at gtksearchengine.c:375
#1 g_cclosure_marshal_VOID__STRINGv at gmarshal.c:1794
#2 _g_closure_invoke_va at gclosure.c:831
#5 _gtk_search_engine_error at gtksearchengine.c:386
#6 query_callback at gtksearchenginetracker.c:297
#7 g_simple_async_result_complete at gsimpleasyncresult.c:763
#8 g_dbus_connection_call_done at gdbusconnection.c:5502
#9 g_simple_async_result_complete at gsimpleasyncresult.c:763
#10 complete_in_idle_cb at gsimpleasyncresult.c:775
#15 gtk_main at gtkmain.c:1219
Created attachment 1061581 [details]
Created attachment 1061582 [details]
Created attachment 1061583 [details]
Created attachment 1061584 [details]
Created attachment 1061585 [details]
Created attachment 1061586 [details]
Created attachment 1061587 [details]
Created attachment 1061588 [details]
Created attachment 1061589 [details]
Created attachment 1061590 [details]
Created attachment 1061591 [details]
Created attachment 1061592 [details]
This is unlikely to be a Bluefish bug. The GTKFileChooser dialog is part of GTK itself. As is the search function of the dialog. The crash appears to have originated in the search function.
Upstream thinks this is a GTK bug.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.