Description of problem: I attempted to browse to extensions.gnome.org Version-Release number of selected component: epiphany-runtime-3.16.0-1.fc22 Additional info: reporter: libreport-2.5.0 backtrace_rating: 4 cmdline: epiphany crash_function: XGetWindowAttributes executable: /usr/bin/epiphany global_pid: 6940 kernel: 4.0.0-0.rc4.git0.1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 13041 Truncated backtrace: Thread no. 1 (10 frames) #0 XGetWindowAttributes at /lib64/libX11.so.6 #1 gtk_socket_realize at /lib64/libgtk-3.so.0 #2 _g_closure_invoke_va at /lib64/libgobject-2.0.so.0 #5 gtk_widget_realize at /lib64/libgtk-3.so.0 #6 gtk_widget_set_parent at /lib64/libgtk-3.so.0 #7 webkitWebViewBaseContainerAdd(_GtkContainer*, _GtkWidget*) at /lib64/libwebkit2gtk-4.0.so.37 #8 g_cclosure_marshal_VOID__OBJECTv at /lib64/libgobject-2.0.so.0 #9 _g_closure_invoke_va at /lib64/libgobject-2.0.so.0 #12 gtk_container_add at /lib64/libgtk-3.so.0 #13 WebKit::WebPageProxy::createPluginContainer(unsigned long&) at /lib64/libwebkit2gtk-4.0.so.37
Created attachment 1007206 [details] File: backtrace
Created attachment 1007207 [details] File: cgroup
Created attachment 1007208 [details] File: core_backtrace
Created attachment 1007209 [details] File: dso_list
Created attachment 1007210 [details] File: environ
Created attachment 1007211 [details] File: limits
Created attachment 1007212 [details] File: maps
Created attachment 1007213 [details] File: mountinfo
Created attachment 1007214 [details] File: namespaces
Created attachment 1007215 [details] File: open_fds
Created attachment 1007216 [details] File: proc_pid_status
Created attachment 1007217 [details] File: var_log_messages
This looks like a bug in WebKit, not in the browser plugin. Does this happen every time you visit extensions.gnome.org? Are you running GNOME in Wayland?
It doesn't seem to be happening to me today. I don't think I was using Wayland that day, but I don't recall for sure. I'll retest later with Wayland.
Well looking at the backtrace and seeing it didn't get any debuginfo, I'm going to move this one to ABRT too. We have no shortage of bugs with good backtraces that it's not worth spending time on ones that ABRT screwed up.
Did you generated the backtrace locally (downloading debuginfo packages) or remotely (uploading the coredump to the retrace server)?
(I am not the reporter but I ran into the same bug and abrt pointed me here) I generated the backtrace locally using gnome-abrt. I don't remember whether I downloaded and installed those packages using `dnf debuginfo-install [packagenames]` or directly by using the gnome-abrt UI.
Honestly, I don't know the answer to those questions any more and when I attempt to reach extensions.gnome.org from Epiphany these days, it appears to work (at least on X)
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.