https://bugzilla.redhat.com/show_bug.cgi?id=1671286
Bug ID: 1671286 Summary: Input does not work some time later in ibus-1.5.19-13.fc29. Product: Fedora Version: 29 Hardware: x86_64 OS: Linux Status: NEW Component: ibus Severity: high Assignee: tfujiwar@redhat.com Reporter: sangu.fedora@gmail.com QA Contact: extras-qa@fedoraproject.org CC: i18n-bugs@lists.fedoraproject.org, shawn.p.huang@gmail.com, tfujiwar@redhat.com Target Milestone: --- Classification: Fedora
Description of problem: Input does not work some time later in ibus-1.5.19-13.fc29.
$journalctl --user -n 30 -f [...] 1월 31 10:49:52 localhost.localdomain org.gnome.Shell.desktop[1613]: The XKEYBOARD keymap compiler (xkbcomp) reports: 1월 31 10:49:52 localhost.localdomain org.gnome.Shell.desktop[1613]: > Warning: Unsupported maximum keycode 374, clipping. 1월 31 10:49:52 localhost.localdomain org.gnome.Shell.desktop[1613]: > X11 cannot support keycodes above 255. 1월 31 10:49:52 localhost.localdomain org.gnome.Shell.desktop[1613]: > Warning: Unsupported high keycode 372 for name <I372> ignored 1월 31 10:49:52 localhost.localdomain org.gnome.Shell.desktop[1613]: > X11 cannot support keycodes above 255. 1월 31 10:49:52 localhost.localdomain org.gnome.Shell.desktop[1613]: > This warning only shows for the first high keycode. 1월 31 10:49:52 localhost.localdomain org.gnome.Shell.desktop[1613]: Errors from xkbcomp are not fatal to the X server 1월 31 10:50:10 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:11 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:11 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:12 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:12 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:12 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:12 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:12 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:12 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:12 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:12 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:12 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:13 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:13 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:13 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:13 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:13 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:13 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:13 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:14 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:14 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:14 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:15 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:15 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:15 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:16 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:16 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 1월 31 10:50:16 localhost.localdomain gnome-shell[1613]: Error processing key on IM: 시간 제한을 넘었습니다 [...]
Version-Release number of selected component (if applicable): 1.5.19-13.fc29
How reproducible: After updating to ibus-1.5.19-13.fc29, always
Steps to Reproduce: 1. 2. 3.
Actual results:
Expected results:
Additional info:
gnome-shell-3.30.2-1.fc29.x86_64 gtk2-2.24.32-4.fc29.x86_64 gtk3-3.24.1-1.fc29.x86_64 ibus-hangul-1.5.1-2.fc29.x86_64
https://bugzilla.redhat.com/show_bug.cgi?id=1671286
--- Comment #1 from fujiwara tfujiwar@redhat.com --- Thank you for the report. BTW, 1.5.19-13 is not on stable yet. https://bodhi.fedoraproject.org/updates/FEDORA-2019-3aa0fbffb4
It would be great if you could provide the reproducing steps. I'm try to reproduce this.
https://bugzilla.redhat.com/show_bug.cgi?id=1671286
Yanko Kaneti yaneti@declera.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |yaneti@declera.com
--- Comment #2 from Yanko Kaneti yaneti@declera.com --- I don't know if its the same thing but recently on rawhide at random points the shell stops accepting keyboard input. The log says something like ... Jan 31 10:29:01 gnome-shell[10841]: Error processing key on IM: Timeout was reached ... and input doesn't work until I switch to a vt and killall ibus-daemon, which fixes it until the next time it happens.
https://bugzilla.redhat.com/show_bug.cgi?id=1671286
Kenneth Topp ken@bllue.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ken@bllue.org
--- Comment #3 from Kenneth Topp ken@bllue.org --- keyboard input has stopped for me me as well, and the issue went away when I downgraded from ibus 1.5.19-12.fc29 to 1.5.19-11.fc29. I'm US keyboard and I don't think I've ever configured any ibus settings. My distro has been installed a long time ago and upgraded to fedora 29.
one thing I can say is that some keyboard controls work: (e.g. Alt-F2 to bring up the gnome-shell run command window).
I don't notice any particular messages in journald at the time.
https://bugzilla.redhat.com/show_bug.cgi?id=1671286
--- Comment #4 from fujiwara tfujiwar@redhat.com --- (In reply to Kenneth Topp from comment #3)
keyboard input has stopped for me me as well, and the issue went away when I downgraded from ibus 1.5.19-12.fc29 to 1.5.19-11.fc29. I'm US keyboard and I don't think I've ever configured any ibus settings.
I guess you downgraded ibus 1.5.19-13.fc29 to 1.5.19-11.fc29 but not ibus 1.5.19-12.fc29.
I still cannot reproduce the problem.
https://bugzilla.redhat.com/show_bug.cgi?id=1671286
Alexander Lindqvist alexander@bitspace.se changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alexander@bitspace.se
--- Comment #5 from Alexander Lindqvist alexander@bitspace.se --- I also have this when it just stops accepting input while typing and just repeats last entered character like it is pressed . Reboot solves it.
$ rpm -q ibus ibus-1.5.19-13.fc29.x86_64
I also upgraded the Kernel at the same time as ibus to kernel-4.20.5-200.fc29.x86_64 (from testing)
I have yet to replicate the problem on kernel-4.20.4-200.fc29.x86_64
https://bugzilla.redhat.com/show_bug.cgi?id=1671286
James Begley bugs@jmbegley.org.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bugs@jmbegley.org.uk
--- Comment #6 from James Begley bugs@jmbegley.org.uk --- I've also run into this problem - the keyboard randomly stops responding to characters and is fixed by a reboot. Special keys (such as volume up/down) continue to work even when the keyboard appears to be unresponsive. I've downgraded from -13 to -12 and have yet to replicate the problem with the following installed:
ibus-gtk2-1.5.19-12.fc29.x86_64 ibus-setup-1.5.19-12.fc29.noarch ibus-1.5.19-12.fc29.x86_64 ibus-wayland-1.5.19-12.fc29.x86_64 ibus-libs-1.5.19-12.fc29.x86_64 ibus-gtk3-1.5.19-12.fc29.x86_64
Changing the kernel version didnt make any difference (tested with 4.20.6-200 or 4.20.5-200, although I didnt go back to kernel 4.20.4-200).
https://bugzilla.redhat.com/show_bug.cgi?id=1671286
James Ralston ralston@pobox.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ralston@pobox.com
--- Comment #7 from James Ralston ralston@pobox.com --- I'm seeing this problem as well, under the MATE desktop.
Some seemingly-random amount of time after logging in, most windows stop accepting input.
Unfortunately, I don't know how to reproduce the issue reliably or consistently. I can't find any consistent trigger for the problem. Sometimes it happens while I'm typing; sometimes it happens when I'm not typing.
Downgrading the ibus packages back to 1.5.19-12.fc29 avoids the issue.
https://bugzilla.redhat.com/show_bug.cgi?id=1671286
fujiwara tfujiwar@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cra@wpi.edu
--- Comment #8 from fujiwara tfujiwar@redhat.com --- *** Bug 1671774 has been marked as a duplicate of this bug. ***
https://bugzilla.redhat.com/show_bug.cgi?id=1671286
fujiwara tfujiwar@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED
--- Comment #9 from fujiwara tfujiwar@redhat.com --- Thank you all. Probably I can reproduce this issue now in a standalone machine but I could not in a VirtualBox VM. Maybe pressing Shift key is needed. Seems still mutex is conflict.
https://bugzilla.redhat.com/show_bug.cgi?id=1671286
--- Comment #10 from Alexander Lindqvist alexander@bitspace.se --- Problem exists on kernel-4.20.4-200.fc29.x86_64 also but took far longer to manifest. Downgrade to 1.5.19-12.fc29 solves it.
https://bugzilla.redhat.com/show_bug.cgi?id=1671286
--- Comment #11 from Kenneth Topp ken@bllue.org ---
(In reply to fujiwara from comment #4)
(In reply to Kenneth Topp from comment #3)
keyboard input has stopped for me me as well, and the issue went away when I downgraded from ibus 1.5.19-12.fc29 to 1.5.19-11.fc29. I'm US keyboard and I don't think I've ever configured any ibus settings.
I guess you downgraded ibus 1.5.19-13.fc29 to 1.5.19-11.fc29 but not ibus 1.5.19-12.fc29.
I still cannot reproduce the problem.
Yes, I did have -13 installed.
Something I just thought of is that I have two usb keyboards and a bluetooth keyboard attached. It seems -13 was removed from the f29 yum channels. I can attempt to reproduce without the extra keyboards and see if that has something to do with the issue.
Ken
https://bugzilla.redhat.com/show_bug.cgi?id=1671286
--- Comment #12 from Alexander Lindqvist alexander@bitspace.se --- when using -13 I got the stuck key or unresponsive keyboard within a few seconds of typing on both the builtin keyboard on the laptop and the external HP USB keyboard (when docked). Im now running ibus-1.5.19-12.fc29.x86_64.
https://bugzilla.redhat.com/show_bug.cgi?id=1671286
--- Comment #13 from Alexander Lindqvist alexander@bitspace.se --- (In reply to Alexander Lindqvist from comment #12)
when using -13 I got the stuck key or unresponsive keyboard within a few seconds of typing on both the builtin keyboard on the laptop and the external HP USB keyboard (when docked). Im now running ibus-1.5.19-12.fc29.x86_64.
Laptop is HP Elitebook 745 G5
https://bugzilla.redhat.com/show_bug.cgi?id=1671286
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |MODIFIED
--- Comment #14 from Fedora Update System updates@fedoraproject.org --- ibus-1.5.19-16.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-3aa0fbffb4
https://bugzilla.redhat.com/show_bug.cgi?id=1671286
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|MODIFIED |ON_QA
--- Comment #15 from Fedora Update System updates@fedoraproject.org --- ibus-1.5.19-16.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-3aa0fbffb4
https://bugzilla.redhat.com/show_bug.cgi?id=1671286
fujiwara tfujiwar@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jsolomon@redhat.com
--- Comment #16 from fujiwara tfujiwar@redhat.com --- *** Bug 1673714 has been marked as a duplicate of this bug. ***
https://bugzilla.redhat.com/show_bug.cgi?id=1671286
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |CLOSED Fixed In Version| |ibus-1.5.19-16.fc29 Resolution|--- |ERRATA Last Closed| |2019-02-14 01:58:00
--- Comment #17 from Fedora Update System updates@fedoraproject.org --- ibus-1.5.19-16.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.
https://bugzilla.redhat.com/show_bug.cgi?id=1671286
Antoine Patte antoinep@toine.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |antoinep@toine.be
--- Comment #18 from Antoine Patte antoinep@toine.be --- Same error on my laptop (Lenovo X270) with Fedora 29 (upgraded from Fedora 28). I have the impression that this issue occurs only with the "internal" keyboard and not an usb keybord.
May 19 15:00:42 lp-20173009 journal[8464]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation May 19 15:00:42 lp-20173009 org.gnome.Shell.desktop[8464]: The XKEYBOARD keymap compiler (xkbcomp) reports: May 19 15:00:42 lp-20173009 org.gnome.Shell.desktop[8464]: > Warning: Unsupported maximum keycode 374, clipping. May 19 15:00:42 lp-20173009 org.gnome.Shell.desktop[8464]: > X11 cannot support keycodes above 255. May 19 15:00:42 lp-20173009 org.gnome.Shell.desktop[8464]: > Warning: Unsupported high keycode 372 for name <I372> ignored May 19 15:00:42 lp-20173009 org.gnome.Shell.desktop[8464]: > X11 cannot support keycodes above 255. May 19 15:00:42 lp-20173009 org.gnome.Shell.desktop[8464]: > This warning only shows for the first high keycode. May 19 15:00:42 lp-20173009 org.gnome.Shell.desktop[8464]: Errors from xkbcomp are not fatal to the X server
[patta@lp-20173009 ~]$ rpm -aq | grep ibus ibus-m17n-1.4.1-1.fc29.x86_64 ibus-cangjie-2.4-13.fc29.noarch ibus-rawcode-1.3.2-13.fc29.x86_64 libusbx-1.0.22-1.fc29.x86_64 ibus-gtk3-1.5.19-16.fc29.x86_64 ibus-libzhuyin-1.9.0-1.fc29.x86_64 ibus-libpinyin-1.11.0-1.fc29.x86_64 ibus-libs-1.5.19-16.fc29.x86_64 libusbx-1.0.22-1.fc29.i686 ibus-setup-1.5.19-16.fc29.noarch ibus-cangjie-engine-cangjie-2.4-13.fc29.noarch ibus-kkc-1.5.22-10.fc29.x86_64 python2-libuser-0.62-18.fc29.x86_64 libuser-0.62-18.fc29.x86_64 ibus-typing-booster-2.6.0-1.fc29.noarch ibus-gtk2-1.5.19-16.fc29.x86_64 ibus-qt-1.3.3-20.fc29.x86_64 libusb-0.1.5-13.fc29.x86_64 ibus-hangul-1.5.1-2.fc29.x86_64 ibus-1.5.19-16.fc29.x86_64 libusal-1.1.11-40.fc29.x86_64 libusbmuxd-1.0.10-10.fc29.x86_64
https://bugzilla.redhat.com/show_bug.cgi?id=1671286
--- Comment #19 from fujiwara tfujiwar@redhat.com --- @antoinep I think your issue is not this bug.
i18n-bugs@lists.fedoraproject.org