-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GUI does not render at all; is "invisible" #969
Comments
Update: I tried clicking the blank window visible below the splash screen, and got a dropdown selection box. I..guess..I can try to find my way through the invisible GUI. So it's not an infinite hang, it seems, but the GUI doesn't render correctly. This really should be looked into. |
which distro and UI are you using? |
Ubuntu 14.10 LTS, I believe. Here's my
And the UI is DWM. I can try loading it in other WM/DE's, but I doubt it'll make a difference, since they all run on top of X11, which does the actual drawing. |
I usually don't have problems with Java UI, for the record. At the worst, a dropdown box's contents will show at some place far away from the actual dropdown box when I click it. |
Update: after almost 20 minutes of trying unsuccessfully to navigate the invisible GUI, I went ahead and ran it on my Windows box for a visual reference. I managed to fill out the form and I have a GUI running right now: However, I will not close this issue, as the "First Run" form still doesn't render any of the GUI elements. This is a serious bug that needs to be fixed. I even mistook it as the launcher freezing/going into an infinite loop. This will be a thorn in a lot of Linux users' sides. As it was for me. Thank you. |
How we can fix a serious which is unreproduciably by us and by other users? Also I've rewritten that dialog but code is unfinished. Might fix this or not. |
I can't even get the damn thing to start. I just get the FTB splash screen with "loading..." and another, blank window titled "First Run", and it just hangs there...for eternity.
The terminal is not printing any errors. If I add
> /dev/null
to dock the stdout stream, it will print nothing at all.In fact, the log messages that print are all successful. It ends in a language file being loaded, followed by an eternal hang.
Here's a screenshot of my desktop. As you can see, it has been "running" for almost ten minutes.
The text was updated successfully, but these errors were encountered: