[gnome-settings-daemon/benzea/misc-fixes: 171/172] rfkill: Allow more time for bluetooth devices to initialize
- From: Benjamin Berg <bberg src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-settings-daemon/benzea/misc-fixes: 171/172] rfkill: Allow more time for bluetooth devices to initialize
- Date: Tue, 16 Apr 2019 08:50:04 +0000 (UTC)
commit 2d088405d99741e30952451cf2b9ff75283a5bdd
Author: Benjamin Berg <bberg redhat com>
Date: Tue May 16 15:35:44 2017 +0200
rfkill: Allow more time for bluetooth devices to initialize
In some corner cases systemd-rfkill may immediately turn of a bluetooth
device that is being added (due to a platform rfkill being unblocked).
Unfortunately the timeout of 500ms is not sufficient of some machines so
increase it to 1s. An example of such a case:
1494941564.350097: idx 0 type 2 op 2 soft 0 hard 0
1494941564.830240: idx 15 type 2 op 0 soft 0 hard 0
1494941564.879854: idx 15 type 2 op 2 soft 1 hard 0
Which is almost 530ms between the platform device being unblocked and
systemd-rfkill blocking the newly appeared rfkill switch.
https://bugzilla.gnome.org/show_bug.cgi?id=782532
plugins/rfkill/rfkill-glib.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
---
diff --git a/plugins/rfkill/rfkill-glib.c b/plugins/rfkill/rfkill-glib.c
index 0dc26f92..d00eed2f 100644
--- a/plugins/rfkill/rfkill-glib.c
+++ b/plugins/rfkill/rfkill-glib.c
@@ -74,7 +74,7 @@ struct _CcRfkillGlib {
G_DEFINE_TYPE (CcRfkillGlib, cc_rfkill_glib, G_TYPE_OBJECT)
-#define CHANGE_ALL_TIMEOUT 500
+#define CHANGE_ALL_TIMEOUT 1000
static const char *type_to_string (unsigned int type);
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]