Try this: echo . | lp -t "foo <bar>" for a queue that is enabled and accepting jobs, but where the printer isn't actually switched on (so that the backend process will start up and just wait until it can print) and run 'kill -11 $PID' on the backend process. system-config-printer-applet will display a message containing <span> markup. Easy fix, already upstream. system-config-printer-1.1.18-6.fc11
system-config-printer-1.1.19-1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/system-config-printer-1.1.19-1.fc11
system-config-printer-1.1.19-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/system-config-printer-1.1.19-1.fc12
system-config-printer-1.1.19-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 system-config-printer'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/system-config-printer-1.1.19-1.fc11
system-config-printer-1.1.19-1.fc12 has been pushed to the Fedora 12 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 system-config-printer'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/system-config-printer-1.1.19-1.fc12
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
system-config-printer-1.1.19-3.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.