Barney Gale

I believe it will be a ninja edit, i.e. it'll work in 1.7.1 final, which will differ very slightly from 1.7.1 pre.

Normally when logging in, the client sends a "handshake" packet to switch to protocol mode 2, then sends a "login start" packet with the player's username. When this bug occurs, the first packet on the wire is the "login start" packet, which upsets the server as it's expecting a handshake.

I've been able to reproduce this on a local server by logging on/off repeatedly. In 20 attempts, 9 succeeded and 11 hung on "logging in...". Successes/failures seemed to come in "runs", e.g. 3 or 4 consecutive attempts would be successful, then I'd get 3 or 4 failures in a row.

This bug affects a variety of graphics cards and drivers, including many modern ones. AFAIK minecraft is the first and only game to die on this bug. I've been playing since alpha and it's going to suck having to stop playing over a bug that's been marked as "invalid" despite its cause not being determined. You can't reasonably say "it's your graphic drivers" if it affects a range of drivers :/

I'm happy to provide a VNC or SSH service to a mojang developer if they want to investigate this further.

As far as I can tell, it's org.lwjgl.opengl.GL11.glGenLists which is the culprit, mostly on intel cards. Anyone fancy making a smaller test program to try and replicate the issue?

For what it's worth:

barney@pine ~ $ dpkg -s libgl1-mesa-glx | grep Version
Version: 9.0.3-0ubuntu0.4

I am also affected. Using integrated Intel graphics.

barney@pine ~ $ glxinfo | grep "OpenGL version"
OpenGL version string: 3.0 Mesa 9.0.3
barney@pine ~ $ java -version
java version "1.7.0_40"
Java(TM) SE Runtime Environment (build 1.7.0_40-b43)
Java HotSpot(TM) 64-Bit Server VM (build 24.0-b56, mixed mode)

Same issue here, though for me it affects 13w38c and 13w39b too! Using integrated intel graphics on Linux.

OpenGL version string: 3.0 Mesa 9.0.3

Could this bug be reassigned? I think Dan Frisk is busy working on MCPE

Kane, this is related to the GS4 Query handler and not the RCON handler. Don't conflate the two.