![]() ![]() I guess a Freemind bug or setting failures something. I don't think ibus does not work with Java applications. ![]() Additional comment from fujiwara on 02:19:14 EDT. OpenJDK Client VM (build 20.0-b11, mixed mode) The only workaround is to quit ibus.Ĭan you reproduce the issue, or am I the only one affected by this problem? It there a way I can help debugging this on my end? I have no message when I launch Freemind from the terminal, and when the bug occurs.Īfter a few minutes of usage, I can not type anything in Freemind. Additional comment from nomnex on 01:48:05 EDT. If I want to input Japanese again in Freemind, I must first terminate Freemind, and re-open it. If I click on a another window, I can select Japanese input as usual). If I restart ibus, I can't input Japanese in the Freemind window (I can's select Japanese input as long as Freemind window is in focus. To re-gain keyboard input in Freemind, I must stop ibus. It only affects the Freemind GUI, outside of it, I can type. I can input English, or Japanese, but after a (short) time, any key press stop working in the Java application (I can only mouse click on the menus.) Additional comment from nomnex on 04:48:37 EST. Additional comment from fujiwara on 01:33:33 EST. either input English (my default language) either JapaneseĪfter some time, any key press is ineffective in the Java application. Version-Release number of selected component (if applicable):Ģ. It seems that ibus, when used with Java applications, causes the lose of keyboard input. I have a limited understanding of interaction between the different software, but reading a similar issue ibus+java applications, see: and (closed) I have first reported a bug about the Freemind package, in 2011, after losing keyboard input when using Japanese Please help with directions (package, or upstream bug tracker): +++ This bug was initially created as a clone of Bug #800736 +++ Restarting PhpStorm does resolve the problem for a time. ![]() Restarting ibus-daemon causes PhpStorm to crash (it used to be that restarting the daemon would fix the problem for a while, but no longer). The symptoms are as described below, to whit: after running the app for a while (some hours) it refuses to respond to the keyboard any longer. I think the Java app itself is irrelevant, it's the fact that it's a Java app that's pertinent. I've cloned an older bug because I'm effectively seeing the same problem, albeit with a newer version of ibus and with PhpStorm instead of Freemind. ![]()
0 Comments
Leave a Reply. |