| Summary: | Pure Qt application crashes asking for icon via QFileIconProvider::icon in secondary thread due to missing KGlobal::locale() call in main thread | ||
|---|---|---|---|
| Product: | [Unmaintained] kdelibs | Reporter: | Matteo Italia <kde> |
| Component: | kdecore | Assignee: | kdelibs bugs <kdelibs-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | adaptee |
| Priority: | NOR | ||
| Version First Reported In: | 4.10.5 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Matteo Italia
2013-07-28 01:57:34 UTC
A brief testcase: https://bitbucket.org/mitalia/kdebug322901 The application creates a separate thread and uses QFileIconProvider::icon from it; launching the application without parameters under Qt 4.8 with KDE integration results in the crash described above. Instead, if you specify "workaround" as command-line parameter, the program calls QFileIconProvider::icon first in the main thread, which indirectly triggers the missing KGlobal::locale() call and avoids the crash. Also, targeting my local Qt 5.1 *without* KDE integration does not result in any problem. Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Andrew, I understand that this is probably an automated post, part of the bugtracker cleanup, but it seriously feels like mockery. The bug has been "stagnant for a long time" because you (not you personally, buy "you KDE people") completely ignored it. I investigated the problem, I reduced it to a minimal test case that always exhibited the problem, and even proposed a possible fix; I don't think I could have done anything more than this, yet nobody even bothered to reply, as it's been my experience in general on KDE's bugtracker. That being said, I re-tested on an Ubuntu 17.10 with KDE 5.10.5, and the problem seems to be resolved; probably this particular bug wasn't included in the umpteenth rewrite of the core libraries; have a good day. |