Comment #2 on issue 1760 by [email protected]: CRITICAL **: xim_open:
assertion 'conn == NULL' failed
https://code.google.com/p/ibus/issues/detail?id=1760
Actually ibus was getting an XIM_DISCONNECT, but not an XIM_CLOSE. The
connection code was recycling a connection object, and it's connect_id.
However since xim_close was not getting called, in this situation, a
subsequent connection was being opened with the same connect_id, resulting
in this assertion failure.
Even if XIM_DISCONNECT was not getting received, I would think that it
should be possible to select StructureNotify on the client's communication
window, and receive a DestroyWindow when the client's window gets
destroyed, making it possible to clean everything up in case the client
gets SIGKILLed.
--
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.
