Summary: | Composite manager crashed twice but translucency still works | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Ryan Reich <ryan.reich> |
Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Backtrace of Crash
Konsole Output while going through crash/restarting (less helpful) |
Description
Ryan Reich
2007-01-28 18:48:33 UTC
Created attachment 19800 [details]
Backtrace of Crash
Hopefully this can help someone fix this.
I've had the same error message, but it appears after kwin has crashed and I restart it via Alt+F2. Translucency usually still occurs after restarting kwin (for inactive or moving windows), although opacity in the window options is no longer there. If I switch my window decorator to something like Crystal, this doesn't occur. If I have Powder as my window decorator, for reiteration, it keeps translucency for inactive windows while removing the opacity option from the window options. The crash preceding my situation of this error message only occurs with particular window decorators, Powder being one of them. And this crash most frequently occurs when performing an action that removes a window's border (including full screen). I believe that it could be the case for other window decorators as well, but I haven't tested anything yet. Created attachment 19801 [details]
Konsole Output while going through crash/restarting (less helpful)
This will probably be less helpful than the backtrace for solving anything. If
there's any way I can be of more use, once someone gets to this bug, get back
to me.
The backtrace shows a crash in powder. We do not ship such decoration. |