On Mon 27 Mar 2017 at 18:45:05 +0200, Dimitri Chausson wrote: > Hi Brian,
Hello Dimitri. > Thanks for asking. I still have this issue, and I am surprised that > nobody reported similar things. This is on testing/unstable? Similar issues have been reported and have been dealt with successfully. They were usually printer-specific and not always easy to track down. > How to know if it is a hardware problem ? The best way would be to > print on another OS .. (I do not have another one yet) Please take a look at LP #872483. Trying the suggestion in comment #6 might indicate a hardware problem or not. The techniques in comment #56 have helped in the past. Regards, Brian.
