Hide Forgot
Any evaluation of this patch? Since the ibus patches are big, I don't think the internal patches for RHEL6 only but also both libx11 and ibus needs to be fixed in upstream. Shall I file the patch in libx11 upstream?
Red Hat Enterprise Linux 6 transitioned to the Production 3 Phase on May 10, 2017. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle This issue does not appear to meet the inclusion criteria for the Production Phase 3 and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: https://access.redhat.com
I investigated another way yesterday. A User runs xwininfo for a window in the second screen, write a special tag with window ID in .Xresoure by manual, and runs xrdb -merge .Xresource. But seems the resource values are not updated until XtDestroyApplicationContext() is called. XtDestroyApplicationContext() calls XDisplayClose() and it means ibus-daemon needs to be restarted. So probably this workaround is not useful. Currently I think it's the only solution to modify XIM data to append the screen ID with my attached patch.
Today I got a chance to chat with X team and got a hint of Screen of Window from focus-in event. Let me create a debug package later.
I had a chance to chat with Peter Hutterer and he gave me to get the screen number. I no longer need to modify libx11.
Please do not comment on this bug which is closed.