From: kotajacob <kotajacob@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package Issue: multiMC
Date: Wed, 15 Sep 2021 09:34:50 +0200 [thread overview]
Message-ID: <20210915073450.m7o2j7PgSz1dlgfI3fssWGofcFmEmzLeqDq0vaBwJFo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32950@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1730 bytes --]
New comment by kotajacob on void-packages repository
https://github.com/void-linux/void-packages/issues/32950#issuecomment-919774064
Comment:
I've had issues in the past with very old versions of minecraft not working properly on newer java versions. In this case you're probably just missing graphics drivers like @Hnaguski said, but you can try launching the 1.8.9 instance with an older jdk. Here's a screenshot of [my beta 1.7.3 instance configured to use openjdk-8](https://paste.nilsu.org/91b5ead8b4bb8f647103fda5397d09055c5c7bd7.webp). You need to install the `openjdk-8` package for that to work.
Ultimately it's looking like the MultiMC package might need to be removed anyway. The [upstream license doesn't permit using the logo or name](https://github.com/MultiMC/MultiMC5/issues/4102) in packages such as ours 🙃. So the only way MultiMC can continue to be packaged is if we forked and renamed it. It's a mess, for now you're best off downloading a [procompiled binary it from their website](https://multimc.org/#Download), installing `qt5-svg`, and downloading the latest java manually like @Hnaguski suggested (or waiting on our package to be updated).
Normally you'd want to extract the MultiMC tar somewhere like `~/.local/opt/` and then link the executable to your local bin with `ln -s ~/.local/opt/MultiMC/MultiMC ~/.local/bin/MultiMC`. You could also create a `multimc.desktop` file in `~/.local/share/applications/` with the following if you want it to show up in most desktop environment launchers:
```desktop
[Desktop Entry]
Version=1
Type=Application
Name=minecraft
GenericName=Minecraft
Comment=Game
Exec=/home/<Your Username>/.local/opt/MultiMC/MultiMC
Actions=
Categories=Game;
```
next prev parent reply other threads:[~2021-09-15 7:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 15:05 [ISSUE] " apirusKde
2021-09-13 15:32 ` apirusKde
2021-09-13 15:32 ` apirusKde
2021-09-13 18:11 ` Hnaguski
2021-09-13 18:44 ` Hnaguski
2021-09-14 12:25 ` apirusKde
2021-09-15 0:07 ` apirusKde
2021-09-15 3:37 ` Hnaguski
2021-09-15 7:34 ` kotajacob [this message]
2021-09-15 23:42 ` ImperatorStorm
2021-09-15 23:42 ` ImperatorStorm
2021-09-16 12:10 ` Duncaen
2021-09-16 12:11 ` Duncaen
2021-09-16 20:24 ` Hnaguski
2021-09-19 7:26 ` fosslinux
2021-09-19 7:31 ` fosslinux
2021-09-23 22:04 ` apirusKde
2021-10-11 12:41 ` [ISSUE] [CLOSED] " apirusKde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210915073450.m7o2j7PgSz1dlgfI3fssWGofcFmEmzLeqDq0vaBwJFo@z \
--to=kotajacob@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).