Bug 491999

Summary: ibus candidate selection up/down arrow keys broken in xchat
Product: [Fedora] Fedora Reporter: Warren Togami <wtogami>
Component: ibusAssignee: Peng Huang <phuang>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: caillon, fedora, i18n-bugs, kevin, petersen, phuang
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-04-01 14:12:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 481098    

Description Warren Togami 2009-03-24 21:59:35 UTC

ibus during candidate selection, the up/down arrow keys are broken in xchat.  SCIM is fine.

Comment 1 Peng Huang 2009-03-28 02:57:14 UTC
This problem is because xchat filters those key events, and ibus can not receive them. It is better to let xchat does not filter those key events when im is active (The pre-edit text is visible).

Comment 2 Warren Togami 2009-03-28 07:03:08 UTC
How is this not an issue for SCIM, IIIMF and XIM?

Comment 3 Peng Huang 2009-03-28 23:34:46 UTC
For IIIMF & XIM, I am not very sure. Properly, Key events will be sent to XIM server before delivering to GDK library.

But for SCIM, I know the detail. SCIM registers a gtk keyboard snooper to get all key events  before events are delivered to widgets. I think it is not a right way. It does not follow gtk im context design. It is just an workaround for those applications.

I think the better solution is fixing it in application, or consider changing the gtk im context's design.

Comment 4 Kevin Kofler 2009-03-28 23:48:25 UTC
It is an issue for IIIMF, we used to have a patch for that, but it broke XIM. See bug 295331.

As far as I know, the current code works fine for XIM and SCIM.

Comment 5 Peng Huang 2009-03-29 06:02:54 UTC
Yeah. It is because SCIM has a workaround for this problem. But it does not follow gtk im context design. I just went through xchat source code. I did not find easy way to know if im context is active. So I fixed it in ibus im module.

But I will file a new bug on gtk upstream. Maybe they will change design of gtk im context.

Comment 6 Warren Togami 2009-03-29 06:06:29 UTC
Do not close as RAWHIDE if the bug is not actually fixed.  Keeping it open for now.