MrKinau

Seems like comments are working most of the time (for me), but there are no mails about state changes at all. There is no comment added to the issue once it’s fixed and I don’t receive any mail that the issue got closed/marked as done, like before the migration.

Thx for your answer, I really appreciate this good communication ❤️

Yeah as said the fallback is working (and honestly for most affected players even better than making OpenGL work xD), but thanks for describing the issue, your testing and test results 👍

Yes, the game no longer crashes 26.3 pre1 and later, but OpenGL is still no longer available. The game automatically selects Vulkan now. I’ve also tested with a laptop with a NVIDIA GTX 1050 as well as integrated intel graphics, OpenGL seems to work on the integrated graphics, but not on the dedicated GPU.

Imo Vulkan is the far better option, but as it was possible to use OpenGL in the past it should theoretically still work, but currently does not. Just to let you know OpenGL is still not working (same error), but the game now automatically switches to Vulkan.

Attached another log of 26.3-pre2 from my main PC (NVIDIA GTX 1080), just in case you want to fix OpenGL, but imo the current state with Vulkan only is fine for me (ig it only affects a handful of legacy GPUs anyways).

The behavior changed with 26.3 Snapshot 9, instead of not spawning a window the game crashes with the attached crashlog.

This issue is fixed with the newly released changes to the online button from 26.2 Snapshot 6

Hi,

I did receive mails for this issue (2 from two previous comments). I can’t explain why I receive mails for this issue, but not for others (maybe it’s because the other issues are within the MC project and not the WEB project?)

I’ve just looked at some issues I definitely had notifications on. One mentionable would be MC-307140 where in my previous screenshot of my mails it’s visible I had notifications on as I got a mail for the added comment on 01/04/2026 but not for the status change and automated comment from 31/03/2026 (and I don’t remember toggling them on between those dates).

On the right hand side in the panel Notifications for both those example issues are turned on, like in my second screenshot.

Although MC-307623 is resolved, this is not fixed with 26.2 snapshot 5

On my machine (only issue when closing after onboarding accessibility) the issue got resolved with snapshot 3, thx.
But I can’t speak for Aleksa Mezei, maybe it’s fixed for you as well?

Correct server download can be found here: https://piston-data.mojang.com/v1/objects/5f2e44493daf3cd4ab757e59921313c9c8d95151/server.jar

From piston meta: https://piston-meta.mojang.com/v1/packages/f8ce00355c7535323ad546f1f702e3aaaa48a99a/26.2-snapshot-3.json

Can confirm, maybe duplicate as this was intended to be fixed as MC-307286 is marked as resolved.

It is definitely better, it’s not happening all the time, but it is still happening on the first launch with a clean installation, I tested a bit around it seems to happen every time the onboarding screen is shown.

Steps to Reproduce

1. Modify the file options.txt: set onboardAccessibility:true or use a clean installation without any previous options.txt

2. Start the game

3. Click Continue in the onboarding screen.

4. Click Quit Game and see the process still running

Observed Beahvior

The process never ends, unless terminated manually using a signal.

Expected Behavior

The process ends after quitting the game.

Video

Another issue I’ve noticed, which seemingly is caused by the same unknown root cause is that chunk loading is pretty slow. Initial spawn chunk loading is fine, but after reloading chunks only the chunks directly around the player load properly and every other chunk takes very long to load or will only load after I looked around or moved. This feels pretty much the same as with the blocks not disappearing as they usually disappear when moving the mouse again, and this issue got introduced in 26.1-snapshot-7 as well.

I can confirm the Vulkan behavior in fullscreen is quite different from the behavior of OpenGL, I don’t have the same issues, but I do have significantly lower FPS when in fullscreen with Vulkan (except when something else like a desktop notification renders on top of the fullscreen window), regardless if it is exclusive fullscreen or not. I can’t see any difference between window manager fullscreen mode and just pressing F11.
Dunno if this is just a hidden KWin/KDE/Wayland/whatever feature or an actual bug.

Side note: Monitor only has 60Hz

boolean chatDisabledOrBlocked = minecraft.player.chatAbilities().canReceivePlayerMessages() || socialManager.isBlocked(id);

should be obvious whats wrong here 😅

Just tested on my Laptop with Ubuntu 25.10 and Mesa with Intel UHD Graphics 630, bug occurs, but looks like it’s happening less often.

Can confirm for 26.1-pre-1

same on X11