I need to do a bit more work to get the project to build properly (getting theagentd to try running it from Eclipse was a bit of an eye-opener as to how much of a faff that was) but then I can easily deploy it to Steam for you. Getting to the bottom of this would seem to be of extreme importance because it does rather look like right now the entire 3.2.x is totally broken and has been for a while!
java -javaagent:lwjglx-debug-1.0.0.jar <...normal arguments..>
java -javaagent:lwjglx-debug-1.0.0.jar=t;o=trace.log <...normal arguments..>
Obviously, I'll be deeply disheartened if this turns out to be a bug in LWJGL. It would mean the testing I perform is lacking and I can't depend on the community to promptly discover and report such issues.
It very much looks like the problem the Minecraft guys were running in to in the thread Spasi linked to back up the thread.
It seems to be exclusive to development type environments, where the game is launched from either an IDE or gradle.