TurboPrint & PrintFab

Hi

I've not had a problem with Turboprint on Linux until now. I've installed 2.58-1 using tgz and deb with the same result.

The printer fails to respond to the correct Ip address given on its front panel i.e. 192.168.1.31. I have pinged this address and get the following:

PING 192.168.1.31 (192.168.1.31): 56 data bytes
64 bytes from 192.168.1.31: icmp_seq=0 ttl=64 time=162.969 ms
64 bytes from 192.168.1.31: icmp_seq=1 ttl=64 time=84.029 ms
64 bytes from 192.168.1.31: icmp_seq=2 ttl=64 time=116.576 ms
64 bytes from 192.168.1.31: icmp_seq=3 ttl=64 time=27.024 ms
64 bytes from 192.168.1.31: icmp_seq=4 ttl=64 time=49.234 ms
64 bytes from 192.168.1.31: icmp_seq=5 ttl=64 time=72.091 ms
64 bytes from 192.168.1.31: icmp_seq=6 ttl=64 time=134.777 ms
64 bytes from 192.168.1.31: icmp_seq=7 ttl=64 time=138.829 ms
^C--- 192.168.1.31 ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max/stddev = 27.024/98.191/162.969/44.536 ms


I've added the printer to the Control using both 'standard printer' OR 'other printer' using CUPS URI = bjnp://192.168.1.31:8611 followed by the printer name. Result is no communication. No test page. The Status Monitor remains greyed out with no reponse. If I close Control and then reopen the printer setup is gone.

The installation puts the bjnp file under /usr/lib/turboprint. It's also under /usr/lib/cups/backend

Can anyone help here please?

I assume from the lack of reponses that I've done everything possible?

The odd thing is that I have 'simple-scan' installed and it works! So the ip address is correct then.

Cliff

I may have found the issue.

E:Unable to locate package python-gobject

This is present at a source file install

Now I have python-gobject installed, in fact I have reinstalled it.

So. Does anyone know if one can pass options/locations to a source file install. I suspect not

Cliff

Hello, older Canon printers use the "BJNP" network protocol, newer ones accept standard network printing protocols like "LPD" and "Socket", some support both. I am not 100% sure about the MG7150.

You can try the following URIs in TurboPrint Control:

bjnp://192.168.1.31
socket://192.168.1.31
lpd://192.168.1.31

where 192.168.1.31 is the printer's IP address (adjust if necessary).
The port number ":8611" at the end of the URI is optional.

For debugging purposes, you can open a Terminal window and enter the command

/usr/lib/cups/backend/bjnp

and check if the printer is found and listed (printer must be powered on and connected via LAN or WiFi).

Also helpful might be the TurboPrint log file /var/log/turboprint/print.log - you can send it by email to mail <at> turboprint <dot> de , please refer to this forum post.

Thanks for that

bjnp://192.168.1.31:8611 or something similar has always worked for me. This time I suspect it is a graphical issue. See my last post.

I just installed Turboprint into another distro from source and it works straight away. The Turboprint Monitor is visible even before setting a printer.

In mine it's greyed out and setting up a printer is lost when Turboprint closed down.

Cliff

Incidently '/usr/lib/cups/backend/bjnp' gives:

network bjnp "Unknown" "Canon network printer"

This is absurd. The ping works and the printer is recognised in the other distro.

This is really strange. Could there be a problem with network or firewall configuration?

Another idea:
As you wrote that the printer setup is lost when you reopen TurboPrint Control, it looks like the printer cannot be saved to the system - possibly because of missing access rights. Please try to start TurboPrint Control from a terminal window with super-user rights by entering "sudo turboprint" (you will be asked for your user password then). Maybe printing fails because the printer is not installed properly in the printing system.

Thanks

The suspected graphical was a red herring. The same errors were present in the setup on the other distro which works.

Just installed my printer by going to http://localhost:631. It appears in Turboprint as normal. I assume it should remain there now!

Can't test it just yet but see no reason it shouldn't work.

I was working with super-user rights when trying to setup through Turboprint. This strange.

Cliff

lpstat -t gives:

scheduler is running
no system default destination
device for MG7150: bjnp://192.168.1.31:8611
MG7150 accepting requests since Wed 17 Dec 2025 09:42:49 PM GMT
printer MG7150 is idle. enabled since Wed 17 Dec 2025 09:42:49 PM GMT