3

I have compiled a simple QT Quick application (using Ruby-Qml, but I don't think this matters) on Ubuntu (18.04) via WSL on Windows 10 v1903 and get the following error when launching with Xming. 

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-xxxx'
failed to get the current screen resources
WARNING: Application calling GLX 1.3 function "glXCreatePbuffer" when GLX 1.3 is not supported!  This is an application bug!
QGLXContext: Failed to create dummy context

Any ideas how to resolve this?

Improve this question
4
  • What version of Windows 10 are you using? Please provide your exact build as an edit to your question.
    – Ramhound
    Nov 16, 2019 at 22:07
  • In order to run QT Quick you will have to upgrade to 1909 and use use a WSL 2 instance
    – Ramhound
    Nov 16, 2019 at 22:26
  • Thanks! I will wait another two weeks if 1909 is ready for the masses and then take the jump. I read some pointers about vcxsrv being a potential solution. What is your take on that?
    – Christopher Oezbek
    Nov 16, 2019 at 22:29
  • Why struggle trying to do something the original version of WSL wasn't designed to support?
    – Ramhound
    Nov 16, 2019 at 22:36

2 Answers 2

Reset to default
7

For those still on Windows 10 v1903:

Improve this answer
1
  • > and ensure that LIBGL_ALWAYS_INDIRECT is unset (export LIBGL_ALWAYS_INDIRECT=) This is what I was missing, and what worked for me, thanks!
    – Youw
    Jul 27, 2021 at 14:41
1

I have compiled a simple QT Quick application (using Ruby-Qml, but I don't think this matters) on Ubuntu (18.04) via WSL on Windows 10 v1903 and get the following error when launching with Xming.

Any ideas on how to resolve this?

The original version of WSL was not designed to run applications with a graphical UI. There are ways around this by remoting into the instance with say Xming, but those solutions, don't always work as you have found.

The simplest solution is to migrate to a WSL 2 instance, Windows 10 version 1909 is the first version that supports WSL 2, which run an actual Linux kernel.

The simplest solution would be to upgrade to Windows 10 version 1909 since it's considered a cumulative update to Windows 10 version 1903, it should be just as stable as Windows 10 version 1903.

Yes; While Windows 10 version 1909 is a feature update, it is running the same build (except incremented by 1) as Windows 10 version 1903.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.