Jacob Lundberg

I also confirm raw input works.

Bizarrely, MultiMC shows lwjgl 3.2.2 is being used.  If I override it with the version previously provided by Dinolek, I get a segfault.  So I guess Mojang tweaked their version of lwjgl 3.2.2 somehow so that it's still broken like 3.2.1.  :-/

But since raw input works this bug isn't deadly anymore (but hopefully they'll fix it someday).

Regarding why it affects fullscreen mode, rather than where things draw it is probably related to other software attempting to grab the pointer for exclusive use.  I have the problem because I use x2x which grabs the pointer when you move it off the edge of your screen.  I think x2x and Minecraft briefly fight over who owns the pointer.  Minecraft wins but not without causing some wild view shifts.  Many window managers have hot spots where if you move the pointer there the WM does something and I think in these situations similarly they may briefly capture the pointer.

Given that Mojang knows how to build the client both ways, if they are going to prefer Mac over Linux I wish they would release a Linux-only client until they can get their house back in order.  This bug really stinks and you have to be a fairly expert user to work around it.

Some friends and I have a creative server and we are experiencing this a lot.  Everybody is trying to be careful to be in Creative mode when teleporting now but even that isn't safe if you fall below the world.  It's routine in 1.14.2 to fall a dozen meters or more because of the extremely slow chunk loading, which often puts us in a lava lake or the like.  All of these teleports worked fine in 1.13.  We can go through and rework all the teleport platforms to be bare stone but it's not very aesthetically pleasing.

This issue does not mention x2x but that is another way to trigger the bug.  I can also confirm the bug in 1.14 through 1.14.2 pre-3.

Using Dinolek's instructions I was able to switch to LWJGL 3.2.2 in MultiMC and it resolves my problem with x2x.  I was not able to get the vanilla launcher to use anything other than LWJGL 3.2.1 so I cannot confirm or deny for the vanilla launcher.

Yes, thank you.  My situation is somewhat different but I can confirm the work-around in that issue (LWJGL to 3.2.2) resolves the problem for me, so it is probably the same bug.