Arch Linux

j33205

Member

Registered: 2015-06-28

Posts: 38

[CLOSED] Terminator conflict with Xcompmgr

Hello. I'm running simply Openbox, and for the purposes of this post, Xcompmgr for composting. Xcompmgr seems to be working fine, it fixed some other window issues I was having like window lag when dragging. Anyway, I would like to apply true transparency to my terminal window, a feature I very much enjoy. I'm using Terminator but am having some weird issues.

I first noticed this when trying to enable transparency via the Preferences dialog in Terminator. I would restart Terminator and it would open not with transparency but instead with the setting I had before, black bg. And when I tried dragging the window I would get tiled shadows of the window, if that makes sense. At some point after fiddling with it for long enough I realized that by closing and restarting Terminator enough (random number of) times it would eventually result in the desired transparency and I wouldn't get drag shadows anymore. Then upon closing the window again I would encounter the same situation whenever I reopened the program afresh.

I now notice that it has nothing to do with the Term transparency setting itself since I now have this problem with any Term setting. It appears to be a conflict between Xcompmgr and Terminator as I don't have this issue with any other program (so far) and it only happens when Xcompmgr is running (Term returns to normal non-transparent self without Xcomp running). Is this a documented thing? Is there a way around this?

Last edited by j33205 (2015-07-29 18:45:22)

loafer

Member

From: the pub

Registered: 2009-04-14

Posts: 1,772

Re: [CLOSED] Terminator conflict with Xcompmgr

I use i3, xcompmgr and Terminator.  I have no problems at all.  I have an intel GMA graphics card.

---

All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.

j33205

Member

Registered: 2015-06-28

Posts: 38

Re: [CLOSED] Terminator conflict with Xcompmgr

It seems to be working fine now, I'm not sure what made it work, could just be the system restart, even though I'm pretty sure I did that already yesterday. Anyway I'm gonna leave this open for another day just in case this is a false positive.