This issue has been present for years, and I believe I first noticed it sometime in 2011. shift+2 and shift+6 are ignored (makes switching quickbar items on ladders/vines using keys more tricky). I never did enough detective work to be certain, but I recall coming to the conclusion that the bug existed in LWJGL's linux support, if it is actually a bug at all; could be LWJGL debug keys that MC is not disabling.
the first crash log I uploaded was for a 1.5.1-pre, which I had upgraded the LWJGL to 2.9.0 but was otherwise unmodded. the second crash log is for an unmodded 1.5 with its default LWJGL. the ignoring of shift+(2 or 6) is reproducible on either one.
yes, very sorry about that. I had forgotten about upgrading the LWJGL until I read the crash report I had just posted, at which time I quickly created a new crash report from a pristine 1.5. If desired, please remove the first crash report.
correct. I have been unable to use both shift+2 and shift+6 in any minecraft version running on linux that I can recall trying those keys in, regardless of whether the included or an updated LWJGL is used.
possibly worthy of note is that I've always used OpenJDK. Don't know if that is a factor at all though.
Going beyond the latest Java version provided for my platform (Debian 7.0; Wheezy) would be a bit difficult. Perhaps the original reporter of this bug is running a newer release and can chime in? Or someone else?
@Kumasasa Could provide some information on your system? Assuming this is a bug in OS specific code shipped with Minecraft, it would be useful to know at the very least your OS platform and version. This way we have an idea on which platforms the bug cannot be reproduced.
I have compiled a test program with LWJGL 2.8.5 and 2.9.0 on linux and confirmed that Keyboard.isKeyDown(Keyboard.KEY_2) incorrectly returns false if the 2 key is pressed after shift is held down. Interestingly, it will return true and continue to return true if pressed first AND THEN shift is held down. Also, I can trigger a sticking key by pressing and holding 2, then pressing and holding shift, then releasing 2, then releasing shift. Keyboard.isKeyDown(Keyboard.KEY_2) will continue to return true even though no keys are down.
So there's a serious bug in LWJGL's linux implementation of Keyboard.isKeyDown(). Does anyone know how to report LWJGL bugs? Their forum registration is very unfriendly to non-java programmers, and I am not one (I only know enough to hack stuff into existing example programs) so I couldn't register.
As it's so minor an issue I don't think I'll spend any more time on it. Unless someone who already has the latest java installed can reproduce it, you may want to close this issue.
Robert Henney
MCL-502
MC-12410
This issue has been present for years, and I believe I first noticed it sometime in 2011. shift+2 and shift+6 are ignored (makes switching quickbar items on ladders/vines using keys more tricky). I never did enough detective work to be certain, but I recall coming to the conclusion that the bug existed in LWJGL's linux support, if it is actually a bug at all; could be LWJGL debug keys that MC is not disabling.
the first crash log I uploaded was for a 1.5.1-pre, which I had upgraded the LWJGL to 2.9.0 but was otherwise unmodded. the second crash log is for an unmodded 1.5 with its default LWJGL. the ignoring of shift+(2 or 6) is reproducible on either one.
yes, very sorry about that. I had forgotten about upgrading the LWJGL until I read the crash report I had just posted, at which time I quickly created a new crash report from a pristine 1.5. If desired, please remove the first crash report.
correct. I have been unable to use both shift+2 and shift+6 in any minecraft version running on linux that I can recall trying those keys in, regardless of whether the included or an updated LWJGL is used.
possibly worthy of note is that I've always used OpenJDK. Don't know if that is a factor at all though.
Going beyond the latest Java version provided for my platform (Debian 7.0; Wheezy) would be a bit difficult. Perhaps the original reporter of this bug is running a newer release and can chime in? Or someone else?
@Kumasasa Could provide some information on your system? Assuming this is a bug in OS specific code shipped with Minecraft, it would be useful to know at the very least your OS platform and version. This way we have an idea on which platforms the bug cannot be reproduced.
I have compiled a test program with LWJGL 2.8.5 and 2.9.0 on linux and confirmed that Keyboard.isKeyDown(Keyboard.KEY_2) incorrectly returns false if the 2 key is pressed after shift is held down. Interestingly, it will return true and continue to return true if pressed first AND THEN shift is held down. Also, I can trigger a sticking key by pressing and holding 2, then pressing and holding shift, then releasing 2, then releasing shift. Keyboard.isKeyDown(Keyboard.KEY_2) will continue to return true even though no keys are down.
So there's a serious bug in LWJGL's linux implementation of Keyboard.isKeyDown(). Does anyone know how to report LWJGL bugs? Their forum registration is very unfriendly to non-java programmers, and I am not one (I only know enough to hack stuff into existing example programs) so I couldn't register.
Thanks. I've opened an issue on this bug there.
Still happens on the latest launcher; from the console output:
"Launcher 1.0.10 (through bootstrap 5) started on linux..."
OS is Debian 7.1
$ java -version
java version "1.7.0_03"
OpenJDK Runtime Environment (IcedTea7 2.1.7) (7u3-2.1.7-1)
OpenJDK 64-Bit Server VM (build 22.0-b10, mixed mode)
The bug is only visual and does not affect usability.
I too suspect it's a java bug.
As it's so minor an issue I don't think I'll spend any more time on it. Unless someone who already has the latest java installed can reproduce it, you may want to close this issue.