mojira.dev
MCL-11234

I can't change my profile's version in linux (Debian)

I tried to change the version in profile from 1.14.2 to 1.8.9, but it didn't work AT ALL!

Linked issues

Comments 16

Please provide the details. In which way did it not work? What happened when you tried?

Well I updated the launcher, I clicked on 'Installations' tab and clicked my profile, and the profile menu appears so I clicked the version dropdown menu and finally clicked 1.8.9 (which is NOT the same version as I've set before), but 1.14.2 (which is the same version as I've set before) is still there in version dropdown menu.

On 2.1.5419 for Debian 9, can't change the version in profile as well.

On the Play tab, to the left of the giant green PLAY button, there is a drop down that has all of the profiles listed that are defined.

Using a mouse to drop down and click on an entry, DOES NOT change the selected profile to the one clicked on.

It ONLY works if you use the keyboard to select the profile and hit Enter.

So, to summarize, the code to handle the mouse click that selects the item from the drop-down list does not result in a change to the selected profile.

 

Probably just got missed in the testing for the new launcher and they can fix for future release.  Until then, you can use the arrow keys as a work around. 🙂

6 more comments

beta seems to have fixed it. I can now change versions

Seems to work, though now getting Launcher update notification. Maybe a ordered inequality should be used for version comparison; 2.1.7658 (the beta's version) > 2.1.5965, yet that is what it points to.

 

Instructions for debian are still incorrect. apt-get does not handle direct install of deb files.

In addition to that minor problem, it continues running after launching minecraft and burns 100% cpu while it's doing it.

A further additional problem is that the beta brings a dependency on java 11, which has issue running some versions of the game. For example, attempting to run 1.12.2 from beta-2.1.7658 results in the following crash

Inconsistency detected by ld.so: dl-lookup.c: 111: check_match: Assertion `version->filename == NULL || ! _dl_name_match_p (version->filename, map)' failed!
 Process crashed with exit code 127

This is apparently a known OpenJDK java 11 issue.

beta 2.1.9080 fixes the 100% cpu burn issue, though the ld.so fault still exists.

Maplra

(Unassigned)

Unconfirmed

Retrieved