We have a server running Centos-3 with all latest updates. The server hosts 3 printers for us which are accessed by various Windows clients.
About 3 months ago we noticed that, after a cups update, if you looked at the print queues in Windows they would show old jobs that had long been printed. After a further cups update this quirk went away but it's just come backs again - possibly after the recent cups update. Or is it me!? Anything worth checking?
Thanks
Nigel Kendrick
Hi Nigel,
On Tue, Feb 08, 2005 at 01:35:55PM -0000, Nigel Kendrick wrote:
We have a server running Centos-3 with all latest updates. The server hosts 3 printers for us which are accessed by various Windows clients.
About 3 months ago we noticed that, after a cups update, if you looked at the print queues in Windows they would show old jobs that had long been printed. After a further cups update this quirk went away but it's just come backs again - possibly after the recent cups update. Or is it me!? Anything worth checking?
Sounds like this:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145639
which seems to be a samba bug introduced in 3.0.4 (?), still there in 3.0.9, and apparently fixed in 3.0.11 (or possibly cvs HEAD, not sure).
There's a patch on that bug report that seems to fix it for most people anyway - we're about to try it on one of our RHEL3 boxes.
Cheers, Gavin
Same here too,
I think last thing I've updated was cups. Try to downgrade cups to previous version. Very annoying, got to say, this happenes for a 2nd or 3rd time in a year period. It is a shame that this very obvious bug recures so many times during this year. And there are people paying serious money to redhat ....
On Tue, 8 Feb 2005 13:35:55 -0000, Nigel Kendrick nigel.kendrick@petdoctors.co.uk wrote:
We have a server running Centos-3 with all latest updates. The server hosts 3 printers for us which are accessed by various Windows clients.
About 3 months ago we noticed that, after a cups update, if you looked at the print queues in Windows they would show old jobs that had long been printed. After a further cups update this quirk went away but it's just come backs again - possibly after the recent cups update. Or is it me!? Anything worth checking?
Thanks
Nigel Kendrick
CentOS mailing list CentOS@caosity.org http://lists.caosity.org/mailman/listinfo/centos