[MCL-26160] The launcher keeps saying that "an unexpected issue has occurred!"

Every time i attempt to open the launcher it runs into an unexpected issue (deleting webcache2 temporarily fixes it; then the file just recreates/regenerates itself like nothing ever happened, so every time the launcher is launched, causing the issue again and again.)

Environment

SteamOS/Arch-Linux

Attachments

launcher_log.txt

launch erceer.txt

Comments 19

Redacted whisper 2025-12-07T12:27:07Z

How will i know when Mojang has even seen my bug report?

Redacted whisper 2025-12-09T18:40:11Z

[media]

di3g12 2025-12-13T17:24:35Z

re install the launcher. happened to me too and that worked fine

Redacted whisper 2025-12-14T12:15:15Z

Already tried that more then once

Redacted whisper 2025-12-14T12:15:25Z

Didn’t work

9 more comments

Redacted whisper 2025-12-14T15:07:15Z

[media]

di3g12 2025-12-14T15:09:00Z

I don’t know then. Sorry.

Redacted whisper 2025-12-15T00:15:25Z

If anyone reads this, message MCL-24881 might be of interest to you…

di3g12 2025-12-15T13:53:51Z

Hello!

Would be pleased if you please de-activated this bug report to avoid doubles.

Thanks!

-di3g12

Redacted whisper 2025-12-15T14:01:33Z

Aren’t doubles supposed to be added to a list? (Nobody on the bug tracker staff seems interested in doing that.)

Redacted whisper 2025-12-15T16:58:12Z

UPDATE: Deleted and reinstalled, and it’s now not even letting me sign in!

Redacted whisper 2025-12-15T17:51:14Z

UPDATE: I am now using a later version

Redacted whisper 2025-12-16T14:49:52Z

Okay, i don’t think i am actually using a later version (only reason i concluded that was cause' the loading screen changed from the copper golem, to husks riding the zombie camels, I don’t recall/know what they are called,) But regardless, the issue is still there, and likely NEVER going to be fixed as mojang clearly can’t figure it out, despite people straight up telling them what the problem is.

Redacted whisper 2025-12-17T19:47:24Z

P.S the preference file was what was causing it. deleting it, and stuffing a folder named the same in it’s place fixed the problem.

Redacted whisper 2025-12-18T20:16:52Z

…And now I have to deal with this nonsense!!!!!

Redacted whisper 2025-12-21T11:36:16Z

(…this latter part seems to have stopped, but it may or may not come back…)

Kroko 2025-12-28T21:52:02Z

How did you solved it? I didn’t understand what file you deleted

Redacted whisper 2025-12-30T17:49:29Z

The file is called “preferences” I deleted it, then I name a folder “preferences” and put the aforementioned folder in the place of the problematic file.

Redacted whisper 2025-12-30T17:50:54Z

The preferences file is located in the default folder, which itself is within webcache2