Thanks for giving me access to poke around. The conclusion is: the Pbuffer implementation in the amdgpu driver you're using is resoundingly broken and not at all compliant with the GLX specification. However, fortunately there's a better workaround than using Pixmaps. It seems that setting VGL_FORCEALPHA=1 in the environment is the magic formula. That forces VirtualGL to return only 32-bit (alpha-channel-enabled) visuals and GLXFBConfigs to the application, as well as to use only 32-bit GLXFBConfigs when creating its own Pbuffers. So the underlying issue seems to be that amdgpu doesn't handle 24-bit Pbuffers.
On 2/15/19 3:44 PM, 'Richard' via VirtualGL User Discussion/Support wrote: > On Fri, 15 Feb 2019 13:48:33 -0600 > DRC <[email protected]> wrote: > >> You could actually do that for VGL as well, but it's useful to make sure >> you can build VGL so I'll be able to do likewise. :) > > Last night's VGL git clone has just compiled with no issues and all > options left at the defaults. The installed version is > virtualgl-2.6.1-4.mga7 from 6 Jan 2019. > > Would you like it out of the way or can you run test builds with it in > place? > > I have also installed debug-info and debug-source rpms for VGL, GL, > GLU, Mesa in case you might find these useful. -- You received this message because you are subscribed to the Google Groups "VirtualGL User Discussion/Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/caed11f8-31e1-4ea2-682a-f00b2ec82d88%40virtualgl.org. For more options, visit https://groups.google.com/d/optout.
