Possibly helpful:
https://forum.qt.io/topic/111553/solved-qt-qpa-plugin-could-not-find-the-qt-platform-plugin-xcb-in
If you get to a point and see a message about a missing xcb, like this:
Could not load the Qt platform plugin "xcb" ...
Here is some information I've collected about it:
Sometimes a new Leo install will not start. The error message is something
like this::
qt.core.plugin.factoryloader: checking directory path
"/usr/bin/platforms" ...
qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""
This application failed to start because no Qt platform plugin could be
initialized. Reinstalling the application may fix this problem.
This could be because the Qt installer didn't install all of its libraries
or they were installed but not into the standard location Qt expects. This
can be cured by exporting the right paths (may be different in different
OSs)::
QT_QPA_PLATFORM_PLUGIN_PATH= /usr/lib/qt6/plugins/platforms
QT_PLUGIN_PATH= /usr/lib/qt6/plugins/platforms
If you have the ``locate`` command you can find the right location; e.g.::
locate -r 'platforms$' |grep -i qt6
/home/tom/.local/lib/python3.11/site-packages/PyQt6/Qt6/plugins/platforms
Otherwise use ``find``::
find / 2>/dev/null -type d -name platforms |grep -i 'qt6'
/home/tom/.local/lib/python3.11/site-packages/PyQt6/Qt6/plugins/platforms
I don't know why the thing is complaining about Wayland. Wayland is a newer
screen construction system, to replace the venerable X11. Wayland is often
trouble. Ubuntu, or at least my install of 22.04/Cinnamon, is still using
X11. You can check with this command in a terminal:
echo $XDG_SESSION_TYPE
On Monday, October 14, 2024 at 6:54:26 PM UTC-4 Edward K. Ream wrote:
> > - Installed Leo on wsl, but Leo does not work.
>
> There is progress to report re Hyper-V services.
>
> After upgrading to Windows Pro, Windows warned me that the memory
> integrity
> <https://support.microsoft.com/en-us/windows/options-to-optimize-gaming-performance-in-windows-11-a255f612-2949-4373-a566-ff6f3f474613>
>
> check could not be enabled because of several installed drivers(!) This was
> an important clue.
>
> I used the device manager (using the "devices by driver" view) to remove
> four offending drivers. Two drivers remained because their descriptions did
> not include driver indices. Sheesh. But googling suggested this approach:
>
> C:\Windows\System32>dir lv*.sys /s /b
> C:\Windows\System32\drivers\lvrs64.sys
> C:\Windows\System32\drivers\lvuvc64.sys
>
> I deleted (by hand) the two offending drivers, and then rebooted.
>
> I then enabled (set to automatic/triggered start) all Hyper-V services in
> the Services manager (tip: accessible via the Task manager). After a
> reboot, *some* Hyper-V services became active!
>
> However, all this did not make Leo usable. Starting Leo from within wsl
> generated some new errors:
>
> Failed to create wl_display (No such file or directory)
> qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even
> though it was found.
> WARNING: dzn is not a conformant Vulkan implementation, testing use only.
> WARNING: Some incorrect rendering might occur because the selected Vulkan
> device (Microsoft Direct3D12 (NVIDIA GeForce RTX 3080)) doesn't support
> base Zink requirements: feats.features.logicOp have_EXT_custom_border_color
> have_EXT_line_rasterization
>
> *Summary*
>
> Nothing now prevents Hyper-V services from running on my machine.
>
> Qt continues to have serious problems when installed in wsl.
>
> Edward
>
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/f76136db-d0d4-4679-b0dc-33e4c802d182n%40googlegroups.com.
