Just something that happened to me recently.
Onno's fix above which works well I am grateful it was available.
My problem was that I built a new system and just wanted to copy over to it my AUSkey. I copied my ~/AUSkey directory but things did not work. Nothing was being written to the ~/AUSkey/logs/abrmessages.log.
Guess what, it was because abrakmbe was not executing.
AUSkey requires that the ~/.local/bin/AUSkey directory be there will all the required bits in it for (in my case) both chrome and firefox.
If this is not here (or wrong) then when you look for your AUSkey it silently is not there.
In addition the routine abrakmbe located in there requires links to old libraries which are normally not found in Linux installs any more.
This is easily fixed with
cd /usr/lib64 # or /usr/lib if you are still 32 bit
ln -s libssl.so.10 libssl.so.1.0.0
ln -s libcrypto.so.10 libcrpyto.so.1.0.0
This then makes it happy. I am not sure for how long version 10 will be the active one and around in the distros but since that one links to the current one my guess is it will be quite a while before this changes.
To help with debugging go to the ~/.local/bin/AUSkey directory and execute abrakmbe directly from the shell. It will display error messages if there is a problem and if not it just waits for input so good old ^C gets you out.
It would be really useful if the login/pick AUSkey process said SOMETHING when it fails.
Also I have not noticed anywhere when you get warned that your AUSkey is nearing expiry or expired, not even in the AUSkey management pages. Mind you it does tell you if its expired but you cannot get there without a valid AUSkey. You can check your expiry by looking in the keystore.xml and look at the field called <notAfter>. They currently seam to be about 1 year after creating (it used to be longer). That caught me out too.