Version-Release number of selected component: epiphany-runtime-3.15.90-4.fc22 Additional info: reporter: libreport-2.4.0 backtrace_rating: 4 cmdline: epiphany crash_function: g_type_check_instance_cast executable: /usr/bin/epiphany kernel: 4.0.0-0.rc3.git0.1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (7 frames) #0 g_type_check_instance_cast at gtype.c:4060 #1 window_focus_out at gtkpopover.c:391 #2 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:85 #7 gtk_widget_event_internal at gtkwidget.c:7787 #8 gtk_main_do_event at gtkmain.c:1703 #13 g_main_context_iteration at gmain.c:3869 #14 g_application_run at gapplication.c:2308
Created attachment 1003553 [details] File: backtrace
Created attachment 1003554 [details] File: cgroup
Created attachment 1003555 [details] File: core_backtrace
Created attachment 1003556 [details] File: dso_list
Created attachment 1003557 [details] File: environ
Created attachment 1003558 [details] File: limits
Created attachment 1003559 [details] File: maps
Created attachment 1003560 [details] File: open_fds
Created attachment 1003561 [details] File: proc_pid_status
Created attachment 1003562 [details] File: var_log_messages
Also reported against California and Nautilus, so most likely a GTK+ bug.
Suggested fix here: https://bugzilla.gnome.org/show_bug.cgi?id=747539
gtk3-3.14.12-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/gtk3-3.14.12-1.fc21
Package gtk3-3.14.12-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gtk3-3.14.12-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-5920/gtk3-3.14.12-1.fc21 then log in and leave karma (feedback).
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.