You were not teleported into the void, your video clearly shows that.
Version 2.1.13509 is affected too, but I can't add it to the field.
It doesn't Vladimir, because this one doesn't happen in 1.15.
That workaround works for me too, thank you so much Adrian!
Also this seems like it might make this quite an easy problem to find and fix for the devs.
Perhaps Mojang could consider keeping older versions of the launcher builds up: I tried editing the AUR build files to see if I have the same problem with a previous version, but couldn't because the build wasn't on Mojang's servers anymore.
The contents of launcher_log.txt are:
[Info: 2020-03-23 14:56:40.601268173: LauncherMain.cpp(84)] Initiated models
[Info: 2020-03-23 14:56:40.601301787: LauncherMain.cpp(211)] Running launcher core (version 2.1.13086)
[Info: 2020-03-23 14:56:40.602823047: LauncherMain.cpp(93)] Initiated launcher controller
[Info: 2020-03-23 14:56:40.603058865: LauncherMain.cpp(226)] Initialization completed
[Info: 2020-03-23 14:56:40.603193281: LauncherMain.cpp(249)] Main process: true
[Info: 2020-03-23 14:56:40.603218492: SentryAPI.cpp(322)] The string '/home/toon' was added to the logging blacklist
[Info: 2020-03-23 14:56:40.603225908: SentryAPI.cpp(322)] The string '///home/toon' was added to the logging blacklist
[Info: 2020-03-23 14:56:40.603229528: LauncherMain.cpp(295)] workDir: .../.minecraft
[Info: 2020-03-23 14:56:40.603237622: SentryAPI.cpp(322)] The string '/opt' was added to the logging blacklist
[Info: 2020-03-23 14:56:40.603241560: SentryAPI.cpp(322)] The string '///opt' was added to the logging blacklist
[Info: 2020-03-23 14:56:40.603244669: LauncherMain.cpp(303)] appDir: .../minecraft-launcherThat's from a different run, but looking at the file I doubt that makes a lot of difference.
Yes this is a duplicate of that one. Sorry!
I think I'm suffering from this in vanilla 1.17.1. Is that possible?