Description of problem: I was editing an image in The GIMP and needed to open another image to copy stuff from. When I went to go open the other image, The GIMP crashed and I was asked to report this error. Version-Release number of selected component: marco-1.12.1-2.fc22 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: marco crash_function: array_free executable: /usr/bin/marco global_pid: 17833 kernel: 4.2.8-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #7 array_free at garray.c:365 #8 g_array_free at garray.c:346 #9 stack_sync_to_server at core/stack.c:1236 #10 meta_stack_remove at core/stack.c:159 #12 meta_window_free at core/window.c:1115 #13 event_callback at core/display.c:2228 #14 filter_func at ui/ui.c:281 #15 gdk_event_apply_filters at gdkevents-x11.c:371 #16 gdk_event_translate at gdkevents-x11.c:969 #17 _gdk_events_queue at gdkevents-x11.c:2358
Created attachment 1113759 [details] File: backtrace
Created attachment 1113760 [details] File: cgroup
Created attachment 1113761 [details] File: core_backtrace
Created attachment 1113762 [details] File: dso_list
Created attachment 1113763 [details] File: environ
Created attachment 1113764 [details] File: limits
Created attachment 1113765 [details] File: maps
Created attachment 1113766 [details] File: mountinfo
Created attachment 1113767 [details] File: namespaces
Created attachment 1113768 [details] File: open_fds
Created attachment 1113769 [details] File: proc_pid_status
Created attachment 1113770 [details] File: var_log_messages
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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.