We’re running a GNOME session in CI by starting a session on the host and injecting X information into CI containers with volume mounts and environment injection. However, GNOME seems to start in the “application switching” mode that seems to interfere with testing. Is there a way to make this not happen? A setting would be ideal, but perhaps we just start an application upon startup?
Thanks. It looks promising, but deploying GNOME extensions over Ansible is proving to be quite difficult, mostly because gnome-extensions wants a running D-Bus session with dconf listening on it. The Ansible role I found is also quite out-of-date and needs a lot of attention besides the D-Bus session thing. Is there a simple way to install an extension without interacting with dconf?