This bug was fixed in the package mir - 0.1.0+14.04.20131030-0ubuntu1
---------------
mir (0.1.0+14.04.20131030-0ubuntu1) trusty; urgency=low
[ Ubuntu daily release ]
* New rebuild forced
[ Alan Griffiths ]
* client: Remove the timeout for detecting server crashes There are
valid cases when the server blocks for an indeterminate amount of
time during a client request, like when a next_buffer request blocks
because a surface is not visible or the server is paused. In such
cases, the timeout mechanism we used to detect server crashes caused
the clients to fail. Furthermore, the clients seem able to detect
server crashes without the timeout, rendering it needless anyway.
(LP: #1245958)
This bug was fixed in the package mir - 0.1.0+14. 04.20131030- 0ubuntu1
--------------- 14.04.20131030- 0ubuntu1) trusty; urgency=low
mir (0.1.0+
[ Ubuntu daily release ]
* New rebuild forced
[ Alan Griffiths ]
* client: Remove the timeout for detecting server crashes There are
valid cases when the server blocks for an indeterminate amount of
time during a client request, like when a next_buffer request blocks
because a surface is not visible or the server is paused. In such
cases, the timeout mechanism we used to detect server crashes caused
the clients to fail. Furthermore, the clients seem able to detect
server crashes without the timeout, rendering it needless anyway.
(LP: #1245958)
[ Ubuntu daily release ]
* Automatic snapshot from revision 1163
-- Ubuntu daily release <email address hidden> Wed, 30 Oct 2013 18:37:21 +0000