I'd like to get MCL-20705 unlinked as a duplicate of this, as it isn't. MCL-20705 is talking about how having two instances of Minecraft running with the new launcher causes it to report you don't own the game; this one is asking about the add/switch account feature. They're two entirely different issues.
can confirm for 21w39a.
ah, so it's only a very slight angle. that explains why i couldn't replicate it, i don't have the time nor patience to be that exact lmao
what angle is it supposed to be fixed for? every test i've run shows it still happens in 38a.
can confirm for 21w38a.
can confirm in 21w37a
this bug still affects 1.17
this definitely is not resolved, and hasn't been for a while. i have no clue why it's marked as resolved.
CR on Minecraft 1.16.4 running Java 8.0_51-b16 on Windows 10 Pro 20H2.
i've got an 8x AMD Ryzen 5 3400G processor and an 8gb Radeon RX 580 card. according to [this StackOverflow page with a similar runtime error|https://stackoverflow.com/questions/25406681/jvm-crash-exception-access-violation], it could possibly be an issue with Java and DirectX, as their responses are to un- and re-install the graphics drivers, disable any card utilities, or to use JVM arguments to disable DirectX.
regardless, i vote to close this as it doesn't seem to specifically be a Minecraft issue–this looks to be specifically Java, which can't be fixed with a Minecraft update.
confirmed for 1.16 pre4
gonna have to contest that, we just got hit with it and we haven't upgraded to 20w21a or later.
can confirm; it doesn't happen just with Advanced Tooltips though.
also confirmed for 20w15a, legit had them right next to me and they're gone without anything else–we're talking master level, too.
Not entirely sure what you mean by that. Can you elaborate for me?
Nope, using the US QWERTY keyboard layout, but I am on Ubuntu 18.04
The comments section of that article are saying that it still hasn't been fixed, regardless of what the "resolution" says at the top.
Player from the Linux version here. Tried this fix, among others, and it doesn't work for me.
This seems like an issue regarding the server's host, and not your Minecraft client. Can you do us a favor- close Minecraft completely (including the launcher). Then, go into your launcher settings and make it so that the launcher stays open when Minecraft launches, and try to reconnect to the server. Give a screenshot of what error the launcher returns, if it still doesn't work.
bump
confirmed in 1.20rc-1