Comment #20 on issue 1760 by [email protected]: CRITICAL **: xim_open:
assertion 'conn == NULL' failed
https://code.google.com/p/ibus/issues/detail?id=1760
My reading of
http://www.x.org/releases/X11R7.7/doc/xproto/x11protocol.html#requests:ChangeWindowAttributes
is that this is documented and explicitly allowed:
"Multiple clients can select input on the same window; their event-masks
are disjoint. When an event is generated, it will be reported to all
interested clients."
When you get an initial XIM_CONNECT message, you can send a
ChangeWindowAttributes for the sending window, requesting StructureNotify,
and you will get a DestroyWindow message when the client disconnects from
the X11 server.
You'll also start getting a few other messages, which can be ignored. The
important thing is that you no longer rely on the client to notify you when
it wishes to disconnect. If the client is killed, the X11 server will
notify you.
--
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.
