[PATCH upower] Fix the LatencyChanged signal

Sascha Silbe silbe at activitycentral.com
Tue May 22 07:44:06 PDT 2012


The type of the 'value' parameter of the LatencyChanged signal is
integer, not boolean. Fixing this causes the signal to actually be
emitted.
---
 Fixes https://bugs.freedesktop.org/show_bug.cgi?id=50211

 src/up-qos.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/up-qos.c b/src/up-qos.c
index 43b8eb5..9484931 100644
--- a/src/up-qos.c
+++ b/src/up-qos.c
@@ -534,7 +534,7 @@ up_qos_class_init (UpQosClass *klass)
 			      G_TYPE_FROM_CLASS (object_class), G_SIGNAL_RUN_LAST,
 			      G_STRUCT_OFFSET (UpQosClass, latency_changed),
 			      NULL, NULL, up_marshal_VOID__STRING_INT,
-			      G_TYPE_NONE, 2, G_TYPE_STRING, G_TYPE_BOOLEAN);
+			      G_TYPE_NONE, 2, G_TYPE_STRING, G_TYPE_INT);
 	signals [REQUESTS_CHANGED] =
 		g_signal_new ("requests-changed",
 			      G_TYPE_FROM_CLASS (object_class), G_SIGNAL_RUN_LAST,
-- 
1.7.10



More information about the devkit-devel mailing list