RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1403077 - Input method offered by ibus does not move to the second window in ZaphodHeads environment
Summary: Input method offered by ibus does not move to the second window in ZaphodHead...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ibus
Version: 6.8
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: rc
: 6.9
Assignee: fujiwara
QA Contact: QE Internationalization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1374441 1461138 1510263 1549171
TreeView+ depends on / blocked
 
Reported: 2016-12-09 01:54 UTC by ptoshniw
Modified: 2020-12-14 07:55 UTC (History)
11 users (show)

Fixed In Version: ibus-1.3.4-10.el6
Doc Type: Bug Fix
Doc Text:
In this release, IBus supports multiple screens in Zaphod mode.
Clone Of:
: 1420662 1549171 (view as bug list)
Environment:
Last Closed: 2018-06-19 05:23:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
setup_ibus.xml (17.50 KB, text/plain)
2016-12-09 01:54 UTC, ptoshniw 		no flags Details
ibus-zaphodheads.log attached (12.72 KB, text/plain)
2016-12-12 05:40 UTC, ptoshniw 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1919 0 None None None 2018-06-19 05:23:19 UTC

Description ptoshniw 2016-12-09 01:54:29 UTC 
Created attachment 1229753 [details]
setup_ibus.xml

Description of problem:
When you use ibus after pressing <ctrl> + <space> user can use Chinese input on screen1 however when he do it on screen2 <ctrl> + <space> does not bring up there the ibus window and user cannot use Chinese input even the ibus cannot cannot be moved to screen2 from screen1

Version-Release number of selected component (if applicable):h
ibus-1.3.4-9.el6.x86_64

How reproducible:
Always

Executed below commands

# ibus-daemon -d –x

Create a file under user home directory as 

# cat /home/user/.i18n

LC_CTYPE="zh_CN.UTF-8"
GTK_IM_MODULE=ibus
QT_IM_MODULE=ibus
XMODIFIERS=@im=ibus


# gconftool-2 --load  setup_ibus.xml

[1] Opened a terminal on screen1 hit [ctrl+space] when I type I can see Chinese font and the rectangular window for input.

[2] Opened another terminal on screen2 moved the mouse to screen2 and started typing, still see Chinese font but does not see the rectangular window on screen two. it remains on screen 1 itself.

Actual results:
The rectangular input window remains on the screen 1.

Expected results:
The rectangular input window should move accordingly on which we are working and entering the chinese characters..

Additional info:
It is happening in the zaphod environment.
Comment 6 ptoshniw 2016-12-12 05:40:05 UTC 
Created attachment 1230691 [details]
ibus-zaphodheads.log attached
Comment 12 fujiwara 2016-12-13 06:41:27 UTC 
Thank you for the testing.
Seems opening GdkDisplay for the second screen is no problem but gtk.gdk.Display is failed for the second screen.
I may mistake the python format.
Let me rewrite the test program with C lang.
Comment 21 fujiwara 2016-12-15 07:56:37 UTC 
(In reply to ptoshniw from comment #20)

Great. thank you for all of your testings.
Now all the debuggings are done at the moment and I understood how ibus can launch the lookup table on the second screen.

Let me create a tentative fix for this bug for one week or next year.
Comment 24 fujiwara 2016-12-23 02:56:50 UTC 
This patch supports GTK2 applications only. I cannot find the client Display variable in XIM protocol.
Comment 76 Chris Williams 2017-06-13 18:12:23 UTC 
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
Comment 88 Jens Petersen 2017-06-26 08:07:56 UTC 
Could you attach the patch?
I think it is good to have more eyes on it.
Comment 89 fujiwara 2017-06-26 10:18:02 UTC 
The current patch is:
https://github.com/fujiwarat/ibus/commits/1.3.y-rhel6
Comment 125 errata-xmlrpc 2018-06-19 05:23:07 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:1919
Note You need to log in before you can comment on or make changes to this bug.