MC-18123Background menu resolution bug
At Minecraft launching the background menu is glitching randomly, there is nothing special to make it glitch.
Environment
Ubuntu 10.04 Lucid Lynx
java version "1.6.0_27"
OpenJDK Runtime Environment (IcedTea6 1.12.5) (6b27-1.12.5-0ubuntu0.10.04.1)
OpenJDK Server VM (build 20.0-b12, mixed mode)
Desktop environment : Gnome2
Created Issue:
Background menu resolution bug
At Minecraft launching the background menu is glitching randomly, there is nothing special to make it glitch.
Environment
Ubuntu 10.04 Lucid Lynx
java version "1.6.0_27"
OpenJDK Runtime Environment (IcedTea6 1.12.5) (6b27-1.12.5-0ubuntu0.10.04.1)
OpenJDK Server VM (build 20.0-b12, mixed mode)
Desktop environment : Gnome2
Attachments1
Added Attachments:
Deleted Comment:
1.6.2
Added Attachments:
Please do not mark issues as private, unless your bug report is a security issue containing information that may compromise your server/client.
Please force a crash by pressing F3 + C for 10 seconds while ingame and attach the crash report here.
Forced crash report
Your Java version is out of date. I would also recommend using Oracle Java. Please update your Java to the latest version (1.7.0_21): http://www.java.com/en/download/. Keep in mind that when using a 32-bit browser on a 64-bit OS the automatic version detection will only show the 32-bit version of Java, the 64-bit version needs to be downloaded manually: http://www.java.com/en/download/manual.jsp.
Please report if the issue persists with the latest Java version.
I use the 32 bit version of Ubuntu, I tried again with the version 1.7.0_21 of java and i have the same problem again.
No-one seems to have issues and hardly anyone plays on linux, with those two combined it smells like your local setup might be the issue :/
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
I updated Minecraft to 1.6.2 and i have the same bug. I think it's really my local setup the issue, i know this bug for a long time.