Version-Release number of selected component: gimp-2.8.2-6.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: gimp-2.8 crash_function: file_save_dialog_response kernel: 3.6.10-2.fc17.i686.PAE truncated backtrace: :Thread no. 1 (9 frames) : #0 file_save_dialog_response at file-save-dialog.c:203 : #1 g_cclosure_marshal_VOID__INT at gmarshal.c:372 : #6 gtk_dialog_response at gtkdialog.c:932 : #7 g_cclosure_marshal_VOID__VOIDv at gmarshal.c:115 : #8 _g_closure_invoke_va at gclosure.c:840 : #11 gtk_button_clicked at gtkbutton.c:1128 : #12 gtk_button_finish_activate at gtkbutton.c:1803 : #13 button_activate_timeout at gtkbutton.c:1743 : #20 app_run at app.c:256
Created attachment 670013 [details] File: core_backtrace
Created attachment 670014 [details] File: environ
Created attachment 670015 [details] File: backtrace
Created attachment 670016 [details] File: limits
Created attachment 670017 [details] File: smolt_data
Created attachment 670018 [details] File: cgroup
Created attachment 670019 [details] File: executable
Created attachment 670020 [details] File: maps
Created attachment 670021 [details] File: dso_list
Created attachment 670022 [details] File: proc_pid_status
Created attachment 670023 [details] File: build_ids
Created attachment 670024 [details] File: open_fds
Created attachment 670025 [details] File: var_log_messages
Sorry for the late response, but can you reproduce this with the current version of the gimp package (2.8.4-3)? There have been fixes in the general area where this bug seems to happen and I'd like to rule out chasing after something that's already been fixed in 2.8.4.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 17'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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.