The input of Linux Fcitx displays abnormally about jetbrainsruntime HOT 37 CLOSED

别抱怨了，实际上人民应该付出行动来修正。有没有人提交过pull request。

from jetbrainsruntime.

I saw a lot of people in the issue and I encountered the same problem.

from jetbrainsruntime.

Could you please report using our bug database https://youtrack.jetbrains.com/issues/JBR

Actually, this bug is reported almost 10 years ago. See https://youtrack.jetbrains.com/issue/JBR-2460. And the bug is still not fixed.

from jetbrainsruntime.

Could you please report using our bug database https://youtrack.jetbrains.com/issues/JBR

Could you please merge this patch so we can close this issue

from jetbrainsruntime.

you can just reset the bundle JBR version, It will work again

double press the shift key , then input "runtime" in the actions tab, and reset the JBR settings in the following dialog

from jetbrainsruntime.

Unfortunately, this is an upstream OpenJDK bug. Even my own Java window program has this problem. The patch mentioned above can solve both JetBrains softwares and my own one. I guess not only should we ask JetBrians to add that patch but also we should complain that to upstream OpenJDK and Oracle, since if they do not fix it at the upstream, this bug will always be there for Java 17, 21, 28, and so on...

I was going to submit feedback to OpenJDK, but I saw this feedback in OpenJDK's Issue, JDK-8279052.

from jetbrainsruntime.

I encountered the same problem. I searched(搜索) for various solutions on the Internet and found(发现) a patch(补丁) in the community(社区): https://github.com/prehonor/myJetBrainsRuntime我遇到了同样的问题。我在互联网上搜索了各种解决方案，并在社区中找到了一个补丁：https://github.com/prehonor/myJetBrainsRuntime However, because the patch(补丁) is too old and cannot be used(使用) directly(直接) in the current(当前) version(版本) of the code(代码), I compared the patch(补丁) modifications and manually modified the same content(内容) in the latest version(版本) submission (50933cd), and ensured successful(成功) compilation. For this purpose(宗旨), I forked a warehouse(仓库) for reference(参考) only: https://github.com/Yu-Xiao-Sheng/JetBrainsRuntime/tree/jbr17但是，由于补丁太旧，无法在当前版本的代码中直接使用，所以我在最新版本提交（ 50933cd ）中对比了补丁修改并手动修改了相同的内容，并确保编译成功。为此，我分叉了一个仓库仅供参考：https://github.com/Yu-Xiao-Sheng/JetBrainsRuntime/tree/jbr17

At the same time, I generated a new patch(补丁) file based on the changed content(内容). The file FixedLinuxFcitx.patch is located in the jbr17 branch(分公司) of the warehouse(仓库). I hope it can be helpful(乐于助人) to you.同时，我根据更改的内容生成了一个新的补丁文件。该文件 FixedLinuxFcitx.patch 位于仓库的 jbr17 分支中。希望对您有所帮助。

If the JetBrains/JetBrainsRuntime warehouse(仓库) continues to be updated in the future(未来), I think a convenient(方便) way is to merge(合并) the contents(内容) of the two warehouses(仓库) JetBrains/JetBrainsRuntime and Yu-Xiao-Sheng/JetBrainsRuntime and recompile, but the validity(有效性) of subsequent(后续) changes cannot be guaranteed.如果以后仓库继续更新，我觉得方便的办法是合并两个 JetBrains/JetBrainsRuntime 仓库的内容 JetBrains/JetBrainsRuntime ， Yu-Xiao-Sheng/JetBrainsRuntime 然后重新编译，但后续更改的有效性无法保证。

Sorry I can't submit(提交) a pull request(请求), I don't know much about it yet.对不起，我无法提交拉取请求，我还不太了解。

This problem has been fixed in the official repository

from jetbrainsruntime.

Thank you for submitting the issue. We regret the inconvenience caused to you.

Could you please provide us with the detailed description of the problem & steps reproducing this issue?

Some developers in the community have provided patches to fix this problem.

