search

mate-desktop / marco

MATE default window manager
https://mate-desktop.org
GNU General Public License v2.0
199 stars 87 forks source link

Black shadow trail when moving windows #273

Open paravoid opened 8 years ago

paravoid commented 8 years ago

The following seems to happen to me with MATE 1.14 on Debian stretch (i.e. using GTK+3). This did not happen before this week's upgrades (i.e. with 1.12/GTK+2). This behavior stops happening if I enable marco's software compositing or if I run marco side-by-side with compton. If it matters, this is on a modern Broadwell system with an i915 display, running what's in Debian stretch/testing.

Basically, when moving a window (any window), over some other window that has a large white area, a very noticeable black trail is left behind in that white area. This is especially easy to trigger with e.g. mate-terminal and pluma, but it's much less noticeable with e.g. caja, for some reason.

What's amazing here, though, is that this behavior stops happening entirely as soon as a context menu (right click or menu bar) shows up. It doesn't even matter if the context menu appears on the same two windows — e.g. with three terminals open, moving the first over the second results in the black trail; right-clicking on the third one makes the black trail disappear between all three(!). If a new window pops up after that, though, the trail will be then noticeable in that new window.

This behavior may be a little hard to describe, so I've made a couple of GIFs to demonstrate it: marco marco2

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/34936382-black-shadow-trail-when-moving-windows?utm_campaign=plugin&utm_content=tracker%2F841233&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F841233&utm_medium=issues&utm_source=github).
ghost commented 6 years ago

I have had this exact same issue for a very long time now. Using a WM such as Metacity seems to fix it, but it isn't that great of a solution.

lukefromdc commented 6 years ago

I've seen issues like this in Marco/Metacity (set noncompositing) as long as GNOME 2 and later MATE have existed. Usually this has been with with the window background-color from the theme as the trail color, and most noticable on slower systems.