Description of problem: In /lib/systemd/system/omniNames.service there is typo in: Group=OmniORB but there should be: Group=omniORB Otherwise startup fails on: Failed at step GROUP spawning /usr/bin/omniNames: No such process Version-Release number of selected component (if applicable): omniORB-server-4.1.6 How reproducible: systemctl start omniNames fails Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
thanks for reporting this issue, it will be fixed by an upcoming update.
omniORB-4.1.6-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/omniORB-4.1.6-2.fc17
omniORB-4.1.6-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/omniORB-4.1.6-2.fc16
omniORB-4.1.6-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/omniORB-4.1.6-2.fc15
Package omniORB-4.1.6-2.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing omniORB-4.1.6-2.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-2046/omniORB-4.1.6-2.fc17 then log in and leave karma (feedback).
Thanks. I have tested, works for me, so I added karma.
omniORB-4.1.6-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
omniORB-4.1.6-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
omniORB-4.1.6-2.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.