| Summary: | Krita crashes when closed | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | thomas.bockman |
| Component: | General | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | crash | CC: | ghevan, halla, kde, silocoder |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 4.2.9 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
thomas.bockman
2020-09-10 20:37:44 UTC
Is the krita version correct? can you please update to latest krita stable (4.3.0) or better yet krita plus and confirm this is still the case? (In reply to vanyossi from comment #1) > Is the krita version correct? Yes. > can you please update to latest krita stable (4.3.0) Done. It still crashes with an extremely similar stack trace. I tried the appimage versions of Krita 4.3.0, and it works. Perhaps the problem is an incompatibility with the version of some dependency currently being used by the Ubuntu packages. 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. *** Bug 426390 has been marked as a duplicate of this bug. *** Also referenced *** Bug 426390 has been marked as a duplicate of this bug. *** I can confirm that this close crash issue no longer exists in version below. https://binary-factory.kde.org/job/Krita_Stable_Appimage_Build/ Last Successful Artifacts gmic_krita_qt-x86_64.appimage 30.52 MB view krita-4.4.0-alpha-c00326b-x86_64.appimage 215.27 MB view Krita-Plus-x86_64.appimage.zsync 377.06 KB view When will this make it to Ubuntu KDE repository? Thanks Same answer as for your other report; though when a distribution will actually package a release and for which update, that's not up to us. We recommend using the appimage in any case, because those use a heavily patched version of Qt. I don't think its the newer version fixing it. The 4.3.0 appimage works correctly, BUT the 4.3.0 Ubuntu package does not. So is this now "resolved fixed" just because the appimage versions work? Are the Ubuntu packages unsupported? We do not support distribution packages; we cannot control what version of Qt, which Qt patches are in -- so, yes, only the appimages are supported by the krita team. (In reply to Boudewijn Rempt from comment #9) > We do not support distribution packages OK. Thanks for explaining. Shouldn't the status be "resolved downstream" then? Because this certainly hasn't been "fixed". Well, maybe. It's not like downstream is reading these reports :-) (In reply to Boudewijn Rempt from comment #11) > Well, maybe. It's not like downstream is reading these reports :-) Sure. It's just that it's confusing as a user to find a bug report marked as "fixed" when nothing was actually directly done about the problem. Created attachment 134270 [details]
New crash information added by DrKonqi
krita (4.2.9) using Qt 5.12.8
- What I was doing when the application crashed:
just looked at a png file and put it on the clipboard
- Unusual behavior I noticed:
none
- Custom settings of the application:
none
-- Backtrace (Reduced):
#12 0x00007fcb035f2908 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007fcb035f2e1d in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007fcb02bc601e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007fcb035f2c29 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
[...]
#17 0x00007fcb02bc601e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
|