Bug 140783 - Composite manager crashed twice but translucency still works
Summary: Composite manager crashed twice but translucency still works
Status: RESOLVED NOT A BUG
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-28 18:48 UTC by Ryan Reich
Modified: 2007-02-24 22:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Backtrace of Crash (3.43 KB, text/plain)
2007-02-24 20:48 UTC, Jacob Beauregard
Details
Konsole Output while going through crash/restarting (less helpful) (523 bytes, text/plain)
2007-02-24 20:59 UTC, Jacob Beauregard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Reich 2007-01-28 18:48:33 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc 3.4.4 
OS:                Linux

If I select translucency from the Control Center, then of course I need to restart my session.  However, when I do so I get a dialog box telling me that the composite manager has crashed twice in the last minute (really, the last five seconds) and will be disabled for the session.  No translucency.  But if I go to the Control Center and unselect and then reselect translucency, the screen refreshes and I get translucency working perfectly immediately.  The composite manager does crash again if I restart the session, though.

Actual KDE version is 3.5.6, but the menu box only shows up to 3.5.5, so I gave it as "recent SVN" build instead.
Comment 1 Jacob Beauregard 2007-02-24 20:48:59 UTC
Created attachment 19800 [details]
Backtrace of Crash

Hopefully this can help someone fix this.
Comment 2 Jacob Beauregard 2007-02-24 20:49:58 UTC
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.
Comment 3 Jacob Beauregard 2007-02-24 20:59:42 UTC
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.
Comment 4 Lubos Lunak 2007-02-24 22:08:05 UTC
The backtrace shows a crash in powder. We do not ship such decoration.