Hi Etienne and Bart
And, thanks for bringing attention to the bug...
It has been a while since I reported submitted the report and I must admit that I do not quite remember the details. I have since found a workaround (I'm able to access the printers directly, thus bypassing the print server entirely).
At the time, I found that my symptoms fitted the ones described in the CUPS report -- printing stopped working after CUPS upgrade from 1.3.8, the errors I got, an identical issue was seen by a collegue running OSX etc (and incidently I am at the same university as Micket in the CUPS report).
But, again, my conclusions were based on symptoms only. I'll see if I can find some time to investigate it again and will get back. So, keep it as a duplicate for the time being.
Hi Etienne and Bart
And, thanks for bringing attention to the bug...
It has been a while since I reported submitted the report and I must admit that I do not quite remember the details. I have since found a workaround (I'm able to access the printers directly, thus bypassing the print server entirely).
At the time, I found that my symptoms fitted the ones described in the CUPS report -- printing stopped working after CUPS upgrade from 1.3.8, the errors I got, an identical issue was seen by a collegue running OSX etc (and incidently I am at the same university as Micket in the CUPS report).
But, again, my conclusions were based on symptoms only. I'll see if I can find some time to investigate it again and will get back. So, keep it as a duplicate for the time being.
All the best
Nikke