Looks like this bug was introduced in telepathy mission-control 5.16.0 Steps to reproduce: gsettings set im.telepathy.MissionControl.FromEmpathy use-conn false Current behavior: MC_DEBUG=all G_MESSAGES_DEBUG=all /usr/lib/telepathy/mission-control-5 2>&1 | grep use-conn (process:23529): mcd-DEBUG: mcd_connectivity_monitor_set_use_conn: use-conn GSettings key changed; new value = false (process:23529): mcd-DEBUG: mcd_connectivity_monitor_set_use_conn: use-conn GSettings key changed; new value = true The real value is being overridden by the default value (true) at startup. If we set the value using gsettings during runtime it works as expected and the connection managers are launched even if there is no network. Expected behavior: mission-control should respect the value defined in gsettings at startup.
Created attachment 89821 [details] [review] connectivity-monitor: start watching 'use-conn' key in constructed
Merged to 5.16 and master. Will be in 5.16.1
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.