Minecraft launcher not launching

Minecraft launcher is not working. The process runs, using 100% of one of my CPU cores, but nothing happens, and there is no output when running from the terminal.

java-8-openjdk is set as the default java environment and I tried using Oracle’s jre8 as well, but it didn’t work. I’ve also seen a couple of people around with the same problem, but couldn’t find an answer. The .tar.gz from minecraft dot net also behaves the same so at least I’m sure it’s not a problem with AUR’s packages.

Any help is appreciated.

Any way of having some relevant output like a log file, terminal content, something like that?
Also it is important, even if not obvious for everyone, to provide the system information like explained in the thread How to provide good information so that all the basic information are already here so people know all the important info about your system before thinking of possible issues/solutions.

Here is the system information:

System:
  Kernel: 5.8.11-1-MANJARO x86_64 bits: 64 compiler: N/A 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.8-x86_64 
  root=UUID=3e2d4c12-940e-4a99-967f-eb6d21cc90e3 rw quiet apparmor=1 
  security=apparmor udev.log_priority=3 
  Desktop: GNOME 3.36.6 tk: GTK 3.24.23 wm: gnome-shell dm: GDM 3.36.3 
  Distro: Manjaro Linux 
Machine:
  Type: Desktop System: Gigabyte product: B450M DS3H v: N/A serial: <filter> 
  Mobo: Gigabyte model: B450M DS3H-CF v: x.x serial: <filter> 
  UEFI: American Megatrends v: F40 date: 05/16/2019 
CPU:
  Topology: 6-Core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 
  family: 17 (23) model-id: 71 (113) stepping: N/A microcode: 8701011 
  L2 cache: 3072 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 86279 
  Speed: 2230 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 
  1: 2465 2: 2144 3: 2196 4: 2196 5: 2185 6: 2195 7: 2196 8: 2196 9: 3370 
  10: 2096 11: 2094 12: 2196 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, IBRS_FW, 
  STIBP: always-on, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: NVIDIA TU104 [GeForce RTX 2070 SUPER] vendor: ZOTAC driver: nvidia 
  v: 450.66 alternate: nouveau,nvidia_drm bus ID: 07:00.0 chip ID: 10de:1e84 
  Display: x11 server: X.Org 1.20.9 compositor: gnome-shell driver: nvidia 
  display ID: :1 screens: 1 
  Screen-1: 0 s-res: 3460x1600 s-dpi: 96 s-size: 915x423mm (36.0x16.7") 
  s-diag: 1008mm (39.7") 
  Monitor-1: DP-0 res: 2560x1440 dpi: 109 size: 597x336mm (23.5x13.2") 
  diag: 685mm (27") 
  Monitor-2: HDMI-0 res: 900x1600 hz: 60 
  OpenGL: renderer: GeForce RTX 2070 SUPER/PCIe/SSE2 v: 4.6.0 NVIDIA 450.66 
  direct render: Yes

The launcher is installed in the same drive as the system.
As for log files, I couldn’t find any. As I said before there is no output in the terminal. On journalctl it states the application was launched, and then there’s a timeout for org.bluez:

out 18 21:03:30 Alice systemd[1447]: Started Application launched by gnome-shell.
out 18 21:03:30 Alice systemd[1447]: gnome-launched-minecraft-launcher.desktop-22585.scope: Succeeded.
out 18 21:03:54 Alice dbus-daemon[704]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)

nothing comes after that. Isn’t org.bluez a bluetooth library? Makes sense it times out because i don’t have a bluetooth antenna, but the timeout comes every time I start the launcher. They are correlated but i can’t see how they’re related

I found the problem. Ryzen 3 processors have this bug where RDRAND always returns 0xFFFFFFFF. My processor started presenting the bug a couple of weeks ago and I decided to update the BIOS to fix it today. And now the RDRAND bug is fixed and minecraft works. My guess is that the game uses RDRAND to generate world elements or something. Hope this threads ends up helping someone in the future

1 Like