Description of problem: Latest release fails to start Version-Release number of selected component (if applicable):fail2ban-0.8.8-1.fc17.noarch How reproducible:always Steps to Reproduce: 1.fail2ban-client start 2. 3. Actual results:Fails to start. Cannot load module common.version Expected results:fail2ban starts Additional info:At some point a test was added to only add the module path if fail2ban appears to be running from /usr. Now that /bin and /usr/bin are joined, the executable appears to be running in /bin rather than /usr/bin so fails to insert the /usr/share/fail2ban directory as a place to look for modules. Commenting out the test in fail2ban-server and fail2ban-client and adjusting the spacing fixes the problem.
fail2ban-0.8.8-3.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/fail2ban-0.8.8-3.fc18
fail2ban-0.8.8-3.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fail2ban-0.8.8-3.fc17
Package fail2ban-0.8.8-3.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fail2ban-0.8.8-3.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-2525/fail2ban-0.8.8-3.fc18 then log in and leave karma (feedback).
fail2ban-0.8.8-3.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 916158 has been marked as a duplicate of this bug. ***
fail2ban-0.8.8-3.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.