I've been having the same issue. I was running Xorg on my system, then switched to Wayland and had this issue. Switching back to Xorg, the problem was resolved. I also tried toggling the Discrete Scrolling and Raw Input settings, but no changes were made. The closest thing was altering the scrolling sensitivity, but got similar results to OP. If there's anything you want me to try out to further diagnose this, please let me know.
Edit: This issue is still prevalent on 1.19.2
Don't you just hate when you search for it and you don't find it? Oh well. I tried.
This is really weird. I was just having this problem and now it's not happening. When I first saw it, I thought something weird happen in Minecraft so I shut down the client. After that, the bug still persisted. Then I logged out of my single player world for a bout 5 minutes, went back on, and it went away. Any explanations for that?
Confirmed for 11b.
Cannot confirm. Falling sand renders perfectly fine. Is there any special steps to reproduce this with, and do you have any screenshots?
I can duplicate this bug every time I make a TNT cannon. It seems to have to do with having enough fire power. For example, 1 block of TNT will not break any blocks underwater, but 5 will break blocks underwater.
It's even on the picture for the snapshot on the Mojang website!
I've also been able to reproduce this many times by pushing a villager into a minecart, pushing the minecart off the rail, and breaking the minecart.
I didn't receive a black screen.
This also happens when the chat is open.
Confirmed in 1.7.2
seed: 5481915211951425789
x = 89
y = 52
z = 28
Flatland setting: 2;7,50x3,2;1;village
I've found a workaround for this issue. The underlying problem appears to be with XWayland. Using this repo (https://github.com/Admicos/minecraft-wayland/tree/one-nineteen , specifically the `one-nineteen` branch), and setting the JVM arguments to `-Dorg.lwjgl.glfw.libname=/usr/lib/libglfw.so`, I was able to patch GLFW to allow Minecraft to run using Wayland natively. After that, scrolling worked as expecting with Raw Input and Discrete Scrolling enabled. Switching back to the non-patched GLFW by removing the JVM arguments, the previous bugged behavior reappeared.