Summary: | Krita get stuck at rendering after opening a new window and new view | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | Pablo <netinfo2k> |
Component: | Usability | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | halla |
Priority: | NOR | ||
Version First Reported In: | 5.1.0 | ||
Target Milestone: | --- | ||
Platform: | Appimage | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Pablo
2022-09-08 12:30:09 UTC
Since I start Krita from the command line, this is are the messages I saw Replacing libstdc++.so.6 with the fallback version: libstdc++.so.6.0.28 → libstdc++.so.6.0.29 Bundle “/home/pablo/.local/share/krita/SK_V1.bundle” is broken. File “brushes/bristles_circle_variable.svg” is missing Bundle “/home/pablo/.local/share/krita/SK_V1.bundle” is broken. File “brushes/circle_hard_eroded.gih” is missing Bundle “/home/pablo/.local/share/krita/SK_V1.bundle” is broken. File “brushes/oil_bristle.png” is missing Could not load the resource from the bundle “paintoppresets” “paintoppresets/Special_dyna_dots.kpp” “/home/pablo/.local/share/krita/Krita_3_Default_Resources.bundle” QObject::startTimer: Timers cannot have negative intervals /tmp/.mount_krita_VheoUu/usr/lib/krita-python-libs/krita added to PYTHONPATH WARNING: KisResourceLocator::loadRequiredResources failed to sanity check the embedded resource: parent resource: KoResourceSignature(“paintoppresets”, “”, “k)_Blender_Basic.kpp”, “k) Blender Basic”) embedded resource: KoResourceSignature(“patterns”, “fdc6eb8cb5e67e92f77e61e822db3e4a”, “4-flathack-black55.png”, “4-flathack-black55.png”) qt.qpa.xkeyboard: QXcbKeyboard::handleKeyEvent: key released, but it has no record in the registry code 37 qtcode 16777249 QFSFileEngine::open: No file name specified SAFE ASSERT (krita): “!m_d->isActive” in file /home/appimage/workspace/Krita_Release_Appimage_Build/krita/libs/ui/tool/KisAsyncColorSamplerHelper.cpp, line 112 QFSFileEngine::open: No file name specified qt.qpa.xkeyboard: QXcbKeyboard::handleKeyEvent: key pressed, but it is already present in the registry code 64 qtcode 16777251 registered qtcode 16777251 Apologies for the late reply, this report got snowed under in the. Also, I'm sorry, but I cannot reproduce this with the 5.2.6 appimage. Without a way to reproduce this reliably, we cannot act on the report. |