MCL-905New Launcher hangs after "Job 'Resources' finished successfully"
When I start the Minecraft.jar it hangs idefinetly at the state described by the Screenshot and log.
The window does not respond to the close Button on the window.
Environment
Linux Fedora 18
Java 1.7.0_11 (Oracle)
Created Issue:
New Launcher hangs after "Job 'Resources' finished successfully"
When I start the Minecraft.jar it hangs idefinetly at the state described by the Screenshot and log.
The window does not respond to the close Button on the window.Environment
Linux Fedora 18
Java 1.7.0_11 (Oracle)
Attachments2
- Unresolved
- Open
- Minecraft - Public
- Unconfirmed
- Freeze Launcher NewLauncher
- 1.6.1
MC-21888
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
Deleted Comment:
No answer, assuming no longer an issue.
I retried it with version 1.7.0_25 (Java 7 update 25). Exactly the same.
When I use OpenJDK it works fine.
Some additional things to note:
*running as root, works fine.
*running as regular user, using DISPLAY=localhost:0, and xhost + localhost, works fine (after getting gdm to start Xorg while allowing TCP connections).
Based on this, it appears to be something related to the default connection type for X11 (unix socket; DISPLAY=:0).
Still persists unchanged with launcher 1.1.1
Behavior is unchanged (including the launch as root or openjdk workaround).
I'm having the exact same problem. Same OS: Fedora 18, x86_64. Launcher version 1.2.1, which is now the latest.
This was fixed in a newer EA release of Java by Oracle, Java 8.
You can grab it here: https://jdk8.java.net/download.html.
Is this still a concern in the current Minecraft version 14w11b / Launcher version 1.3.11 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
This ticket is incomplete without the requested information, no response has been received within a reasonable time and we are assuming the issue has been resolved. If you are still experiencing this issue, we can reopen it at your request.
Please review the guidelines before reporting issues.