Red Hat Bugzilla – Bug 625900
STR #3436: Jobs buttons not working correctly when viewing a specific printer
Last modified: 2012-02-20 22:09:36 EST
Description of problem:
After selecting a printer to view under the Printers tab in the
web interface; the "Show Completed Jobs," "Show All Jobs," and
"Show Active Jobs" buttons do not behave properly. They should be
showing results based on the specific printer selected, but they
are showing results globally across all printers.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install RHEL 5.5 with cups
2. Add various printers and send some jobs to be printed
3. Access CUPS web interface and click "Printers"
4. Select a printer
5. Click "Show Completed Jobs" or "Show All Jobs"
Jobs from all printers are shown.
Jobs from only the selected printer should be shown.
Appears to be the same as STR #3436. Patch from that STR has
resolved the situation in the customer's environment.
Created attachment 440007 [details]
Patch adapted from upstream by firstname.lastname@example.org
I note that he upstream patch at http://www.cups.org/strfiles/3436/str3436.patch seems to set PRINTER_URI_SUPPORTED to be a URL fragment rather than the destination as the above patch does.
Since the str3436 patch is for a version of cups which doesn't add ? to the end of the url fragment at this point I went for an ugly hack to mimic the behaviour as closely as possible, and in simple tests it seems to work for us.
Created attachment 456547 [details]
also based on upstream pacth...
Just my (ugly) version of the patch...
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.