socphoenix, 4 months ago

I had this when it was using a cups generic driver on a cannon I think printer. Switching to the manufacturers drivers fixed the issue.