https://bugs.kde.org/show_bug.cgi?id=457974
--- Comment #40 from Maximilian Federle <max.fede...@gmail.com> --- (1) I found an "okay" way: 1. In launch configuration: Check 'Use external terminal' 2. Input command: bash -c 'unset LIBGL_DRIVERS_PATH && unset QML2_IMPORT_PATH && %exe' (2) No such issues. You can debug this issue in the same way as we debugged kdeveloped: set QT_DEBUG_PLUGINS=1 (3) Well, the QML2_IMPORT_PATH and LIBGL_DRIVERS_PATH vars are necessary because the snap has its files separate from the host's files. This is necessary so that it doesn't crash because it's trying to mix libraries, as you could see when you first reported this bug. The problem is, your little demo app has been compiled on the host, with the hosts libraries. Therefore, those two variables confuse this app, and it tries to load incompatible mesa drivers or the QML components. To prevent that, we must unset them before continuing. I researched a way to get rid of QML2_IMPORT_PATH, but I've only found the aforementioned workaround for LIBGL_DRIVERS_PATH so far. The snap itself is still missing the qtquick2 controls package and some icon theme. As for the snap vs AppImage: The snap packaging is not developed by the upstream kdevelop project, but by a separate effort in the KDE Neon project: https://invent.kde.org/packaging/snapcraft-kde-applications/-/tree/Neon/release/kdevelop. I suspect it has seen little to no use in the past. -- You are receiving this mail because: You are watching all bug changes.
