@rienna no missing lib. The problem might be libwayland* version is too old that they do not include wl_proxy_marshal_flags. You may need to upgrade them.

===some people suggested:
You can reinstall the wayland package to fix the listed errors
https://bbs.archlinux.org/viewtopic.php?id=272846

@dev_liya Sir, my error is about similar to you but it didn't work for me.
Error: The kit supports "", but the device uses "arm64-v8a, armeabi-v7a, armeabi".

@Christian-Ehrlicher I need to create a .txt file for the output of auto tests for documentation I am trying to put together. Thanks!

@jsulm Oh great, that actually has worked. Thank you so much :)

@Christian-Ehrlicher Yup.. it worked when i upgraded my Qt version. Thanks a lot.

Just for education purposes, can i ask lets say if i am still using qt 5.8.0 and i wish to remove this message. Is there a way to do that? I believe this message is caused by this qt sqldriver file called qsql_psql.cpp. So I tried to remove the code that prompts this message in qsql_psql.cpp file and it didnt work when i run my application.

qt_generate_deploy_qml_app_script() is not available for static builds right now.

In a static Qt build, runtime dependencies are usually baked into the binary. What are you expecting from the deployment API for static Qt builds?

@acetone said in QSslSocket failure from Online Installer version (Ubuntu):

Solved by manual linking with openssl1 and ssl1.

Download old openssl sources: wget https://www.openssl.org/source/openssl-1.1.1q.tar.gz Compile: tar -xf openssl-1.1.1q.tar.gz cd openssl-1.1.1q ./config make Add to project: # .pro file: LIBS += -L/path/to/openssl-1.1.1q -lcrypto -L/path/to/openssl-1.1.1q -lssl

This fixed the issue for me on Ubuntu 22.04 / Qt 5.15 but only when starting my program from Qt Creator, running it from the console shows the same ssl error...

@veryqtperson said in QT 6.4.1 build from source. Can't get xcb configured.:

sudo apt install '^libxcb.*-dev' libx11-xcb-dev libglu1-mesa-dev libxrender-dev libxi-dev libxkbcommon-dev libxkbcommon-x11-dev

Thanks for that solution, it solved my problem.
I had exactly the same error message as the OP - not exactly very helpful.
I have experienced this before with other versions but generally deleteng all the Qt folders and config files and then re-installing has worked but not this time!

What I don't understand is that I had 6.4.3 running perfectly and I could compile and run Qt apps, console apps and QtQuick apps and then after the upgrade Qt suddenly wouldn't run any graphical programs. Console apps were fine.
The first attempt at upgrading, I just told the maintenance tool to delete 6.4.3 and install 6.5.1 so why did those libraries disappear?

Very happy that it is all working again now and I will save that command in case I need it next time!

@devQt93 this post doesnt have any help for a while. I just want to push it on top and take a look for any help.

I suspect that the libraries are installed along another module but I currently don't know which one.

Got the same problem when building a static Qt 6.5.1 on Steam Deck (Arch Linux), where zstd was provided by Homebrew (didn't want to risk messing up the "main" environment by installing system-wide dependencies via pacman).

As I understood, what's happening (at least, in my case) is that in /home/linuxbrew/.linuxbrew/lib/cmake/zstd/zstdTargets.cmake there is this line:

foreach(_cmake_expected_target IN ITEMS zstd::libzstd_shared zstd::libzstd_static)

And the fix (for building static Qt 6.5.1 as of now) is to remove zstd::libzstd_shared part. That is most certainly not a great idea, especially that this file isn't meant to be modified, but I really can't tell where this actually needs to be "fixed": on Qt side (in FindWrapZSTD.cmake?), or in the Homebrew zstd formula, or elsewhere. Either way, after I left only the static variant in zstdTargets.cmake, static Qt configured and built without problems (and then I reverted these changes that I made in zstdTargets.cmake).

Related to that, there is this bugreport and this commit, which you could apply on top of 6.5.1 sources, but that won't resolve the problem still - it will only make you delete zstd::libzstd_static from zstd's config instead of zstd::libzstd_shared (which means that you'll end up with zstd being a shared/dynamic library dependency of your Qt build).

Finally, peculiarly enough, building a static Qt on Mac OS, where zstd is also provided by Homebrew, didn't cause this problem for me (with Qt 6.5.1), although this topic claims that it might happen there too.

So, coming back to the original post in this thread, I would suggest you to take a look at zstd package that you have installed in your system - probably you'll be able to apply the same workaround in zstdTargets.cmake. Another option, I reckon, would be to disable zstd in Qt configuration, but I'm not sure if it is an optional dependency (still?).

@SGaist said in Kali Linux - Could not load the Qt platform plugin, (I need your help).:

Hi and welcome to devnet,
By default, for security purposes, root does not have access to the window server.
Do you really need to run that application as root ?

Thank you very much for answering. I will do this.

@JoeCFD said in "No QML utility installed" not letting me use Qt6:

@sierdzio this place is not a good place because it is user name dependent. For deployment and team work, /opt is the traditional location for third party installation on Unix/Linux

Do you have multiple users on your system? I doubt that. Installing for current user is simpler.

For deployment people would typically use some CI/CD solution, where Qt is delivered in a different form anyway.

But of course, it's up to everybody to decide for themselves.

You can, check the bug report system to see if there's already something there and if not, create a new ticket.

Hi and welcome to devnet,

Are you trying to build a Qt Designer plugin with a build for wasm ?

This does not make sense, designer is a host application.

Hi,

If memory serves well it's x86_64h that should be used.