This commit was not intended for the master branch.

This reverts commit 451acbfb.

This commit was not intended for the master branch.

This reverts commit 4cc26ccf.

This adds the required code to use GUdev to monitor for the existence of
the rfkill device. This is relevant as the rfkill device might not exist
initially if the rfkill module is not loaded during login.

Fixes issue #52

The only benefit of doing so is that we can print information about not
finding any rfkill devices. This is not really helpful overall, so
simply remove the code.

Jan Tojnar authored 7 years ago and Benjamin Berg committed 6 years ago

https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/16

Benjamin Berg authored 6 years ago and Benjamin Berg committed 6 years ago

The rfkill code will cancel any running task when a new task comes in.
This makes sense in most cases, but the code would cancel the
cancellable from the outside scope which may be reused. This effectively
resulted in all changes to be cancelled immediately when this
compression happened once.

Fix the issue by creating a new cancellable and propagating the
cancelled state rather then setting it on the passed in cancellable.

g_app_info_create_from_commandline interprets the % character of
commands that are entered by the user. So escape all % characters by
doubling them so that they are not stripped from the resulting command
line.

Fixes: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/34

Shows a volume above 100% icon for output only in case we have a current
level above 100.
This new icon will be sent to any Shell version, including older version
which will show up 100 for level and this volume above 100% icon.

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

This option is sent to the Shell so that we can set the maximum level limit
when showing the OSD.
100 is the default value, when the parameter is unset. max_level can only be
above 100.
Old versions of the shell will display a level 100% in the OSD if current
level is above 100 and will ignore the max_level parameter.

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

Use the pulseaudio maximum allowed volume if allow-volume-above-100-percent
gsettings key is true.
Pass that information to the OSD so that the Shell can show it without
any UI change:
The > 100% volume values are scaled to fit into the 100% fill bar.
Depends on the required gsettings-desktop-schemas version.

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

Port the test suite to python 3.

Fixes #65

Reset the idle time and wait for lid inhibition to be removed.

This should make the test more reliable avoiding some potential race
conditions.

This drops Rui and Oliver from the maintainer list and adds Carlos and
Benjamin.

notify_notification_close() expects that a parameter will be available for
the error location, which could be a dangling pointer in a register or
on the stack in the case of some architectures.

This was caught by GNOME/glib#1425 which allows us to check proper type
parameters.

Remove the duplicate list of system file system types from g-s-d in
favour of the one in GLib, as long as we depend on a suitable GLib
version (2.56.0). In time, this conditional check can be dropped.

GLib doesn’t list network file systems in its list, so check those
separately.

Signed-off-by: Philip Withnall <withnall@endlessm.com>