Bug 1377287

Summary: [epiphany] error 71 (Protocol error) dispatching to Wayland display
Product: [Fedora] Fedora Reporter: Joachim Frieben <jfrieben>
Component: gtk3Assignee: Matthias Clasen <mclasen>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: cosimo.cecchi, gecko-bugs-nobody, mcatanzaro+wrong-account-do-not-cc, mclasen, rob.townley
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: gtk3-3.21.6-2.fc25 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-24 14:02:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Joachim Frieben 2016-09-19 11:39:52 UTC 
Description of problem:
In a Fedora 25 "GNOME" (on Wayland) session, browser "Web" (epiphany) aborts when launched with the error message:

  "(epiphany:1842): Gdk-WARNING **: Error 71 (Protocol error) dispatching to
   Wayland display."

Version-Release number of selected component (if applicable):
epiphany-3.21.92-1.fc25

How reproducible:
Always

Steps to Reproduce:
1. Start "GNOME" (on Wayland) session.
2. Launch "Web" (epiphany).

Actual results:
"Web" (epiphany) aborts and emits error message cited above.

Expected results:
"Web" (epiphany) starts up as expected.

Additional info:
1. 'GDK_BACKEND=x11 epiphany' starts up successfully.
2. In a virtual "GNOME" (on Wayland) guest session but not on real hardware,
   the error message is preceded by the message:
   "WaylandCompositor requires eglCreateImage and eglDestroyImage.
   Nested Wayland compositor could not initialize EGL".
Comment 1 Michael Catanzaro 2016-09-19 16:19:07 UTC 
Should be fixed in GTK+ 3.22.0
Comment 2 Michael Catanzaro 2016-09-19 16:19:35 UTC 
(In reply to Michael Catanzaro from comment #1)
> Should be fixed in GTK+ 3.22.0

Actually the patch isn't upstream yet. So "hopefully" rather than "should"