| Summary: | pykrita dockers: SIGSEGV when docking | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | dirtyice <kdebugs> |
| Component: | Dockers | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | halla |
| Priority: | NOR | ||
| Version First Reported In: | 5.1.4 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=429201 | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | valgrind output | ||
|
Description
dirtyice
2022-12-26 21:03:09 UTC
Can you reproduce this with the appimage? Created attachment 154833 [details]
valgrind output
Output from valgrind (Conditional jump or move depends on uninitialised value errors were ignored, because there are a lots of them). Probably only the first error is relevant, as the others seem like the consequences of the first use after free error.
(In reply to Halla Rempt from comment #1) > Can you reproduce this with the appimage? No, it seems to work with the appimage. The appimage doesn't seem to use system theme and it's full of animations, which looks like I managed to disable in my local config somehow, and there are animation related lines in the backtrace. Will check this out. Seems like it only does this if I set the style to QtCurve in qt5ct. With Fusion or Windows it works (I don't have other styles installed). Also it is the only style that lacks animations when I try to dock a docker. 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. Then it's probably a bug in the QtCurve style, not Krita. I've checked a few other QT Styles, but I could only reproduce this crash with QtCurve. I've updated QtCurve to the latest git master (78fe0fc1a888edc5d4cbfecc285f3287c13fe7d3) but no change. It looks like QTCurve's bgndOpacity is the culprit here, adding krita to noBgndOpacityApps is a possible workaround that fixes the issue. Searching for bgndOpacity here yielded only one result, #429201, which suggests this is an application error, not QtCurve... but I'm not a Qt wizard enough to say that. I checked that comment, but it doesn't contain enough information to do anything, and I don't have a build of Krita that can use platform Qt plugins. I've asked for more information. 5.15 TEST Sorry, I don't think we can do much more about this. |