Comment #4 on issue 1760 by [email protected]: CRITICAL **: xim_open:
assertion 'conn == NULL' failed
https://code.google.com/p/ibus/issues/detail?id=1760
The problem was that the client never receives any response to XIM_OPEN in
this situation. The client sent XIM_OPEN, and after the server hit the
assertion, the server did not send any reply message at all, not XIM_ERROR,
not anything. The client was waiting for any response from the server, and
no response was being sent.
Although there's no mention of an explicit timeout to an XIM_OPEN, in the
XIM protocol documentation, I now added a timeout to keep the client from
waiting forever, for a response; and send an XIM_DISCONNECT if the timeout
occurs. I don't know if Xlib implements a timeout for XIM_OPEN, itself.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
You received this message because you are subscribed to the Google
Groups "ibus-devel" group.
iBus project web page: http://code.google.com/p/ibus/
iBus dev group: http://groups.google.com/group/ibus-devel?hl=en
---
You received this message because you are subscribed to the Google Groups "ibus-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
