Honestly, even though I use my system java and not the bundled one for the game, it is true that the launcher shouldn't need it, right? I think timo_capa is right
Search Criteria
Package Details: minecraft-launcher 1:1.0.1221-3
Package Actions
Git Clone URL: | https://aur.archlinux.org/minecraft-launcher.git (read-only, click to copy) |
---|---|
Package Base: | minecraft-launcher |
Description: | Official Minecraft Launcher |
Upstream URL: | https://mojang.com/ |
Keywords: | game minecraft |
Licenses: | custom |
Conflicts: | minecraft-launcher-beta |
Provides: | minecraft-launcher-beta |
Submitter: | shoghicp |
Maintainer: | pschichtel |
Last Packager: | pschichtel |
Votes: | 1097 |
Popularity: | 2.93 |
First Submitted: | 2017-01-18 14:17 (UTC) |
Last Updated: | 2024-06-17 22:10 (UTC) |
Dependencies (6)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libgpg-error (libgpg-error-gitAUR)
- zlib (zlib-ng-compat-gitAUR, zlib-gitAUR, zlib-ng-compat)
- flite (flite1AUR) (optional) – narrator support
- org.freedesktop.secrets (keepassxc-gitAUR, gnome-keyring-gitAUR, pass-secrets-gitAUR, keepassxc-allow-aur-extension-originAUR, keepassxc-allow-aur-extension-origin-binAUR, pass-secret-service-binAUR, dssdAUR, pass-secret-service-gitAUR, bitw-gitAUR, gnome-keyring, keepassxc, kwallet, kwallet5) (optional) – persistent login support
Sources (3)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 52 Next › Last »
jpegxguy commented on 2022-01-06 12:04 (UTC)
timo_capa commented on 2022-01-06 10:51 (UTC)
Gonna sound weird, but why is java a dependency?
minecraft-launcher doesn't depend on it, and the game itself ships a bundled java version for compatibility reasons
logothete commented on 2022-01-03 07:39 (UTC)
@kamilst96 Thanks for the reply. Unfortunately, that binary executes with error:
terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_M_construct null not valid
which seems to be the same as what's going on with the installed version as well.
Any theories as to what may be missing?
kamilst96 commented on 2022-01-02 18:04 (UTC)
@logothete Launch this binary from terminal: https://launcher.mojang.com/v1/objects/ce9e6169550628003e22de8086e9fe1186c2285e/minecraft-launcher
I blindly rebuilt arch installation and tried this launcher directly (1035), via AUR (928), and via my own PKGBUILD (1035). All of them worked with KDE / GNOME on X11, so you've done something specific in your install, or maybe forgot something.
logothete commented on 2021-12-30 17:32 (UTC)
Installation either through yay or through downloading and using makepkg leaves me with a launcher that won't launch at all, and gives no GUI indication of failure either. However, looking at my logs, I see the rather large:
Process 30502 (minecraft-launc) of user 1000 dumped core.
(a hundred odd lines of modules; not particularly relevant) Stack trace of thread 30502:
0 0x00007fec63f83d22 raise (libc.so.6 + 0x3cd22)
1 0x00007fec63f6d862 abort (libc.so.6 + 0x26862)
2 0x00007fec6430d802 _ZN9__gnu_cxx27__verbose_terminate_handlerEv (libstdc++.so.6 + 0x99802)
3 0x00007fec64319c8a _ZN10__cxxabiv111__terminateEPFvvE (libstdc++.so.6 + 0xa5c8a)
4 0x00007fec64319cf7 _ZSt9terminatev (libstdc++.so.6 + 0xa5cf7)
5 0x00007fec64319f8e __cxa_throw (libstdc++.so.6 + 0xa5f8e)
6 0x00007fec6431036c _ZSt19__throw_logic_errorPKc (libstdc++.so.6 + 0x9c36c)
7 0x00000000004cd43a n/a (minecraft-launcher + 0xcd43a)
8 0x000000000043f0de n/a (minecraft-launcher + 0x3f0de)
9 0x0000000000410b56 n/a (minecraft-launcher + 0x10b56)
10 0x000000000041db10 n/a (minecraft-launcher + 0x1db10)
11 0x000000000040958c n/a (minecraft-launcher + 0x958c)
12 0x00007fec63f6eb25 __libc_start_main (libc.so.6 + 0x27b25)
13 0x000000000040ccf9 n/a (minecraft-launcher + 0xccf9)
Stack trace of thread 30504:
0 0x00007fec64d9a8ca __futex_abstimed_wait_common64 (libpthread.so.0 + 0x158ca)
1 0x00007fec64d94574 pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf574)
2 0x0000000000470689 n/a (minecraft-launcher + 0x70689)
3 0x00007fec64347782 execute_native_thread_routine_compat (libstdc++.so.6 + 0xd3782)
4 0x00007fec64d8e259 start_thread (libpthread.so.0 + 0x9259)
5 0x00007fec640455e3 __clone (libc.so.6 + 0xfe5e3)
ELF object binary architecture: AMD x86-64
Sorry for how much text that is. Anyone have any ideas for what's the matter here? Arch install is relatively fresh, maybe a week or so old, with no real problems.
kamilst96 commented on 2021-12-18 15:46 (UTC) (edited on 2021-12-18 16:11 (UTC) by kamilst96)
Bootstrap version 1035 is available, released 20210916, but it's not available as tar.gz.
Maybe you could follow Gentoo repo which tracks Mojang launcher meta.
Here's an example commit of what I mean: GitHub
cosmicmarley17 commented on 2021-12-16 19:37 (UTC) (edited on 2021-12-16 19:39 (UTC) by cosmicmarley17)
For people having issues needing to log into Microsoft every time, this solution from the wiki solved it for me: https://wiki.archlinux.org/title/GNOME/Keyring#--start_step
You have to have gnome-keyring installed.
huantian commented on 2021-12-15 20:17 (UTC)
@nebulon download the tar.go in the source and then download the launcher from the official site. You’ll see that they are identical
nebulon commented on 2021-12-15 18:38 (UTC)
@HurricanePootis I would agree with the flagging as explained in the flag comment: https://aur.archlinux.org/pkgbase/minecraft-launcher/flag-comment/
HurricanePootis commented on 2021-12-14 21:20 (UTC)
@Philanche This package isn't out of date, nor is the reason you stated correct. This package is a launcher for a tool that downloads that actual client that we run on our computer, so stating that the client is out of date is incorrect. Checking the version on my own client, I can see that this "out of date" package has me running the latest version of the client available.
Pinned Comments
petr commented on 2021-10-08 09:04 (UTC)
The package version is the version of the launcher bootstrap - the part that actually downloads and updates the launcher.
That means the version number of the actual launcher (2.x.xxx) is different from the version here (9xx+) on a fundamental level, and should not be compared.
The package is outdated only when the bootstrap version you get here is different from the bootstrap version you would get from minecraft.net when using the raw tarball.