Bug#979177: cups-filters-core-drivers: Adding a printer impossible because "driverless" is too slow

2021-01-07 Thread Till Kamppeter

I have released cups-filters 1.28.7 with the fix now.

https://github.com/OpenPrinting/cups-filters/releases/tag/1.28.7



Bug#979177: cups-filters-core-drivers: Adding a printer impossible because "driverless" is too slow

2021-01-07 Thread Till Kamppeter
I have investigated the problem further and the problem is caused by 
"driverless" sending get-printer-attributes IPP requests to each printer 
it lists, to check the quality of driverless printing support. See


https://github.com/OpenPrinting/cups-filters/pull/235

This makes "driverless" taking too long time, especially if there are 
many printers. See the investigations on


https://github.com/OpenPrinting/cups/issues/65

Therefore I have removed the feature again now, on both master and 1.x 
branches of cups-filters:


https://github.com/OpenPrinting/cups-filters/commit/3fddcf5

https://github.com/OpenPrinting/cups-filters/commit/aae86d2

Please test, this should solve your problem.

I will release cups-filter 1.28.7 soon, with this change included.



Bug#979177: cups-filters-core-drivers: Adding a printer impossible because "driverless" is too slow

2021-01-06 Thread Till Kamppeter

The problem also got reported upstream:

https://github.com/OpenPrinting/cups/issues/65

Could you also see the discussion there and try what got suggested there?

I by myself am not able to reproduce it, so I need someone who can 
reproduce it to find out under which conditions it happens.


   Till



Bug#979177: cups-filters-core-drivers: Adding a printer impossible because "driverless" is too slow

2021-01-06 Thread Brian Potkin
Any progress on this issue, Shai?

Cheers,

Brian.



Bug#979177: cups-filters-core-drivers: Adding a printer impossible because "driverless" is too slow

2021-01-04 Thread Brian Potkin
tags 979177 moreinfo
thanks


On Sun 03 Jan 2021 at 23:24:10 +0200, Shai Berger wrote:

> Package: cups-filters-core-drivers
> Version: 1.28.6-1
> Severity: normal
> 
> Dear Maintainer,
> 
> I've seen some misbehavior from my printer, and tried to remove and add it
> back again. This failed, with the symptoms described in
> https://unix.stackexchange.com/questions/276736/cups-adding-printer-fails-with-unable-to-get-list-of-printer-drivers-success
> that is, no matter what interface I use -- KDE, Gnome or the web
> via localhost:631 -- I get the same error when trying to find
> drivers for the printer:
> 
>   Unable to get list of printer drivers:
>   Success
> 
> Following the advice on that page, I tried to see if removal of
> one of the files in /usr/lib/cups/driver can help me get faster
> results, and I found that the guilty script was
> /usr/lib/cups/driver/driverless

Thank you for your report, Shai.

How do you go on with 'lpinfo -m' when
  * /usr/lib/cups/driver/ contents are as normal?
  * /usr/lib/cups/driver/ contains only driverless?
 
> I then tried to run this script in isolation, and got:
> 
> $ time /usr/lib/cups/driver/disabl/driverless list
> DEBUG: Started ippfind (PID 19070)
> Failed to get info about driverless support.
> "driverless:ipp://HP%20OfficeJet%206950%20%5B00A23E%5D%20(USB)._ipp._tcp.local/"
>  en "HP" "HP OfficeJet 6950, driverless - cannot check driverless status, 
> cups-filters 1.28.6" "MFG:HP;MDL:OfficeJet 
> 6950;CMD:PCLM,PCL,PWGRaster,AppleRaster,JPEG,URF,PWG;"
> "driverless-fax:ipp://HP%20OfficeJet%206950%20%5B00A23E%5D%20(USB)._ipp._tcp.local/"
>  en "HP" "HP OfficeJet 6950, Fax, driverless - cannot check driverless 
> status, cups-filters 1.28.6" "MFG:HP;MDL:OfficeJet 
> 6950;CMD:PCLM,PCL,PWGRaster,AppleRaster,JPEG,URF,PWG;"
> DEBUG: ippfind (PID 19070) exited with no errors.
> 
> real3m1.817s
> user0m0.005s
> sys 0m0.015s

