Bug 458875 - Krita get stuck at rendering after opening a new window and new view
Summary: Krita get stuck at rendering after opening a new window and new view
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: Usability (show other bugs)
Version: 5.1.0
Platform: Appimage Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-08 12:30 UTC by Pablo
Modified: 2024-10-31 11:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pablo 2022-09-08 12:30:09 UTC
SUMMARY
Krita gets stuck at rendering if another view of the file is open, this behaviour also happens with a new image.

STEPS TO REPRODUCE
1. Create a new document or open an existing .kra
2. Create a new window (Window -> New Window)
3. In the second window make a new view of the same file (Window -> New view)
4. Start editing the file on the first window

OBSERVED RESULT
After a few edits (been clicking repeatedly for around 5 seconds) Krita gets stuck at rendering,  the interface can still be usable (like changing colos, selecting tools or brushes, menu options) but no more drawing is possible.
The file cannot be saved, saving shows the "waiting for image operation to complete" dialog and clicking on the "save without waiting" button and entering a new file name shows the same "waiting for image operation to complete" dialog without buttons this time.
I tried different brushes and the get the same issue, so it doesn't seem brush dependent.
This is reproduced 100% of the time.


EXPECTED RESULT
Rendering should finish independently of using another view or not.

SOFTWARE/OS VERSIONS
Qt 5.12.8 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 9.3.0) on "xcb" 
OS: Ubuntu 20.04.4 LTS [linux version 5.4.0-73-generic]

ADDITIONAL INFORMATION
Comment 1 Pablo 2022-09-08 12:32:50 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
Comment 2 Halla Rempt 2024-10-31 11:18:33 UTC
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.