Bug 466657
| Summary: | Discarding the key events and same output regardless of the key | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Akira TAGOH <tagoh> | ||||||||||
| Component: | scim | Assignee: | Peng Huang <phuang> | ||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | medium | ||||||||||||
| Version: | 10 | CC: | i18n-bugs, petersen, phuang | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | All | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2008-12-02 00:54:55 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 438944, 452849 | ||||||||||||
| Attachments: |
|
||||||||||||
Could you provide a patch to fix XIM problem? Thanks. Created attachment 320277 [details]
test code for discarding the key event issue
% gcc scim_discarding.c `pkg-config --cflags --libs gtk+-2.0 gio-2.0`
% GTK_IM_MODULE=xim XMODIFIERS=@im=SCIM ./a.out
After pressing the button, "ab" should be put on the entry. otherwise SCIM may be discarding the forward event.
Created attachment 320278 [details]
test code for output the same result regardless of the key
% gcc scim_repeat.c `pkg-config --cflags --libs gtk+-2.0 gio-2.0`
% GTK_IM_MODULE=xim XMODIFIERS=@im=SCIM ./a.out
After pressing the button, "abc" should be put to the entry box. but actual result is "aaaaaa". this testing code is sending KeyPress and KeyRelease events for "a", "b" and "c". and usually GTK+ and other toolkits doesn't take any actions for KeyRelease event. thus, this means SCIM sends back the forward event for "a" with KeyPress 6 times.
Created attachment 320407 [details]
test code for discarding the key event issue
missed one ClientMessage event
Created attachment 320412 [details]
proposed patch
Fixed in scim-1.4.7-35.fc10. Thanks. This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |
Description of problem: key input too faster and too much messes up SCIM. Version-Release number of selected component (if applicable): scim-1.4.7-34.fc10 Steps to Reproduce: 1.input something too much and too faster 2. 3. Actual results: discarding the key event or return the same key event regardless of what pressing/releasing the key. Expected results: should works expectedly. Additional info: Technically it happens when multiple XIM_FORWARD_EVENT is added to the property when the key event is delivered faster than processing it in SCIM. and when it's there more than 4 in the property, it results the same output regardless of what you are pressing/releasing the key. otherwise the key event is discarded. Why it returns the same key event when the property has something more than 4, IMdkit is getting the value from the property wrongly. a quote from man page: int XGetWindowProperty(Display *display, Window w, Atom property, long long_offset, long long_length, Bool delete, Atom reg_type, Atom *actual_type_return, int *actual_format_return, unsigned long *nitems_return, unsigned long *bytes_after_return, unsigned char **prop_return); ... long_length Specifies the length in 32-bit multiples of the data to be retrieved. and XGetWindowProperty won't delete the property value even if "delete" is True, when there are still unread data. To do the right thing, read the data with the proper length to not discard the event. and if there are still the unread data in the property, read next data with "long_offset".