I get a similar real time and output to you but without "Failed to get
info about driverless support." and "cannot check driverless status,".
It would seem your device failed to respond to any requests for the IPP
versions available. This is a check for which type of driverless support
is available. The absence of the information does not appear to be a
show stopper as a URI (ipp://...) is still obtained.

> Noticing my specific printer named in the output -- could it be
> that the script tries to communicate with it, but fails to do it
> in a robust way?

It doesn't look like it. The driverless output seems reasonable to me.

Please give the outputs of

  systemctl list-units "ipp-usb*" | grep service

and

  lpstat -t

Regards,

Brian.



Bug#979177: cups-filters-core-drivers: Adding a printer impossible because "driverless" is too slow

2021-01-03 Thread Shai Berger
Package: cups-filters-core-drivers
Version: 1.28.6-1
Severity: normal

Dear Maintainer,

I've seen some misbehavior from my printer, and tried to remove and add it
back again. This failed, with the symptoms described in
https://unix.stackexchange.com/questions/276736/cups-adding-printer-fails-with-unable-to-get-list-of-printer-drivers-success
that is, no matter what interface I use -- KDE, Gnome or the web
via localhost:631 -- I get the same error when trying to find
drivers for the printer:

Unable to get list of printer drivers:
Success

Following the advice on that page, I tried to see if removal of
one of the files in /usr/lib/cups/driver can help me get faster
results, and I found that the guilty script was
/usr/lib/cups/driver/driverless

I then tried to run this script in isolation, and got:

$ time /usr/lib/cups/driver/disabl/driverless list
DEBUG: Started ippfind (PID 19070)
Failed to get info about driverless support.
"driverless:ipp://HP%20OfficeJet%206950%20%5B00A23E%5D%20(USB)._ipp._tcp.local/"
 en "HP" "HP OfficeJet 6950, driverless - cannot check driverless status, 
cups-filters 1.28.6" "MFG:HP;MDL:OfficeJet 
6950;CMD:PCLM,PCL,PWGRaster,AppleRaster,JPEG,URF,PWG;"
"driverless-fax:ipp://HP%20OfficeJet%206950%20%5B00A23E%5D%20(USB)._ipp._tcp.local/"
 en "HP" "HP OfficeJet 6950, Fax, driverless - cannot check driverless status, 
cups-filters 1.28.6" "MFG:HP;MDL:OfficeJet 
6950;CMD:PCLM,PCL,PWGRaster,AppleRaster,JPEG,URF,PWG;"
DEBUG: ippfind (PID 19070) exited with no errors.

real3m1.817s
user0m0.005s
sys 0m0.015s

Noticing my specific printer named in the output -- could it be
that the script tries to communicate with it, but fails to do it
in a robust way?

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'unstable'), (800, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_IL.UTF-8, LC_CTYPE=en_IL.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cups-filters-core-drivers depends on:
ii  bc 1.07.1-2+b2
ii  cups-ipp-utils 2.3.3op1-3
ii  libc6  2.31-6
ii  libcups2   2.3.3op1-3
ii  libcupsfilters11.28.6-1
ii  libgcc-s1  10.2.1-3
ii  liblcms2-2 2.9-4+b1
ii  libpoppler-cpp0v5  20.09.0-3
ii  libqpdf28  10.0.4-1
ii  libstdc++6 10.2.1-3
ii  poppler-utils  20.09.0-3
ii  zlib1g 1:1.2.11.dfsg-2

cups-filters-core-drivers recommends no packages.

cups-filters-core-drivers suggests no packages.

-- no debconf information