[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: problem adding cups print queue to debian live starting with buster



Not exactly cross purposes.  I'm encountering the cups error before I
get the chance to even select any specific printer or printer
interface.  Given that this is with Debian live[1], I'll be using it,
as I have in the past, with USB or network printers or even a parallel
port printer if I have one.  The test setup I have right now for
reporting on and researching this problem has both USB and network
printers available.  The PC looks like it has a parallel port and I do
have a parallel port printer nearby if that helps.  I definitely would
like to figure out what's wrong, as Debian live is a useful tool, and
it was great when printing worked with it.  (I don't care if it's a
real bug or just a dumb user mistake to figure out and share.)

The computer, printer, and network haven't changed since this was
working with the last Debian 9 point release XFCE live image.

Let me walk through the scenario again, with a more step by step
detail.  (And please ask if I should flesh out anything even further!)

Step 1:  Boot debian-live-10.1.0-amd64-xfce.iso[2].  (Image written to
read only thumb drive.  Thumb drive read back to verify checksum and
image integrity.)  Packages in this image are listed in [3].

Step 2:  sudo apt-get update

Note:  no sudo apt-get upgrade this time just to keep it simple.

Note:  sources.list only contains one line:  deb
http://deb.debian.org/debian/ buster main

Step 3:  sudo apt-get install cups

Note:  cups server was not installed, so need to install.  Same with
Debian 9 live.  Additional packages apt-get installed are in [3].
Could there be something else required?

Step 4:  sudo /etc/init.d/cups start

Note:  no custom configuration changes before starting cups server.
Wasn't required for Debian 9 live.

Note:  at this point, cups has 8 lines in /var/log/cups/error_log.

     E [29/Oct/2019:14:40:35 +0000] Unable to open
\"/usr/share/cups/mime\": Permission denied
     E [29/Oct/2019:14:40:35 +0000] Unable to open \"/etc/cups\":
Permission denied
     E [29/Oct/2019:14:40:35 +0000] Unable to open
\"/usr/share/cups/mime\": Permission denied
     E [29/Oct/2019:14:40:35 +0000] Unable to open \"/etc/cups\":
Permission denied
     E [29/Oct/2019:14:40:35 +0000] cupsdLoadBanners: Unable to open
banner directory "/usr/share/cups/banners": Permission denied
     E [29/Oct/2019:14:40:35 +0000] Unable to open spool directory
"/var/spool/cups": Permission denied
     E [29/Oct/2019:14:40:35 +0000] Unable to open directory
"/var/spool/cups/tmp" - Permission denied
     E [29/Oct/2019:14:40:35 +0000] Unable to open directory
"/var/cache/cups" - Permission denied

Those look dire.  New with buster?

ls -ld on those directories shows:
     drwxr-xr-x 2 root root 240 Oct 29 14:40 /usr/share/cups/mime
     drwxr-xr-x 5 root lp 220 Oct 29 14:40 /etc/cups
     drwxr-xr-x 2 root root 180 Oct 29 14:40 /usr/share/cups/banners
     drwxrwx--T 2 root lp 40 Aug 21 07:43 /var/spool/cups/tmp
     drwxrwx--- 3 root lp 80 Oct 29 14:40 /var/cache/cups

Note:  at this point, cupsd process is running as root.

Step 5:  XFCE menu:  Applications:  Settings:  Print Settings

ps -efd | grep user | grep print suggests that starts:
     user      1125   987  0 02:37 ?        00:00:02 /usr/bin/python3
/usr/share/system-config-printer/applet.py
     user      6263  1075  2 14:47 ?        00:00:01 /usr/bin/python3
/usr/share/system-config-printer/system-config-printer.py

Note:   The dialog box for the print settings comes up ok.  There is a
cupsd access log message showing the connection made without error.

Step 6:  In the print settings application, click on add printer.  It
asks for username & password authentication.  It did not do this with
buster 9.  Cancel.

Note:  is there a new need for user to be member of lp or lpadmin
group?  user is member of neither.

Step 7:  sudo adduser user lp

Step 8:  sudo adduser user lpadmin

Step 9:  logout and back in.  Verify user now member of those groups as well.

Step 10:  start prnt settings application again.  Select add printer.

Note:  no longer get the request to authenticate.  However, now get an
error dialog popup that says:
     "CUPS server error
      There was an error during the CUPS operation: 'Internal Server Error'."
With cancel & retry buttons.

/var/log/cups/access_log looks ok containing:
localhost - - [29/Oct/2019:14:47:18 +0000] "POST / HTTP/1.1" 200 273
Create-Printer-Subscriptions successful-ok
localhost - - [29/Oct/2019:14:51:34 +0000] "POST / HTTP/1.1" 401 147
CUPS-Get-Devices successful-ok
localhost - root [29/Oct/2019:14:51:34 +0000] "POST / HTTP/1.1" 500
147 CUPS-Get-Devices -
localhost - - [29/Oct/2019:14:51:34 +0000] "POST / HTTP/1.1" 401 147
CUPS-Get-Devices successful-ok
localhost - user [29/Oct/2019:14:51:34 +0000] "POST / HTTP/1.1" 403
147 CUPS-Get-Devices successful-ok
localhost - - [29/Oct/2019:14:51:34 +0000] "POST / HTTP/1.1" 401 147
CUPS-Get-Devices successful-ok
localhost - - [29/Oct/2019:14:54:35 +0000] "POST / HTTP/1.1" 401 147
CUPS-Get-Devices successful-ok
localhost - root [29/Oct/2019:14:54:35 +0000] "POST / HTTP/1.1" 500
147 CUPS-Get-Devices -
localhost - - [29/Oct/2019:14:54:35 +0000] "POST / HTTP/1.1" 401 147
CUPS-Get-Devices successful-ok
localhost - user [29/Oct/2019:14:54:35 +0000] "POST / HTTP/1.1" 500
147 CUPS-Get-Devices -
localhost - - [29/Oct/2019:14:54:40 +0000] "POST / HTTP/1.1" 200 152
Cancel-Subscription successful-ok
localhost - - [29/Oct/2019:14:57:38 +0000] "POST / HTTP/1.1" 200 273
Create-Printer-Subscriptions successful-ok
localhost - - [29/Oct/2019:14:57:42 +0000] "POST / HTTP/1.1" 401 147
CUPS-Get-Devices successful-ok
localhost - root [29/Oct/2019:14:57:42 +0000] "POST / HTTP/1.1" 500
147 CUPS-Get-Devices -
localhost - - [29/Oct/2019:14:57:42 +0000] "POST / HTTP/1.1" 401 147
CUPS-Get-Devices successful-ok
localhost - user [29/Oct/2019:14:57:42 +0000] "POST / HTTP/1.1" 500
147 CUPS-Get-Devices -

/var/log/cups/error_log has no new entries.  So, cups client says
server had internal error, but server didn't log anything.

Note:  I still haven't gotten to the point of picking any specific
printer or specific printer interface.  :-(

Thanks and best regards,

Drew

Footnotes:
1 https://www.debian.org/CD/live/
2 https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/
3 https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/debian-live-10.1.0-amd64-xfce.packages
4 Additional packages installed by apt-get install cups:
  bc colord colord-data cups-browsed cups-core-drivers cups-daemon
  cups-filters cups-filters-core-drivers cups-ipp-utils cups-ppdc
  cups-server-common ghostscript libcolorhug2 libfontembed1 libgusb2
  libgutenprint-common libgutenprint9 liblouisutdml-bin liblouisutdml-data
  liblouisutdml8 libqpdf21 poppler-utils printer-driver-gutenprint ssl-cert


On Tue, Oct 29, 2019 at 10:13 AM Brian Potkin <claremont102@gmail.com> wrote:
>
> On Tue 29 Oct 2019 at 02:45:27 +0000, Drew Arnett wrote:
>
> > Hi Brian,
> >
> > Thanks for the question.
> >
> > I get the error just when I click on add printer which is before I
> > even get to select any type of printer, let alone point at a printer
> > interface.
> >
> > Any and all ideas for trouble shooting welcome.  I'll do legwork to
> > get more info, but I'm not very knowledgeable about cups, so hoping
> > for a bit of help in that regard,
> >
> > Thanks and best regards,
> >
> > Drew
> >
> > On Mon, Oct 28, 2019 at 5:27 PM Brian Potkin <claremont102@gmail.com> wrote:
> > >
> > > On Mon 28 Oct 2019 at 14:00:13 +0000, Drew Arnett wrote:
> > >
> > > > Starting with buster, I haven't been able to setup a printer in cups.
> > > > I've tried the 10.0.0 and the 10.1.0 versions of the amd64 xfce live
> > > > image.  9.x xfce images worked OK, so something has changed.
> > >
> > > Drew - knowing the make and model of the printer would be very useful.
>
> Perhaps we are a little at cross-purposes. I wish to know what printer
> model is being set up. Knowing whether a USB or network connection is
> intended would also be good.
>
> Cheers,
>
> Brian.


Reply to: