From d0bab1f7acfd76b5634013c0f16c19570ac2932e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Florian=20M=C3=BCllner?= <fmuellner@gnome.org>
Date: Wed, 3 Jun 2015 12:30:12 +0200
Subject: [PATCH] network: Initialize primary and VPN connections on startup

We only connect to the corresponding property notifications after both
Client and RemoteSettings are ready, so we may miss the initial signal
emission. Make sure to pick up the connections in this case to fix the
network indicator not showing up.

https://bugzilla.gnome.org/show_bug.cgi?id=772249
---
 js/ui/status/network.js | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/js/ui/status/network.js b/js/ui/status/network.js
index 6f42aea06..fee703bed 100644
--- a/js/ui/status/network.js
+++ b/js/ui/status/network.js
@@ -1632,6 +1632,8 @@ const NMApplet = new Lang.Class({
         this._readConnections();
         this._readDevices();
         this._syncNMState();
+        this._syncMainConnection();
+        this._syncVPNConnections();
 
         this._client.connect('notify::manager-running', Lang.bind(this, this._syncNMState));
         this._client.connect('notify::networking-enabled', Lang.bind(this, this._syncNMState));