Bug 592352 - Should escape job titles in error dialog markup
Should escape job titles in error dialog markup
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: system-config-printer (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Tim Waugh
Yulia Kopkova
Depends On: 592350
  Show dependency treegraph
Reported: 2010-05-14 11:56 EDT by Tim Waugh
Modified: 2010-11-15 09:49 EST (History)
5 users (show)

See Also:
Fixed In Version: system-config-printer-1.1.16-11.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 592350
Last Closed: 2010-11-15 09:49:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 567324 None None None Never

  None (edit)
Description Tim Waugh 2010-05-14 11:56:02 EDT
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.

Comment 1 Tim Waugh 2010-05-14 11:56:21 EDT
Fix is in commit d850270.
Comment 2 RHEL Product and Program Management 2010-05-14 13:04:53 EDT
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
Comment 5 releng-rhel@redhat.com 2010-11-15 09:49:37 EST
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.

Note You need to log in before you can comment on or make changes to this bug.