I added a second display and Krita 4.3.0 is now crashing every time I open it. paradox@primary /mnt/primary $ krita qt.gui.icc: fromIccProfile: Invalid ICC profile - invalid white-point QPngHandler: Failed to parse ICC profile qt.gui.icc: fromIccProfile: Invalid ICC profile - invalid white-point QPngHandler: Failed to parse ICC profile qt.gui.icc: fromIccProfile: Invalid ICC profile - invalid white-point QPngHandler: Failed to parse ICC profile qt.gui.icc: fromIccProfile: Invalid ICC profile - invalid white-point QPngHandler: Failed to parse ICC profile qt.gui.icc: fromIccProfile: Invalid ICC profile - invalid white-point QPngHandler: Failed to parse ICC profile QObject::startTimer: Timers cannot have negative intervals /usr/lib64/krita-python-libs/krita added to PYTHONPATH ASSERT (krita): "screen < QGuiApplication::screens().size() && screen >= 0" in file /var/tmp/portage/media-gfx/krita-4.3.0/work/krita-4.3.0/libs/widgets/KoToolBox.cpp, line 51 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = krita path = /usr/bin pid = 12369 KCrash: Arguments: /usr/bin/krita KCrash: Attempting to start /usr/lib64/libexec/drkonqi org.kde.drkonqi: Unable to find an internal debugger that can work with the KCrash backend [1]+ Stopped SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo ~AMD64 kernel 5.8.12 KDE Plasma Version: 5.74.0 qtwayland 5.15.1
Sorry, to clarify I am using x and not wayland.
Please update to the latest beta (https://krita.org/en/item/second-beta-out-for-krita-4-4-0/). This crash happens when there is more than one monitor in some configurations, but it's been fixed since.
Well, I'm not sure about 4.4.0 but it is fixed in the git build.