The IMEI was not being properly displayed in the UI; the code would load it
reading 'EquipmentIdentifier' from ModemManager, but the UI wasn't getting
refreshed properly when that happened. So at the end, the IMEI was stored but
not shown. This patch fixes the issue, by reloading the UI element when the IMEI
is retrieved.
The same issue was happening with the Operator Code, with the additional issue
being that this property is meant to change whenever the registration info in
the modem changes. Therefore, we now listen to the 'RegistrationInfo' signal to
detect the changes and update the Operator Name when that happens.
https://bugzilla.gnome.org/show_bug.cgi?id=688211
Done with:
sed -i -e 's/RfkillGlib/CcRfkillGlib/g' \
-e 's/RFKILL_GLIB/CC_RFKILL_GLIB/g' \
-e 's/rfkill_glib/cc_rfkill_glib/g' \
-e 's/RFKILL_TYPE_GLIB/CC_RFKILL_TYPE_GLIB/g' \
rfkill-glib.[ch] cc-network-panel.c
This would need to be done when we reset the copy/paste from
gnome-bluetooth.
And not just wireless. We need to use /dev/rfkill directly
to make sure that all the devices (3G, GPS, Bluetooth, etc.) get
switched off correctly when airplane mode is on.
https://bugzilla.gnome.org/show_bug.cgi?id=675778
Conflicts:
panels/network/cc-network-panel.c
Because it's not just about disabling the network, it needs
to disable a host of other wireless devices, and those need to
be blocked even if you end up plugging them into your computer.
Conflicts:
panels/network/cc-network-panel.c
Rename NetDeviceWired to NetDeviceEthernet, but split out most of the
code into a new NetDeviceSimple superclass that can later be used for
other device types that we provide only minimal UI/support for.
https://bugzilla.gnome.org/show_bug.cgi?id=677143
We support multiple kinds of wireless networks; clarify which kind
we're talking about here.
Also, add "Wi-Fi" and "Wifi" to the desktop file search keywords
(leaving "Wireless" there as well).
https://bugzilla.gnome.org/show_bug.cgi?id=677143
gnome-shell relies on being able to call
gnome-control-center network connect-8021x-wifi <DEVICE> <AP>
This was broken in the big refactoring of the wifi panel
last cycle. Bring it back.
Instead of manually handling button release events on the
treeview, use activatable cell renderers for the ssid text
and for the arrow, and connect to activate signals for them.
We use cell area focus-sibling technology to make the keynav
in the list just have focus locations for the ssid and the
arrow.
This makes the details pages reachable by keynav, which was
not the case before.
The mode cell renderer had a property named 'mode', which
clashed with the GtkCellRenderer property of that name, which
confused the treeview keynav.
Rename the new property to ap-mode.
Remove the reference to the new longer existing viewport_list
widget, and be more careful about getting a NMRemoteSettings
object when calculating the last used time.
