[X2Go-User] Fedora 36 and glx fails with GLXUnsupportedPrivateRequest

[sairuk]

I played with these a bit beforehand, both glxinfo -i  and
LIBGL_ALWAYS_INDIRECT=1 will product the same results for a glxinfo run

glxinfo -i results: https://termbin.com/hwu2

LIBGL_DEBUG=verbose output with or without -i it is the same additional
output

name of display: :50.0
libGL: MESA-LOADER: dlopen(/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so)
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/user/.drirc: No such file or
directory.
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/user/.drirc: No such file or
directory.
X Error of failed request:  GLXUnsupportedPrivateRequest
  Major opcode of failed request:  143 (GLX)
  Minor opcode of failed request:  17 (X_GLXVendorPrivateWithReply)
  Serial number of failed request:  27
  Current serial number in output stream:  27

I also tried a few of the mesa envvars but I can't find my notes, so I'll
have to go through them again although I do recall MESA_DEBUG not adding
anything additional to this output and a couple of the others broke the
output in weird and wonderful ways.

https://docs.mesa3d.org/envvars.html

sai

On Sun, Jun 12, 2022 at 11:00 PM Ulrich Sibiller <uli42 at gmx.de> wrote:

> If I get that right GLX offers the X_GLXVendorPrivateWithReply
> request. This request knows 4 subcommands in NX:
>
> __GLXdispatchVendorPrivProcPtr
> __glXVendorPrivTable_EXT[__GLX_MAX_VENDPRIV_OPCODE_EXT -
> __GLX_MIN_VENDPRIV_OPCODE_EXT + 1] = {
>        __glXDisp_AreTexturesResidentEXT, /* 11 */
>        __glXDisp_DeleteTextures, /* 12 */
>        __glXDisp_GenTexturesEXT, /* 13 */
>        __glXDisp_IsTextureEXT, /* 14 */
>
> So chances are that glxinfo is using another one. So probably our Mesa
> version 6.4.2 does not come with this/those additional subcommands.
>
> I am wondering if we can tweak glxinfo to work nevertheless. Can you
> please try if LIBL_DEBUG=verbose glxinfo shows more information? Can
> you check the environment variables mentioned here:
> https://dri.freedesktop.org/wiki/TestingAndDebugging/? Does it make a
> difference if you call glxinfo with -i?
>
> Uli
>
>
> On Sun, Jun 12, 2022 at 1:01 AM sairuk <sairuk at gmail.com> wrote:
> >
> > Thanks Neal, this is what I ended up doing as well for Zoom.
> >
> > The Zoom issue led me to note the difference in behaviour after it
> started crashing, I want to be careful not to detract from the actual glx
> issue even if it turns out to be mesa related.
> >
> > Unfortunately no movement on the bug Norman raised yet
> >
> > sai
> >
> > On Sun, Jun 12, 2022 at 12:28 AM Neal Becker <ndbecker2 at gmail.com>
> wrote:
> >>
> >> sairuk wrote:
> >>
> >> > Maybe they did, couldn't say. my use case probably won't be a popular
> one
> >> > but i'll run it through it anyway. My setup might not even be optimal
> so I
> >> > am happy to consider advice.
> >> >
> >> > This was a finding while I was investigating why Zoom started crashing
> >> > after the whiteboard update (only if the whiteboard was open, and it
> was
> >> > only for me). I've been using Zoom within x2go XFCE sessions since
> 2020
> >> > without issue, (recommended or not) it works fine for daily use imo. I
> >> > could rollback Zoom to 5.9.x series and it was/is fine. Unfortunately
> due
> >> > to a vuln in the xmpp chat protocol implementation of Zoom min
> versions
> >> > needed to be enforced at 5.10.x series which has the new whiteboard
> >> > implementation.
> >> >
> >> > Additional to updating Zoom I'd inplace upgraded the x2go endpoint OS
> from
> >> > 20.04 (x2go glx working, mesa 21) to 22.04 (x2go glx broken, mesa 22)
> >> > while on Zoom 5.9.x series client and only noticed some slight
> performance
> >> > degradation in general session use but hadn't bothered to investigate
> it,
> >> > I expect (now) it is related to the lack of glx.
> >> >
> >> > Zoom will not start without the glx extension, and using
> >> > LIBGL_INDIRECT_ALWAYS is problematic (slow) as were some other envars
> I
> >> > was testing which broke a lot of additional stuff. I don't have my
> notes
> >> > with me now though.
> >> >
> >> >
> >> If you just want to use zoom then use their web app instead of the
> native
> >> zoom app.  I always do this with zoom, teams, etc. because the options
> for
> >> sharing are better in chrome than the native apps.
> >>
> >> _______________________________________________
> >> x2go-user mailing list
> >> x2go-user at lists.x2go.org
> >> https://lists.x2go.org/listinfo/x2go-user
> >
> > _______________________________________________
> > x2go-user mailing list
> > x2go-user at lists.x2go.org
> > https://lists.x2go.org/listinfo/x2go-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.x2go.org/pipermail/x2go-user/attachments/20220613/94ab1e11/attachment.htm>