This package uses java-runtime-openjdk provided by Arch. Screaming Frog does not officially support openjdk. If you are running into any issues with it on your machine try the screamingfrogseospider-jre version of the package which uses Screaming Frog's bundled version of Java. If you need to reach out to their support for an issue, use that package to make sure you are using the version of java supported by them.

This package uses java-runtime-openjdk provided by Arch. Screaming Frog does not officially support openjdk. If you are running into any issues with it on your machine try the screamingfrogseospider-jre version of the package which uses Screaming Frog's bundled version of Java. If you need to reach out to their support for an issue, use that package to make sure you are using the version of java supported by them.

@garganite This version of the package uses the bundled Arch version of openjdk.

If you are running into any issues with openjdk version of java, we also have the screamingfrogseospider-jre package in the AUR which uses the bundled java version provided by Screaming Frog.

Looking at the comments you left it looks like your AI just changed the package to use the bundled version of java. So, you can just use the screamingfrogseospider-jre version of the package from the AUR instead of this one.

Thanks @plainlystated! I pasted your comment into AI, and it did the below and it worked. I'm a complete Linux newbie, perhaps someone could fix the PKGBUILD?

====================

The issue is occurring because the original PKGBUILD removed the bundled JRE that comes with the official .deb release to favor the system's JRE, which caused strict vendor and version requirement checks in Screaming Frog to fail.

I updated the PKGBUILD to stop removing the bundled JRE:

bash In build() phase Instead of deleting: rm -rf "$srcdir/usr/share/screamingfrogseospider/jre" Kept it to make sure the app uses its official JRE. And I reinstalled the package using makepkg -f -si --noconfirm.

I have launched the spider manually on your machine via terminal and saw it run successfully past the usual errors without complaining about a mismatched Java environment. It has already successfully run and closed gracefully!

You should now be able to run Screaming Frog SEO Spider perfectly through the desktop shortcut or terminal.

Looks like they bumped the deb version again. Getting the same error as others.

Here's how I installed the package. I'm an arch newb so this may be wrong but it worked for me.

install pacman-contrib from pacman

clone the repo from https://aur.archlinux.org/screamingfrogseospider.git

update pkgver to 23.3 in PKGBUILD (not sure this is needed/used) (also may want to check on the screaming spider site to see the current version number)

(within the repo dir)

updpkgsums # recalculate the broken sum

makepkg -si # install the re-built package

pacman -Q screamingfrogseospider # verify it's installed

Not sure if there's a way to PR the updated sum, but the change in PKGBUILD is (first entry):

ce865aeff9fe3816d44bc74baddd10549d33466c6aaba5d8d0a4e12a88e3a21b9cc3875f5eb9fe8a67a3e5bd0516b37627557cf21e1e3bcef183f6a995eb83e5

@matth Huge thanks! The alternate package installed fine and reported the bundled version of Java. Unfortunately, I still have the menu issue, with drop down menus truncated so that the last few items are not visible (the are reachable using keyboard navigation).

If it helps others with the same issue, I'm using:

xorg-server 21.1.13-1 i3-wm 4.23

@axolx No issues here with the menus and I am using the same openjdk version that you are using.

I pushed up a package that provides the bundled java version, so if you install this it will use the bundled java when you start it to see if that helps you https://aur.archlinux.org/packages/screamingfrogseospider-jre

I've encountered UI problems with screamingfrogseospider 20.2-1, which I didn't have in previous versions. Specifically, the menu bar drop-down menus are truncated, such that the last few options of each menu become inaccessible.

I contacted Screaming Frog support and they believe the problem is that the app is using the wrong Java version. According to Help > Debug... the app uses:

Java Info: Vendor 'Arch Linux' URL 'https://openjdk.org/' Version '22.0.2' Home '/usr/lib/jvm/java-22-openjdk'

According to Screaming Frog support, it should use the Java version bundled with the app:

Java Info: Vendor ‘Eclipse Adoptium’ URL ‘https://adoptium.net/’ Version ‘21.0.2’ Home ‘/usr/share/screamingfrogseospider/jre’

Is this a packaging issue? Let me know how I can help troubleshoot.

@byt34ter That is just because they just released a new version and unfortunately when they do that they remove the link to the old version making it a redirect to the new.

The package is now updated to the new version.

I tried to install the package using AUR (version 20.1-1) but I got the following error:

==> Validating source files with sha256sums...
    screamingfrogseospider_20.1_all.deb ... FAILED
    LICENSE ... Passed
    screamingfrogseospider ... Passed
==> ERROR: One or more files did not pass the validity check!
 -> error making: screamingfrogseospider-exit status 1
 -> Failed to install the following packages. Manual intervention is required:
screamingfrogseospider - exit status 1

It seems that the .deb file didn´t pass the sha256 check. I tried downloading the git repository and installing it from with makepkg. It returned the same error.

Here's what I found: - The sha256sum doesn´t match the package hash. - It tries to download the latest version from the software website, which is the 20.2-1. This causes the error in the validity check.

How I solved the issue: - I manually downloaded the latest version (20.2-1) from the software website (https://download.screamingfrog.co.uk/products/seo-spider/screamingfrogseospider_20.2_all.deb?noredirect) - I moved the downloaded package into the repository and I deleted the old one (version 20.1) - I changed the version in the PKGBUILD file from 20.1 to 20.2 - I calculated the sha256 and the b2 sum of the new package (I know it's useless, but I didn´t find any hash of the package in the original website) - I built the package and it all went well.

I wrote this comment just to inform the maintainer about the issue I got.