Summary: | KDE daemon crashed after connecting power | ||
---|---|---|---|
Product: | [Unmaintained] solid | Reporter: | Wawrzyniec "Wawrzek" NiewodniczaĆski <wawrzek> |
Component: | powermanagement-daemon | Assignee: | Dario Freddi <drf> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | bernhard, faisne, itbepa, james, kde, kesarling, soitanen.michael, thijs22nospam, tipasergio |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 4.7.2 | |
Sentry Crash Report: |
Description
Wawrzyniec "Wawrzek" NiewodniczaĆski
2011-04-01 00:58:14 UTC
*** Bug 271342 has been marked as a duplicate of this bug. *** *** Bug 273153 has been marked as a duplicate of this bug. *** *** Bug 269922 has been marked as a duplicate of this bug. *** *** Bug 272034 has been marked as a duplicate of this bug. *** *** Bug 272250 has been marked as a duplicate of this bug. *** Git commit 0802a5da6cfaa79c91a7e46ddfa86f1c049a48c4 by Dario Freddi. Committed on 30/09/2011 at 12:45. Pushed by dafre into branch 'master'. Move the activity simulation AFTER removing idle timeouts. Otherwise, timeouts might be triggered out when the actions are still being unloaded, and hence still listening to them. BUG: 269855 M +4 -2 powerdevil/daemon/powerdevilcore.cpp http://commits.kde.org/kde-workspace/0802a5da6cfaa79c91a7e46ddfa86f1c049a48c4 Git commit 80ab498f0a9ca69abc82c2e01a491f19a239d9a0 by Dario Freddi. Committed on 30/09/2011 at 12:45. Pushed by dafre into branch 'KDE/4.7'. Move the activity simulation AFTER removing idle timeouts. Otherwise, timeouts might be triggered out when the actions are still being unloaded, and hence still listening to them. BUG: 269855 FIXED-IN: 4.7.2 M +4 -2 powerdevil/daemon/powerdevilcore.cpp http://commits.kde.org/kde-workspace/80ab498f0a9ca69abc82c2e01a491f19a239d9a0 *** Bug 285710 has been marked as a duplicate of this bug. *** *** Bug 291644 has been marked as a duplicate of this bug. *** Bug 291644 has a near identical backtrace, but is reported with 4.7.4, which is after the fix. |