| Summary: | Crash when pressing insert (Add Paint Layer) while renaming a layer | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | bird_d <relay198> |
| Component: | Layer Stack | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | crash | CC: | halla, nicolas.fella |
| Priority: | NOR | ||
| Version First Reported In: | 5.2.2 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | gdb trace log | ||
|
Description
bird_d
2024-01-24 11:42:51 UTC
Please check with the appimage first. If that doesn't crash (and it doesn't for me) it's very likely a problem with the distribution's build: it might have enabled asserts, for instance. In that case, we need a backtrace. (removing qt6 tag since Krita isn't actually using Qt6) Created attachment 165195 [details] gdb trace log Ah, seems to be like you said. The Flatpak and Appimage do not trigger this. > Thread 1 "krita" received signal SIGSEGV, Segmentation fault. > QHashData::nextNode (node=node@entry=0x55555a068560) at tools/qhash.cpp:591 > > 591 if (next->next) I have attached the full gdb trace log in case it's needed. Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. Sorry, since the log doesn't include debug symbols nor an assert message, we cannot use it. |