Closed Mikaela closed 2 years ago
Failed to load vulkan: Cannot load library vulkan: (vulkan: cannot open shared object file: No such file or directory)
initInstance: No Vulkan library available
Failed to create platform Vulkan instance
This error comes from some issue with the org.kde.Platform and isn't a problem as long as it can fall back to some other backend like OpenGl.
xkbcommon: ERROR: Couldn't process include statement for 'fi(altgr-intl)'
xkbcommon: ERROR: Abandoning symbols file "(unnamed)"
xkbcommon: ERROR: Failed to compile xkb_symbols
xkbcommon: ERROR: Failed to compile keymap
[2:8:0409/192258.386123:FATAL:xkb_keyboard_layout_engine.cc(640)] Keymap file failed to load: fi-altgr-intl
This error results in the crash and I think depending on how flatpak handles keyboard configurations it could be an Fedora issue or an issue with the org.{freedesktop, kde}.Platform runtime not including your keymap.
Does this happen with other flatpaks using Qt?
I am not sure what are Qt using flatpaks, but at least io.github.NhekoReborn.Nheko and org.telegram.desktop work properly.
Nheko uses Qt5 and telegram uses the freedesktop.sdk and builds its own Qt6.
You could try https://flathub.org/apps/details/org.bunkus.mkvtoolnix-gui and see if it works (uses org.kde.Platform 6.2).
org.bunkus.mkvtoolnix-gui
starts without issues
Upon migrating to sway, I can no longer reproduce this issue.
I don't know which of these is the error that prevents Jami from starting. I am using Fedora 36 with i3.
I wanted to try the flatpak as the repository doesn't support Fedora 36 and Jami installed from there got uninstalled during the update.