Bug 592352

Summary: Should escape job titles in error dialog markup
Product: Red Hat Enterprise Linux 6 Reporter: Tim Waugh <twaugh>
Component: system-config-printerAssignee: Tim Waugh <twaugh>
Status: CLOSED CURRENTRELEASE QA Contact: Yulia Kopkova <ykopkova>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: azelinka, jpopelka, ovasik, twaugh, ykopkova
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: system-config-printer-1.1.16-11.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 592350 Environment:
Last Closed: 2010-11-15 14:49:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 592350    
Bug Blocks:    

Description Tim Waugh 2010-05-14 15:56:02 UTC
Also affects RHEL-6.

+++ This bug was initially created as a clone of Bug #592350 +++

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

Comment 1 Tim Waugh 2010-05-14 15:56:21 UTC
Fix is in commit d850270.

Comment 2 RHEL Program Management 2010-05-14 17:04:53 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 5 releng-rhel@redhat.com 2010-11-15 14:49:37 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.