Deleting 'plasma-browser-integration' fixes "An unexpected issue has occurred"
Search Criteria
Package Details: minecraft-launcher 1:2.1.3-3
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: | 1133 |
| Popularity: | 5.51 |
| First Submitted: | 2017-01-18 14:17 (UTC) |
| Last Updated: | 2025-04-19 12:06 (UTC) |
Dependencies (7)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc-libs-snapshotAUR)
- gtk3 (gtk3-classic-xfceAUR, gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-patched-filechooser-icon-viewAUR)
- libgpg-error (libgpg-error-gitAUR)
- zlib (zlib-gitAUR, zlib-ng-compat-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-gitAUR, dssdAUR, pass-secret-serviceAUR, pass-secret-service-gitAUR, keepassxc-qt6AUR, himitsu-secret-serviceAUR, kwallet-gitAUR, pass-secret-service-binAUR, gopass-secret-serviceAUR, rosec-binAUR, rosec-gitAUR, keepasschi-gitAUR, gnome-keyring, keepassxc, kwallet) (optional) – persistent login support
Sources (4)
joeswanson commented on 2026-02-09 04:12 (UTC)
kiwiarch commented on 2026-01-24 10:26 (UTC) (edited on 2026-01-24 10:29 (UTC) by kiwiarch)
launcher just hangs.
Created browser window for reuse: 0x600004
terminate called after throwing an instance of 'std::bad_function_call'
what(): bad_function_call
[175107:175156:0124/232503.438061:ERROR:ffmpeg_common.cc(965)] Unsupported pixel format: -1
terminate called after throwing an instance of 'std::bad_function_call'
what(): bad_function_call
terminate called after throwing an instance of 'std::bad_function_call'
what(): bad_function_call
terminate called after throwing an instance of 'std::bad_function_call'
what(): bad_function_call
terminate called after throwing an instance of 'std::bad_function_call'
what(): bad_function_call
[174961:175004:0124/232507.953750:ERROR:cast_crl.cc(443)] CRL - Verification failed.
Created browser window for reuse: 0x600016
terminate called after throwing an instance of 'std::bad_function_call'
what(): bad_function_call
I have tried deleting the webcache2 as in the previous comment. Still the same issue I have also tried reinstalling the launcher
pokexpert commented on 2025-11-06 10:56 (UTC)
I am unable to login into my micorosft account, it seems to be a 400 error on microsoft part. Once i enter my password, i get :
Please retry with a different device or other authentication method to sign in. For more details, please see this link
On windows it also affects the "legacy launcher", using the windows 11/10 launcher and logging in via the xbox app works.
Looking around in the log, i see various errors but this one seems to be the most important :
login_xxxxxxxx.js(1)] OnConsoleMessage: Uncaught (in promise) Error: Error with conditional UI:SecurityError: The relying party ID is not a registrable domain suffix of, nor equal to the current domain.
Using prism launcher works, maybe this official launcher is deprecated?
S.Lijmerd commented on 2025-10-30 09:44 (UTC) (edited on 2025-10-30 09:46 (UTC) by S.Lijmerd)
@EsGeh: These are not problems with the package.
-
To have persistent login support you need to install any of the password services that are clearly stated under "Dependencies" as "persistent login support" in both the AUR entry and the PKGBUILD.
-
This is a problem with the launcher, not the package. Multiple people in the comments seem to have already posted solutions for other people with similar problems below. Though from skimming the logs I suspect it might related to not having a password service installed. If you don't find a solution the arch wiki entry for minecraft has a list of alternative 3rd party launchers (intended for mods, but perfectly fine for vanilla as well).
EsGeh commented on 2025-10-11 08:22 (UTC)
Problems with this package:
- I have to log in to the microsoft account with username & password every fucking time!
- Sometimes indeterministically, after login, the program hangs and does not start the launcher
Deleting rm -rf ~/.minecraft/launcher doesn't solve anything.
This is what is printed in the console when the launcher successfully starts after login:
$ minecraft-launcher
OK
sh: Zeile 1: orca: Kommando nicht gefunden
Created browser window for reuse: 0x1800003
[11994:11994:1011/095648.182074:ERROR:browser_main_loop.cc(280)] Gdk: _gdk_frame_clock_freeze: assertion 'GDK_IS_FRAME_CLOCK (clock)' failed
[11994:12119:1011/095648.250562:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
[11994:12119:1011/095648.250707:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
[11994:12119:1011/095648.250808:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
[12061:12126:1011/095648.965613:ERROR:ffmpeg_common.cc(965)] Unsupported pixel format: -1
Created browser window for reuse: 0x1800015
[11994:11994:1011/100212.757742:ERROR:browser_main_loop.cc(280)] Gdk: _gdk_frame_clock_freeze: assertion 'GDK_IS_FRAME_CLOCK (clock)' failed
[11994:11994:1011/100236.909165:ERROR:atom_cache.cc(229)] Add chromium/x-source-url to kAtomsToCache
[11994:11994:1011/100238.842842:ERROR:browser_main_loop.cc(280)] Gdk: _gdk_frame_clock_thaw: assertion 'GDK_IS_FRAME_CLOCK (clock)' failed
Created browser window for reuse: 0x180001c
[11994:11994:1011/100242.812327:ERROR:browser_main_loop.cc(280)] Gdk: _gdk_frame_clock_freeze: assertion 'GDK_IS_FRAME_CLOCK (clock)' failed
[11994:11994:1011/100257.222805:ERROR:browser_main_loop.cc(280)] Gdk: _gdk_frame_clock_thaw: assertion 'GDK_IS_FRAME_CLOCK (clock)' failed
[12061:12126:1011/100316.573977:ERROR:ffmpeg_common.cc(965)] Unsupported pixel format: -1
[11994:11994:1011/101258.850134:ERROR:browser_main_loop.cc(280)] Gdk: _gdk_frame_clock_thaw: assertion 'GDK_IS_FRAME_CLOCK (clock)' failed
This is what is printed in the console when it hangs after login:
$ minecraft-launcher
sh: Zeile 1: orca: Kommando nicht gefunden
Created browser window for reuse: 0x1600003
[13124:13124:1011/101306.656195:ERROR:browser_main_loop.cc(280)] Gdk: _gdk_frame_clock_freeze: assertion 'GDK_IS_FRAME_CLOCK (clock)' failed
[13124:13254:1011/101306.724576:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
[13124:13254:1011/101306.725385:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
[13124:13254:1011/101306.725543:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
[13196:13260:1011/101307.453257:ERROR:ffmpeg_common.cc(965)] Unsupported pixel format: -1
Created browser window for reuse: 0x1600015
[13124:13124:1011/101322.468087:ERROR:browser_main_loop.cc(280)] Gdk: _gdk_frame_clock_freeze: assertion 'GDK_IS_FRAME_CLOCK (clock)' failed
[13124:13124:1011/101413.532258:ERROR:atom_cache.cc(229)] Add chromium/x-source-url to kAtomsToCache
[13124:13124:1011/101414.690140:ERROR:browser_main_loop.cc(280)] Gdk: _gdk_frame_clock_thaw: assertion 'GDK_IS_FRAME_CLOCK (clock)' failed
Created browser window for reuse: 0x160001c
[13124:13124:1011/101418.851841:ERROR:browser_main_loop.cc(280)] Gdk: _gdk_frame_clock_freeze: assertion 'GDK_IS_FRAME_CLOCK (clock)' failed
[13124:13124:1011/101430.589425:ERROR:browser_main_loop.cc(280)] Gdk: _gdk_frame_clock_thaw: assertion 'GDK_IS_FRAME_CLOCK (clock)' failed
syndromeimpostor commented on 2025-09-03 23:52 (UTC)
For me, the launcher needed fpt.live.com (not ftp)
If you're running pihole or another DNS blocker, you'll have to whitelist the domain.
pschichtel commented on 2025-04-19 12:07 (UTC)
@ussur: That workaround is easy and good enough to integrate into the package, which I did in my latest change.
ussur commented on 2025-04-19 11:04 (UTC)
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.
delve commented on 2025-04-12 00:39 (UTC)
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!
archgirl commented on 2025-04-01 02:42 (UTC)
thank you turcid! deleting plasma-browser-integration works for me. hopefully kde fixes that 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.