Description of problem:
After sending a job to a remote printer, cups fails to determine that it has
completed.

Version-Release number of selected component (if applicable):
cups-1.2.1-1.7

How reproducible:
Always

Steps to Reproduce:
1. Print a job from GNOME with eggcups running.
2. tail -f /var/log/cups/access_log or tail -f /var/log/error_log
3.
  
Actual results:
In access_log, the following cycle of messages repeats every 5 seconds:

localhost - - [27/Jun/2006:08:35:07 -0400] "POST / HTTP/1.1" 200 75
CUPS-Get-Printers successful-ok
localhost - - [27/Jun/2006:08:35:08 -0400] "POST /printers/laser HTTP/1.1" 200
138 Get-Job-Attributes client-error-not-found
localhost - - [27/Jun/2006:08:35:13 -0400] "POST /printers/laser HTTP/1.1" 200
138 Get-Job-Attributes client-error-not-found

In error_log, the following message repeats every 5 seconds:

E [27/Jun/2006:08:39:33 -0400] Get-Job-Attributes client-error-not-found: Job
#62 does not exist!

The eggcups applet never turns grey and the document status window always shows
status unknown.


Expected results:
No errors, eggcups applet greys out, job status window indicates that job has
completed.

Additional info:

Filed under cups because the problem started occurring when I updated to latest
cups errata release.

This is a very annoying problem on a laptop as status messages keep the disk
spinning.