Comment 1 for bug 375169
Revision history for this message
| Scott James Remnant (Canonical) (canonical-scott) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
This is caused by a bug in the D-Bus timeout patches.
The HAL author was involved in the original discussions about those, so had pre-empted the use of INT_MAX in pending call timeout arguments - thus HAL was using code that had never been tested, since a version of D-Bus that supported INT_MAX to mean "no timeout" had not yet been written.
The first of the patches uploaded was the wrong one that had missing code; this has been rectified