mojira.dev

Crystal Soulslayer

Assigned

No issues.

Reported

View all
MC-78787 Exception_Access_Violation crash NOT related to graphics drivers Invalid

Comments

Uninstall  the launcher, download the .deb from the website, and let it auto-update. Worked for me.

I've been playing this game since 2011, first on Windows and now on Linux, and this is the first time I've ever had an issue with the launcher. That's pretty remarkable reliability for any kind of software. I'm guessing the issue came up from the process of getting the existing launcher to play nice with Microsoft's fancy-dancy login system across three platforms, which must have been quite a process. Hiccups are understandable.

Thanks to the team who sorted this out. I hope you guys get paid many emeralds. 🙂

Attempted to update via apt. It said there was an update, but it seems to be installing the same version again.

michelle@Minty:~$ sudo apt reinstall minecraft-launcher
The following packages will be REINSTALLED:
  minecraft-launcher 
0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/52.3 MB of archives. After unpacking 0 B will be used.
(Reading database ... 390789 files and directories currently installed.)
Preparing to unpack .../minecraft-launcher_2.1.9618_amd64.deb ...
Unpacking minecraft-launcher (2.1.9618) over (2.1.9618) ...
Setting up minecraft-launcher (2.1.9618) ...
Processing triggers for desktop-file-utils (0.23+linuxmint8) ...
Processing triggers for gnome-menus (3.13.3-11ubuntu1.1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for mime-support (3.60ubuntu1) ...

Uninstalled the launcher and tried the .deb. It gives its version as 1.1.26. Still having the same issue. I'm attaching my bootstrap-log (which I think is the installation log?) and launcher-log, which is still complaining about glibc 2.29.

I'm not sure whatever version is on the package repo is completely up-to-date, because it seems like this is an earlier version than the one available in this tracker. 2.1.9618 vs. 2.3.377. When I get the launcher to start, it always says there's an update available and links to the minecraft.net download page for Linux, even though that's an older version.

Edit: Okay, the update manager had an update for minecraft-launcher. This time, the launcher opened without me having to reinstall dependencies as I did before, but it's still not able to authorize a login and it's still version 2.1.9618.

Workaround for now: use a third-party launcher. Another user and I were able to get the vanilla launcher to start, but it isn't communicating correctly with Mojang's authentication servers. (Issue MCL-22271 if you're curious.)

I've been using PolyMC, which you can get right off the Mint 19 Software Manager. It works great. There are others, and they tend to have good wikis and/or YouTube videos to explain how to set them up. It takes a few minutes, but it's probably way easier than upgrading your entire OS version. 🙂

It seems the devs are assuming that, because these versions of Linux are long-term support, glibc and/or its parent library is backwards-compatible. For whatever reason, distro maintainers do not want the update installed on older systems. No idea why. But I remembered that I actually had this issue with glibc/libc6 earlier this year. A modding tool for Baldur's Gate: Enhanced Edition used the updated library version and I got it to work by downloading the tool's source code and compiling it on my own machine. (I'm a Linux n00b, so it was an adventure.) If that incident would be helpful to whoever's working on this problem, I can track down the related forum posts.

Hi there. I should have clarified--it has happened in modded Minecraft, but it also happens in vanilla on a fresh installation with no mods anywhere near it, and even to the launcher itself. Do I still need to create a new ticket?