Version-Release number of selected component: gimp-2.8.4-1.fc18 Additional info: backtrace_rating: 4 cmdline: gimp-2.8 crash_function: _gail_text_view_delete_range_cb executable: /usr/bin/gimp-2.8 kernel: 3.7.9-201.fc18.x86_64 uid: 1000 ureports_counter: 1 xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #0 _gail_text_view_delete_range_cb at gailtextview.c:1438 #5 gtk_text_buffer_emit_delete at gtktextbuffer.c:1613 #6 gtk_text_buffer_delete at gtktextbuffer.c:1644 #7 gtk_text_buffer_set_text at gtktextbuffer.c:842 #8 gimp_text_buffer_set_text at gimptextbuffer.c:208 #9 gimp_text_tool_connect at gimptexttool.c:1022 #10 gimp_text_tool_set_drawable at gimptexttool.c:1678 #11 gimp_text_tool_control at gimptexttool.c:336 #12 gimp_tool_control at gimptool.c:552 #13 tool_manager_control_active at tool_manager.c:301
Created attachment 734277 [details] File: backtrace
Created attachment 734278 [details] File: cgroup
Created attachment 734279 [details] File: core_backtrace
Created attachment 734280 [details] File: dso_list
Created attachment 734281 [details] File: environ
Created attachment 734282 [details] File: limits
Created attachment 734283 [details] File: maps
Created attachment 734284 [details] File: open_fds
Created attachment 734285 [details] File: proc_pid_status
Created attachment 734286 [details] File: var_log_messages
Please describe (as details as possible) what you did when GIMP crashes. If you can provide step-by-step instructions to reproduce this issue, it would be very helpful to fix this bug.
This bug is fixed upstream in gtk-2-24: commit ba5ac33cdc18fe252de9baac6a2927f9ea77e6ab Author: Michael Natterer <mitch> Date: Sun Apr 21 05:09:52 2013 +0200 entry: unset the completion in dispose() not finalize() Most likely fixes whatever evil gail interaction causing a crash I could never reproduce but has been reported several times against GIMP. The same fix is in GTK+ 3.x already (bug #683983). gtk/gtkentry.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
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.
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.