Keyboard input sometimes stops working

[cjy]

After the upgrade to 7.10, sometimes keyboard input stops working in just one program.

When it happens, I can input data in a different program and copy-and-paste to the one without working input.

It begins during program execution (In other words, while using a program it just occurs; It is not in this state from the beginning of program execution)

I have SCIM installed, but am using English/Keyboard at the time this happens. While in the broken state, switching input modes to Japanese - Anthy does not fix the situation.

[cjy (chris-yokum)]

Also, keyboard keys which relate to the window manager still work. I can press Alt-F4 to close the app, Alt-Tab to switch programs. But anything within the application does not work.

[James Collier (james-collier412)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

[drdan14 (dgolden1)]

I have the same problem; I've noticed it in both Matlab and Kile on Ubuntu 7.10 while using Compiz. I don't yet know how to replicated it in Kile, but here are the steps in Matlab:

o In the command window, open a new figure by typing
>> figure [enter]
o While the figure is opening, mash on the keyboard constantly
o Matlab will stop accepting keyboard input for that session, and it will be necessary to quit and restart Matlab to restore keyboard input
o Mouse input is not affected

I've previously reported the bug in Matlab in the ubuntu support forums here: http://ubuntuforums.org/showthread.php?t=1001036.

Thanks for your help!
Dan

[drdan14 (dgolden1)]

In Kile, keyboard input can usually be restored by ALT-TABbing out and back into the program, but this fix does not work in Matlab.

[drdan14 (dgolden1)]

I'm sorry, I meant that I noticed it when upgrading to Ubuntu *8.10*, Intrepid, not 7.10 as I originally wrote.

[drdan14 (dgolden1)]

I've noticed that Kile consistently stops accepting keyboard input when information in the "Structure" pane is updated, e.g., when changing any layout of the document. Alt-TABing out and back into Kile always fixes the problem.

[Andres Mujica (andres.mujica)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in KILE.
For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https://wiki.ubuntu.com/ReportingBugs.

[Andreas Wenning (andreas-wenning)]

I've just tested with the new version of Kile in jaunty; and can't reproduce the problem of keyboard input stopping to work after updates occurs in the structure pane. This seems to be the original cause for the problem in Kile, so this is as far as i can see fixed.

[zhyznd (oiuznd)]

I don't know for sure. However, I found the default editor in scilab, which also named scipad, has the same problem like kile. They both can freeze the keyboard occasionally. I think the same problem must has the similar reason, so there must be something wrong not with kile or scipad themselves but with kio or something else.

[phsamuel (phsamuel)]

I encounter the same problem for kile, matlab, and idle (python). I'm using 9.04 AMD64 and I think the bug for idle is most repeatable. For example, in idle,

type

open('abc')

The hint will come out and afterward ('abc') is highlighted and the keyboard freezes. I have to click any other window to click back idle again to get the keyboard going.

[phsamuel (phsamuel)]

The source of the bug seems to be from scim. After uninstalling scim, the problem disappeared. But it is only a workaround. Hopefully there will be a real fix.

https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104

[J (ouyang-jie)]

uninstalling scim does not fix the problem. I have matlab R2009a and ubuntu 8.04 with visual effect enabled. The keyboard randomly quit on Matlab and cannot be recovered unless restart matlab. really annoying.

[phsamuel (phsamuel)]

J, it may be stupid for me to ask. But did you reboot after removing scim? This is one of the few times that one needs to reboot linux to get thing fixed. Maybe restarting X will work too but I never tried.

There are lots of jvm problem regarding Matlab. It may worth try changing to another jvm also

http://www.mathworks.com/support/solutions/en/data/1-1812J/index.html

Just curious, does idle have any problem in your case? Before I uninstalled scim, that bug (#12) is 100% repeatable in 9.04.

[J (ouyang-jie)]

Yes, I rebooted the box after removing scim and it didn't make difference.
The jvm problems have been there for a long time. I first noticed the
conflict between matlab/jvm and the visual effect which makes blank matlab
windows. Then I set the matlab_java to sun jre and also the awt_toolkit to
Mtoolkit. Somehow these two settings do not play together nicely. So I keep
the awt_toolkit setting which fix the blank window problem. Now the keyboard
quit sometimes on matlab and it is pretty random. BTW, this problem exists
on 9.04 too.

I did not have the idle problem or at least it was really really rare or it
does not get many chances to be idle.

On Sun, Sep 13, 2009 at 1:21 AM, phsamuel <email address hidden> wrote:

> J, it may be stupid for me to ask. But did you reboot after removing
> scim? This is one of the few times that one needs to reboot linux to get
> thing fixed. Maybe restarting X will work too but I never tried.
>
> There are lots of jvm problem regarding Matlab. It may worth try
> changing to another jvm also
>
> http://www.mathworks.com/support/solutions/en/data/1-1812J/index.html
>
> Just curious, does idle have any problem in your case? Before I
> uninstalled scim, that bug (#12) is 100% repeatable in 9.04.
>
> --
> Keyboard input sometimes stops working
> https://bugs.launchpad.net/bugs/157289
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “kile” package in Ubuntu: Confirmed
> Status in “python-defaults” package in Ubuntu: New
> Status in “scilab” package in Ubuntu: Confirmed
> Status in “scim” package in Ubuntu: New
>
> Bug description:
> After the upgrade to 7.10, sometimes keyboard input stops working in just
> one program.
>
> When it happens, I can input data in a different program and copy-and-paste
> to the one without working input.
>
> It begins during program execution (In other words, while using a program
> it just occurs; It is not in this state from the beginning of program
> execution)
>
> I have SCIM installed, but am using English/Keyboard at the time this
> happens. While in the broken state, switching input modes to Japanese -
> Anthy does not fix the situation.
>

[J (ouyang-jie)]

phsamuel, I am sorry I misunderstood your question. I didn't use idle so I
cannot say it has the same issue or not.

On Sun, Sep 13, 2009 at 1:21 AM, phsamuel <email address hidden> wrote:

> J, it may be stupid for me to ask. But did you reboot after removing
> scim? This is one of the few times that one needs to reboot linux to get
> thing fixed. Maybe restarting X will work too but I never tried.
>
> There are lots of jvm problem regarding Matlab. It may worth try
> changing to another jvm also
>
> http://www.mathworks.com/support/solutions/en/data/1-1812J/index.html
>
> Just curious, does idle have any problem in your case? Before I
> uninstalled scim, that bug (#12) is 100% repeatable in 9.04.
>
> --
> Keyboard input sometimes stops working
> https://bugs.launchpad.net/bugs/157289
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “kile” package in Ubuntu: Confirmed
> Status in “python-defaults” package in Ubuntu: New
> Status in “scilab” package in Ubuntu: Confirmed
> Status in “scim” package in Ubuntu: New
>
> Bug description:
> After the upgrade to 7.10, sometimes keyboard input stops working in just
> one program.
>
> When it happens, I can input data in a different program and copy-and-paste
> to the one without working input.
>
> It begins during program execution (In other words, while using a program
> it just occurs; It is not in this state from the beginning of program
> execution)
>
> I have SCIM installed, but am using English/Keyboard at the time this
> happens. While in the broken state, switching input modes to Japanese -
> Anthy does not fix the situation.
>

[phsamuel (phsamuel)]

J, I'm not sure I had the same kind of bug as you do. When you open multiple figures in matlab and then close all figures using "close all", does the bug occur?

That is,

Type

>> figure; figure; figure; figure;

then type

>> close all

In my case, the bug was 100% reproducible in this situation also. That is, I could not type in anything any more in the command window until I clicked some other window first.

[J (ouyang-jie)]

No the bug did not happen.

On Sun, Sep 13, 2009 at 6:33 PM, phsamuel <email address hidden> wrote:

> J, I'm not sure I had the same kind of bug as you do. When you open
> multiple figures in matlab and then close all figures using "close all",
> does the bug occur?
>
> That is,
>
> Type
>
> >> figure; figure; figure; figure;
>
> then type
>
> >> close all
>
> In my case, the bug was 100% reproducible in this situation also. That
> is, I could not type in anything any more in the command window until I
> clicked some other window first.
>
> --
> Keyboard input sometimes stops working
> https://bugs.launchpad.net/bugs/157289
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “kile” package in Ubuntu: Confirmed
> Status in “python-defaults” package in Ubuntu: New
> Status in “scilab” package in Ubuntu: Confirmed
> Status in “scim” package in Ubuntu: New
>
> Bug description:
> After the upgrade to 7.10, sometimes keyboard input stops working in just
> one program.
>
> When it happens, I can input data in a different program and copy-and-paste
> to the one without working input.
>
> It begins during program execution (In other words, while using a program
> it just occurs; It is not in this state from the beginning of program
> execution)
>
> I have SCIM installed, but am using English/Keyboard at the time this
> happens. While in the broken state, switching input modes to Japanese -
> Anthy does not fix the situation.
>

[Rlgc79 (rlgc79)]

The bug happens on both my laptop and my desktop... Using Matlab on my laptop has become impractical.

[quote]
|>> figure; figure; figure; figure;

>then type

>>> close all

>In my case, the bug was 100% reproducible in this situation also.

[J (ouyang-jie)]

It is really disappointing. The keyboard bug happened twice last night. I am
afraid I have to dump ubuntu as my working OS.

On Fri, Sep 25, 2009 at 11:46 AM, Rlgc79 <email address hidden> wrote:

> The bug happens on both my laptop and my desktop... Using Matlab on my
> laptop has become impractical.
>
>
> [quote]
> |>> figure; figure; figure; figure;
>
> >then type
>
> >>> close all
>
> >In my case, the bug was 100% reproducible in this situation also.
>
> --
> Keyboard input sometimes stops working
> https://bugs.launchpad.net/bugs/157289
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “kile” package in Ubuntu: Confirmed
> Status in “python-defaults” package in Ubuntu: New
> Status in “scilab” package in Ubuntu: Confirmed
> Status in “scim” package in Ubuntu: New
>
> Bug description:
> After the upgrade to 7.10, sometimes keyboard input stops working in just
> one program.
>
> When it happens, I can input data in a different program and copy-and-paste
> to the one without working input.
>
> It begins during program execution (In other words, while using a program
> it just occurs; It is not in this state from the beginning of program
> execution)
>
> I have SCIM installed, but am using English/Keyboard at the time this
> happens. While in the broken state, switching input modes to Japanese -
> Anthy does not fix the situation.
>

[phsamuel (phsamuel)]

Yeah. I love ubuntu when it works: the stability and speed... but I couldn't really imagine a keyboard bug occurs so often in an OS before encountering it. The worst thing is that it is around for years and the importance is still "undecided". I guess it is still many years before Linux can really take over.

[Andreas Wenning (andreas-wenning)]

Setting back to fix released for kile. I think we can safely say, that this is not unique for kile and a lower-layer issue.

[Mander (arwintcher)]

I have just had this problem today for the first time. Using Kile 2.0.84 on Ubuntu 9.04, 64 bit. I am using an external keyboard with a laptop but they are both standard English language keyboards. I tried alt-tab and restarting kile but no effect. Suddenly the only key that works in Kile is space bar.

[Luke Chou (xsnipersgox)]

It is freezing too in Quanta and other apps, try these fixes:

https://bugs.launchpad.net/ubuntu/+source/scim/+bug/293001
https://bugs.launchpad.net/ubuntu/+source/scim/+bug/163325

[vahagn (vahag-1985)]

I can confirm this problem. It also appears after monitor is putted to sleep and then turning it on.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Rolf Leggewie (r0lf)]

does this ever occur in trusty or later?

There's also been some further upstream work on bugs like this lately. If you are still affected I'd love to hear if the latest upstream can fix this issue.

[Rolf Leggewie (r0lf)]

https://launchpad.net/~r0lf/+archive/ubuntu/stable/+packages

[Launchpad Janitor (janitor)]

This bug was fixed in the package scim - 1.4.17-1

---------------
scim (1.4.17-1) unstable; urgency=medium

  [ Tz-Huan Huang ]
  * new upstream release 1.4.17
    - fixes "scim breaks compose key". Closes: #618763, LP: #610979.
    - fixes "Backspace and delete keys dysfunctional in gedit".
      Closes: #747154, LP: #1315579, LP: #343708, LP: #157289.
    - fixes "problem in 'quick find/search' of generic file manager".
      Closes: #821869, LP: #287719.
  * drop two patches that were upstreamed

  [ Rolf Leggewie ]
  * control: switch homepage for scim from sf.net to github

 -- Rolf Leggewie <email address hidden> Tue, 31 May 2016 15:15:06 +0800