I am using Ubuntu 18.04 – I am not yet ready to upgrade to 20.04. I want to test the 4.3 beta, but all 4.3 beta versions (and even 4.3.1 alpha) I have tried, always abort at the begining with this message in the terminal:
ASSERT (krita): "screen < QGuiApplication::screens().size() && screen >= 0" in file /home/appimage/workspace/Krita_Release_Appimage_Build/krita/libs/widgets/KoToolBox.cpp, line 51 Aborted
I have Krita version 4.2.9-4~bionic from the krita-lime PPA running perfectly in my system. All previous Krita versions from the PPA and also all appimages have always worked well. I have three screens, one of them being a Wacom Cintiq, and again, always working fine with krita pre-4.3.
The problem only happens with the 4.3 betas and 4.3.1 alpha versions. This is the full output from the command line:
$ ./krita-4.3.0-beta2-x86_64.appimage QObject::startTimer: Timers cannot have negative intervals Could not find platform independent libraries <prefix> Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>] /tmp/.mount_krita-0PvtPO/usr/lib/krita-python-libs/krita added to PYTHONPATH ASSERT (krita): "screen < QGuiApplication::screens().size() && screen >= 0" in file /home/appimage/workspace/Krita_Release_Appimage_Build/krita/libs/widgets/KoToolBox.cpp, line 51 Aborted
The error happens independently of how many screens are turned on: with only one screen (main), or with main and the second, or with the Cintiq display also on (or not), the problem and error message is always identical, no changes.
What I have done:
I have tried uninstalling the PPA krita 4.2.9-4~bionic and deleting all krita related files in
~/.config/ , as well as deleting the
~/.local/share/krita folder before attempting to run any of the beta appimages. The ASSERT message is always the same.
If I reinstall krita 4.2.9-4~bionic from the PPA with
sudo apt install krita and put back all the deleted files and folder, and run a beta appimage, the ASSERT message is the same, the only difference is that there are many messages of this kind:
NOT COOL: Duplicated action name from xml data:
However bad those might be, they seem unrelated to the Abort problem, because though I can make them disappear by deleting my installation’s fiiles, that doesn’t help with the ASSERT.
Finally, I have tried to find a way of testing v4.3 beta with Flatpak, but I could not find any unstable version in
https://flathub.org/repo/flathub.flatpakrepo or in
https://distribute.kde.org/kdeapps.flatpakrepo, and this one
https://binary-factory.kde.org/job/Krita_nightly_flatpak/ doesn’t seem to contain a flatpakrepo file and I could not find anywhere any documentation suggesting how this could be used by users to test krita 4.3 beta.
My goal is to be able to test 4.3 beta in my system and more importantly, to highlight that this error that I am experiencing might mean future problems for systems that may have similar configurations like mine.
Have anybody else experienced similar troubles? Any additional ideas or information whether is possible to use a Flatpak for 4.3 beta?