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 768929 - glimagesink fails to open X11 display when built with --disable-x11
glimagesink fails to open X11 display when built with --disable-x11
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
git master
Other Linux
: Normal normal
: 1.9.2
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-07-18 16:26 UTC by zacattackcit
Modified: 2016-11-15 05:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description zacattackcit 2016-07-18 16:26:02 UTC 
I'm building gst-plugins-bad on the Raspberry Pi 3, so I've built it with --disable-x11.  However, I'm hitting a run time error.  When I run a test pipeline:

gst-launch-1.0 videotestsrc ! glimagesink

I get the following error:

ERROR              gldisplay gstgldisplay_wayland.c:120:gst_gl_display_wayland_new: Failed to open X11 display connection with name, '(null)'

Looks like something related to X11 is still being used?  The null name in there is also suspicious.
Comment 1 Tim-Philipp Müller 2016-07-18 16:49:55 UTC 
I think it's just the debug message that's confusing here:

 commit c593e0a17ff8a53e41c77fc7c33c0991f7c3399f
 Author: Tim-Philipp Müller <tim@centricular.com>
 Date:   Mon Jul 18 17:43:23 2016 +0100

    gl: wayland: improve debug message when connecting to display
    
    And another copy'n'paste-o.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=768929

name=NULL means use the default.

Do other wayland apps work from that command line? Maybe you need to set WAYLAND_DISPLAY explicitly?