LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux Deepin (https://www.linuxquestions.org/questions/linux-deepin-101/)
-   -   Brother MFC-J4510DW does not print although print jobs complete successfully (https://www.linuxquestions.org/questions/linux-deepin-101/brother-mfc-j4510dw-does-not-print-although-print-jobs-complete-successfully-4175621598/)

willi53 01-14-2018 08:06 AM

Brother MFC-J4510DW does not print although print jobs complete successfully
 
3 Attachment(s)
I am having a weird problem with CUPS and my Brother printer. Whatever I print gets entered into the printer queue and completes successfully, yet the printer sits there idling and does nothing. Scanning works!

I re-installed the printer using different methods and different URIs, it is always the same result (unless I specify a wrong URI of course).

Method 1: http://support.brother.com/g/s/id/li...ion_prn1a.html, using an lpd:// URL.

Method 2: https://gist.github.com/ragusa87/89806ffba57ef9f5a67a, which is basically the same, just with an ipp:// URL.

Here are a few debugging commands:

Code:

root@wzb-PC:/home/wzb# /usr/lib/cups/backend/snmp
network lpd://BRN30055C2C6AED/BINARY_P1 "Brother MFC-J4510DW" "Brother MFC-J4510DW" "MFG:Brother;CMD:HBP,BRPJL,URF;MDL:MFC-J4510DW;CLS:PRINTER;CID:Brother IJ Type3;URF:SRGB24,W8,CP1,IS1,MT1-8-11,OB9,PQ4-5,RS300,OFU0,DM4;" ""

Code:

root@wzb-PC:/home/wzb# lpinfo -l -v
[truncated]
Device: uri = socket://192.168.178.23
        class = network
        info = Brother MFC-J4510DW on 192.168.178.23
        make-and-model = Brother MFC-J4510DW
        device-id = MFG:Brother;CMD:HBP,BRPJL,URF;MDL:MFC-J4510DW;CLS:PRINTER;CID:Brother IJ Type3;URF:SRGB24,W8,CP1,IS1,MT1-8-11,OB9,PQ4-5,RS300,OFU0,DM4;
        location =
Device: uri = ipp://192.168.178.23
        class = network
        info = Brother MFC-J4510DW on 192.168.178.23
        make-and-model = Brother MFC-J4510DW
        device-id = MFG:Brother;CMD:HBP,BRPJL,URF;MDL:MFC-J4510DW;CLS:PRINTER;CID:Brother IJ Type3;URF:SRGB24,W8,CP1,IS1,MT1-8-11,OB9,PQ4-5,RS300,OFU0,DM4;
        location =
Device: uri = dnssd://Brother%20MFC-J4510DW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-30055c2c6aed
        class = network
        info = Brother MFC-J4510DW
        make-and-model = Brother MFC-J4510DW
        device-id = MFG:Brother;MDL:MFC-J4510DW;CMD:HBP,BRPJL,URF;
        location =
Device: uri = lpd://BRN30055C2C6AED/BINARY_P1
        class = network
        info = Brother MFC-J4510DW
        make-and-model = Brother MFC-J4510DW
        device-id = MFG:Brother;CMD:HBP,BRPJL,URF;MDL:MFC-J4510DW;CLS:PRINTER;CID:Brother IJ Type3;URF:SRGB24,W8,CP1,IS1,MT1-8-11,OB9,PQ4-5,RS300,OFU0,DM4;
        location =
Device: uri = ipp://BRN30055C2C6AED.local:631/ipp/printer
        class = network
        info = Brother MFC-J4510DW (driverless)
        make-and-model = Brother MFC-J4510DW
        device-id = MFG:Brother;MDL:MFC-J4510DW;CMD:AppleRaster,URF;
        location =

Code:

wzb@wzb-PC:~$ lp cupslog.txt
Anfrage-ID istMFCJ4510DW-33 (1 Datei(en))  <--- nothing prints, and the job completes

The CUPS error log and a few screenshots are attached.

I would be grateful for any hints and suggestions.

Cheers, Willi

ferrari 01-14-2018 01:48 PM

This type of behaviour can happen when there are missing libraries (required by the filter) sometimes. Increasing the verbosity of CUPS logging may yield further information about what is failing. That can be done with
Code:

cupsctl --debug-logging
Examine the CUPS error log after a print job has been sent again.

I'm not familiar with deepin at all, but I did find this thread which may provide some useful advice (particularly the last post by kelbodelta)...
https://bbs.deepin.org/forum.php?mod...ead&tid=131621

willi53 01-15-2018 01:31 PM

Thanks for your suggestion, ferrari! :thumbsup:

I actually suspected something in the filter chain. But now it is getting embarrassing ...

I switched on the detailed CUPS error log and tried to print a page ... and what a surprise - it printed !!!

This kind of Murphy's law I actually like. But don't ask me what it was. Perhaps it just needed another reboot to activate something that was not active before.

Anyway, perhaps this thread and the links can help somebody else with a similar problem.

Cheers, Willi

ferrari 01-15-2018 02:04 PM

Thanks for the update.


All times are GMT -5. The time now is 02:58 PM.