Summary: | segfault when reloading kscreen kded4 module | ||
---|---|---|---|
Product: | [Plasma] KScreen | Reporter: | Achim Bohnet <ach> |
Component: | kded | Assignee: | Alex Fiestas <afiestas> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | dvratil |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kscreen/40735b21adb5131fd6b6336a5ba1c3b5ccfaa434 | Version Fixed In: | |
Sentry Crash Report: |
Description
Achim Bohnet
2013-01-08 22:13:01 UTC
Happens with git sources for 8. Jan 2013 evening. Contains commit 66432954 Environment is kubuntu 12.10 with kde 4.10 rc2 pkgs Git commit 40735b21adb5131fd6b6336a5ba1c3b5ccfaa434 by Dan Vrátil. Committed on 09/01/2013 at 09:38. Pushed by dvratil into branch 'master'. Null Generatorpointer in Generator::destroy() Fixes crash when reloading the KDED module, because Generator::self() was returning pointer that has been previously deleted in Generator::destroy() when the module was unloaded. M +1 -0 kded/generator.cpp http://commits.kde.org/kscreen/40735b21adb5131fd6b6336a5ba1c3b5ccfaa434 Mmm why is kscreen-console (libkscreen) being affected by code of kscreen ? The fact that kscreen-console was running is unrelated, the backtrace clearly comes from KDED and I was able to reproduce the crash locally without running kscreen-console. I updated to bug title accordingly. |