I have been trying to debug my OpenGL graphics application using Nvidia Linux graphics debugger, the debugger application starts and installs the debugger to the device (graphics) correctly, but when trying to Launch the application to debug it shows this message
This application failed to start because it could not find or load the Qt platform plugin "xcb" in "". Available platform plugins are:
eglfs, linuxfb, minimal, minimalegl, offscreen, xcb. Reinstalling the
application may fix this problem. Aborted (core dump)
The application starts fine as standalone but starting with Linux GD.
I have seen lot of posts relating to xcb but could not find any answer relating to starting application using Nvidia linux graphics debugger
nvidia drivers I am using 378
os-ubuntu 16.04
Nvidia liniux graphics debugger 2.0
Qt opengl context
I had the same issue, and solved it by changing the LD_LIBRARY_PATH to the Qt installation path (on the launch environment options)
LD_LIBRARY_PATH=<some_dir>/Qt/5.7/gcc_64/lib
Related
i am trying launch houdini on linux, but i get this error .
./houdini
Qt Error: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, webgl, xcb.
2031: (sent by pid 2031)
Crash log saved to /tmp/houdini_temp/crash.santifer_2031_log.txt
help me, thanks Folks
i expecting launch houdini on DebianLinux
I was having this same issue on Pop_OS 22.04 running wayland. I was able to resolve it by running Houdini with the following command:
QT_QPA_PLATFORM=xcb /opt/hfs19.5.303/bin/houdini
Just replace the "hfs19.5.303" with whatever version you are trying to actually run. I also just learned that as of QT5.11 you can set a fallback of x11 as well in case wayland isn't working via:
QT_QPA_PLATFORM="wayland;xcb"
Update: The problem does not occur with the NVIDIA driver version 510 anymore.
I am running Android Studio 2020.3.1 on Wayland and I'm using the proprietary NVIDIA driver version 495, which allows me to use the the regular GBM implementation of Wayland instead of the especially tailored EGL version.
My problem is, that every time I try to start an Android emulator (AVD) via the AVD Manager, I get the following message after a few seconds:
The emulator process for AVD Pixel_2_API_30 has terminated.
Starting the AVD from the command-line shows that a segmentation fault occurred:
INFO | Android emulator version 31.1.4.0 (build_id 7920983) (CL:N/A)
WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
INFO | Info: Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. ((null):0, (null))
Fontconfig warning: "/usr/share/fontconfig/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs"
WARNING | cannot add library /home/letorbi/Android/Sdk/emulator/qemu/linux-x86_64/lib64/vulkan/libvulkan.so: failed
INFO | added library /home/letorbi/Android/Sdk/emulator/lib64/vulkan/libvulkan.so
Segmentation fault (core dumped)
How can I get more information and is there a workaround to prevent the segfault?
For what it's worth, Wayland EGL is able to start the emulator somehow, but I see nothing but a black screen on the device. X11 is working, but I'd like to stay on Wayland if it is possible.
I was able to work around the segmentation fault, by disabling the Vulkan support for AVDs. This can be easily achieved by adding the following line to the file ~/.android/advancedFeatures.ini:
Vulkan = off
I've got this hint from an answer in a related question. This answer also suggests to add GLDirectMem = on, but that line was not needed to solve my problem. However, some benchmarking revealed that it might improve the performance a little bit, so you might want to add that line as well.
I tried setting up Nannou following the instructions here.
I am running Debian Buster on a MacBook with an NVIDIA graphics card (GK107M [GeForce GT 750M Mac Edition]).
I tried running the example and get the error
thread 'main' panicked at 'could not build default app window: NoAvailableAdapter'
It seems this is an error when Nannou tries to open a window -- something about its communication with the window manager (Gnome on xOrg), or something about vulcan-tools.
Any ideas for how to debug this?
The issue is that I was using the open-source Nouveau driver for my graphics card (the default on Debian) which does not currently support Vulkan, which is required for Nannou.
By installing the proprietary nvidia graphics driver, the problem was resolved.
I was able to install the nvidia driver by running
apt install nvidia-driver,
and then rebooting my computer,
as described in this tutorial https://linuxconfig.org/how-to-install-nvidia-driver-on-debian-10-buster-linux
Now nannou works :)
i have been using the Qt Wayland plugin for developing a display manager for linux. i tried running the display manager that i built, on a terminal session but it shows like
qt.qpa.plugin: Could not find the Qt platform plugin "wyland" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, webgl, xcb.
i know that it is because i didn't run it on a wayland compositor. but i try building the wayland compositor examples that you have given and it works fine when running in my desktop but when i run it from the terminal i receive the same problem. so how can i start qtwayland compositor from terminal without using --platform xxxx
i like to know how weaston launches from terminal by itself without any platform support and will i be able to launch the qt wayland compositor like that ?
QtWayland compositors are cross-platform applications and can run on multiple backends. When you start it with --platform wayland, your are basically trying to start the compositor within another Wayland compositor.
Normally compositors are run from a tty using the eglfs backend. i.e. start your compositor with:
./compositor --platform eglfs
If you get errors launching the compositor app, then special configuration may be needed for your device. The Qt embedded linux documentation may give some pointers. Even if you're on desktop, this is the place to look. If you're on open-source mesa, you probably want to look at the section for eglfs_kms.
Once you've got the compostor running, clients can be started with:
./app --platform wayland
Steps I have tried to create stand alone web application
Host PC is Ubuntu 14.04, 64 bit OS.
Qt version - Qt5.6.
Testing on the virtual Box Ubuntu 14.04, 64 bit OS.
Application is working properly in the Host PC.
I copied all the web dependent files & process, platform dependent files and the lib files where the executable file is present, then I redirected the library path to the Present working directory of the executable.
command used : chrpath -r ./lib AppName
then when i run the application its breaking as
This application failed to start because it could not find or load the Qt platform plugin "xcb".
Available platform plugins are: xcb.
Reinstalling the application may fix this problem.
Aborted (core dumped)
I ran the ldd on libqxcb.so to find the dependent files.
command : ldd libqxcb.so
I solved this by manually coping the "not found files" to /usr/lib path
libQt5XcbQpa.so.5
libQt5DBus.so.5
libQt5Core.so.5
libQt5Gui.so.5
Now the application is breaking due to the below error :
QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled
Qt WebEngine data directory not found at location /home/user/Qt5.5.1/5.5/gcc_64. Trying application directory...
Qt WebEngine Plugins directory not found. Trying fallback directory... Plugins as for example video codecs MAY NOT work.
Installed Qt WebEngine locales directory not found at location /home/user/Qt5.5.1/5.5/gcc_64/translations/qtwebengine_locales. Trying application directory...
Qt WebEngine data directory not found at location /home/user/Qt5.5.1/5.5/gcc_64. Trying application directory...
Qt WebEngine Plugins directory not found. Trying fallback directory... Plugins as for example video codecs MAY NOT work.
Installed Qt WebEngine locales directory not found at location /home/user/Qt5.5.1/5.5/gcc_64/translations/qtwebengine_locales. Trying application directory...
QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled
QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled
QOpenGLWidget: Failed to create context
QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled
QOpenGLWidget: Failed to create context
composeAndFlush: makeCurrent() failed
composeAndFlush: makeCurrent() failed
composeAndFlush: makeCurrent() failed
Segmentation fault (core dumped)
Can anyone guide me to solve above problem.
Thanks in advance.
Do you have a desktop version of Ubuntu running in virtual box?
Have you enabled "Enabled 3D Acceleration" in the VM options.
Have you installed the Virtualbox video drivers?
The issue is QtWebengine needs OpenGL to work that is why you are getting this error:
QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled