Arch Linux User Repository

I seem to be having a different issue than what others are describing. Suddenly today, I an unable to start the launcher without getting a generic "An unexpected issue occurred" message. Here's what I get in the terminal:

$ minecraft-launcher
sh: line 1: orca: command not found
Created browser window for reuse: 0x1600004
[34399:34552:0308/133050.212343:ERROR:mime_util_xdg.cc(137)] Invalid mime.cache file does not contain null prior to ALIAS_LIST_OFFSET=44
[34399:34552:0308/133055.416488:ERROR:cast_crl.cc(443)] CRL - Verification failed.

Edit: I found that deleting the webcache2 directory in the .minecraft directory fixes the issue for me.

The package version is the version of the launcher bootstrap - the part that actually downloads and updates the launcher.

That means the version number of the actual launcher (2.x.xxx) is different from the version here (9xx+) on a fundamental level, and should not be compared.

The package is outdated only when the bootstrap version you get here is different from the bootstrap version you would get from minecraft.net when using the raw tarball.

@ussur: That workaround is easy and good enough to integrate into the package, which I did in my latest change.

Somehow, if file .minecraft/webcache2/CEF_VERSION exists - it makes launcher fail to start. Launcher goes to "Whoops!" menu. If you delete that file - for some reason launcher starts being able to start. Btw that file's only contents are:

127.3.5+g114ea2a+chromium-127.0.6533.120

Also, for some reason, removing package plasma-browser-integration also fixes that issue with CEF_VERSION file.

Really weird issue, hope it gets fixed.

I just wanted to say that after having the same issue with the launcher not working as others have been having, I finally managed to fixed it by removing plasma-browser-integration. Thanks!

thank you turcid! deleting plasma-browser-integration works for me. hopefully kde fixes that issue.

Update: ftp.live.com had to be whitelisted in my network. I have found this error when trying to login on the first screen. an embeddet browser window pops up, flashes with the microsoft login ant turns grey, no interaction possible. deleting webcache2 folder makes no difference, also removing plasma-browser-integration does nothing. i heard a blocked domain on pihole like adblockers may be the issue for me but i wasnt able to find the correct to whitelist.

❯ minecraft-launcher
OK
Created browser window for reuse: 0x1c00004
terminate called after throwing an instance of 'std::bad_function_call'
  what():  bad_function_call
[48234:48267:0331/183153.289265:ERROR:cast_crl.cc(443)] CRL - Verification failed.
terminate called after throwing an instance of 'std::bad_function_call'
  what():  bad_function_call
Created browser window for reuse: 0x1c00016
[48234:48234:0331/183159.527834:ERROR:bad_message.cc(29)] Terminating renderer for bad IPC message, reason 213

I can confirm wheat32's problem with the "unexpected issue" error message and that deleting webcache2 also fixes it. The error comes back on the next launch and one must delete webcache2 every time one opens the launcher.

I checked and I do have plasma-browser-integration installed.

Can confirm that having plasma-browser-integration installed seems to break the launcher. However I think I have found the issue!

When plasma-browser-integration is installed, it puts the extension in /usr/share/chromium/extensions/cimiefiiaegbelhefglklhhakcgmhkai.json. This appears to let chromium browsers automatically install the extension. I looked through the logs for Minecraft (Specifically the log file ~/.minecraft/launcher_cef_log.txt) and found that the chrome browser that the Minecraft launcher uses was trying to load that extension. This seems to completely break the built-in web browser, preventing it from launching. I did also notice a similar file, /usr/share/google-chrome/extensions/cimiefiiaegbelhefglklhhakcgmhkai.json that was last changed on March 11 '25, which happens to be the latest update of the package, so maybe reverting is an option?

I'm not sure how to prevent it from auto installing that extension, but removing that file or uninstalling if you have no conflicts seems to be the best workaround for now.

Also can affected people check if they have the package plasma-browser-integration installed? Yes, in my case I do have the package 'plasma-browser-integration' installed.

I've reported this issue upstream:

• KDE: https://bugs.kde.org/show_bug.cgi?id=501866
• Mojang: https://report.bugs.mojang.com/servicedesk/customer/portal/2/MC-295726

Also can affected people check if they have the package plasma-browser-integration installed?