[Fedora-i18n-bugs] [Bug 1673714] New: sudden loss of input in gnome-shell

https://bugzilla.redhat.com/show_bug.cgi?id=1673714

            Bug ID: 1673714
           Summary: sudden loss of input in gnome-shell
           Product: Fedora
           Version: 29
            Status: NEW
         Component: ibus
          Assignee: tfujiwar(a)redhat.com
          Reporter: jsolomon(a)redhat.com
        QA Contact: extras-qa(a)fedoraproject.org
                CC: i18n-bugs(a)lists.fedoraproject.org,
                    shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
  Target Milestone: ---
    Classification: Fedora



Description of problem:

gnome-terminal and activities overlay stop receiving any input from the
keyboard, except for some strange exceptions. the super key still opens/closes
activities, and I was able to input text into nautilus search and firefox, but
any newly opened gnome-terminal, gedit or vte instance also stopped receiving
input. xterm still accepts input, however.

Version-Release number of selected component (if applicable):


How reproducible:

Sometimes

Steps to Reproduce:

Uncertain of exact steps, but halfline and I determined that it is an ibus
issue and probably has to do with stalls in a compositor.

Actual results:

various gnome-shell applications no longer receive keyboard input

Expected results:

able to use keyboard to input into terminal/gnome-shell search

Additional info:

Lenovo ThinkPad T480s
Fedora 29
kernel version 4.20.4-200.fc29.x86_64
ibus-1.5.19-13.fc29.x86_64

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Fedora-i18n-bugs] [Bug 1673714] sudden loss of input in gnome-shell

https://bugzilla.redhat.com/show_bug.cgi?id=1673714

fujiwara <tfujiwar(a)redhat.com&gt; changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
         Resolution|---                         |DUPLICATE
        Last Closed|                            |2019-02-08 03:43:16



--- Comment #1 from fujiwara <tfujiwar(a)redhat.com&gt; ---
Sorry for the trouble. It was hard to reproduce the issue but I think it's now
fixed.

*** This bug has been marked as a duplicate of bug 1671286 ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.