Unfortunately we have got neither pull requests related to this issue nor patches in any other format. Any references to these fix would be appreciated?

from jetbrainsruntime.

Thank you for submitting the issue. We regret the inconvenience caused to you.

Could you please provide us with the detailed description of the problem & steps reproducing this issue?

Some developers in the community have provided patches to fix this problem.

Unfortunately we have got neither pull requests related to this issue nor patches in any other format. Any references to these fix would be appreciated?

Use any fcitx input. When inputting Chinese or Japanese in IDEA, the input software cannot get the focus position of the cursor.
This patch is not provided by me, sorry I can’t submit a pull requests. But I can provide a git repository of patches. https://github.com/prehonor/myJetBrainsRuntime

from jetbrainsruntime.

I encountered the same problem.

from jetbrainsruntime.

I encountered the same problem.

from jetbrainsruntime.

I encountered the same problem.

from jetbrainsruntime.

Have the same issue.

from jetbrainsruntime.

I have the same problem

from jetbrainsruntime.

me too.

from jetbrainsruntime.

I have the same problem

from jetbrainsruntime.

俺也一样

from jetbrainsruntime.

This bug exits with 8 years and with another 6 month passed,it hasn't been fixed yet.This is the discussion about this bug
https://youtrack.jetbrains.com/issue/JBR-2460

from jetbrainsruntime.

Unfortunately, this is an upstream OpenJDK bug. Even my own Java window program has this problem. The patch mentioned above can solve both JetBrains softwares and my own one. I guess not only should we ask JetBrians to add that patch but also we should complain that to upstream OpenJDK and Oracle, since if they do not fix it at the upstream, this bug will always be there for Java 17, 21, 28, and so on...

from jetbrainsruntime.

same problem,please fix it

from jetbrainsruntime.

now the problem is nobody PR.
I hope somebody do this

from jetbrainsruntime.

@NikitkoCent Could you please take a look at suggested patches fixing this issue

This patch is not provided by me, sorry I can’t submit a pull requests. But I can provide a git repository of patches. https://github.com/prehonor/myJetBrainsRuntime

from jetbrainsruntime.

Could you please report using our bug database https://youtrack.jetbrains.com/issues/JBR

from jetbrainsruntime.

I have the same problem

from jetbrainsruntime.

i have the same problem

from jetbrainsruntime.

I encountered the same problem. I searched for various solutions on the Internet and found a patch in the community: https://github.com/prehonor/myJetBrainsRuntime
However, because the patch is too old and cannot be used directly in the current version of the code, I compared the patch modifications and manually modified the same content in the latest version submission (50933cd), and ensured successful compilation. For this purpose, I forked a warehouse for reference only: https://github.com/Yu-Xiao-Sheng/JetBrainsRuntime/tree/jbr17

At the same time, I generated a new patch file based on the changed content. The file FixedLinuxFcitx.patch is located in the jbr17 branch of the warehouse. I hope it can be helpful to you.

If the JetBrains/JetBrainsRuntime warehouse continues to be updated in the future, I think a convenient way is to merge the contents of the two warehouses JetBrains/JetBrainsRuntime and Yu-Xiao-Sheng/JetBrainsRuntime and recompile, but the validity of subsequent changes cannot be guaranteed.

Sorry I can't submit a pull request, I don't know much about it yet.

from jetbrainsruntime.

I encountered the same problem. I searched for various solutions on the Internet and found a patch in the community: https://github.com/prehonor/myJetBrainsRuntime However, because the patch is too old and cannot be used directly in the current version of the code, I compared the patch modifications and manually modified the same content in the latest version submission (50933cd), and ensured successful compilation. For this purpose, I forked a warehouse for reference only: https://github.com/Yu-Xiao-Sheng/JetBrainsRuntime/tree/jbr17

At the same time, I generated a new patch file based on the changed content. The file FixedLinuxFcitx.patch is located in the jbr17 branch of the warehouse. I hope it can be helpful to you.

