0xEARTH
- EarthToAccess
- earthtoaccess
- America/New_York
- Yes
- No
Out of the blue, my Minecraft starts to display these odd white lines, that almost seem like the Wither shield, across my screen. There's also random colored "noise" all over it, almost like dead pixels. This happened shortly after joining my Realm post-1.14 update.
I'd like to be able to post some form of steps-to-repro, but quite frankly I don't know how or why this happened to me to start. It happens in every perspective, and doesn't go away on death. Leaving and rejoining doesn't help either. It also does not go over any GUI, and happens in any gamemode.
Out of the blue, my Minecraft starts to display these odd white lines, that almost seem like the Wither shield, across my screen. There's also random colored "noise" all over it, almost like dead pixels. This happened shortly after joining my Realm post-1.14 update.
I'd like to be able to post some form of steps-to-repro, but quite frankly I don't know how or why this happened to me to start. It happens in every perspective, and doesn't go away on death. Leaving and rejoining doesn't help either. It also does not go over any GUI, and happens in any gamemode.
Edit:// I'm willing to mark this closed since it randomly fixed itself today, and therefore can't help in fixing a problem that no longer exists. I hope, however, that this is something that will have an eye out for, since it was very odd and random.
Out of the blue, my Minecraft starts to display these odd white lines, that almost seem like the Wither shield, across my screen. There's also random colored "noise" all over it, almost like dead pixels. This happened shortly after joining my Realm post-1.14 update.
I'd like to be able to post some form of steps-to-repro, but quite frankly I don't know how or why this happened to me to start. It happens in every perspective, and doesn't go away on death. Leaving and rejoining doesn't help either. It also does not go over any GUI, and happens in any gamemode.
Edit:// I'm willing to mark this closed since it randomly fixed itself today, and therefore can't help in fixing a problem that no longer exists. I hope, however, that this is something that will have an eye out for, since it was very odd and random.
Edit Apr 28:// The issue has returned. An updated image is below, next to the other. I should point out that no errors occur in the launcher when this happens.
Out of the blue, my Minecraft starts to display these odd white lines, that almost seem like the Wither shield, across my screen. There's also random colored "noise" all over it, almost like dead pixels. This happened shortly after joining my Realm post-1.14 update.
I'd like to be able to post some form of steps-to-repro, but quite frankly I don't know how or why this happened to me to start. It happens in every perspective, and doesn't go away on death. Leaving and rejoining doesn't help either. It also does not go over any GUI, and happens in any gamemode.
Edit:// I'm willing to mark this closed since it randomly fixed itself today, and therefore can't help in fixing a problem that no longer exists. I hope, however, that this is something that will have an eye out for, since it was very odd and random.
Edit Apr 28:// The issue has returned. An updated image is below, next to the other. I should point out that no errors occur in the launcher when this happens.
Edit Apr 28 (2):// After copying /home/$USER/.minecraft to another folder (/home/$USER/.minecraft\ copy), and running a second account on the same Realm, I've confirmed that it seems to only be that instance of Minecraft.
Out of the blue, my Minecraft starts to display these odd white lines, that almost seem like the Wither shield, across my screen. There's also random colored "noise" all over it, almost like dead pixels. This happened shortly after joining my Realm post-1.14 update.
I'd like to be able to post some form of steps-to-repro, but quite frankly I don't know how or why this happened to me to start. It happens in every perspective, and doesn't go away on death. Leaving and rejoining doesn't help either. It also does not go over any GUI, and happens in any gamemode.
Edit:// I'm willing to mark this closed since it randomly fixed itself today, and therefore can't help in fixing a problem that no longer exists. I hope, however, that this is something that will have an eye out for, since it was very odd and random.
Edit Apr 28:// The issue has returned. An updated image is below, next to the other. I should point out that no errors occur in the launcher when this happens.
Edit Apr 28 (2):// After copying /home/$USER/.minecraft to another folder (/home/$USER/.minecraft\ copy), and running a second account on the same Realm, I've confirmed that it seems to only be that one instance of Minecraft.
When a game has been launched on one Microsoft account, and you attempt to open the game in a second account, it will report the second account does not own Minecraft: Java Edition.
It should be noted that it does not impede the ability to play. You can still hit "Play Demo" and the game will open and authorize normally without problem, provided you're logged in with the correct account.
Specific steps to reproduce;
- Open the Launcher and log into any account.
- Hit play to start the game.
- Re-open (or switch to) the Launcher, and switch accounts.
Your Launcher should now instruct you to play in the Demo, or to buy the full game. Again, this does not impede playability, and users can still open the game normally.
This happens even after logging out of and restarting the Launcher entirely.
Edit: It's come to my attention that this may be either a duplicate of [
MCL-19984|https://bugs.mojang.com/projects/MCL/issues/MCL-19984;] however, this also specifically states a potential cause.
When a game has been launched on one Microsoft account, and you attempt to open the game in a second account, it will report the second account does not own Minecraft: Java Edition.
It should be noted that it does not impede the ability to play. You can still hit "Play Demo" and the game will open and authorize normally without problem, provided you're logged in with the correct account.
Specific steps to reproduce;
- Open the Launcher and log into any account.
- Hit play to start the game.
- Re-open (or switch to) the Launcher, and switch accounts.
Your Launcher should now instruct you to play in the Demo, or to buy the full game. Again, this does not impede playability, and users can still open the game normally.
This happens even after logging out of and restarting the Launcher entirely.
Edit: It's come to my attention that this may be either a duplicate of [
MCL-19984|https://bugs.mojang.com/projects/MCL/issues/MCL-19984;] however, this also specifically states a potential cause.When a game has been launched on one Microsoft account, and you attempt to open the game in a second account, it will report the second account does not own Minecraft: Java Edition.
It should be noted that it does not impede the ability to play. You can still hit "Play Demo" and the game will open and authorize normally without problem, provided you're logged in with the correct account.
Specific steps to reproduce;
- Open the Launcher and log into any account.
- Hit play to start the game.
- Re-open (or switch to) the Launcher, and switch accounts.
Your Launcher should now instruct you to play in the Demo, or to buy the full game. Again, this does not impede playability, and users can still open the game normally.
This happens even after logging out of and restarting the Launcher entirely.
Edit: It's come to my attention that this may be either a duplicate of [
MCL-19984|https://bugs.mojang.com/projects/MCL/issues/MCL-19984]; however, this also specifically states a potential cause.
When a game has been launched on one Microsoft account, and you attempt to open the game in a second account, it will report the second account does not own Minecraft: Java Edition.
It should be noted that it does not impede the ability to play. You can still hit "Play Demo" and the game will open and authorize normally without problem, provided you're logged in with the correct account.
Specific steps to reproduce;
- Open the Launcher and log into any account.
- Hit play to start the game.
- Re-open (or switch to) the Launcher, and switch accounts.
Your Launcher should now instruct you to play in the Demo, or to buy the full game. Again, this does not impede playability, and users can still open the game normally.
This happens even after logging out of and restarting the Launcher entirely.
Edit: It's come to my attention that this may be either a duplicate of
[MCL-19984|https://bugs.mojang.com/projects/MCL/issues/MCL-19984]; however, this also specifically states a potential cause.
When a game has been launched on one Microsoft account, and you attempt to open the game in a second account, it will report the second account does not own Minecraft: Java Edition.
It should be noted that it does not impede the ability to play. You can still hit "Play Demo" and the game will open and authorize normally without problem, provided you're logged in with the correct account.
Specific steps to reproduce;
- Open the Launcher and log into any account.
- Hit play to start the game.
- Re-open (or switch to) the Launcher, and switch accounts.
Your Launcher should now instruct you to play in the Demo, or to buy the full game. Again, this does not impede playability, and users can still open the game normally.
This happens even after logging out of and restarting the Launcher entirely.
Edit: It's come to my attention that this may be
eithera duplicate of MCL-19984; however, this also specifically states a potential cause.
When a game has been launched on one Microsoft account, and you attempt to open the game in a second account, it will report the second account does not own Minecraft: Java Edition.
It should be noted that it does not impede the ability to play. You can still hit "Play Demo" and the game will open and authorize normally without problem, provided you're logged in with the correct account.
Specific steps to reproduce;
- Open the Launcher and log into any account.
- Hit play to start the game.
- Re-open (or switch to) the Launcher, and switch accounts.
Your Launcher should now instruct you to play in the Demo, or to buy the full game. Again, this does not impede playability, and users can still open the game normally.
This happens even after logging out of and restarting the Launcher entirely.
Edit: It's come to my attention that this may be a duplicate of
MCL-19984; however, this also specifically states a potential cause.When a game has been launched on one Microsoft account, and you attempt to open the game in a second account, it will report the second account does not own Minecraft: Java Edition.
It should be noted that it does not impede the ability to play. You can still hit "Play Demo" and the game will open and authorize normally without problem, provided you're logged in with the correct account.
Specific steps to reproduce;
- Open the Launcher and log into any account.
- Hit play to start the game.
- Re-open (or switch to) the Launcher, and switch accounts.
Your Launcher should now instruct you to play in the Demo, or to buy the full game. Again, this does not impede playability, and users can still open the game normally.
This happens even after logging out of and restarting the Launcher entirely.
Edit: It's come to my attention that this may be a duplicate of
MCL-19984; however, this also specifically states a potential cause.


bump
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.
Player from the Linux version here. Tried this fix, among others, and it doesn't work for me.
The comments section of that article are saying that it still hasn't been fixed, regardless of what the "resolution" says at the top.
Nope, using the US QWERTY keyboard layout, but I am on Ubuntu 18.04
Not entirely sure what you mean by that. Can you elaborate for me?
Out of curiosity, is there any way to continue with the "workaround" fix? Albeit unsupported I'm attempting to install and play Minecraft on a Windows XP system. I can't use 1.6.93 because it requires Java 8, which is incompatible with Windows XP, and the new launcher simply fails to run ("Unable to start Minecraft Runtime Environment" error keeps popping up).I can't seem to get the "fixed" version showing in the launcher settings. (I should mention I am trying it on 20w13b.)
Yea, I know. I personally have been using Ubuntu for a while and I've got a Windows 10 computer, I'm just messing with Windows XP on a virtual machine and wanted to see if Minecraft runs well enough on it. I'm fairly certain it would, but I can't get it to actually open because of the launcher issue. Using new software etc. is definitely viable as I already am using said software and hardware, I just wanted to know if it was possible so I could potentially mess with things.
also confirmed for 20w15a, legit had them right next to me and they're gone without anything else–we're talking master level, too.
can confirm; it doesn't happen just with Advanced Tooltips though.
gonna have to contest that, we just got hit with it and we haven't upgraded to 20w21a or later.
confirmed for 1.16 pre4
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.
this definitely is not resolved, and hasn't been for a while. i have no clue why it's marked as resolved.
this bug still affects 1.17
can confirm in 21w37a
can confirm for 21w38a.
what angle is it supposed to be fixed for? every test i've run shows it still happens in 38a.
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
can confirm for 21w39a.
I would like to add a vote to this and re-open it.
MCL-20048and this ticket are two separate issues entirely, the former being about the lack of an "Add Accounts" feature making the process long and tedious, and the latter is regarding an actual authorization problem from within the Launcher itself. They are not the same issue by any means, a very minor exception being that they both deal with multiple accounts.Once again bumping this, as this and
MCL-20048are different.I'd like to get
MCL-20705unlinked as a duplicate of this, as it isn't.MCL-20705is 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.confirmed in 1.20rc-1