Summary: | krita segfaults on start after displaying the splash screen | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | Timo Gurr <timo.gurr> |
Component: | General | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dimula73, halla |
Priority: | NOR | ||
Version First Reported In: | 5.0.0 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/graphics/krita/commit/23e23f871bc8a9f13c3272b09c640f3bf21bb395 | Version Fixed In: | |
Sentry Crash Report: | |||
Attachments: |
coredump.txt
krita-20211228-114604.kcrash coredump.txt krita-20211230-093915.kcrash |
Description
Timo Gurr
2021-12-28 11:25:07 UTC
Created attachment 144904 [details]
krita-20211228-114604.kcrash
The crash looks weird, though it might be related to the fact that Krita is built against Qt 5.15, which is unsupported officially. Could you check if Krita Appimage package runs fine on your system? Krita Appimage works on my system but does not solve my problem, I'm trying to update our distribution package to the latest Krita version (4.4.8 -> 5.0.0). My previous reports for Krita 4.4.8 were also on a system using/running qt 5.15 already which is in fact the supported qt version by KDE getting bugfixes (https://invent.kde.org/qt/qt/qtbase/-/commits/kde/5.15) and which is used by basically any distributions nowadays afaiks even on Debian 10. 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. Created attachment 144955 [details]
coredump.txt
Adding another kcrash/coredump from krita rebuilt after updating system to the latest versions of related components, e.g. frameworks, plasma, qtbase.
SOFTWARE/OS VERSIONS
Operating System: Exherbo Linux
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2 (qtbase kde/5.15 branch fixes up to 5.15.2_p263)
Kernel Version: 5.15.1 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz
Memory: 11.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 530
Created attachment 144956 [details]
krita-20211230-093915.kcrash
It's another case of where KoColorSpaceRegistry::instance()->p709SRGBProfile() returns 0, I think. I don't understand the check in any case: sRGB is only true if (colorSpace()->profile()->uniqueId() == KoColorSpaceRegistry::instance()->p709SRGBProfile()->uniqueId()) which doesn't look like a correct way to determine whether the colorspace is sRGB? Git commit b61faec61a081d27b11be1d1929ed51da95e6bb8 by Halla Rempt. Committed on 08/03/2022 at 12:53. Pushed by rempt into branch 'krita/5.0'. Properly check whether the profile is sRGB M +8 -2 libs/pigment/KoColor.cpp https://invent.kde.org/graphics/krita/commit/b61faec61a081d27b11be1d1929ed51da95e6bb8 Git commit 23e23f871bc8a9f13c3272b09c640f3bf21bb395 by Halla Rempt. Committed on 08/03/2022 at 12:55. Pushed by rempt into branch 'master'. Properly check whether the profile is sRGB (cherry picked from commit b61faec61a081d27b11be1d1929ed51da95e6bb8) M +8 -2 libs/pigment/KoColor.cpp https://invent.kde.org/graphics/krita/commit/23e23f871bc8a9f13c3272b09c640f3bf21bb395 *** Bug 445348 has been marked as a duplicate of this bug. *** |