Arch Linux User Repository

The pro and community editions were merged in version 2026.4

jdk 21

sudo archlinux-java set java-21-openjdk

burpsuite-pro
Could not start Burp: java.awt.AWTError: Assistive Technology not found: org.GNOME.Accessibility.AtkWrapper

jdk 17

sudo archlinux-java set java-17-openjdk

burpsuite-pro
Error: LinkageError occurred while loading main class burp.StartBurp
 java.lang.UnsupportedClassVersionError: burp/StartBurp has been compiled by a more recent version of the Java Runtime (class file version 65.0), this version of the Java Runtime only recognizes class file versions up to 61.0

works with:

sudo archlinux-java set java-21-openjdk
sudo sed -ie '/^assistive_technologies=/s/^/#/' /etc/java-openjdk/accessibility.properties

Thanks, @nns. I am not familiar with the merging process. I've added added you as a co-maintainer for the burpsuite-pro package, in case this is required. Yes, please leave me as co-maintainer and let me know if you need me to do anything else.

Thanks!

Hey freb! Sounds good to me. I'll merge this package into that one and add you as a co-maintainer (if you wish).

Hi, I maintain the burpsuite-pro package. That package also uses the early-adopter channel, so it looks like our packages currently do the same thing. If you plan on continuing support for this package for the foreseeable future, I'll likely discontinue maintenance on mine. I'd love to know your thoughts on this.

At the expense of some extra disk space the jar could be copied into $pkgdir before modifying it, leaving the original (and its checksum) intact.

The PKGBUILD file alters the downloaded JAR file to remove the Windows and Mac OS versions of the embedded Chromium browser. This saves 100's of MB in disk space.

However, since the PKGBUILD checksum is calculated on the original JAR, which we have altered, re-installing from cache won't work. You will get the following error unless you perform a cleanBuild:

==> Validating source files with sha256sums...
 burpsuite-pro-2022.2.3.jar ... FAILED

@idontusearchbtw, that is expected when you attempt to re-install the package using the cache. The reason is that the PKGBUILD alters the downloaded JAR to remove the embedded versions of chromium for Mac and Windows to save space. You need to cleanBuild the package so that it will download and verify the original JAR to get past that error. You could also alter the PKGBUILD and replace the checksum with "SKIP" to get around it without doing an additional download.

If anyone knows a way to add multiple checksums for the same file or another fix, I'd love to hear it.

Validating source files with sha256sums... burpsuite-pro-2022.2.3.jar ... FAILED

@lord, thanks for the heads up. The PKGBUILD was up-to-date, but my hook to update the metadata went missing. I've fixed it now.