-
-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blank screen on KDE with VirtualGL on EGL with NVIDIA #224
Comments
It works if the compositor is off, but when it's on, it doesn't work with or without +wm. |
Hard to say. Regular Qt applications work with VirtualGL, so I would need a better understanding of what Plasma is doing differently. Unfortunately, the odds that I will be able to look into this anytime soon are close to zero. TurboVNC doesn't officially support Plasma, so it falls into the category of "community support." That means that I am happy to integrate patches that fix issues with it, but diagnosing those issues isn't something I can do outside of the context of a paid support contract. |
I needed the compositor off anyways, so it will be kept that way for now... |
About how much would be the range of that paid contract, by the way? We have a potential sponsor. |
Contact me through e-mail: |
There is one way to use VirtualGL + KWin Compositing: Set |
XRender is not in Ubuntu 22.04. Possible fix:
I will tell you if it is successful, and if you should add that to the docs or not. |
It's still broken. The last time I made it work was through llvmpipe. I guess it's something with the pixmaps that must be supported. |
Is there a way to tell Qt to use GLX ( |
Possible, however the VLC issue arise additionally in 3.0.91. This issue is in 3.0.2 as well as 3.0.9x. I am trying to make some time for reproducing this. |
Nope, not solved. Plus, an immense black border around Firefox. |
|
Yeah, I personally observed the issue after the VLC issue was fixed, and that issue affected the EGL/X11 front end, whereas this issue affects the GLX front end with the EGL back end. I suspect that it's because the EGL back end doesn't yet implement |
What would be the steps needed for support? |
Contact me through e-mail: |
Any news on this front? It might be worth trying the latest pre-release build, which includes a fix for the EGL back end that affected other applications. |
Hi, Darrell. Always a pleasure to converse with you. |
Lastest 3.1.x Stable build: |
Related to: https://gitlab.gnome.org/GNOME/gtk/-/issues/4815
|
Environment: Ubuntu 22.04 with KDE, using
vglrun +wm startplasma-x11
with Xvfb withexport VGL_DISPLAY="egl"
.What I am supposed to see (In the exact same condition except when using Xorg with NVIDIA 515 drivers):
What I see:
Is there any other considerations for using QT desktop environments with VirtualGL?
I believe these issues may be affected by QT XCB.
The text was updated successfully, but these errors were encountered: