Bug#795404: cups-backend-bjnp: stops printing after some lines
On Mon 17 Aug 2015 at 22:51:08 +0200, Björn Siebke wrote:
> thank you once again for trying to get that printer working!
Thank you in anticipation of some more testing from from you, Björn.
>
> > We can test if this behaviour is independent of CUPS and the filtering
> > system too,
> >
> > DEVICE_URI=bjnp://db-printer.fritz.box:8611 /usr/lib/cups/backend/bjnp 1 1 1 1 1 /etc/services
>
> I tried this both with and without sudo:
>
> $ sudo DEVICE_URI=bjnp://db-printer.fritz.box:8611
> /usr/lib/cups/backend/bjnp 1 1 1 1 1 /etc/services
> [sudo] password for bjoern:
> INFO: Attempting to connect to host db-printer.fritz.box on port 8611
> STATE: +connecting-to-device
> STATE: -connecting-to-device
> INFO: Connected to db-printer.fritz.box...
> DEBUG: Connected to [192.168.178.27]:8611 (IPv4)...
The printer is found; UDP broadcasts are used, I think. It doesn't look
like you have a network problem.
> PAGE: 1 1
> DEBUG: bjnp_backendRunLoop(print_fd=4, device_fd=5
> INFO: Sent print file, 0 bytes...
> INFO: Ready to print.
>
> But the printer did nothing.
This looks like a problem with the backend. I am a bit surprised no data
are shown as being sent to the printer even though it didn't print.
Please enable debug logging in CUPS as described at
https://wiki.debian.org/Dissecting%20and%20Debugging%20the%20CUPS%20Printing%20System
Empty the error_log and do
lp -d queue_name -o raw some_small_file
This does the same as the previous command and uses only the backend
filter. Attach the error_log to your next mail.
It is rare for me to complile a program from source code but compiling
the bjnp backend is within my capabilities. So would you proceed as
follows:
1. Download the 2.0 version from
http://sourceforge.net/projects/cups-bjnp/
2. Unpack with
tar zvxf cups-bjnp-2.0.tar.gz
3. Download the gcc, libcups2-dev and make packages.
4. Do './configure' and 'make' in the unpacked directory. The commands
should run without error and you should end up with a bjnp binary. It
can be reduced in size with 'strip bjnp' but I don't think this is
strictly necessary for it to work.
5. Replace the present backend with this new one, matching permissions
and ownership with
chown root.root bjnp
chmod 755 bjnp
6. Print and report.
I do not think I can devise anything else for you to do after this.
> >> What do you mean by that? Ping the router? Ping cups (which is on my
> >> laptop)?
> >
> > Ping the printer is what I meant.
>
> I then tried to ping.
>
> $ ping db-printer.fritz.box:8611
> ping: unknown host db-printer.fritz.box:8611
ping doesn't need a port number. Leave off the ":8611".
> Then I looked up the IP adress and changed the router to give the
> printer a fixed IP adress.
>
> $ ping 192.168.178.27
> PING 192.168.178.27 (192.168.178.27) 56(84) bytes of data.
> 64 bytes from 192.168.178.27: icmp_seq=1 ttl=64 time=5.73 ms
> 64 bytes from 192.168.178.27: icmp_seq=2 ttl=64 time=7.56 ms
> 64 bytes from 192.168.178.27: icmp_seq=3 ttl=64 time=5.09 ms
> 64 bytes from 192.168.178.27: icmp_seq=4 ttl=64 time=7.13 ms
> 64 bytes from 192.168.178.27: icmp_seq=5 ttl=64 time=5.68 ms
> 64 bytes from 192.168.178.27: icmp_seq=6 ttl=64 time=7.40 ms
> 64 bytes from 192.168.178.27: icmp_seq=7 ttl=64 time=5.09 ms
> 64 bytes from 192.168.178.27: icmp_seq=8 ttl=64 time=5.25 ms
> 64 bytes from 192.168.178.27: icmp_seq=9 ttl=64 time=4.98 ms
> 64 bytes from 192.168.178.27: icmp_seq=10 ttl=64 time=4.97 ms
> 64 bytes from 192.168.178.27: icmp_seq=11 ttl=64 time=6.70 ms
> 64 bytes from 192.168.178.27: icmp_seq=12 ttl=64 time=4.93 ms
> ^C
> - --- 192.168.178.27 ping statistics ---
> 12 packets transmitted, 12 received, 0% packet loss, time 11015ms
> rtt min/avg/max/mdev = 4.938/5.881/7.567/0.987 ms
>
> This worked!
> So I did some tests by changing the URI in settings.
>
> bjnp://db-printer.fritz.box:8611 -> problem as decribed initially
> ipp://db-printer.fritz.box:8611 -> printer not reachable
> bjnp://192.168.178.27 -> problem as decribed initially
> ipp://192.168.178.27 -> works!
>
> Finally, I removed the package cups-backend-bjnp. Everything still works!
Perhaps another indication the bjnp backend is misbehaving.
Cheers,
Brian.
Reply to: