Package Details: screamingfrogseospider 11.3-1

Git Clone URL: (read-only)
Package Base: screamingfrogseospider
Description: A small desktop program you can install on your PC or Mac which spiders websites’ links, images, CSS, script and apps from an SEO perspective.
Upstream URL:
Licenses: custom
Submitter: matth
Maintainer: matth
Last Packager: matth
Votes: 13
Popularity: 0.024140
First Submitted: 2013-03-18 21:25
Last Updated: 2019-05-31 19:11

Latest Comments

1 2 3 4 Next › Last »

seotronix commented on 2019-09-28 02:23

Hi! If you received this error: "Error: JavaFX detected no fonts! Please refer to release notes for proper font configuration" we fixed installing the "ttf-ms-fonts" package from AUR

matth commented on 2019-05-31 19:13

Thanks for the report @exoro

It looks like they just released version 11.3, but in doing so they also updated the download for 11.2 to download 11.3 instead which broke the hash check for 11.2 since it was getting the 11.3 file contents.

I've updated this package to use 11.3 now.

exoro commented on 2019-05-31 18:17

It keeps failing the validity check updating to the new version.


==> Validating source files with sha256sums...

    screamingfrogseospider_11.2_all.deb ... FAILED

    LICENSE ... Passed

==> ERROR: One or more files did not pass the validity check!

Any tips?

matth commented on 2019-05-28 17:06

Yeah, it could be the DE. I'm using awesome on Arch.

It does make sense to use the shipped jre. I didn't even realize that it included one as I just always ran it with the system OpenJDK since I first made this package 6 years ago.

infinitnet commented on 2019-05-28 16:48

Wow, thanks for the extremely fast fix @matth! All working fine for me now after updating to your latest commit.

Odd that it's working for you with OpenJDK. Might be related to the DE or distro then. I'm on Manjaro KDE and that's on which Screaming Frog support was also able to reproduce this issue with the previous version of your AUR package. Just in case you want to look into this some more. Generally I think it makes most sense to just always use the shipped JRE, as this will work for everyone and if it doesn't, we know it's a bug Screaming Frog will fix with an update and not some unexpected incompatibility. :)

matth commented on 2019-05-28 16:19

Thanks @infinitnet

I switched the package to use the included JRE by default instead of OpenJDK.

Very strange that I've never had an issue with it using OpenJDK, but this should work for everyone else and I can still use OpenJDK myself if I choose.

infinitnet commented on 2019-05-28 10:21

@matth I've had the same issue as @depe and talked to their support, which has been extremely helpful and actually installed Manjaro to reproduce this etc.

The conclusion is that this bug appears when using OpenJDK 8 which your launch script calls. Instead, you have to use Oracle Java 8 or ideally the JRE their .deb file already ships with, as that would assure 100% compatibility.

They suggested that you hit them up at their support email (ask for Liam) if there are any questions to make this AUR package work for everyone. :)

depe commented on 2019-04-18 03:24

@matth yeah very odd, see screenshot of e.g. License -> Enter License:

I tried uninstalling and reinstalling, and also tried executing a wrapper script to make sure Java 8 is being used.

Only interesting error I see in the console logs is related to Arial font:

[JavaFX-Launcher] WARN - Unable to find a suitable Arial font - letting system select best matching font

Can't imagine this would cause the info dialog box to be cut off however.

matth commented on 2019-04-17 19:13

@depe the package has now been updated to 11.2

I tested those popup windows you mentioned and they displayed fine for me.

depe commented on 2019-04-17 17:55

I was able to install latest 11.2 by editing source package file per below. However, many popup windows (e.g. Configuration menu -> Speed; Help menu -> About) within the app are being completely cut off at about 5px vertically and therefore inaccessible. Anyone else experienced this? Wondering if it's a Java issue, or whether it's a font sizing / DPI issue in general system settings.