Bug 72003

Summary: use-conn setting not working correctly
Product: Telepathy Reporter: Tiago Salem Herrmann <tiago.herrmann>
Component: mission-controlAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED FIXED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium Keywords: patch
Version: git master   
Hardware: Other   
OS: All   
Whiteboard: review+
i915 platform: i915 features:
Attachments: connectivity-monitor: start watching 'use-conn' key in constructed

Description Tiago Salem Herrmann 2013-11-25 20:18:53 UTC 
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.
Comment 1 Guillaume Desmottes 2013-11-26 09:21:32 UTC 
Created attachment 89821 [details] [review]
connectivity-monitor: start watching 'use-conn' key in constructed
Comment 2 Guillaume Desmottes 2013-11-26 09:30:52 UTC 
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.