| Summary: | Krita crash with QT_QPA_PLATFORMTHEME=kde | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | Oleg Nikitin <asrifox> |
| Component: | * Unknown | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | crash | CC: | asrifox, dimula73, halla, kde |
| Priority: | NOR | ||
| Version First Reported In: | 5.1.5 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Oleg Nikitin
2023-07-02 10:40:57 UTC
Please report this to Arch. It's not something we can fix in Krita. FWIW, this happens on Fedora too, so is this a problem for all downstreams? And if it is, what path should they take to resolve it? It seems rather bizarre to me that a KDE-affiliated application crashes on start with `QT_QPA_PLATFORMTHEME=kde` to me, but maybe I don't understand the implications. The crash obviously happens in KDEPlasmaPlatformTheme.so, somewhere in Qt's opengl code. So, how is this a bug in krita? If the bug is in QT, then why was the advice to punt the report down to Arch, instead of up to QT? Also, the fact that it's *only* Krita that segfaults in this fashion suggests that this is unlikely to be a general, common QT problem, and is likely somehow related to how Krita is instantiating the QCoreApplication. In addition, the fact that Krita stops crashing if QT_QPA_PLATFORMTHEME is set to something other than `kde` suggests that the problem is related to the combination of Krita+KDEPlasmaPlatformTheme+QT. Since this is 100% reproducable, I'm happy to assist in providing information, if anyone cand provide some indication on what info would be useful. Hi, pdf! During startup phase, Krita creates a dozen of QApplication objects to probe all supported openGL modes and then discards them. That is usually not favored by the themes code, because they expect QApplication to be created only once (they tend to use static data that they don't dispose on destruction). That is the problem we had to patch/workaround in our version of Qt/KF5. Most probably, this crash has the same nature. |