Description of problem: This felt a lot like Bug 1050735, but abrt didn't think so, so here goes: Opened Photoshop document Placed some guides Copied, and pasted-as-new a couple pieces Exported my pieces as .jpgs. Done! Closed Gimp. Gimp asked if I wanted to save each image (1 imported .psd + 2 exported .jpgs) No. No. No. Then crash with the last Save? dialog still showing. Version-Release number of selected component: gimp-2.8.10-4.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/gimp-2.8 crash_function: gtk_widget_queue_draw executable: /usr/bin/gimp-2.8 kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_widget_queue_draw at gtkwidget.c:3779 #2 Oxygen::ToolBarStateData::delayedUpdate at /usr/src/debug/oxygen-gtk2-1.4.1/src/animations/oxygentoolbarstatedata.cpp:330 #3 Oxygen::ToolBarStateData::updateState at /usr/src/debug/oxygen-gtk2-1.4.1/src/animations/oxygentoolbarstatedata.cpp:176 #4 Oxygen::ToolBarStateData::registerChild at /usr/src/debug/oxygen-gtk2-1.4.1/src/animations/oxygentoolbarstatedata.cpp:115 #5 Oxygen::draw_box at /usr/src/debug/oxygen-gtk2-1.4.1/src/oxygenstylewrapper.cpp:1096 #6 _gtk_button_paint at gtkbutton.c:1511 #7 gtk_toggle_button_expose at gtktogglebutton.c:440 #8 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 #13 gtk_widget_event_internal at gtkwidget.c:5017 #14 gtk_widget_send_expose at gtkwidget.c:4846 Potential duplicate: bug 1015759
Created attachment 847873 [details] File: backtrace
Created attachment 847874 [details] File: cgroup
Created attachment 847875 [details] File: core_backtrace
Created attachment 847876 [details] File: dso_list
Created attachment 847877 [details] File: environ
Created attachment 847878 [details] File: exploitable
Created attachment 847879 [details] File: limits
Created attachment 847880 [details] File: maps
Created attachment 847881 [details] File: open_fds
Created attachment 847882 [details] File: proc_pid_status
Created attachment 847883 [details] File: var_log_messages
*** Bug 1015759 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.