(In reply to comment #10)
> I have never set a colormap on the root window ^_^;
you shouldn't anyway.
> but it does on the dock's window.
that would be the proper approach.
> maybe a bug in gtkgl?
maybe. in some base of cairo-dock for sure.
> by the way how do you know this is a custom color map? and who set this ?
Jedi abilities. I "sensed" it would be sth. like this...
ok, i just used my cheap & ordinary human brain.
"sth." in cairo-dock must change "sth." with global and persistant impact, "let's just check the root window... hmmmm, RGB_DEFAULT_MAP looks unfamiliar but i know that colormaps are related to ARGB windows - let's just remove it"
-> all new undecorated clients get shadowed again, therefore are not ARGB
-> that's it. Ensured the culprit by logging into a "failsafe" session, checked root properties (no colormap), launched cairo-dock (yes colormap), concluded:
(In reply to comment #10)
> I have never set a colormap on the root window ^_^;
you shouldn't anyway.
> but it does on the dock's window.
that would be the proper approach.
> maybe a bug in gtkgl?
maybe. in some base of cairo-dock for sure.
> by the way how do you know this is a custom color map? and who set this ?
Jedi abilities. I "sensed" it would be sth. like this...
ok, i just used my cheap & ordinary human brain.
"sth." in cairo-dock must change "sth." with global and persistant impact, "let's just check the root window... hmmmm, RGB_DEFAULT_MAP looks unfamiliar but i know that colormaps are related to ARGB windows - let's just remove it"
-> all new undecorated clients get shadowed again, therefore are not ARGB
-> that's it. Ensured the culprit by logging into a "failsafe" session, checked root properties (no colormap), launched cairo-dock (yes colormap), concluded:
YOUR FAULT ;-)