On 25/02/2020 04:53, gumb wrote:
On 24/02/2020 11:57, jdd@dodin.org wrote:
Le 24/02/2020 à 11:51, gumb a écrit :
The print queue in either cups interface or the Plasma printer applet shows all these attempts as 'completed' jobs, and the printer status as 'ready'. But there's no actual communication.
did you try to ping the printer? print with lpr to see if there is a message? what dmesg say? logs?
I can ping the printer:
ping 192.168.0.57 PING 192.168.0.57 (192.168.0.57) 56(84) bytes of data. 64 bytes from 192.168.0.57: icmp_seq=1 ttl=255 time=234 ms 64 bytes from 192.168.0.57: icmp_seq=2 ttl=255 time=216 ms 64 bytes from 192.168.0.57: icmp_seq=3 ttl=255 time=198 ms 64 bytes from 192.168.0.57: icmp_seq=4 ttl=255 time=180 ms 64 bytes from 192.168.0.57: icmp_seq=5 ttl=255 time=161 ms ^C --- 192.168.0.57 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4004ms rtt min/avg/max/mdev = 161.932/198.043/234.167/25.514 ms
I don't know what you mean by print with lpr. I've already posted cups logs elsewhere on this thread and dmesg doesn't show anything related. I've just tried changing the protocol in the CUPS interface, to http and then the HP/JetDirect you mentioned elsewhere, specifying socket://192.168.0.57:9100 (I don't know where this 9100 comes from but I see it mentioned everywhere - does it require entering in the firewall config?).
I found this FAQ on the Brother website: https://www.brother.fr/services-et-supports/dcp-j572dw/faqs/how-to-trouble-s...
and I followed it through but it's always the same. I try printing a test page from the CUPS interface, the print job shows as processing and after a few seconds disappears as though all is well, but there's nothing actually being sent to the printer.
Hmm, well colour me hrmphed. Nothing isn't making any sense here. Printing is still completely impossible. According to all sources, everything is fine. There's just no actual transmission of print documents. I found out that the mysterious lpr you refer to is related to lpd and referred to as lpd/lpr in certain places, so I tried the script setup again with that option. Like so many other options, it reports back: lpadmin: Bad device-uri "lpd". But it completes the script install and asks me to specify the ip address at the end, which I always keep the same, 192.168.0.57. I then went into CUPS interface, Modify Printer, and selected the lpd option. The example it gives has /queue appended. I don't know if I should copy that literally of if 'queue' refers to some variable that I should know, so I just entered the address as lpd://192.168.0.57/queue In any case, it still doesn't work. I've tried most of the options now, from the script install and then putting CUPS / YaST up to date afterwards. Nothing succeeds. On the contrary, I just looked in YaST Scanner setup for the first time. It has one entry under Driver for 'brother4' with 'at' under Scanner. And another with Driver listed as 'dev0,Brother,DCP-J572DW', and 'Brother DCP-J572DW at dev0' under Scanner. If I try to edit either of these, there's no corresponding file in the list. The only four Brother entries are for other models all listed as unsupported, and there's no place to select any custom file. The test option produced failure messages. So I thought great, even if I get printing working there'll be no scanning going on here. And then I opened skanlite, it picked up my scanner immediately, and I proceeded to preview and scan a document perfectly. So I have a printer setup that says all is fine but doesn't work at all, and a scanner setup that says all is bust and works fine. FFS. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org