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"
Related
I am running the Opencv 4.4.0 in a Ubuntu 20.04 AWS-Ec2 instance connected with VSCODE trough the Remote Explorer module.
I am trying to open an image that I have uploaded to the project.
import cv2
img = cv2.imread("imgs/cat1.jpg")
cv2.imshow("Output", img)
But when I run the file (pressing the green arrow) I get the follow error:
(env) ubuntu#ip-xxx-xx-xx-xxx:~/vhosts/opencv-ml-images$ /bin/python3 /home/ubuntu/vhosts/opencv-ml-images/chapter1.py
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "/home/ubuntu/.local/lib/python3.8/site-packages/cv2/qt/plugins" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: xcb.
Aborted (core dumped)
Does someone knows what is happening? maybe something related to the fact I am running the opencv in a remote computer? How to sove it?
I think what you are trying to do is run it on Remote Desktop Connection. I was having the same problem but I am running WSL 2 (Both are quite similar). And I solved it by setting up environment for GUI applications on WSL 2 from https://wiki.ubuntu.com/WSL . Just start your X server and run the code again. It should work. If not, do reply so that we can sort it out together.
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
Introduction
I've just installed a networking simulator Called Netkit. On Debian stretch stable. Using the official installation guide here.
Installation
After setting the correct paths and installing. I then run the check_configuration.sh script.
Everything is checked OK, and it has found the terminal emulator xterm which is needed for netkit. And recieve the complete message.
[ READY ] Congratulations! Your Netkit setup is now complete!
Enjoy Netkit!
The Problem
Running netkit using the command:
vstart pc1
The xterm netkit-kernel emulator starts running. However I'm getting an infinite loop of the same error message:
ubda: can't open "home/foo/netkit/pc1.disk" failed, errno= 13
So im guessing it's because the file is missing? if so how do i obtain it? and if not, what is causing this error. I've followed the install guide completely.
I'm assuming your system is not a 32bit system. Netkit is only supported on the 32-bit architecture(unless the compatibility libraries are installed). Hence I would suggest you download a 32-bit VM(instead of installing the libraries) and run Netkit on the same(worked fine for me).
Check position of your lab-folder..
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
I'm using appimage http://appimage.org to pack my application in a standalone excutable.
I'm doint this on debian testing lenny.
My application uses a lot of opensource libraries (qt, python pythonqt fftw hdf4/5 gsl netpbm qwt) and everything was ok using Qt4. I can compile my app on debian and create an appdir image that run smoothly on mint (with xfce).
This stopped working when I switch to Qt5.
Now the appimage runs on debian, but not on mint, I get this error:
This application failed to start because it could not find or load the Qt platform plugin "xcb".
Available platform plugins are: eglfs, kms, linuxfb, minimal, minimalegl, offscreen, xcb.
Reinstalling the application may fix this problem.
Aborted
Notice that the messege is non-consistent: firts it says I lack xcb and than it maks as available.
I did copied the plugins directory in my app usr/lib tree.
I have xcb installed on host apt-get install libx11-xcb1
My AppRun file looks like this:
#!/bin/bash
HERE="$(dirname "$(readlink -f "${0}")")"
cd "${HERE}/usr/"
export LD_LIBRARY_PATH="${HERE}/usr/lib/:${LD_LIBRARY_PATH}"
export PATH="${HERE}/usr/bin:${PATH}"
export QT_PLUGIN_PATH="${HERE}/usr/lib"
exec "${HERE}/usr/bin/Neutrino" "$#"
cd -
What am I missing?
Many Qt5 applications such as Krita, Scribus, and Subsurface are being distributed as AppImages, so it is definitely possible.
Probably you are missing some components that need to be bundled inside the AppImage. Especially, Qt plugins need to be bundled inside the AppImage for it to work.
See here for an example of a Qt5.5 app being packaged as an AppImage.
Note that it is generally recommended to use an old base system such as CentOS 6 for compiling, because the resulting AppImages will be compatible to more distributions rather than just the latest ones.
If you post a link to your project or open an issue on https://github.com/probonopd/AppImages/issues I can possibly give you more detailed directions.