X11.XInputMetho d.setXICFocus( Ljava/awt/ peer/ComponentP eer ZZ) V+25 X11.XInputMetho d.setXICFocusNa tive(JZZ) V+0 Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) Siginfo: si_signo= SIGSEGV: si_errno=0, si_code=2 (SEGV_ACCERR), si_addr=0x269bce28 log):Ĭurrent thread (0x2760c000): JavaThread "AWT-EventQueue-0" Just a few major highlight from the generated report, which I have just attached (hs_err_ pid29918. I just arrived in this bug now, and tried the recommended "ibus restart" to get text input working again, but after a few seconds with input working again, the Java application died miserably. Java HotSpot(TM) Server VM (build 24.72-b04, mixed mode) Java(TM) SE Runtime Environment (build 1.7.0_72-b14) Of course, while using Java version 7, which is the only release JOSM is "qualified" to run with: Because the solution is to quit the iBus Daemon, I suspect iBus to be the problem.īeing hit by this one for a long time now, when using JOSM (all released stable JARs for a couple year now, if not more). 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. I also have NO input method selected, I have the input methods turned OFF. Please notice: I do NOT want to input Chinese or Japanese or anything like it. I'm using Ubuntu 9.10 with version 1.0927- 2ubuntu2 of iBus and version 2.2.1 of ThinkingRock. Also restarting the Java application helps to postpone the problem until it occurs again some minutes later. When closing the iBus Daemon the input works again after some seconds. 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. This is a very unfortunate bug, as it is hard to reproduce :(.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |