mojira.dev
MCL-12552

Dependency on default-jre in debian package breaks pre 1.13 minecraft installations

The deb writes "default-jre" as a dependency in the affected versions rather than the previously specified "oracle-java8-installer | openjdk-8-jre". default-jre depends on openjdk-11-jre.

As noted in another issue MCL-11767 this breaks use of versions of minecraft earlier than 1.13, with no trivial work around. If you are not depending on java 11, please revert this dependency to java 8 (I have confirmed that indeed you are not by temporarily alterning my java install).

Comments 22

It won’t let me play mineville city it says disconnected world please fix thing bug

Brian, that's completely unrelated. Create a new bug report if you think it's a bug.

This is a one-line change to fix. Is there any reason it's taken more than 6 weeks without movement?

Hi, Is there currently no way to launch versions prior to 1.13? Can I manually change the dependency to openjdk-8-jre? Do I have install Java 8 to do that?

You can edit the control file in the deb. You need to  change the dependency from "default-jre" to the previously used deps, "oracle-java8-installer | openjdk-8-jre".

In the absence of adequate support provided here, you can follow the instructions here. I used the ar approach (after "Rather than mess with permissions...") since it's simpler.

12 more comments

It's working for me with 1.15. Maybe Mojang will migrate to Java11 at some point, but they haven't yet.

It worked after I've done sudo apt purge openjdk-11-*. Thank you so much for your help and patience! You are absolutely the most helpful person I've met on the internet in my entire life!

No worries. Glad I could help.

The final issue that you saw is useful information, and I'm not sure how Mojang will deal with it when they get around to trying to fix this. Obviously openjdk-11-jre semantically conflicts with minecraft-launcher. The old way of dealing with this might have been to add a Conflicts: openjdk-11-jre to the deb control file. This is now necessary since many users will have unfortunately installed Java 11 because of the incorrect Depends: default-jre declaration; these all need to be fixed (at least for people who want to run older versions of Minecraft), but there is no automatic way to do this, and a Conflicts: declaration is pretty heavy handed (though the alternative of a Breaks: field is not possible since it has to be made in the breaker, not the breakee).

The only suggestion that I can make here is that the package should detect the presence of openjdk-11-jre during pre-inst and emit a warning to the user with instructions to remove that package. Maybe they should talk to a debian packager to understand how to get themselves out of the mess they have created.

Mojang, lyssnar ni inte?

This is still broken on the recently released 2.1.10835 version. This means that an upgrade from a manually fixed version as described above will break the user again. Thanks.

Note the default-jre in the Depends line here.

Package: minecraft-launcher
Version: 2.1.10835
Architecture: amd64
Maintainer: Petr Mrázek <[email protected]>
Description: Official Minecraft Launcher
Homepage: https://minecraft.net/
Pre-Depends: dpkg (>= 1.14.0), wget | curl, ca-certificates
Depends: default-jre, gconf-service, libasound2 (>= 1.0.23), libatk1.0-0 (>= 1.12.4), libc6 (>= 2.11), libcairo2 (>= 1.6.0), libcups2 (>= 1.4.0), libdbus-1-3 (>= 1.1.4), libexpat1 (>= 1.95.8), libfontconfig1 (>= 2.8.0), libgcc1 (>= 1:4.1.1), libgconf-2-4 (>= 2.31.1), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.26.0), libgtk2.0-0, libgtk-3-0 (>= 3.18.9), libnspr4 (>= 1.8.0.10), libnss3 (>= 3.17.2), libpango1.0-0 (>= 1.14.0), libstdc++6 (>= 4.8.0), libx11-6 (>= 2:1.4.99.1), libxcomposite1 (>= 1:0.3-1), libxcursor1 (>> 1.1.2), libxdamage1 (>= 1:1.1), libxext6, libxfixes3, libxi6 (>= 2:1.2.99.4), libxrandr2 (>= 2:1.2.99.3), libxrender1, libxss1, libxtst6, libx11-xcb1, libxcb1, libbz2-1.0, lsb-base (>= 4.1), xdg-utils (>= 1.0.2), wget, libcurl3 | libcurl4
Copyright: All rights reserved

Hi there!

Does this issue still occur on the newest version of the Launcher?
If yes, could you please write how to reproduce this issue in a manner written below?

Steps to Reproduce:

  1.  

  2.  

  3.  

Observed Results:

(Briefly describe what happens)

Expected Results:

(Briefly describe what should happen)

This ticket will automatically reopen when you reply.

Dan Kortschak

(Unassigned)

Unconfirmed

crash

Retrieved