- For the switches to work, unity-control-center needs to be started with the right COMPIZ_CONFIG_PROFILE (same as Unity) - in a VM, this will normally be "ubuntu-lowgfx"
- nautilus, which is launching unity-control-center here has COMPIZ_CONFIG_PROFILE="ubuntu" (the default from /etc/X11/Xsession.d/65compiz-profile-on-session
- Because gnome-session has the same value, and gnome-session launches nautilus
- And gnome-session doesn't get the value from Unity because it starts up before Unity does, and Unity's systemd (or upstart - this is also broken on 16.04's current dailies) jobs are where the profile is decided
I guess that the COMPIZ_CONFIG_PROFILE calculation needs to be moved earlier in the session startup.
True, good find
I think it's like this
- For the switches to work, unity-control- center needs to be started with the right COMPIZ_ CONFIG_ PROFILE (same as Unity) - in a VM, this will normally be "ubuntu-lowgfx" center here has COMPIZ_ CONFIG_ PROFILE= "ubuntu" (the default from /etc/X11/ Xsession. d/65compiz- profile- on-session
- nautilus, which is launching unity-control-
- Because gnome-session has the same value, and gnome-session launches nautilus
- And gnome-session doesn't get the value from Unity because it starts up before Unity does, and Unity's systemd (or upstart - this is also broken on 16.04's current dailies) jobs are where the profile is decided
I guess that the COMPIZ_ CONFIG_ PROFILE calculation needs to be moved earlier in the session startup.