This relies on patches that turn the recent-files-max-age gtk
setting into an X setting which is backed by a gsetting.

Fix focus handling in the screen lock dialog - focus got stuck
in the combo box.

Adapt to the privacy schema key name: 'stealth-mode' ended up
as 'hide-identity'.

This relies on new settings and D-Bus API in the g-s-d
housekeeping plugin.

Control whether the users full name is shown permanently on screen.

These controls duplicate what we currently have in the screen
panel - it will have to be removed there.

This adds a panel where we present information and controls
affecting the users privacy. This initial commit just puts
the framework in place, the panel itself is empty.

As we need that to get the right name from "hostname".

Increase the width slightly to 860 from 850.

https://bugzilla.gnome.org/show_bug.cgi?id=683499

Left-over files from update-icon-cache shouldn't be created
in the first place when running distcheck.

Some files were removed from the libgnome-volume-control
git sub-module, and POTFILES.in didn't get updated.

https://bugzilla.gnome.org/show_bug.cgi?id=688291

Now that we have a HighContrast-specific WM theme.

https://bugzilla.gnome.org/show_bug.cgi?id=688257

GtkTable was deprecated in GTK+ 3.4.

https://bugzilla.gnome.org/show_bug.cgi?id=688254

Remove the use of gdk_threads_enter and gdk_threads_leave functions, as
they have been deprecated, and also replace gdk_threads_add_idle with
g_idle_add.

https://bugzilla.gnome.org/show_bug.cgi?id=688231

The g_type_init function was deprecated in glib 2.35.1 and the type system
is now initialised automatically.

https://bugzilla.gnome.org/show_bug.cgi?id=688231

Set the dialog hint on the window so that it is treated correctly by the
window manager.

https://bugzilla.gnome.org/show_bug.cgi?id=688198

Then don't mark it for translation. Duh.

cf. https://bugzilla.gnome.org/show_bug.cgi?id=681834

Fixes: https://bugzilla.gnome.org/688055

Fixes: https://bugzilla.gnome.org/668312

Fixes: https://bugzilla.gnome.org/687875

Online Accounts and User Accounts are very similar names.

https://bugzilla.gnome.org/show_bug.cgi?id=688003

As fallback is going away. #fallback

https://bugzilla.gnome.org/show_bug.cgi?id=682863

As the fallback mode is going away. #fallback

This reverts commit 658083ff.

https://bugzilla.gnome.org/show_bug.cgi?id=682871

Conflicts:
	panels/region/gnome-region-panel-input.c

As the fallback mode is going away. #fallback

This reverts commit dee8e091.

https://bugzilla.gnome.org/show_bug.cgi?id=682871

As fallback is now gone. #fallback

https://bugzilla.gnome.org/show_bug.cgi?id=682861

Now that the fallback mode is gone. #fallback

https://bugzilla.gnome.org/show_bug.cgi?id=682862

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

Rather than having an unusable switch (which wouldn't represent
the real state of the connection), show a spinner until the
connection is finished doing.

The only time we were looking at the powered state of the adapter
is when the killswitch state was changing. Except that we're fast enough
that bluetoothd didn't have time to power up the adapter, so its
state was unpowered, which we would set the switch to.

The switch was off, the adapter was on.

We fix that problem by tracking the powered state of the adapter
separately.

https://bugzilla.redhat.com/show_bug.cgi?id=841881