See bug 1003193 for details.
I expect this is in reference to libusb-compat's 0be16b8 (use atexit() to call libusb_exit(), 2013-04-04) [1] which landed in libusb-compat v0.1.5, so I thought I'd drop a pointer for others hitting this issue. [1]: http://www.libusb.org/ticket/130
For those waiting for a fix for this, sorry for taking so long to fix this. An updated package fixing this is now on its way.
libusb-0.1.5-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/libusb-0.1.5-3.fc20
libusb-0.1.5-3.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/libusb-0.1.5-3.fc19
Package libusb-0.1.5-3.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libusb-0.1.5-3.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-2544/libusb-0.1.5-3.fc19 then log in and leave karma (feedback).
libusb-0.1.5-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
libusb-0.1.5-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.