Hello, when I'm executing the Minecraft Launcher on Gentoo Linux it creates an empty '~/.minecraft/launcher_log.txt' file and immediately crashes without providing any error.
GNU gdb doesn't provide any useful information - the Launcher simply dies with -1 (code 0377):
??$ gdb ./minecraft-launcher ??
— GNU gdb (Gentoo 8.3 vanilla) 8.3
— Copyright (C) 2019 Free Software Foundation, Inc.
— License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
— This is free software: you are free to change and redistribute it.
— There is NO WARRANTY, to the extent permitted by law.
— Type "show copying" and "show warranty" for details.
— This GDB was configured as "x86_64-pc-linux-gnu".
— Type "show configuration" for configuration details.
— For bug reporting instructions, please see:
— <https://bugs.gentoo.org/>.
— Find the GDB manual and other documentation resources online at:
?? <http://www.gnu.org/software/gdb/documentation/>.??
— For help, type "help".
— Type "apropos word" to search for commands related to "word"...
— Reading symbols from ./minecraft-launcher...
— (No debugging symbols found in ./minecraft-launcher)
— (gdb) run
??Starting program: /home/hekarath/minecraft-launcher/minecraft-launcher ??
— [Thread debugging using libthread_db enabled]
— Using host libthread_db library "/lib64/libthread_db.so.1".
— [Inferior 1 (process 19856) exited with code 0377]
— (gdb)
Previous Java version of Launcher was working fine for me.
Linked issues
Attachments
Comments 18
No. No other file was created. At the moment I have to use the old Java launcher which is working fine, although it's not supported.
BTW. why are you marking bug as resolved while it is not?
Because quite often people don't respond to our questions. If we would leave a ticket that is awaiting response open, we would have thousands of 'zombie tickets'. If a ticket is resolved as 'Awaiting Response' it will be reopened automatically as soon as the reporter replies.
Can you provide some more details about your system? Are you using a 32bit or a 64bit system, what's your processor, graphics card, etc.?
Thank you for clarifying.
OS I'm using is Gentoo Linux 64bit, running:
Kernel 5.2.3,
Wayland 1.17,
XOrg Server 1.20.5,
Gnome 3.30.2,
GTK+ 3.24.10 and 2.24.32.
I'm using ThinkPad X1 Carbon 6th with:
i7-8650U CPU,
16GB LPDDR3 RAM,
Intel UHD Graphics 620.
Based on Arch Linux package dependencies for Minecraft Launcher I should have everything the launcher needs, including:
alsa-lib-1.1.8,
libxcb-1.13.1,
nss-3.46,
libX11-1.6.8,
libXtst-1.2.3,
libXScrnSaver-1.2.3,
xrandr-1.5.0.
A new beta version of the launcher has been released; if you would like to check whether it now works, you can download it here: https://www.minecraft.net/en-us/article/try-new-minecraft-launcher-beta (The article is a bit old, but the links should be up to date.)
That would be great Petr. The less dependencies you have, the larger audience will be able to run the Minecraft Launcher. Less dependencies always means less issues.
Worth mentioning is that GConf is not used by any modern app. Gnome 3 and it's apps works flawlessly without it.
Will you consider upgrading CEF? Its wayland support was upstreamed, a while ago. There are also some pending pull requests related to ozone.
I filed another bug report (MCL-13763). GConf is not merely "old", it's ancient. Every person using Linux won't have it installed. Lack of wayland nativity is another major problem.
MCL-14336. Gconf is no longer required. Does this fix the problem?
I can confirm that now the launcher works perfectly fine, no Gconf is required anymore. Thank you for solving this!
Apart from the empty launcher.log file, have any other files been created? Specifically, nativelog.txt or updateLog.txt? If so, could you attach those files?