Arch Linux User Repository

For suggestions, issues, etc., please file them at https://gitlab.archlinux.org/freso/java-chatty – if submitting merge requests, do so against the java-chatty branch.

Note that when Twitch changes things, it may take a short while for those changes to get accounted for in a proper release of Chatty. If this is the case, and you need the new feature, you can try using java-chatty-beta or java-chatty-git until a new full release has been made addressing the change.

There is now also a chatty-beta package for those who want to be bleeding bleeding edge: https://aur.archlinux.org/packages/chatty-beta

For users who have used this PKGBUILD on version earlier than 0.9.x, note that from PKGBUILD 0.9.1-1 onwards, the PKGBUILD will not include as many patches as <0.9 PKGBUILDs did. One of the things this means is that the configuration will now be read from $HOME/.chatty instead of $HOME/.config/chatty. I'd recommend to either create a symlink (cd $HOME && ln -s .config/chatty .chatty) or move (or copy) the directory (cd $HOME && mv .config/chatty .chatty) prior to running version 0.9.x+ the first time.

If you get the following error (or similar) when compiling:

> BUG! exception in phase 'semantic analysis' in source unit '_BuildScript_' Unsupported class file major version 70

and you have a suitable version of Java installed, it's likely because your /usr/bin/java belongs to the latest version. To fix this, set your JAVA_HOME to your Java 1.8 or other suitable installation. Example:

$ JAVA_HOME=/usr/lib/jvm/java-8-openjdk makepkg -si

The package fails to build in a chroot:

   > BUG! exception in phase 'semantic analysis' in source unit '_BuildScript_' Unsupported class file major version 69

Full log:

==> Making package: java-chatty 0.28-1 (Fri 19 Dec 2025 03:43:01 PM MST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting build()...
WARNING: A restricted method in java.lang.System has been called
WARNING: java.lang.System::load has been called by net.rubygrapefruit.platform.internal.NativeLibraryLoader in an unnamed module (file:/home/username/.cache/yay/java-chatty/src/.gradle/wrapper/dists/gradle-8.2.1-bin/5hap6b9n41hkg4jeh2au2pllh/gradle-8.2.1/lib/native-platform-0.22-milestone-24.jar)
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module
WARNING: Restricted methods will be blocked in a future release unless native access is enabled


FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'chatty-0.28'.
> Could not open cp_proj generic class cache for build file '/home/username/.cache/yay/java-chatty/src/chatty-0.28/build.gradle' (/home/username/.cache/yay/java-chatty/src/.gradle/caches/8.2.1/scripts/d2a8r4ggmeph28jnxd767unwl).
   > BUG! exception in phase 'semantic analysis' in source unit '_BuildScript_' Unsupported class file major version 69

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 5s
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: java-chatty-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
java-chatty - exit status 4

On sway (wayland) I have to run it like this: "_JAVA_AWT_WM_NONREPARENTING=1 java -jar Chatty.jar" Else chatty only uses a small screenspace.

@nbisby They both provide /usr/bin/chatty (and probably other chatty name conflicts, but I didn't check further than /usr/bin).

Marking this as conflicts with chatty means that it will cleanly remove old twitch chatty before installing this, but leaves in conflict with gnome-chatty, since that has the chatty name now, right? I assume there isn't a conflict between java-chatty and gnome-chatty.

For suggestions, issues, etc., please file them at https://gitlab.archlinux.org/freso/java-chatty – if submitting merge requests, do so against the java-chatty branch.

Note that when Twitch changes things, it may take a short while for those changes to get accounted for in a proper release of Chatty. If this is the case, and you need the new feature, you can try using java-chatty-beta or java-chatty-git until a new full release has been made addressing the change.

Now I added gnome-chatty as chatty into the extra repository, so if you want to keep this package, upload it in a different name (e.g. chatty-twitch or java-chatty), and request a merge.

I plan to move the package purism-chatty as 'chatty' into the official repositories, so this package should to be renamed to something else like 'chatty-twitch-client'.