I can confirm this for sun java 1.6.0_43-b01. I have to keep hammering
keys and it's not easy to reproduce except when I least want it.

Killing ibus doesn't help, because the problem persist as long as ibus
is running (it starts itself up again). Running the following simple
script lets me type in the application again.

If the java application is closed and started again, the application
accepts keyevents until at a random time it stops again.

I've debugged the application (it's my own app) and I can see no Events
being handled for keys, so either it's lowlevel, or it's in ibus.

Running 12.10, but please note that I'm running HotSpot JVM, ie Oracle's
binary distribution of java that isn't really modern when it comes to
X11. If someone cares about this bug enough to investigate, I can try it
on icedtea as well.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/481656

Title:
  iBus blocks input in Java application

Status in IBus:
  Unknown
Status in Iced Tea:
  Confirmed
Status in “ibus” package in Ubuntu:
  Incomplete
Status in “icedtea-java7” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: ibus

  This is a very unfortunate bug, as it is hard to reproduce :(.

  I use ThinkingRock, a Java application, and after some time the
  keyboard input stops working for this application, meaning I can still
  use my mouse to manipulate the program, but I cannot type anything.
  When closing the iBus Daemon the input works again after some seconds.
  Also restarting the Java application helps to postpone the problem
  until it occurs again some minutes later.

  I'm using Ubuntu 9.10 with version 1.2.0.20090927-2ubuntu2 of iBus and
  version 2.2.1 of ThinkingRock. My Java version is 6-15-1.

  Please notice: I do NOT want to input Chinese or Japanese or anything
  like it. I just want to normally use my keyboard. I also have NO input
  method selected, I have the input methods turned OFF.

  I have yet to test this behavior with other Java applications (maybe
  it's a bug in ThinkingRock?), so I'd be happy if somebody can confirm
  this bug for other Java applications. Because the solution is to quit
  the iBus Daemon, I suspect iBus to be the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/481656/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to