Comment #16 on issue 1760 by takao.fujiwara1: CRITICAL **: xim_open:
assertion 'conn == NULL' failed
https://code.google.com/p/ibus/issues/detail?id=1760
OK, I could reproduce your problem with your app.
Your app sends XIM_DISCONNECT without XIM_CLOSE.
Is it an application falure?
If an application implements both XIM_CLOSE and XIM_DISCONNECT and get
SEGV, probably both XIM_CLOSE and XIM_DISCONNECT is lost or XIM_DISCONECT
only is lost.
Because I think XIM_CLOSE should be sent before XIM_DISCONNECT.
ibus-x11 does not receive both XIM_CLOSE and XIM_DISCONNECT from xterm +
Xorg.
1. neither XIM_CLOSE nor XIM_DISCONNECT
2. XIM_CLOSE only
3. XIM_CLOSE and XIM_DISCONNECT
Currently I don't think your situation can happen normally.
--
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.
