severity 795404 important
thanks
Hello Björn. Thank you for your report. I think it is reasonable to
assume that having printed on one occasion you will be able to do it
again. Hence reducing severity.
On Thu 13 Aug 2015 at 19:48:29 +0200, Björn Siebke wrote:
> * What led up to the situation?
> Yesterday I newly installed my Canon Pixma MG6650 - it worked. I successfully
> printed some pages. Today, after having changed nothing, I tried it again.
>
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
> Clicked on "print" in LOWriter.
Rather than having to take into account what an application does I'd do
test printing with a small text file or PDF using the lp command.
> * What was the outcome of this action?
> The printer started with the first lines of the document and then stopped. The
> printer's display showed a printing process going on. The queue told me there
> was no connection ("printer connected?"). I used the troubleshooting dialogue
> (protocol attached).
Even though it looks like the printer was found
'device-id':
'MFG:Canon;CMD:BJL,BJRaster3,BSCCe,NCCe,IVEC,IVECPLI;SOJ:BJNP2,BJNPe;MDL:MG6600
series;CLS:PRINTER;DES:Canon MG6600
series;VER:3.010;STA:10;FSI:00;HRI:D;MSI:AOFF,B015,DAT,E3,HFSF,JOFF,K21000700,LOFF;PDR:4;PSE:ADMM96370;CID:CA_IVEC1TYPE4_IJP;',
'device-info': 'Canon MG6600 series db-printer.fritz.box',
'device-make-and-model': 'Canon MG6600 series'}}
and there was some printing it wouldn't do any harm to look at the
network setup first. Switching db-printer.fritz.box and the printer off
for a few minutes before reconnecting the power is worth a go. You could
also consider using a fixed address and putting it in the device-uri
when the queue is created. Pinging the server while printing would test
it doesn't disappear.
The message
'printer-state-message': u"Network host 'db-printer.fritz.box' is busy; will
retry in 15 seconds...",
comes from the bjnp backend.
Let's see how you go with that before we move on to other things.
Regards,
Brian.
