Bug 480266

Summary: Crash when pressing insert (Add Paint Layer) while renaming a layer
Product: [Applications] krita Reporter: bird_d <relay198>
Component: Layer StackAssignee: 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
STEPS TO REPRODUCE
1. Begin renaming layer
2. Press insert

OBSERVED RESULT
Crashes

EXPECTED RESULT
Nothing

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS 
KDE Plasma Version: 5.92.0
KDE Frameworks Version: 5.248.0
Qt Version: 6.7.0
Kernel Version: 6.6.10-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 1700 Eight-Core Processor
Memory: 47.0 GiB of RAM
Graphics Processor: AMD Radeon RX 6600 XT
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7B79
System Version: 3.0
Comment 1 Halla Rempt 2024-01-24 11:45:35 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.
Comment 2 Nicolas Fella 2024-01-24 12:34:02 UTC Comment hidden (spam)
Comment 3 bird_d 2024-01-24 17:55:38 UTC
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.
Comment 4 Bug Janitor Service 2024-01-25 03:45:35 UTC
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.
Comment 5 Halla Rempt 2024-01-25 08:31:29 UTC
Sorry, since the log doesn't include debug symbols nor an assert message, we cannot use it.