Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at

Bug 1236389

Summary: Minecraft not starting under wayland (No modes available)
Product: [Fedora] Fedora Reporter: srakitnican <samuel.rakitnican>
Component: waylandAssignee: Adam Jackson <ajax>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: ajax, michael.wiktowy, ofourdan
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-07 14:25:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1277927    
Description Flags
crash report from Minecraft Launcher none

Description srakitnican 2015-06-28 13:26:18 UTC
Created attachment 1044019 [details]
crash report from Minecraft Launcher

Description of problem: Minecraft not starting under when running wayland 

Version-Release number of selected component (if applicable):

How reproducible: Always

Steps to Reproduce:
1. $ java -jar ~/.minecraft/Minecraft.jar
2. choose profile and click 'Play' in Minecraft Launcher

Actual results: Minecraft crashing with report and going back to launcher

Expected results: Minecraft starting up

Additional info:

Comment 1 Olivier Fourdan 2015-07-06 14:23:36 UTC
It fails because "No OpenGL context found in the current thread."

Does the same work under an X11 GNOME regular session?

Could you please post the output of "glxinfo" under both GNOME Wayland and X11 session on your system for comparison?

Comment 3 Olivier Fourdan 2015-07-06 14:59:56 UTC
Actually, I've been able to reproduce locally.

Comment 5 Olivier Fourdan 2015-07-07 14:01:44 UTC
OK, sorry, I was wrong in comment 1, this is not an issue with OpenGL contexts but this is rather an issue with xrandr.

The library lwjgl as used by Minecraft invokes "xrandr -q" (the command line) and parses the output trying to get the different modes available.

Xwayland will report only one output with only one mode and apparently lwjgl is not happy with that and will report 0 mode (still not sure why it fails to parse at least the only one mode available), thus causing the "No modes available" error.

Simulating as many modes as with the regular X server (for example, capture the output of "xrandr -q" as taken from a regular X session and copy it to a dummy shell script that will echo it to stdout, call that script "xrandr" and adds this first in the shell PATH) does fix the issue, lwjgl happily find several modes and Minecraft will run just fine - It won't run fullscreen though, as xrandr is only "simlated" by a shell script.

So, I am really not sure it's a bug in Xwayland (definitely *not* a bug in Wayland, the protocol, as neither Java nor lwjgl have been ported to Wayland AFAIK), it looks like a bug or at least a weakness in the parsing of xrandr output in lwjgl to me.

Comment 6 Olivier Fourdan 2015-07-07 14:25:28 UTC
Closing as cantfix, lwjgl-2.x should be able to parse the output of "xrandr -q" under Xwayland even when there is only one output and one mode reported.

Comment 7 Olivier Fourdan 2015-12-16 14:00:58 UTC
*** Bug 1287864 has been marked as a duplicate of this bug. ***