Summary: | Crash in QIconPrivate::~QIconPrivate after KAlarm exits | ||
---|---|---|---|
Product: | [Applications] kalarm | Reporter: | RJ <ogldelphi> |
Component: | general | Assignee: | David Jarvie <djarvie> |
Status: | CLOSED FIXED | ||
Severity: | crash | CC: | cfeck, ogldelphi, palo.kisa |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
See Also: | https://github.com/lxde/lxqt/issues/1193 | ||
Latest Commit: | 2a5b20e0d6713889a59b7cf55d9d293d97a8a4c2 | Version Fixed In: | 16.12.0 |
Description
RJ
2016-11-08 18:09:53 UTC
This issue could be caused by "libqtxdg". I have no idea what component is responsible for loading this library, neither Qt nor KDE sources reference it. (In reply to Christoph Feck from comment #1) > This issue could be caused by "libqtxdg". I have no idea what component is > responsible for loading this library, neither Qt nor KDE sources reference > it. libqtxdg is library from lxqt desktop. Anyway, if you start lxqt desktop and then start Kalarmm on it then close it from tray icon you will get crash. That it. Is this a bug in lxqt or kalarm itself, please let me know. Yes, but the question is how XdgIconLoaderEngine comes into KAlarm. I guess LXQt has its own Qt platform integration plugin which then uses libqtxdg, so I suggest to report the problem to LXQt developers. (In reply to Christoph Feck from comment #3) > Yes, but the question is how XdgIconLoaderEngine comes into KAlarm. > > I guess LXQt has its own Qt platform integration plugin which then uses > libqtxdg, so I suggest to report the problem to LXQt developers. Let them know https://github.com/lxde/lxqt/issues/1193 I believe the reason here is a dangling QApplication object, see the comments in LXQt bug tracker -> https://github.com/lxde/lxqt/issues/1193#issuecomment-260337417 Thanks for the analysis. I will suggest a patch to kalarm developers (either using a scoped pointer as suggested, or simply by creating the application object on the stack, as suggested by Qt examples). palinek, I decided to use the version you suggested. If you want proper attribution for the patch, please state your full name. Thank you for coming up with a fix. What you suggested in the LXQt bug tracker is fine apart from needing some adjustments to make it compile. I'd prefer to make the commit myself since I like to use certain conventions for bugfix commits, but equally I'd be happy to attribute you as the author of the patch - as Christoph suggests, you might want to state your full name for that. > I'd prefer to make the commit myself since I like to use certain conventions
> for bugfix commits, but equally I'd be happy to attribute you as the author of
> the patch - as Christoph suggests, you might want to state your full name for
> that.
I've changed the nick used here to the real name. Feel free to use it to preserve authorship or do your own commit (I do not insist in preserving the authorship as I don't know how many other changes you need to do).
The fix is now committed with you as the author, and will be in version 2.11.11 (KDE Applications 16.12) - git commit 2a5b20e0d6713889a59b7cf55d9d293d97a8a4c2 (16.08 branch). This could potentially fix other crashes which have been reported on application exit, so thank you for making the effort to find the cause of this bug. |