Kaze

Hello, I have the exact same issue (same logs) on a Pi 5 with Raspbian on the 4k page kernel. I built both Box86 and Box64 out of the master...

Great news! I installed libibus (sudo apt install libibus-1.0-5) aaaand It works! So all it needs is an update to the installSteam.sh script to install it, and also a little...

I could remove the bugged doors by using this command : `/kill @e[limit=1,sort=nearest,type=littletiles:litte_animation]`

This one looks pretty tricky, because it's not systematic : It's not the first time I have it, and the only solution I have so far is to use backups....

So I downloaded my server world and removed all chunks aside of the buggy ones and tried that in singleplayer. The internal server hang is still present, which is a...

This is getting even wierder now... I removed Starlight from both client and server but I still have the issue... Ok so I had to remove both Starlight and Chipped...

I prepared a region file containing only 4 chunks copied from my world, 2 of them are causing the issue (the ones where the wall is), so that you can...

I didn't tested more blocks so far, but I had this issue with the "Massive Cobblestone Bricks" and "Weathered Cobblestone". Btw, I noticed that the texture of the "massive" does...

I just tried to load the corrupted chunk in a new world with the same environment than back then, but I encountered a new behavior that I didn't had back...

I can still trigger the issue on the latest LT : ``` "Worker-Main-10" daemon prio=1 Id=137 WAITING on java.util.concurrent.CompletableFuture$Signaller@65575e6b at java.base@20/jdk.internal.misc.Unsafe.park(Native Method) - waiting on java.util.concurrent.CompletableFuture$Signaller@65575e6b at java.base@20/java.util.concurrent.locks.LockSupport.park(Unknown Source) at...