GNOME Bugzilla – Bug 741011
"Pick better system rgba visuals for GL" broke wayland
Last modified: 2016-01-10 18:37:02 UTC
Just got this mail: ---------------------------- gtk+ commit dae447728db32a5a7162d9216f2e2343837cbae4 gnome-wayland session hasn't been working for me with gtk+ git, I've bisected to the above commit. I think the problem is, the code also gets run with Xwayland and it gets stuck somewhere due the Xwayland not being ready yet. Does it even make sense run _gdk_x11_screen_update_visuals_for_gl() when running gnome-wayland? Commenting out the call makes git master work again for me. ---------------------------- I don't know the details here. Does Xwayland support GLX?
Jasper: Any ideas?
Xwayland definitely supports GLX, however as I understand it, the compositor is responsible for launching the Xwayland server*, and setting the environment for X11 clients. I'm not sure about the code flow though. I'm running a patched gtk+ to try the wayland gdk backend first, which isn't as tested as I think it should be. Right now I get this behaviour from gnome-shell: launch wayland application->env contains no DISPLAY launch X application->env contains DISPLAY=:1 gnome-shell knows the Xwayland display number, but would _gdk_x11_screen_update_visuals_for_gl() ? *The compositor listens on the X server port, and launches Xwayland on demand, and closes it down when the last client exits.
Created attachment 291984 [details] Xwayland glxinfo output This is my glxinfo output when running under gnome-shell wayland.
(In reply to comment #2) > I'm running a patched gtk+ to try the wayland gdk backend first, which isn't as > tested as I think it should be. Right now I get this behaviour from > gnome-shell: No need to patch gtk for that, just use GDK_BACKEND=wayland,x11 <your app> to try wayland before x11
That doesn't affect anything launched from gnome-shell itself.
(In reply to comment #0) > I don't know the details here. Does Xwayland support GLX? Yep. Do you know why it hangs or where it hangs on?
This seems to be a general DRI3 issue: https://bugzilla.redhat.com/show_bug.cgi?id=1174257
Alex: the bug you linked only affects remote/indirect GLX, not local sessions.
Daniel: It seems similar though, and I was thinking maybe Xwayland is similar to remote in the sense that it doesn't support DRI3 (or maybe it does?)
Not sure if it does or doesn't, but the issue over remote specifically was that it was hitting DRI3 codepaths with a totally valid DRI3 setup, but Xorg would get confused about the inability to send file descriptors over a remote connection and just do nothing useful, leaving the client hanging. Since the connection is local, even if it's DRI3 at fault (which would leave me extremely unsurprised), it can't be the same bug per se.
current GTK+ works fine under wayland.