Summary: | Plasma panel does not recovery after suspend and reenable composite | ||
---|---|---|---|
Product: | [Plasma] plasma4 | Reporter: | LuRan <hephooey_dev> |
Component: | panel | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
LuRan
2010-12-16 22:34:37 UTC
I added some kDebug code to ThemePrivate::compositingChanged(), this bug is very easy to trigger when the compositing is restarted: changing the advanced options in kwin, remove a monitor in nvidia-settings, etc. the compositingChanged function get the initial disabling signal, but it still consider the compositing is off when it is reenabled. If I disable compositing again using Alt+Shift+F12, compositingChanged works again and received the compositing off signal, but it is NEVER called again no matter how many times I disable/enable compositing after that. I do not know if it is because plasma spend too much time to discard the cache and cannot responding fast enough. One quite reliable way to reproduce the bug is to restart kwin by kwin --replace, with 6-8 window opened and some special effect like blur enable. After some debug, this bug seems to be a duplicate of 179042 *** This bug has been marked as a duplicate of bug 179042 *** |