Re: Printing problem (was snapshot.debian.org)
Recent message with screenshots didn't get through (at least yet) - text below, plus another observation.
On Mon 6 Jun 2022, at 16:53, Gareth Evans <donotspam@fastmail.fm> wrote:
> On Mon 6 Jun 2022, at 16:23, Eduardo M KALINOWSKI
> <eduardo@kalinowski.com.br> wrote:
>> On 06/06/2022 10:48, Gareth Evans wrote:
>>> Not sure what's happened though as it worked perfectly with both auto-detected and manually-added printer profiles from Bullseye until a week or two ago. My logs suggest no update to system-config-printer. I did change the printer's hostname (on printer console) but both the printer and laptop have been restarted several times since then, printers re-added and re-auto-detected etc.
>>
>> In my case it never worked any other way. But I never dug very deep to
>> try to find out why.
>>
>>> Why should adding via the command line work, but not via system-config-printer or localhost:631?
>>
>> I guess adding it in CUPS web interface (localhost:631) should work, if
>> the exact same parameters are selected: the ipp:// url and the "CUPS PPD
>> generator" (selected by "-m everywhere" option) as opposed to
>> "cups-filters PPD generator".
>>
>> That might be the explanation (at least for my case). From what I
>> understand from https://wiki.debian.org/CUPSDriverlessPrinting , there
>> are those two options, and "The cups-filters PPD generator is used by
>> default with cups-browsed". In theory either should work, but there's
>> probably some quirk in the printer and some small difference between the
>> two methods.
>>
>> --
>> Tchurin-tchurin-tchun-clain!
>>
>> -- Chapolim
>>
>> Eduardo M KALINOWSKI
>> eduardo@kalinowski.com.br
>
> When adding a printer with system-config-printer, it is detected and
> listed under "Network Printer" in the list (when expanded) (twice). I
> currently see what's in the screenshots attached, but sometimes the
> "IPP network printer via DNS-SD" connection option changes to something
> involving AppSocket/... at the beginning.
>
> There seem to be different connections available at different times.
>
> Any ideas why that should be?
>
> It seems to me that something has changed. Given the problem was the
> same with an identical printer on a different network, I guess it's
> something to do with CUPS (or its config) rather than the printer
> itself misbehaving. I had factory-reset it a couple of days ago.
>
> Thanks,
> Gareth
>
>
> Attachments:
> * Screenshot at 2022-06-06 16-39-52.png
> * Screenshot at 2022-06-06 16-40-03.png
$ driverless list
DEBUG: Started ippfind (PID 95003)
"driverless:ipp://Brother%20MFC-L2740DW%20series._ipp._tcp.local/" en "Brother" "Brother MFC-L2740DW series, driverless, cups-filters 1.28.7" "MFG:Brother;MDL:MFC-L2740DW series;CMD:PWGRaster,AppleRaster,URF,PWG;"
"driverless-fax:ipp://Brother%20MFC-L2740DW%20series._ipp._tcp.local/" en "Brother" "Brother MFC-L2740DW series, Fax, driverless, cups-filters 1.28.7" "MFG:Brother;MDL:MFC-L2740DW series;CMD:PWGRaster,AppleRaster,URF,PWG;"
DEBUG: ippfind (PID 95003) exited with no errors.
The error log except attached earlier includes:
[line no] log text
[30] D [06/Jun/2022:13:32:04 +0100] [Job 6] printer-is-accepting-jobs boolean true
D [06/Jun/2022:13:32:04 +0100] [Job 6] printer-state enum idle
D [06/Jun/2022:13:32:04 +0100] [Job 6] printer-state-reasons keyword none
D [06/Jun/2022:13:32:04 +0100] [Job 6] ---- end-of-attributes-tag ----
D [06/Jun/2022:13:32:04 +0100] [Job 6] IPP/2.0 Get-Job-Attributes #22
D [06/Jun/2022:13:32:04 +0100] [Job 6] ---- operation-attributes-tag ----
D [06/Jun/2022:13:32:04 +0100] [Job 6] attributes-charset charset utf-8
D [06/Jun/2022:13:32:04 +0100] [Job 6] attributes-natural-language naturalLanguage en-gb
D [06/Jun/2022:13:32:04 +0100] [Job 6] printer-uri uri ipp://mfcl2740dw.local:631/ipp/faxout
^^^^^^^^^^
Fax????
D [06/Jun/2022:13:32:04 +0100] [Job 6] job-id integer 82
<snip>
D [06/Jun/2022:13:32:04 +0100] [Job 6] ---- unsupported-attributes-tag ----
D [06/Jun/2022:13:32:04 +0100] [Job 6] requested-attributes keyword job-media-sheets-completed
D [06/Jun/2022:13:32:04 +0100] [Job 6] ---- job-attributes-tag ----
D [06/Jun/2022:13:32:04 +0100] [Job 6] job-id integer 82
D [06/Jun/2022:13:32:04 +0100] [Job 6] job-impressions-completed integer 0
D [06/Jun/2022:13:32:04 +0100] [Job 6] job-name nameWithoutLanguage Test Page
D [06/Jun/2022:13:32:04 +0100] [Job 6] job-originating-user-name nameWithoutLanguage user
D [06/Jun/2022:13:32:04 +0100] [Job 6] job-state enum canceled
D [06/Jun/2022:13:32:04 +0100] [Job 6] job-state-reasons keyword job-canceled-at-device"
^^^^^^^^^^^^^^^^^^^^^^
...even though it wasn't (at least not by me).
Does any of this suggest it's presenting/being auto-detected as (only) a fax machine ... and cancelling the job because the fax function isn't set up/connected/never has been?
Thanks,
Gareth
Reply to: