Arch Linux User Repository

I have added _JAVA_OPTIONS='-Dawt.useSystemAAFontSettings=gasp to the launcher script. This seemed to solve most of the pixelated fonts for me. I am reluctant to add more options since those setting should be up to each user, but you can easily modify the cgoban3 script to try other options.

@xyproto, thanks for the script, this may get me back into playing again. I stopped playing online partly because the fonts bug my eyes enough that I just couldn't go onto CGoban any longer.

Dumb question perhaps but how would one use this script with CGoban? How do I call it when starting the application? I'm using SwayFX for now so I don't know of an easy way to do this off-hand. I know I can put it into my ~/scripts directory but how do i then tell CGoban to use the damn thing?

This small shell script makes CGoban 3 look nicer and run smoother here (Using the latest version of OpenJDK, currently at version 22):

#!/bin/sh
export _JAVA_OPTIONS='-Dawt.useSystemAAFontSettings=gasp -Dswing.aatext=true -Dsun.java2d.xrender=true -Dswing.defaultlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel -Dswing.defaultfont=JetBrainsMono-Regular -Dfile.encoding=UTF-8 -Xms512m -Xmx1g -XX:+UseZGC -XX:MaxGCPauseMillis=10 -XX:+AlwaysPreTouch -XX:+UseStringDeduplication -XX:+UnlockExperimentalVMOptions -Dsun.java2d.uiScale=2.5'
java -jar /usr/share/java/cgoban3/cgoban.jar "$@"

@dysphoria, thank you for the updated build. I'm going to look at it to see how I can do this myself in the future if I need to. I really need to learn to make PKGBUILDs on my own. Regardless, I appreciate your efforts. :)

As for the fonts, I'm wondering if I should bug the KGS support team about it.

The PKGBUILD now skips the checksum of the source .jar file; for now that should stop the checksum errors on install.

So far, I don't know of any solution to the pixelated fonts.

@dysphoria, thanks for the reply. I have tried it since Feb 19 so it seems that is likely the issue. I tried again a day or so ago but got the same error which is a pain but I get it's not your fault. I'll just wait until things get smoothed over and use what I have right now as it still works.

Side note - is there anything one can do about their awful fonts that are blurred to rat shit? I've used this software for a decade off and on but the fonts were always terrible. I've looked around on the web for a solution to that but never seen an answer.

@MoonSwan Did you build before or after the package was updated to version 3.5.144 (on 19/Feb)?

The validity check can fail when KGS updates the .jar file but this package hasn't yet been updated with the new checksums. Since the file is always called cgoban.jar on the KGS site, it could be a few days before I notice that there was an update.

There might a possible fix 'soon'. Starting with their KGS-AI releases it seems they do keep different named versions for it (see: https://downloads.kgsai.com/). It is currently behind (still on 3.5.143) but if they keep this updated I'll switch to it on the next update.

I went to build this app a few weeks ago. Imagine my surprise when it still errors out by failing a validity check 5 years after the bug below was reported. I used the makepkg --syncdeps --install option and it still failed. Clearing my yay cache also did not help. In the end I had to force the installation, something one should not have to do with a package as far as I know.

I'd like to add that this build was tried on a completely new installation of Arch so there was also no chance that I had an old jar file hanging about either.

So my question is: why does this happen and can it be fixed?

Anyone knows why the font looks pixelated? I used "jre-openjdk" package. Should I have used a different one?

checksums are wrong and need to be updated