Matthew Strelsky

Sadly, after a long wait of 7 years, Mojang has chosen to refuse to fix this bug to the detriment of the international community. 

Will a moderator please change the status to "refuse to fix". I'm tired of constantly updating the versions effected by this bug and am heartbroken but can no longer keep this bug report updated.

Updated to include 1.18 now that it is released. Hopefully this bug will be fixed some day. Even just implementing the workaround we suggested in the comments would be good enough but there's nothing the end user can do but wait for Mojang. It's been a long wait but I'm still hopeful.

None of the integrated graphics hardware in the CPUs listed for your device support OpenGL 3.2 and therefore your computer does not support the minimum requirements.

Information on your computer found here: https://support.hp.com/ee-en/document/c02781693

Minecraft Minimum System Requirements are found here: https://help.minecraft.net/hc/en-us/articles/360035131371-Minecraft-Java-Edition-System-Requirements-

Interestingly, the minimum requirements state OpenGL 4.4 is required, but afaik it works with anything 3.2 and up.

Without sharing the error log there's no way to determine what the issue is. However it it unlikely that it is an issue on Mojang's end. 

Ensure you have the latest version of Java on your system (JRE 16) and that your OpenGL driver's support OpenGL 3.2. Granted those are only guesses for solutions to your problem without the logs.

Regardless this isn't an issue for Mojang.

I can confirm this happens to me as well, but it also happens  in 1.16.5. When left clicking an item that is in an itemframe, and the item frame is placed on the bottom of the block, the item tends to get stuck on top of the block.

This means that if you placed an itemframe on the ceiling of a room on your house and left clicked an item out of it, you would have to go all the way outside your house and get on top of the roof to get your item back.

Thank you for the additional input! Hopefully we do get this fixed soon. It's been a problem for at least 5 years now and effects a large portion of the Minecraft user base. I'm surprised it hasn't been a higher priority for Mojang.

I noticed Adrian Östergård updated the severity of this bug report. Thank for doing that and thank you Octopus Tea for confirming my observation with a different IME.

Again, I fully understand if nobody on the dev team has access to a non-Windows machine to test the fix on. I would be more than happy to assist in testing bug fix implementations for this issue.

Alright, so after hours of research into LWJGLv3 and GLFW and trying to trick the minecraft launcher to load compiled versions of the latest glfw git repo I made an accidental discovery. IME input technically does work. There's nothing wrong with it looking for the input per say it's just not accepting it for other reasons. I'll explain.

When you activate IME input you do so by pressing a key combination. In my case this is the FCTIX default of CTRL+SPACE. Minecraft sees you press these buttons and does nothing. When you use IME input mode you have two options to complete your input. You can either press ESC to escape back out of IME input mode(pressing the key combination again also works) and ignore the input, or you can press ENTER/RETURN to confirm the input and place it in the text area. Minecraft still handles these button inputs while IME input is enabled.   This IS the problem. 

I was able(as seen in the screenshot) to type in the world search using my IME because pressing ENTER on a search that has no results doesn't do anything. When you press enter in chat it sends the message, but when you are using IME input the message gets sent before the IME sends the text over.

Basically, the best solution is for Mojang Studios to add a configuration option in the settings to add your keyboard shortcut for your IME. When Minecraft sees you press this input, it should then ignore all keyboard presses until either ESC, ENTER/RETURN, or the IME Keyboard Shorcut is pressed/pressed again.

Updated to include 1.16.  This bug has existed for almost 5 years now. It's as if Mojang only cares about it's English speaking player base. Extremely disheartening.

I would have updated it to include the April fool's day snapshot for laughs but it doesn't matter since this bug will probably never get fixed anyways. 

I'll still keep doing my due diligence and update the bug report to include every snapshot and release versions affected until it does get fix though..... No matter how many years it takes.

Edit because I just saw the above comment by a mod

Thank you for the info but this bug has never been listed as "in progress" and it has existed since 2015

Is there any way to find out if this is being worked on or to just politely remind the right people that it exists? It's a bug that has existed since 2015 and greatly effects multi-language communities. I would be more than happy to work directly with one of the Minecraft developers to help fix this bug. I'm aware that you might not have anyone in the office with a Linux setup. I can provide contact information upon request.

Minecraft is a game that should be enjoyed by everyone together, regardless of location and language. Being able to play Minecraft with my friends in Japan is great and even more fun while I'm learning their language(Japanese) and they are learning mine(English). It's a burden though to not be able to type in Japanese in game chat though because the game doesn't handle my IME input properly. Minecraft is the only program I've ever encountered with this issue.

Issue still exists in 1.15 pre-release 1. Also would it be possible to grant me ownership of the issue so I can update it with the new versions as affected? The user who opened the issue doesn't have any know activity on their activity feed after July 2018.

Issue still exists in 19w44a.

Thank you Michael Wobst for re-opening this issue. I would like to provide my input that this issue still exists on the latest Minecraft snapshot 19w41a on Xubuntu Linux 19.04 running Oracle Java Runtime "1.8.0_221". When I type using my IME the IME popup appears to show I'm typing in Japanese but once I go to send the input the Minecraft chat stays blank. Typing in another windows and then copying and pasting the text does work but it is an extremely annoying workaround.