gnome-shell/js
Andre Moreira Magalhaes dd846f1ba2 rfkill: Always sync state on construction
This fixes an issue where the indicator can be out of sync until the
RfkillManager (used by it) properties change.

The problem is that multiple instances of the indicator will use
the same RfkillManager instance (getRfkillManager() returns a singleton)
that only guarantees to emit the changed signal in two scenarios:
when the D-Bus proxy connects and when the proxy properties change.

If by the time an indicator is instantiated the RfkillManager's D-Bus
proxy is already connected, that indicator would only sync its state
when the RfkillManager properties change.

Let's fix that by always syncing the state on construction - in the worst
case scenario the RfkillManager's D-Bus proxy won't have connected yet
and the indicator state will be temporarily out of sync but once it gets
connected the indicator will sync again with the correct state.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/1386
2020-08-02 19:57:11 +00:00
..
dbusServices Move screencasting into a separate service process 2020-07-31 10:51:12 +02:00
gdm loginDialog: Reset auth prompt on vt switch before fade in 2020-07-27 16:18:44 -04:00
misc Move screencasting into a separate service process 2020-07-31 10:51:12 +02:00
perf cleanup: Require "dangling" commas 2019-11-11 19:25:14 +00:00
portalHelper js: Don't use templates in files with translations 2020-02-17 23:20:40 +01:00
ui rfkill: Always sync state on construction 2020-08-02 19:57:11 +00:00
js-resources.gresource.xml Move screencasting into a separate service process 2020-07-31 10:51:12 +02:00
meson.build extensions-app: Move Extensions app to new subproject 2020-03-27 23:33:30 +00:00
portal-resources.gresource.xml js: Remove unused files from resources 2020-03-09 13:18:48 +00:00