MinePro120

That still happens in 1.16.4, although more rarely, at least in the server version (Horse moved wrongly, that also results in a kick if allow-flight=false).

This should be marked as solved.

It could be a security issue if the hacker can change the book or something like this. Anyways, that's a whole other topic and I'm not sure how secure or not this is. Nevertheless, it is definitely inconsistent with what the signs do and I think they should all work the same way, whatever this way is.

Confirmed in 1.16.3

No, that's not a duplicate of those bugs. As a matter of fact,  I checked them before reporting and could not reproduce them in 1.16.3. Also, they use different JSON tags ("selector" and "score").

Version 1.16.3, I couldn't reproduce 😃. I noticed some weird behaviour though; when arrows hit the painting (or the half of the block the painting is on)  they just disappear, and (most of the times) the player takes damage as if they were hit by the arrow returning back to them (no matter the angle and only if the arrow was shot with the highest speed).

Setting level-type to default solved the issue. It wasn't an issue after all, just that in previous version of minecraft I didn't get any erros for my wrong generator-settings.

v2.1.17417, latest I could find from minecraft.net right now, still an issue.

I was talking about GNU/Linux, not Windows. Never had this issue on Windows. Anyways, my solution was to create the swiftshader folder where the launcher (not .minecraft) is located and paste the binaries from the link I provided above. But the issue could be very different on Windows. Run the launcher from the cmd prompt for some output.

Good to know. This affects only items, not the respective blocks, right? I had some signs in my inventory that executed commands when right-clicked. It might have to do with that.

Just updated a server from 1.15.2 to 1.16.2 and I had :

Unable to resolve BlockEntity for ItemStack: minecraft:dark_oak_sign
Unable to resolve BlockEntity for ItemStack: minecraft:birch_sign
Unable to resolve BlockEntity for ItemStack: minecraft:acacia_sign

The warns appeared only once though. Is it something that could possibly cause world corruption?

Back when I created the server, I copied the world from singleplayer and set "leve-type" to "flat". I think, due to bug MC-134900, I wasn't given any error then (my "generator-settings" has always been blank) but now I am. Am I right? If that's the case, I should close this issue.

I found something! If the "level-type" is set to default (instead of "flat" that it was before) the message disappears. Is this expected behaviour though?

I have trouble recreating the issue on another world and thus it should probably be marked as resolved.

The issue persists on 1.16.2-pre1. Also, the paintings that become invisible, don't seem to have a hitbox.

Could it be that they simply forgot to add the "swiftshader" folder in the launcher's directory? The fix seems pretty easy and straightforward, since the launcher searches for the 2 files in that folder. If we run the launcher from a terminal and head to the "Skins" section the outcome would be :

OpenSUSE Tumbleweed here. EZ solution : get the precompiled binaries from here, rename them to libEGL.so and libGLESv2.so, and put them in a folder named "swiftshader" in the launcher's directory.

Yep, I was working on a map too. Imagine dozens of painting becoming thin air by adding this tag...

Oh, because I saw many newer issues been given attention. Thanks.

What about my other issue? Will someone ever see it? I've seen many cases with issues remaining unanswered (by mods or official support).