thank you turcid! deleting plasma-browser-integration works for me. hopefully kde fixes that issue.
Search Criteria
Package Details: minecraft-launcher 1:2.1.3-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/minecraft-launcher.git (read-only, click to copy) |
---|---|
Package Base: | minecraft-launcher |
Description: | Official Minecraft Launcher |
Upstream URL: | https://mojang.com/ |
Keywords: | game minecraft |
Licenses: | custom |
Conflicts: | minecraft-launcher-beta |
Provides: | minecraft-launcher-beta |
Submitter: | shoghicp |
Maintainer: | pschichtel |
Last Packager: | pschichtel |
Votes: | 1105 |
Popularity: | 7.54 |
First Submitted: | 2017-01-18 14:17 (UTC) |
Last Updated: | 2025-03-22 14:57 (UTC) |
Dependencies (7)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classic-xfceAUR, gtk3-classicAUR, gtk3-patched-filechooser-icon-viewAUR)
- libgpg-error (libgpg-error-gitAUR)
- zlib (zlib-ng-compat-gitAUR, zlib-gitAUR, zlib-ng-compat)
- flite (flite1AUR) (optional) – narrator support
- orca (orca-gitAUR) (optional) – screen reader support
- org.freedesktop.secrets (gnome-keyring-gitAUR, pass-secrets-gitAUR, keepassxc-allow-aur-extension-originAUR, keepassxc-allow-aur-extension-origin-binAUR, bitw-gitAUR, keepassxc-qt6AUR, pass-secret-service-binAUR, keepassxc-gitAUR, dssdAUR, pass-secret-service-gitAUR, gnome-keyring, keepassxc, kwallet, kwallet5) (optional) – persistent login support
Sources (3)
archgirl commented on 2025-04-01 02:42 (UTC)
TotalPr0st commented on 2025-03-31 16:42 (UTC) (edited on 2025-03-31 16:46 (UTC) by TotalPr0st)
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
Veraxis commented on 2025-03-26 02:11 (UTC)
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.
turcid commented on 2025-03-23 20:19 (UTC)
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.
simonb commented on 2025-03-22 20:56 (UTC)
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.
pschichtel commented on 2025-03-22 15:55 (UTC)
I've reported this issue upstream:
pschichtel commented on 2025-03-22 15:30 (UTC)
Also can affected people check if they have the package plasma-browser-integration
installed?
pschichtel commented on 2025-03-22 15:21 (UTC) (edited on 2025-03-22 15:21 (UTC) by pschichtel)
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.
cbjake commented on 2025-03-22 14:59 (UTC)
Got the 'Whoops an unexpected error occurred', followed what wheat32 suggested and could get it to launch 1 time. Next launch same error. Did a bit more digging and found I only needed to delete $HOME/.minecraft/webcache2/Default/Preferences each time rather than the whole webcache2 folder.
archgirl commented on 2025-03-22 03:41 (UTC) (edited on 2025-03-22 04:44 (UTC) by archgirl)
EDIT #2: Nope. Not fixed... Closed the game and relaunched and now i'm getting: [*@archlinux ~]$ minecraft-launcher sh: line 1: orca: command not found Created browser window for reuse: 0x2c00004 terminate called after throwing an instance of 'std::bad_function_call' what(): bad_function_call
EDIT: Fixed after completely deleting all traces of minecraft-launcher and reinstalling.
Broken for me. When I launch minecraft-launcher it just opens up a window for chromium.
Here's the log: [*@archlinux ~]$ minecraft-launcher Opening in existing browser session. sh: line 1: orca: command not found
I did a clean install twice and keep getting the same issue.
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.