Replacing X11 instances leads to non-composited-like Gtk applications
As visible in this screencast:
Using --replace
leads to the replacing instance not to be considered the proper compositor, while stopping both instances and starting a new one in the same display works fine (also for previously opened windows there).
Note that the XSelection
for CM compositor is properly set in the window manager, using a tool such as x11-compositor-checker.c, so it could also be a toolkit issue. The weird thing is that newly launched applications are also affected.
Edited by Marco Trevisan