Red Hat Bugzilla – Bug 1253775
[abrt] gedit: gtk_text_iter_make_real(): gedit killed by SIGSEGV
Last modified: 2016-07-19 13:30:44 EDT
Description of problem:
Think this crash happened when my wired network connection went away. I was using USB tethering and stepped away from the system for a time; I think the tethering in Android is set to turn off if no data passes for some time. So when I came back it was off. I tried to run a search in gedit (ctrl+f) and it just crashed.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 gtk_text_iter_make_real at gtktextiter.c:213
#1 gtk_text_iter_forward_to_tag_toggle at gtktextiter.c:4189
#2 smart_forward_search_async_step at gtksourcesearchcontext.c:1019
#3 smart_forward_search_async at gtksourcesearchcontext.c:1110
#4 gtk_source_search_context_forward_async at gtksourcesearchcontext.c:3343
#5 start_search at gedit/gedit-view-frame.c:393
#6 search_entry_changed_cb at gedit/gedit-view-frame.c:1163
#10 g_signal_emit_by_name at gsignal.c:3401
#11 end_change at gtkentry.c:2921
#15 g_signal_emit_by_name at gsignal.c:3401
Potential duplicate: bug 1196831
Created attachment 1063078 [details]
Created attachment 1063079 [details]
Created attachment 1063080 [details]
Created attachment 1063081 [details]
Created attachment 1063082 [details]
Created attachment 1063083 [details]
Created attachment 1063084 [details]
Created attachment 1063085 [details]
Created attachment 1063086 [details]
Created attachment 1063087 [details]
Created attachment 1063088 [details]
Created attachment 1063089 [details]
Another user experienced a similar problem:
1: I opened a plain text (XML) file in gedit. The file contained two lines - first a short line (XML declaration) and second a very very long line (all the rest of the XML code).
2: I tried to find a string which should have been in the second line. After pressing CTRL+F gedit shown the search widget for inputting the searched text and I entered it.
3: gedit was not responding for a while.
4: The 'application is not responding' pop-up window was shown to me and I quit gedit.
5. I opened gedit once again.
6: I tried to do the steps 1 and 2 again.
7: gedit was not responding for a while and then quit itself.
cmdline: /usr/bin/gedit --gapplication-service
reason: gedit killed by SIGSEGV
runlevel: N 5
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.