Re: non installed printer can not be removed
> On 17 Jun 2022, at 01:56, Gareth Evans <donotspam@fastmail.fm> wrote:
> On Thu 16 Jun 2022, at 22:13, Hans <hans.ullrich@loop.de> wrote:
>> Hi folks,
>>
>> I am struggeling with a little problem, I can not explain.
>>
>> A friend of mine uses a printer (Samsung SL-C480FW), which is connected to the
>> router with wireless. However, although there are no drivers and no ppd-files
>> installed, the printer is seen by cups (and also by system-printer-config) but
>> can not be used (think, because the missing ppd-file).
>>
>> When this is installed, udev-entries and so on are set, then the printer is
>> seen for example with ipp://192.168.*.*.
>>
>> However, printing does not work, although the printer gets data, but then
>> hangs. I believe, this is a driver problem (because this appeared, since my
>> friend got a new router (FritzBox).
>>
>> I hope, for this I will find a solution, so hints are welcome, buut not the
>> reason for this thread.
>>
>> Much more I am interested, to know, why I can not delete the printer in CUPS
>> or system-config-printer? Any printer I add, can be deleted, but the last
>> entry can not be deleted.
>>
>> What is wrong? Why does the kernel see the correct printer, and where does it
>> get its information? It is not connected at the USB-port, so no information
>> could be taken from this.
>>
>> Any ideas?
>>
>> Thanks for any help!
>>
>> Best regards
>>
>> Hans
>
> Various sources (but not HP documentation afaics) suggest this printer is airprint-compatible.
>
> https://www.amazon.co.uk/Samsung-C480FW-Colour-Multifunction-Printer/dp/B010NE2HKI
>
> https://productz.com/en/samsung-xpress-sl-c480fw/p/wxnG7
>
> If so, I would suggest "cannot delete" = continuous autodetection.
>
> What is the output of
>
> $ driverless
>
> As for not actually being able to print, I have a problem like that too which has only recently emerged with an airprint printer which worked until recently.
>
> You might find you can print (as I do) if you add a queue via lpadmin.
>
> As helped me recently:
>
> "# lpinfo -v
>
> to get a list of URLs (the one starting with ipp:// is the one
> necessary), and then something like
>
> # lpadmin -p Brother2740 -v IPP_URL_FROM_ABOVE -E -m everywhere"
>
> https://lists.debian.org/debian-user/2022/06/msg00212.html
>
Can anyone with a fax-capable MFP confirm that driverless autodetected printing works with CUPS on Debian 11 with the latest stable CUPS version?
My debug-enabled cups error log includes the following, which makes me wonder if it's being identified correctly:
Does this suggest it's being detected as (only) a fax? (Though this relates to a queue manually added with system-config-printer as nothing is autodetected)
D [17/Jun/2022:00:47:45 +0100] [Job 36] Resolving \"Brother MFC-L2740DW series\", regtype=\"_ipp._tcp\", domain=\"local.\"...
D [17/Jun/2022:00:47:45 +0100] [Notifier] state=3
D [17/Jun/2022:00:47:45 +0100] [Notifier] PrinterStateChanged
D [17/Jun/2022:00:47:45 +0100] [Job 36] Color Manager: Calibration Mode/Off
D [17/Jun/2022:00:47:45 +0100] [Job 36] PID 2953512 (/usr/lib/cups/filter/bannertopdf) exited with no errors.
D [17/Jun/2022:00:47:45 +0100] [Job 36] Calling FindDeviceById(cups-MFC-L2740DW_DLIPP)
D [17/Jun/2022:00:47:45 +0100] [Job 36] Found device /org/freedesktop/ColorManager/devices/cups_MFC_L2740DW_DLIPP
D [17/Jun/2022:00:47:45 +0100] [Job 36] Calling org.freedesktop.ColorManager.Device.Get(ProfilingInhibitors)
D [17/Jun/2022:00:47:45 +0100] [Job 36] Calling FindDeviceById(cups-MFC-L2740DW_DLIPP)
D [17/Jun/2022:00:47:45 +0100] [Job 36] Found device /org/freedesktop/ColorManager/devices/cups_MFC_L2740DW_DLIPP
D [17/Jun/2022:00:47:45 +0100] [Job 36] Calling GetProfileForQualifiers(Gray.Stationery.600dpi...)
D [17/Jun/2022:00:47:45 +0100] [Job 36] Found profile /org/freedesktop/ColorManager/profiles/MFC_L2740DW_DLIPP_Gray__
D [17/Jun/2022:00:47:45 +0100] [Job 36] Calling org.freedesktop.ColorManager.Profile.Get(Filename)
D [17/Jun/2022:00:47:45 +0100] [Job 36] Resolved as \"ipp://mfcl2740dw.local:631/ipp/faxout\"...
system-config-printer refuses to persist changes to the driver for autodetected queues with previous cups versions which do autodetect it, hanging on to the version including "...fax, driverless...".
Thanks,
Gareth
Reply to: