goa_warning is meant for goa-daemon, and it does not really add any
value in this case. Switching to g_warning lets us cut down on the
number of symbols that are exported from libgoabackend.
https://bugzilla.gnome.org/show_bug.cgi?id=693261
The vlan page (and other virtual devices) use network-simple.ui,
and the off switch in that pages heading was not centered relative
to the rest of the heading, as it is in other pages. This shows
up as the switch jumping up and down as you switch pages.
https://bugzilla.gnome.org/show_bug.cgi?id=693004
In bug 689638, the designers only asked for the list icons
to be symbolic, not the big icons in the page headings. The
current code was failing on both ends: virtual devices like
vlan still had non-symbolic icons in the list, and several
pages (e.g mobile and proxy) had symbolic icons in the headings.
https://bugzilla.gnome.org/show_bug.cgi?id=693001
It's confusing to call an ethernet device "disconnected" when it is
plugged in but not in use. Just don't say anything instead.
Also, update the icon logic to show the "disconnected" icon in this
state, rather than the "connected" one, since it's confusing for the
icon to change even though the network connection hasn't been
activated.
https://bugzilla.gnome.org/show_bug.cgi?id=646029
Since the notification filtering was merged in gnome-shell, the right
key is o.g.d.notifications.show-in-lock-screen, and the previous one
is simply ignored.
https://bugzilla.gnome.org/show_bug.cgi?id=692938
This is consistent with the guideline to use symbolic icons for
classes and reserve full color icons for "things" like apps, people,
documents, pages, etc.
It is also consistent with how these devices are displayed in the
network menu, notifications, and dialogs.
https://bugzilla.gnome.org/show_bug.cgi?id=689638
Recent NetworkManager can create AP-mode hotspots instead of Ad-Hoc
mode ones, which are less compatible with mobile devices. Do that
if NetworkManager and the device support it.
https://bugzilla.gnome.org/show_bug.cgi?id=686732
This could create crashers when no errors were detected, but
either the D-Bus call or loading the pixbuf return NULL.
Conflicts:
panels/background/cc-background-panel.c
In addition to simplifying a bunch of places that were calling
nm_remote_settings_list_connections() +
nm_device_filter_connections(), this also ensures we filter out slave
connections everywhere (except when they are the active connection).
https://bugzilla.gnome.org/show_bug.cgi?id=677145
Bond, bridge, and VLAN devices may not actually exist until their
connections are brought up. So for those types, create device items
(of type NetVirtualDevice or a subclass) as soon as we see the
NMConnection, and then watch for the NMDevice being added later.
https://bugzilla.gnome.org/show_bug.cgi?id=677145
Unfortunately, the VPN plugins provide their own .ui files for their
editor pages, so we can't make them look competely GNOME-3-ish. But
the code does try to fix them up a little bit by realigning the
labels.
vpn-helpers.[ch] is nearly identical to network-manager-applet's,
but eventually this code will move into libnm-gtk.
https://bugzilla.gnome.org/show_bug.cgi?id=691285
This code is fairly independent of the rest, and we don't want
net-device-wifi.c to become too massive and unmaintainable.
The code in connection-editor/ is fairly similar to
nm-connection-editor, with some simplification because we
currently only edit wireless connections.
The code in wireless-security/ is almost a straight copy
of the same code in nm-connection-editor, with some changes
to the .ui files to make them fit better in the new design.
When the user switches the hotspot switch off, we present a
confirmation dialog which can be canceled. We do keep the
hotspot running in that case, but we forget to set the switch
back to 'on'. Fix that.
