Description of problem: When a new printer is added with system-config-printer, literal spaces the URI are rendered incorrectly. This causes Samba errors and does not allow the printer to print. Version-Release number of selected component (if applicable): CUPS 1.4.6 Samba Client 3.5.8 system-config-printer 1.3.2 How reproducible: Easily, at least on my machine. Steps to Reproduce: 1. Open system-config-printer 2. Click "Add" 3. Click "Network Printer" and "Find Network Printer" 4. Enter hostname and click "Find" 5. Configure or don't configure firewall when prompted, result is the same. 5. Click "Browse" 6. Find desired printer under workgroup and hostname 7. Select driver 8. Print test page Actual results: Test page never prints. System-config-printer shows "Printer State: Processing -- Unable to connect to CIFS host, will retry in 60 seconds..." The URI of the printer does not show a "%20" for a literal space, and instead only shows a "20". E.g. smb://WORKGROUP/PC/HP20Photosmart20Plus20B209a-m instead of smb://WORKGROUP/PC/HP%20Photosmart%20Plus%20B209a-m If the URI is changed to the correct syntax, the test page prints fine. Expected results: Test page should print and the URI should automatically have the correct symbols for a literal space. Additional info:
Fixed upstream (8f29215).
system-config-printer-1.3.3-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/system-config-printer-1.3.3-1.fc15
Package system-config-printer-1.3.3-1.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing system-config-printer-1.3.3-1.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/system-config-printer-1.3.3-1.fc15 then log in and leave karma (feedback).
system-config-printer-1.3.3-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.