Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ibus-skk conflicts with Key Repeat feature #64

Open
yunazuno opened this issue Jun 23, 2018 · 2 comments
Open

ibus-skk conflicts with Key Repeat feature #64

yunazuno opened this issue Jun 23, 2018 · 2 comments

Comments

@yunazuno
Copy link

Environment

  • Fedora 28
  • ibus-skk-1.4.3-2.fc28.x86_64
  • libskk-1.0.3-2.fc28.x86_64
  • ibus-1.5.18-5.fc28.x86_64

Steps to reproduce

  1. Enable Key Repeat feature through gsettings set org.gnome.desktop.peripherals.keyboard repeat true or gnome-control-center > Universal Access > Typing > Repeat Keys
  2. Open an application (gedit for example)
  3. Switch IME to ibus-skk
  4. Press [Enter] key inside text area then release the key immediately

Expected Result

The application inserts a line break

Actual Result

The application continues to insert line breaks forever

Notes

I've experienced the same unexpected behaviour with other special keys such as [Backspace] and [Page Up]. For instance, [BackSpace] removes entire characters behind a cursor despite I released the key immediately. Note that I don't see the problem with other IME such as ibus-kkc-1.5.22-9.fc28.x86_64 and ibus-mozc-2.23.2815.102-1.fc28.x86_64.

The problem is resolved after I applied ueno/libskk#52, I'm not sure a root cause though.

@ueno
Copy link
Owner

ueno commented Jun 25, 2018

Thank you for looking into it. It sounds like key repeat is handled too late by mutter (previously, it synthesized repeated key events before calling IM, but it now seems to do that afterwards. @garnacho, do yo have any ideas?).

In any case, the fix in libskk should help, so I will make a release shortly.

@lissyx
Copy link

lissyx commented Nov 29, 2022

Thank you for looking into it. It sounds like key repeat is handled too late by mutter (previously, it synthesized repeated key events before calling IM, but it now seems to do that afterwards. @garnacho, do yo have any ideas?).

In any case, the fix in libskk should help, so I will make a release shortly.

Did it ever shipped ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants