I would like to request this to be reopened. I am on a Gentoo machine (OpenRC) encountering this exact same sequence of error messages as of today, when using a fresh download of the generic Linux Minecraft launcher binary from https://www.minecraft.net/en-us/download .
A preview of stdout show that it is nearly identical:
https://launchermeta.mojang.com/v1/products/launcher/6f083b80d5e6fabbc4236f81d0d8f8a350c665a9/linux.json
[0830/043014.088271:INFO:main_context.cpp(130)] CEF initialized successfully.
[0830/043014.088310:INFO:main_context.cpp(132)] CEF version: 99.2.14+g3f796b8+chromium-99.0.4844.84
sh: line 1: orca: command not found
Created browser window for reuse: 0x3600002
[0830/043014.150985:ERROR:browser_main_loop.cc(268)] Gdk: _gdk_frame_clock_freeze: assertion 'GDK_IS_FRAME_CLOCK (clock)' failed
[0830/043044.434315:INFO:CONSOLE(2)] "LauncherError: Account context took too long to request account information.", source: mojang://launcher/static/js/app.1bced5cc.bundle.js (2)
terminate called after throwing an instance of 'std::bad_function_call'
what(): bad_function_call
The launcher itself takes about 20-30 minutes to initialize on a machine on which it previously took <0.5 seconds. Worse, the game itself takes even longer–upwards of one hour.
The same message sequence gets printed to stdout consistently, even when I tried redownloading the binary and also running:
rm -rf ~/.minecraft
About the only other help I can offer is that I use a utility to constantly track my PC's data upload/download rates. As the launcher does its thing, this utility shows that transfer is at 0kBup/0kBdown for almost the entirety of the 10 minutes; if I open a web browser window and start streaming a video, transfer jumps way up..so the problem is definitely not related a slow transfer speed. Something else is making the launcher RIDICULOUSLY slow but somehow functional. And my PC has not changed since the last time I used Minecraft, which would have been a few weeks ago.
EDIT: Wanted to add one more detail, possibly useful.. Once the launcher actually finally started data transfer, it did not take long for the game to start. It seemed to get hung up on parts of the initialization
Yes, glitches persist in both fullscreen and windowed mode
Edited the original post to clarify that this does not cause a crash - just a visual bug
I have replicated multiple times with different file manager applications, but this does not ever crash the game or result in any error output to game logs–just the visual issue shown in the provided video. I believe the crash at the end of the video is just the result of me force-closing the Minecraft window. I do not have a ~/.minecraft/crash-reports
directory.
I have uploaded the latest game log anyways after trying this, i.e. ~/.minecraft/logs/latest.log
.
Sure. I will link a resource pack here called PACK1.
http://www.mediafire.com/file/lg2062hbnk1zfyp/PACK1.rar
In the resource pack, I've replaced the texture for the diamond hoe with Damage: 1561 (supposedly Unbreakable as well, but as indicated in my post, the "damaged" predicate is ignored) with a texture called "forgery"
Request to reopen this please. Still getting the exact same error and launcher_log.txt when I download the latest version of the Linux minecraft-launcher binary from https://launcher.mojang.com/download/Minecraft.tar.gz. The issue that this was said to be a duplicate of has a workaround solution that only applies to Windows machines; thus, this is not the same issue.