Summary: | Screen goes black if I make a window full-screen and I disable, then enable compositing | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Grósz Dániel <groszdanielpub> |
Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | cfeck, jnelson-kde, russianneuromancer |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Grósz Dániel
2009-12-27 03:16:38 UTC
I had the same problem yesterday playing in SMPlayer fullscreen. The video had lags, and I was blaming composite (which is bullshit, since in fullscreen mode, the compositing is effectively disabled), so I disabled it while it was in fullscreen mode. I cannot remember the next actions exactly, but I ended up in black screen whenever I tried to activate compositing, switching it off showed desktop normally. SMPlayer was already terminated. I also use intel 945, so it may be an upstream bug. using an nvidia (proprietary driver for now) I have the same problems. openSUSE 11.2, KDE 4.2, 4.3 and 4.4 Possibly related: bug 205803 Also possibly related: bug 185127 confirmed (nvidia) the screen does however not "go black" but just show the root window, but no windows (including the desktop) at all (i've a root pixmap) - so this is _no_ upstream bug. the reason is ilkely that kwin messes up the suspension/unredirection (rather than pot. tagging all windows invisible) as neither fullscreen aniimations (tabswitch etc.) nor other things (clock) are painted. interestingly, just activating (unredirected) composition on a window that became fullscreen while compositing is suspended does not cause this. konsole does btw. not work as it's ARGB by default and thus can not cause unredirecting I can't reproduce this issue with KWin 4.8.2. can't reproduce either - now it would be great to figure which change actually fixed it ;-) (it's not the graphicssystem) If anyone still experiences this with >= 4.8 - please reopen the bug |