If the JetBrains/JetBrainsRuntime warehouse continues to be updated in the future, I think a convenient way is to merge the contents of the two warehouses JetBrains/JetBrainsRuntime and Yu-Xiao-Sheng/JetBrainsRuntime and recompile, but the validity of subsequent changes cannot be guaranteed.

Sorry I can't submit a pull request, I don't know much about it yet.

They have already had an official try on this issue https://youtrack.jetbrains.com/issue/JBR-2460/Wrong-position-of-input-window-and-no-input-preview-with-fcitx-and-ubuntu-13.04

it's Fixed in JBR builds: jbr17.1162.7

from jetbrainsruntime.

I encountered the same problem. I searched for various solutions on the Internet and found a patch in the community: https://github.com/prehonor/myJetBrainsRuntime However, because the patch is too old and cannot be used directly in the current version of the code, I compared the patch modifications and manually modified the same content in the latest version submission (50933cd), and ensured successful compilation. For this purpose, I forked a warehouse for reference only: https://github.com/Yu-Xiao-Sheng/JetBrainsRuntime/tree/jbr17我遇到了同样的问题。我在网上搜索了各种解决方案，在社区里找到了一个补丁： https://github.com/prehonor/myJetBrainsRuntime 但是，由于补丁太旧，无法在当前版本的代码中直接使用，所以我对比了补丁修改，并在最新版本提交（50933cd）中手动修改了相同的内容，并确保编译成功。为此，我分叉了一个仓库仅供参考：https://github.com/Yu-Xiao-Sheng/JetBrainsRuntime/tree/jbr17
At the same time, I generated a new patch file based on the changed content. The file FixedLinuxFcitx.patch is located in the jbr17 branch of the warehouse. I hope it can be helpful to you.同时，我根据更改的内容生成了一个新的补丁文件。该文件 FixedLinuxFcitx.patch 位于仓库的 jbr17 分支中。希望对您有所帮助。
If the JetBrains/JetBrainsRuntime warehouse continues to be updated in the future, I think a convenient way is to merge the contents of the two warehouses JetBrains/JetBrainsRuntime and Yu-Xiao-Sheng/JetBrainsRuntime and recompile, but the validity of subsequent changes cannot be guaranteed.如果以后仓库继续更新，我觉得方便的办法是合并两个 JetBrains/JetBrainsRuntime 仓库的内容 JetBrains/JetBrainsRuntime ， Yu-Xiao-Sheng/JetBrainsRuntime 然后重新编译，但后续更改的有效性无法保证。
Sorry I can't submit a pull request, I don't know much about it yet.对不起，我无法提交拉取请求，我还不太了解。

They have already had an official try on this issue https://youtrack.jetbrains.com/issue/JBR-2460/Wrong-position-of-input-window-and-no-input-preview-with-fcitx-and-ubuntu-13.04他们已经对这个问题进行了正式尝试 https://youtrack.jetbrains.com/issue/JBR-2460/Wrong-position-of-input-window-and-no-input-preview-with-fcitx-and-ubuntu-13.04

it's Fixed in JBR builds: jbr17.1162.7它在 JBR 版本中已修复：jbr17.1162.7

Great, it turned out to be recently fixed!

from jetbrainsruntime.

@Yu-Xiao-Sheng try 2023.3.2, it just works like a charm

from jetbrainsruntime.

@Yu-Xiao-Sheng try 2023.3.2, it just works like a charm试试 2023.3.2，它就像一个魅力

Yes, I am using Intellij IDEA2023.3.2 on Ubuntu22.04. Unfortunately, I also encountered this problem. Apart from this problem, it works really well.

I'm not sure if it's normal for other people to be in this kind of environment

from jetbrainsruntime.

@Yu-Xiao-Sheng try 2023.3.2, it just works like a charm试试 2023.3.2，它就像一个魅力

Yes, I am using Intellij IDEA2023.3.2 on Ubuntu22.04. Unfortunately, I also encountered this problem. Apart from this problem, it works really well.

I'm not sure if it's normal for other people to be in this kind of environment

