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
..
accessibility.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
bluetooth.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
brightness.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
keyboard.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
location.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
network.js	network: Don't assume the active connection has been processed first	2018-09-03 23:34:07 +00:00
nightLight.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
power.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
rfkill.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
screencast.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
system.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
thunderbolt.js	thunderbolt: honor boltd's AuthMode property	2018-03-05 22:03:28 +01:00
volume.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00