Bug 50211 - doesn't emit LatencyChanged signal
Summary: doesn't emit LatencyChanged signal
Status: RESOLVED FIXED
Alias: None
Product: upower
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: All All
: medium normal
Assignee: Richard Hughes
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-22 06:08 UTC by Sascha Silbe
Modified: 2012-05-22 10:53 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Fix the LatencyChanged signal (1015 bytes, patch)
2012-05-22 07:35 UTC, Sascha Silbe 		Details | Splinter Review
View All

Description Sascha Silbe 2012-05-22 06:08:44 UTC 
When calling RequestLatency() (interface org.freedesktop.UPower.QoS), the LatencyChanged signal doesn't get emitted. strace'ing upowerd revealed the following error messages:

** (upowerd:24916): CRITICAL **: marshal_basic: assertion `b == TRUE || b == FALSE' failed

** (upowerd:24916): WARNING **: failed to marshal parameter 2 for signal LatencyChanged
Comment 1 Sascha Silbe 2012-05-22 07:35:57 UTC 
Created attachment 61961 [details] [review]
Fix the LatencyChanged signal

The type of the 'value' parameter of the LatencyChanged signal is
integer, not boolean. Fixing this causes the signal to actually be
emitted.
Comment 2 Richard Hughes 2012-05-22 10:53:17 UTC 
Pushed to master, many thanks!

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.