Bug 1377287 - [epiphany] error 71 (Protocol error) dispatching to Wayland display
Summary: [epiphany] error 71 (Protocol error) dispatching to Wayland display
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk3
Version: 25
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-19 11:39 UTC by Joachim Frieben
Modified: 2016-09-24 14:02 UTC (History)
5 users (show)

Fixed In Version: gtk3-3.21.6-2.fc25
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-24 14:02:53 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 771561 0 Normal RESOLVED Epiphany application mode on Wayland broken with WebKit 2.13.92 2020-01-04 05:23:45 UTC

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"
Note You need to log in before you can comment on or make changes to this bug.