Iain Lane 7dbcd26619 network: Don't assume the active connection has been processed first ... `NMConnectionDevice._sync()` is responsible for setting up the active connection that we'll end up displaying. It expects the active connection to already be in a map `_connectionItems`. If it isn't in there, we get a null dereference and the indicator can get into a weird state where it doesn't display devices / connections properly. Let's change this expectation. If there is an active connection, `_deviceAdded()` will eventually get to it and call `_sync()` to set up the active connection state. We make `_sync()` tolerate there being no active connection when it's called. Closes: https://gitlab.gnome.org/GNOME/gnome-shell/issues/140 (cherry picked from commit 5d61e2563d)		2018-09-03 23:34:07 +00:00
..
extensionPrefs	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
gdm	gdm, util: Always allow to retry login in unlock mode	2018-07-25 20:38:58 +00:00
misc	objectManager: correct other invalid index code in onNameVanished	2018-09-04 01:11:40 +02:00
perf	cleanup: Use arrow notation for anonymous functions	2018-02-21 13:55:00 +00:00
portalHelper	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
ui	network: Don't assume the active connection has been processed first	2018-09-03 23:34:07 +00:00
js-resources.gresource.xml	thunderbolt: add policy provider and indicator	2018-02-05 21:38:49 +01:00
meson.build	build: Support the meson build system	2017-07-20 00:20:54 +02:00