Comment #5 on issue 1760 by takao.fujiwara1: CRITICAL **: xim_open:
assertion 'conn == NULL' failed
https://code.google.com/p/ibus/issues/detail?id=1760
Now ibus-x11 releases connect_id in both XIM_CLOSE and XIM_DISCONNECT:
https://github.com/ibus/ibus/commit/991eebc31aa605fbce03edda6eaecfd06c2fcb1b
It would be great if your problem could be fixed in ibus-x11 since the
server side is complicated.
I guess you mean to send XIM_ERROR with _Xi18nSendMessage() in
OpenMessageProc() but I'm not sure if the XIMS and connect_id are valid and
feel a little risky.
I'd like to suggest to fix the issues in your application since I cannot
reproduce your problem and none report the same issue.
--
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.
