mojira.dev

Aaron Franke

Assigned

No issues.

Reported

MC-118861 Minecraft does not launch on Linux when laptop display is disabled Duplicate MC-100129 Zombies can attack through the corners of blocks Duplicate MC-90798 Minecraft crashes when the game is fullscreened using the Steam controller Fixed MC-38427 Game crashes when rendering item 36 Duplicate MC-19938 Title screen background flashes when exiting to the title. Fixed MC-5368 Mining with tools resets cracking action when damage values are updated/Items move in hand when their count or damage changes Fixed

Comments

I experienced this bug today, mending pickaxe in hand, picking up XP doesn't repair the pickaxe.

I fixed it by restarting my game, and now it works fine.

Can no longer reproduce in 17w47b but I am able to reproduce in 1.12.2.

Despite this being a LWJGL issue, shouldn't the confirmation status still be marked as "Confirmed" rather than "Unconfirmed"? There are 11 duplicates.

I've attached two from the 1.12 crashes and one from the 1.8.2 crashes.

I can confirm that this bug happens in 1.10.2.

I have the same issue in 1.10.2.

I tried to reproduce this in 1.10.2 and the bug no longer exists. The bug has been fixed, and this ticket should be closed.

Partially confirmed for Minecraft 1.10.2. I can't reproduce the tool metadata issue (I may just be having really good ping) but adding items to the stack you're holding still causes the cracking action to reset.

This is NOT a duplicate of 5520. This has nothing to do with multiple monitors, this computer only has 1 monitor. I'm also using Windows, not Mac.

Confirmed for 1.8.1 release.

It is disappointing that the migration away from IDs did not fix this, I wpuld have figured that they'd have checked the code then, but oh well.

If I were to make a suggestion to Mojang, you may as well drop Java 6 support anyway when you drop OpenGL 1.0. Java 8 is right around the corner, its first releases are already out, and most machines capable of Java 6 and Minecraft can use 7.

redstonehelper, what are your computer's specifications?

Can we get some tests comparing 1.5.2 (or whatever version was before this bug) and the latest snapshot? From what I hear, this problem keeps getting better, so I want to see results between now and before the bug, to see if it is at least close to the same, in which case this bug should be marked as solved.

This bug is not present in 1.7.2. Where is the close issue button?

Soniji said he tested this in 13w39b.

@Matt Enloe

Problem exists in both a normal server and in Bukkit/Craftbukkit. However, Spigot has fixed this problem.

What do you mean update affected versions? Is Minecraft 1.6.2 not the latest version? I am unable to find any version released beyond 1.6.2.

This is now fixed in 13w22a.