summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPhilip Withnall <withnall@endlessm.com>2017-02-09 14:25:50 +0000
committerBastien Nocera <hadess@hadess.net>2017-02-14 19:03:41 +0100
commit0da930316569c77ce6a6dbcb5f236ebee1fb0738 (patch)
treec2e477b08c433d1956345e4362943b84d83c3869
parentaa92455b1c7b2b17a4d4617fab944d46748c7c2f (diff)
downloadgnome-settings-daemon-0da930316569c77ce6a6dbcb5f236ebee1fb0738.tar.gz
rfkill: Add a comment with basic testing instructions
As much as I would love to, I don’t have time to write a unit testing harness which mocks up a slow rfkill FD. So this will have to do. Suggestion: run it in a tight loop, alternating between enabled and disabled. See what breaks. https://bugzilla.gnome.org/show_bug.cgi?id=778383
-rw-r--r--plugins/rfkill/gsd-rfkill-manager.c20
1 files changed, 20 insertions, 0 deletions
diff --git a/plugins/rfkill/gsd-rfkill-manager.c b/plugins/rfkill/gsd-rfkill-manager.c
index 5470ce75..6e6e130c 100644
--- a/plugins/rfkill/gsd-rfkill-manager.c
+++ b/plugins/rfkill/gsd-rfkill-manager.c
@@ -20,6 +20,26 @@
*
*/
+/* Test with:
+ * gdbus call \
+ * --session \
+ * --dest org.gnome.SettingsDaemon.Rfkill \
+ * --object-path /org/gnome/SettingsDaemon/Rfkill \
+ * --method org.freedesktop.DBus.Properties.Set \
+ * "org.gnome.SettingsDaemon.Rfkill" \
+ * "AirplaneMode" \
+ * "<true|false>"
+ * and
+ * gdbus call \
+ * --session \
+ * --dest org.gnome.SettingsDaemon.Rfkill \
+ * --object-path /org/gnome/SettingsDaemon/Rfkill \
+ * --method org.freedesktop.DBus.Properties.Set \
+ * "org.gnome.SettingsDaemon.Rfkill" \
+ * "BluetoothAirplaneMode" \
+ * "<true|false>"
+ */
+
#include "config.h"
#include <gio/gio.h>