downlords-faf-client: Linux: client "freezes" on the play tab
system specs and distro | client installed through the AUR package
The play tab poses problems for me. When the client boots directly into the play tab, after the first few clicks on the buttons inside the tab, it ceases to respond. When I put the window in the background (switch to another tab or workspace in i3-wm), while leaving the client on the play tab, the window will be completely white when I come back to it.
Even in the unresponsive state, I can still switch to another tab like News, Chat etc. they all work properly as far as I can see.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 46 (29 by maintainers)
Another workaround that works for me:
Well we could just make it an X on linux instead of š
We could probably close this right?
Hey, so Iām the maintainer of the AUR package. I have never experienced this issue and nobody ever mentioned it in the comments š¦
Nevertheless, Iāve updated the package to use Oracleās JDK 14 to work around an issue with Archās OpenJDK so maybe try that out and see if it works for you.
JavaFX 14 was released today: https://github.com/openjdk/jfx/blob/9db2ff258fde2a60b1494857e2cacbf76791f4aa/doc-files/release-notes-14.md
This problem happened with me. I fixed it by unchecking the āShow private gamesā box blindly. Whenever it is selected, the Play tab freezes completely, but unchecking it makes it usable again.
For those of you trying to find the checkbox, it is directly under the V in the Vault tab.
Iām also experiencing this issue exactly as described.
Iām also using Arch and installed the downlords-faf-client packages from the aur. My window manager is i3 if that makes any difference.
Hereās a list of my installed fonts
Looking around a bit more on how fonts are managed with JavaFX, I found this page. Where they said the java launch options could be changed to ignore fontconfig, by adding this:
-Dprism.useFontConfig=falseSo I changed the bash file for starting the FAF client to include the above in the Java launch options. Using the above, the bug does not occur anymore, not even on i3.
AUR packageā¦ did not know there was something like that