Clément Vuchener

How can you link that to outdated drivers? I am talking about compatibility with an upcoming display server protocol (wayland) or its compatibility layer (xwayland).

I realize it is a very low priority bug, and it may be marked as wontfix but not resolved.

Yes, my drivers are up to date and Minecraft works on Xorg. I am not using wayland with outdated drivers.

Did you read my report before posting that? Are you a bot?

It looks like a lwjgl bug. I wrote a short test program :

import org.lwjgl.LWJGLException;
import org.lwjgl.input.Keyboard;
import org.lwjgl.opengl.Display;
import org.lwjgl.opengl.DisplayMode;

public class KeyboardTest {
	public static void main (String[] args) {
		try {
			Display.setDisplayMode (new DisplayMode (800, 600));
			Display.create ();
		}
		catch (LWJGLException e) {
			e.printStackTrace ();
			System.exit (0);
		}

		while (!Display.isCloseRequested ()) {
			while (Keyboard.next ()) {
				String state;
				if (Keyboard.getEventKeyState ())
					state = "pressed";
				else
					state = "released";
				int key = Keyboard.getEventKey ();
				System.out.println (Keyboard.getKeyName (key) + " (" + key + ") " + state);
			}
			Display.update ();
		}

		Display.destroy ();
	}
}

Pressing ^ twice, gives the output:

CIRCUMFLEX (144) released
NONE (0) pressed
CIRCUMFLEX (144) released

Edit: This method outputs NONE key for the key I reported in the first message. Now, I understand what you mean by "no eventKey given by LWJGL".
Edit2: I posted a bug report on the LWJGL forum : http://lwjgl.org/forum/index.php/topic,5477.msg28937.html

A dead key is a key that does not write a character, but it modifies the next character. For example typing ^, then e, writes ê.
I don't really know lwjgl works, but I think it should be handled with a key code rather than a character code. Like the modifier keys (ctrl, alt, shift, ...) do not have associated characters but work fine.

Also, while in game, pressing ^ change the behaviour of the next non-modifier key :
– for actions that last for the time the key is pressed (like moving), the action starts with a delay (waiting for a repeat event ?).
– for other actions (quick slot, inventory, ...), the action is completely ignored.

It may come from a limitation of lwjgl as I have seen a lot of software having issues with this key.

14w34c fixes it for my french keyboard. Key names are correct (it is better than Windows on that point, now).

There is still a problem with the dead key ^: I have to press it twice, both in the option menu and in game.

Playing 14w30c in single player, boats seem to be unusable. I broke 5 boats in a row in open ocean and only once found the drops on the shore some blocks away. I was also teleported on a short distance twice which hinted me to the location desync.

Edit: I managed to use my sixth boat a little longer and there was a lot of teleportations (the last one about 30-50 blocks away). In the end new chunks stopped being displayed (not sure if related) and I was sailing in the void above some ocean particles.

Edit2: Nevermind, I had a forgotten automatic chicken farm exploding. Boats went buggy before anything else. This is just boats being very sensitive to lag. Nothing new.

It happened to me with 14w30c. It can be easily reproduced in creative mode.

This seems related with this issue from LWJGL : http://lwjgl.org/forum/index.php?topic=3950.0