Just to double check since we think weโve isolated this to GNOME desktops with Wayland, could you launch the game with GDK_BACKEND=x11 and see if it still happens?
Could you clarify if this is a bug in SDL or the game? If itโs an SDL bug then it should be reported to them rather than us.
This is an issue with the JVM you're using rather than the game
Does this occur on the latest snapshot?
We do not have enough information to find the cause of this issue.
Please attach the crash report found in minecraft/crash-reports/crash-<DATE>-client.txt or minecraft/hs_err_pid<number>.log here.
To learn more about how to find the above files, see this page.
This issue is being temporarily resolved as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.
Quick Links:
๐ Bug Tracker Guidelines โ ๐ฌ Community Support โ ๐ง Mojang Support (Technical Issues) โ ๐ง Microsoft Support (Account Issues)
๐ Project Summary โ โ๏ธ Feedback and Suggestions โ ๐ Game Wiki
Is this still an issue in the latest snapshot?
Is this still present in the latest snapshot?
@tangey1021 Do you mean that this does not occur in snapshot 9?
Do you have a minimal datapack available to reproduce this?
I'm unable to reproduce this on my machine, but I've added an error screen that should make it easier to notice. Please let us know if this happens again and attach logs if possible.
Is this still an issue in the latest snapshot?
I'm not seeing this behaviour locally, I'm chalking this up to luck
This seems to have been fixed since the bug was opened, you just need to add an equippable component to the poppy since they don't have one by default.
/item replace entity @e[type=minecraft:copper_golem] saddle with minecraft:poppy[minecraft:equippable={slot:saddle}]
I've been trying to reproduce this for a while unsuccessfully, are you sure it's not one of the endermen teleporting into and hitting you?
Is this still an issue in the current version of the game? I can see that code has been added to prevent this scenario in the past 5 years @Avoma
Is this still an issue in the latest snapshot? There was a fix for spawn eggs which also affects this
I canโt reproduce this on macOS in the latest snapshot, is this still an issue on your end?
edit: also tested it on Windows 11 and couldnโt reproduce it there either
In the latest snapshot, the repro case seems to work without an issue if you use `armor.chest` instead, this also works with other slots like `armor.legs` etc.
Is there something I'm missing here?
Does this still occur in the latest snapshot? I can't reproduce this with the repro steps
TNT can be ignited using the can_break component instead.