While your servers were down, every time I launched the launcher it would hang with a window with only the title and close button. Every thing else was blank and the close button did not work. Had to shut it down with the system monitor or a reboot.
As soon as your servers came back up, the problem went away.
Description
Description
Details
Details
- Task Type
- Bug
Testing Results
- Affected Gamemode(s)
- none/unspecified
- Reproducible
- uncertain
- Category
- Launcher
- First occurrence (version)
- 0.19592
Hardware/Software/System
- OS-Specific
- No
- Hardware-Specific
- No
- Video Card Vendor
- uncertain
Steps to reproduce
Have your servers go down.
Launch launcher.
Debian 8 (mate desktop)
Tester information (Internal use only)
Assumable main factor in the problem:
Have the site unreachable. (No connection to internet at all) and it skips directly and causes no hanging.
If the name is resolved, and the connection times out, it does this for every single step again.
Rare corner case, but should possibly offer after 10seconds to go into "offline mode" and skip all further connection attempts.
Serverconfig (server.cfg)
<replace this line with the file content>
Clientconfig (settings.cfg)
<replace this line with the file content>
Can't find file.
Java Version (32bit)
Error: This Java instance does not support a 32-bit JVM.
Please install the desired version.
Java Version (64bit)
java version "1.8.0_74"
Java(TM) SE Runtime Environment (build 1.8.0_74-b02)
Java HotSpot(TM) 64-Bit Server VM (build 25.74-b02, mixed mode)
Related Objects
Related Objects
Event Timeline
Comment Actions
-Validated-
-Confirmed-
Added relevant information to reproduce in tester information field.
Comment Actions
Interesting response to not having a connection.
Adding an offline-only mode and have the launcher intelligently fallback to it should resolve this issue.
This also ties in nicely with the planned registry/auth/forums/etc. status indicators.
Comment Actions
It happens the same way on my windows 8.1 computer, but not reliable enough.
It usually took ages to load the initial window, and then came up with the "login" screen, but sometimes it really got stuck for several minutes.
So could be a missing timeout handler on some type of connection.