Summary: | kactivitymanagerd: Crash when logging out of Plasma | ||
---|---|---|---|
Product: | [Plasma] kactivitymanagerd | Reporter: | Rainer Finke <rainer> |
Component: | general | Assignee: | Ivan Čukić <ivan.cukic> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | fabian, plasma-bugs |
Priority: | NOR | ||
Version: | 5.10.95 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | https://commits.kde.org/kactivitymanagerd/ed092b96f7af1701808c2c76e15f3ae68f150a4c | Version Fixed In: |
Description
Rainer Finke
2017-10-09 19:06:56 UTC
This should have been fixed with Qt 5.8, see bug 348194. Ok, strange this was Qt 5.9 or maybe 5.10 beta already. I will test again and tell you if it is still an issue in Qt 5.10 beta and Plasma 5.11.1. This is definitely still an issue. Using Qt 5.10.0, Plasma 5.12 beta and KDE Frameworks 5.42 here, 100% reproducible. It crashes with a fatal message, which is not visible in the log, but from the backtrace likely to be qFatal("QThread: Destroyed while thread is still running"); Git commit ed092b96f7af1701808c2c76e15f3ae68f150a4c by Fabian Vogt. Committed on 22/01/2018 at 07:53. Pushed by fvogt into branch 'Plasma/5.12'. Actually quit threads nicely Summary: 27c0245b1715044cf4d401f1c9d7e7a915a4f3c5 ("[resources] Nicely quit threads") has no effect as the threads are not running an event loop. Instead use the QThread::requestInterruption() mechanism. Test Plan: kactivitymanagerd left a coredump on each logout if kate was opened before logging out. Now it doesn't do that anymore. Reviewers: #plasma, ivan, anthonyfieroni Reviewed By: #plasma, ivan Subscribers: lbeltrame, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D9998 M +3 -2 src/service/Resources.cpp M +3 -2 src/service/plugins/sqlite/ResourceScoreMaintainer.cpp https://commits.kde.org/kactivitymanagerd/ed092b96f7af1701808c2c76e15f3ae68f150a4c |