After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 773205 - GLES2 aborts with "Gdk-ERROR: Error flushing display: Broken pipe" quickly
GLES2 aborts with "Gdk-ERROR: Error flushing display: Broken pipe" quickly
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: Wayland
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2016-10-19 07:34 UTC by Sodhi, Cedric
Modified: 2018-04-15 00:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sodhi, Cedric 2016-10-19 07:34:30 UTC
No X11 libraries, therefore no GLX and MESA is compiled without OpenGL support and only GLES2 support (libepoxy was patched to compile under these circumstances by applying the for instance https://github.com/anholt/libepoxy/pull/80 - but that shouldn't affect the matter at hand).

libepoxy also had another bug, which would fail to report the correct value from epoxy_egl_get_current_gl_context_api (s.a. https://github.com/anholt/libepoxy/pull/90). Consequential attempts to load libGL.so would crash any GTK program. For the sake of testing GLES2 capabilities, epoxy_egl_get_current_gl_context_api was modified and hardcoded to return EGL_OPENGL_ES_API to the effect that GTK/epoxy would no longer attempt to load libGL.so - (hopefully), this shouldn't affect the matter at hand, either.

Then, with, for example WebkitGTK+ / MiniBrowser starting the program does succeed (in the sense that it does not crash due to missing libGL.so). It also seems to be able to render pages.

However (for example), right clicking on the page to bring up the context menu will terminate the program with

Gdk-ERROR **: Error flushing display: Broken pipe.

The backtrace is inconclusive as far as I can see, from bottom to top:

main -> gtk_main -> g_main_loop_run -> ?? (glib) -> g_main_context_prepare -> gdk_event_source_prepare(wayland/gdkeventsource.c:66) -> g_log ...
Comment 1 Matthias Clasen 2018-02-10 05:21:19 UTC
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 2 Matthias Clasen 2018-04-15 00:24:27 UTC
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new