~vcs-imports/gnome-settings-daemon/+git/gnome-settings-daemon:jjardon/no_AM_GLIB_GNU_GETTEXT

Last commit made on 2016-01-10
Get this branch:
git clone -b jjardon/no_AM_GLIB_GNU_GETTEXT https://git.launchpad.net/~vcs-imports/gnome-settings-daemon/+git/gnome-settings-daemon

Branch merges

Branch information

Name:
jjardon/no_AM_GLIB_GNU_GETTEXT
Repository:
lp:~vcs-imports/gnome-settings-daemon/+git/gnome-settings-daemon

Recent commits

5f1df50... by Javier Jardón

configure.ac: Do not use AM_GLIB_GNU_GETTEXT

060a9c3... by Javier Jardón

Remove unneeded X includes

6695560... by Mario Blättermann

Updated German translation

233df0a... by Bastien Nocera

media-keys: Add labels for the rfkill OSD

Which should hopefully make the icons a bit clearer.

eb4fad0... by Bastien Nocera

rfkill: Limit 2-step unlocking to Bluetooth rfkill

In 5f29c37ed0fd8c7496a071b8b5fa74cd861e1886 we added a two-step
mechanism to avoid Bluetooth rfkills from being stuck in rfkill'ed mode.
The problem is that the 2-step unblocking will take Bluetooth adapters
out of rfkill even if they were disabled when we went into airplane
mode.

So only apply this two-step unlocking when enabling Bluetooth.

aec68cc... by Mario Blättermann

Updated German translation

3fa0f72... by Bastien Nocera

media-keys: Add support for Killswitch media keys

Add support for the XF86Bluetooth, XF86WLAN and XF86UWB media keys.
The first one will toggle Bluetooth on/off, as the Bluetooth panel does,
the latter ones will toggle the global software killswitch.

The reasoning behind those 2 keys toggling the global software
killswitch is that:
- we don't have a killswitch for only WiFi
- there are very very few laptops with a UWB killswitch button, if
  anyone actually remembers what UWB actually is
- there are no XF86 keys for the global killswitch, so they usually get
  mislabeled as the WLAN killswitch

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

3025c4c... by Jason Gerecke

common: wrap grab_button with gdk_error_trap_push/pop

The XIGrabButton and XIUngrabButton functions can fail with e.g. BadDevice,
so we should be careful to catch the error and not crash.

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

69c8524... by Rui Matos

power: Sync IIO light sensor values right after claiming the interface

In case the IIO sensor daemon doesn't change the values immediately
after we claim the interface, we should get them to be in sync from
the start.

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

6b38a7d... by Rui Matos

power: Watch IIO light sensor only while we're the active session

We can't change the brightness in that case but we can and should
avoid any polling the IIO sensor daemon might have to do while
inactive.

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