grahamrow
Issue with the Qt platform plugin "xcb"
Thank you @grahamrow for your work! Well, I downloaded Muview (2.1.3.3) and I am facing the following error: This application failed to start because it could not find or load the Qt platform plugin "xcb" in "". Available platform plugins are: xcb I am using Fedora and I am not good in Linux. I worked with chatgpt and I reinstalled the following libraries: libxcb, libxcb-devel, libX11, libX11-devel, libXcursor, libXcursor-devel, libXrandr, libXrandr-devel, libXi, libXi-devel, fontconfig and freetype and it doesn't help. The problem is with the library: "libfontconfig.so.1" and I can open Muview2-x86_64.AppImage with the following command: LD_PRELOAD=/ruta/a/libfontconfig.so.1 ./Muview2-x86_64.AppImage This was my experienced. Thanks again for your work!
libfontconfig should not be bundled inside the AppImage. If it is, then it should be removed.
Reference: https://github.com/AppImageCommunity/pkg2appimage/blob/3076946d2cc4f4909d7927f9477e3178d5c04d02/excludelist#L119
Unrelated side note: I was successfully able to run the provided Intel/AMD Muview2-x86_64.AppImage on the ARM 64-bit Raspberry Pi 5 just fine (details).
I have tried the above in ubuntu 24.04.1 LTS. It is giving the following error:-
" LD_PRELOAD=/ruta/a/libfontconfig.so.1 ./Muview2-x86_64.AppImage ERROR: ld.so: object '/ruta/a/libfontconfig.so.1' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. ERROR: ld.so: object '/ruta/a/libfontconfig.so.1' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. This application failed to start because it could not find or load the Qt platform plugin "xcb" in "".
Available platform plugins are: xcb.
Reinstalling the application may fix this problem. Aborted (core dumped) "
The muview version 2.1.2 ubuntu one works fine. Can you give me solution as soon as possible. My research depends on it.
Please use strace to see what is missing. Do you know how to use that tool?
I am sorry. But, I don't know how to use strace. Also, I recently upgraded from 22.04 LTS to 24.04.1 LTS. Is the issue happening because of this?