Description of problem: Trying to refer to the local machine by any name other than 'localhost' should fail but instead libcups gets stuck in a loop. Version-Release number of selected component (if applicable): cups-1.4-0.rc1.15.fc11.x86_64 How reproducible: 100% Steps to Reproduce: 1.lpstat -h localhost4 -s Actual results: Never finishes. Expected results: Error message.
For me it works good: Version-Release number of selected component (if applicable): cups-1.4-0.rc1.18.fc11.x86_64 Steps to Reproduce: 1.lpstat -h localhost4 -s Actual results: no system default destination lpstat: No such file or directory lpstat: No such file or directory
Oh, it only happens when using an actual fully-qualified domain name. For instance, here I use 'lpstat -h worm.elk -s'.
cups-1.4.1-1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/cups-1.4.1-1.fc11
cups-1.4.1-1.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update cups'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-10152
cups-1.4.1-2.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update cups'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-10152
cups-1.4.1-4.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update cups'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-10152
cups-1.4.1-4.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.