The "orca: command not found" line is probably not related to any of the issues, but I've just added orca as an optional dependency.
@cbjake your hint regarding the Preferences file made me dig deeper. For me it helped removing just the plasma integration extension:
# yq from go-yq package
yq eval -i -o json --prettyPrint 'del(.extensions.settings.cimiefiiaegbelhefglklhhakcgmhkai)' ~/.minecraft/webcache2/Default/Preferences
Does that help anyone else? The extension is automatically added again, so this has to be done everytime.
Pinned Comments
wheat32 commented on 2025-03-08 18:32 (UTC) (edited on 2025-03-08 19:30 (UTC) by wheat32)
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:
Edit: I found that deleting the webcache2 directory in the .minecraft directory fixes the issue for me.
petr commented on 2021-10-08 09:04 (UTC)
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.