which input method are you using? ibus or fcitx5?

What's your JBR version of Intellij IDEA 2023.3.2 ? I've tried PHPStorm/Goland/Ride 2023.3.2, both works well with fcitx5

can you paste the output of this command ?

env |grep -i IM_ 

from jetbrainsruntime.

@Yu-Xiao-Sheng try 2023.3.2, it just works like a charm试试 2023.3.2，它就像一个魅力try 2023.3.2， it just works like a charm试试 2023.3.2，它就像一个魅力

Yes, I am using Intellij IDEA2023.3.2 on Ubuntu22.04. Unfortunately, I also encountered this problem. Apart from this problem, it works really well.是的，我在 Ubuntu22.04 上使用 Intellij IDEA2023.3.2。不幸的是，我也遇到了这个问题。除了这个问题之外，它的工作非常好。

I'm not sure if it's normal for other people to be in this kind of environment我不确定其他人处于这种环境中是否正常

which input method are you using? ibus or fcitx5?您使用的是哪种输入法？IBUS还是FCITX5？

What's your JBR version of Intellij IDEA 2023.3.2 ? I've tried PHPStorm/Goland/Ride 2023.3.2, both works well with fcitx5您的 Intellij IDEA 2023.3.2 的 JBR 版本是什么？我试过 PHPStorm/Goland/Ride 2023.3.2，两者都适用于 fcitx5

can you paste this command output?你能粘贴这个命令输出吗？

env |grep -i IM_ 

Of course, this is the result:

I am using fcitx4.2.9.8

from jetbrainsruntime.

I doubt that You're not using a Fixed version of JBR, the genuine version of 2023.3.2 is bundled with
jbr17.1087.9 ,this version has a patch for this issue backported

if you can confirm that the version of JBR is jbr17.1087.9, I think there is some problem with your fictx4, I can not test with fictx4 because I'm using fcitx5

from jetbrainsruntime.

I doubt that You're not using a Fixed version of JBR, the genuine version of 2023.3.2 is bundled with jbr17.1087.9 ,this version has a patch for this issue backported

if you can confirm that the version of JBR is jbr17.1087.9, I think there is some problem with your fictx4, I can not test with fictx4 because I'm using fcitx5

I think you are right, before I replaced my own compiled jbr, the backup version of the bound jbr runtime environment was jbr17.1087.7

from jetbrainsruntime.

I doubt that You're not using a Fixed version of JBR, the genuine version of 2023.3.2 is bundled with jbr17.1087.9 ,this version has a patch for this issue backported 我怀疑您没有使用 JBR 的固定版本，2023.3.2 的正版与 jbr17.1087.9 捆绑在一起，此版本针对此问题向后移植了补丁
if you can confirm that the version of JBR is jbr17.1087.9, I think there is some problem with your fictx4, I can not test with fictx4 because I'm using fcitx5如果你能确认JBR的版本是jbr17.1087.9，我认为你的fictx4有一些问题，我不能用fictx4测试，因为我使用的是fcitx5

I think you are right, before I replaced my own compiled jbr, the backup version of the bound jbr runtime environment was jbr17.1087.7我想你是对的，在我替换我自己编译的jbr之前，绑定的jbr运行时环境的备份版本是jbr17.1087.7

I think, maybe if I install Intellj a few days later, I won't have this problem.

from jetbrainsruntime.

you can just reset the bundle JBR version, It will work again您可以重置捆绑的 JBR 版本，它将再次工作

double press the shift key , then input "runtime" in the actions tab, and reset the JBR settings in the following dialog双击 Shift 键，然后在“操作”选项卡中输入“运行时”，并在以下对话框中重置 JBR 设置

This is great, I have successfully changed to the latest runtime version and the problem no longer exists in this jbe version!

from jetbrainsruntime.

As you may have noticed, the issue (https://youtrack.jetbrains.com/issue/JBR-2460) was fixed in 2023.3.2, so I'm closing it. If you experience some problems with it, feel free to leave a comment through the provided link.

from jetbrainsruntime.