mojira.dev
MCL-24924

Minecraft launcher works fine for second before showing ''Whoops! an error occurred'' message.

Launcher works fine for a second before showing a message that says ‘'Whoops! An unexpected issue occurred; we are sorry for the inconvenience. Please try restarting your Launcher. If that does not resolve the issue, please log a bug report HERE’' and a green button that says ‘'Try Again’', if I click the ‘'Try Again’' button it works for a second before showing the same message again, in that second, if I am fast enough, I can actually launch minecraft. I have uninstalled and re-installed multiple times and that did not change anything.

Linked issues

Attachments

Comments 29

Same here for the Linux version of the Launcher

Same here on Linux kernel 6.11.0-19-generic

Same problem here with Ubuntu based 24.04 distro

Workaround: Delete the webcache2 directory inside $HOME/.minecraft.

I uninstalled the launcher again and installed a windows legacy launcher and that works.

19 more comments

@Donuts1000 I posted the Log here already on “24/Jul/25 12:16 PM”

Try this:

  • Clear Launcher Cache Delete the .minecraft/webcache2 folder to reset the Chromium UI cache.

  • Also consider removing .minecraft/launcher_prefs.json and .minecraft/launcher_profiles.json to force regeneration.

@Donuts1000 Thanks a million!

Actually a simple rm -rf ~/.minecraft/webcache2/does the trick and in contrast to deleting the whole ~/.minecraft folder (which was my current workaround) that is much better because there is no need to re-login and re-download the full 500-600MB each time!

Still the problem exists, a second start in row while keeping the ẁebchache2 folder fails each time.

Same here on KDE neon 22.04 6.2

Hello. I encountered the same bug. The login attempt ends with a "whoops" error. I get an Xbox window where I select my account, and it gets stuck for almost a minute before the error.

Moreover, cleaning the specified folders isn't enough; I literally have to perform a clean install every time to log in. Killing the processes with PKILL -9 isn't enough either; I have to reboot the system.

After a successful login, when I restart the launcher, the launcher forgets about the login. I suspect the launcher is malfunctioning on KDE with the wallet disabled. I haven't encountered such problems on another Arch but DE "Cinnamon" installation.

Benjamin Smith

(Unassigned)

Community Consensus

Retrieved