>>997
It sounds like the executable bit got stripped
To fix that:
chmod 755 client server
Though (if this is indeed the problem) I'd be worried that it happened in the first place. Perhaps whatever you used to extract the tar.gz is faulty.
>>989
If you are on Arch Linux, I've been maintaining an AUR package which should handle everything for you.
https://aur4.archlinux.org/packages/hydrus/
Please note, if you try to install hydrus from the AUR and get served version 159 instead of the latest, it means your AUR helper is pointing to the old AUR and might need updating. If you run into any problems (i.e. if the install is any more complicated than just pointing your AUR helper at it and letting it do its thing), leave me a comment there and I'll fix it up if I can.
If you're on Arch, here are a few reasons you should use this rather than the official release IMO:
* It takes the size of the Hydrus release down from 164MB (from the Linux tar.gz) to about 30MB. If you remove the source and help files too (there's an option in the PKGBUILD to safely do this), you can get a nice minimal Hydrus install at 2.8MB(!)
* It's kept in source form, so you can go in there and hack at it if you must. (Unless you explicitly opt to remove the source of course) This is better than just cloning from the github, because that requires manually setting up dependencies and such.
* When an error occurs, the tracebacks include a snippet of source code. (Pic related). This makes it easier for the technically inclined to diagnose bugs, and makes bug reports more accurate.
* You don't have to find and install all the python dependencies, you'll just pull them from the AUR like with any other program
* There are some (minimal) patches to the code to fix some issues like the "Just set up a server on this computer" option not working, and to cleanly separate the hydrus installation from the hydrus user data.
* It pulls from the git repository, so if you keep the PKGBUILD (and related files) in a safe place, updating it only has to fetch the differences since last update rather than the entire source code. I also make it pull from a specific commit hash, which ensures that the source is not tampered with and that the patches apply cleanly to a version they've been tested on.
* You can keep it updated using your usual AUR helper, along with your other AUR packages, in the usual fire-and-forget way. No need to go and download the new version manually.
* It's in your menus! (Pic related; I put it under both "Internet" and "Graphics" since I wasn't sure…)
* Hydrus is kept in /opt/hydrus while your hydrus data is kept in ~/.local/share/hydrus. So not only are they both "out of the way" (i.e. not cluttering your downloads folder), you can delete or upgrade hydrus without worrying about your hydrus data – or you can do the opposite, delete your hydrus data and keep your install so you can get it up and running again very quickly.
* It uses your local installation of ffmpeg, upnpc, wxgtk, etc. rather than giving you another one.
* If you're using linux-grsec you don't need to explicitly give hydrus MPROTECT permissions every update.
Also, if someone on a non-Arch distro is reading this, I encourage you to provide packages for users of your distro. It makes things a lot easier for other people and it can be your contribution to open source!