public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Network printer not being found
Date: Fri, 30 Oct 2020 11:20:05 +0000	[thread overview]
Message-ID: <9795641.nUPlyArG6x@peak> (raw)
In-Reply-To: <1850536.yKVeVyVuyW@lenovo.localdomain>

[Some snipping]

On Thursday, 29 October 2020 19:25:47 GMT Michael wrote:
> On Thursday, 29 October 2020 14:16:17 GMT Peter Humphrey wrote:
> > Before my trials with booting, and eventually rebuilding everything from
> > the ground up, my Lexmark C2425 printer was working fine. Now the KDE
> > system settings printer applet can't detect it, even though pinging it
> > works.
> Is the IP address of the printer the same?

Yes.

> When you 'nmap -A -T4 -Pn -v <PRINTER_IP>' do you see open ports?  It should
> offer 80, 443, 515, 9100, 631 depending on the protocols it uses.

It offers 21, 80, 443, 515, 631, 4000, 5001, 9100 and 9500.

> > Then when I point firefox to localhost:631 cups's behaviour has changed.
> > If
> > I click Adding Printers and Classes, instead of a dialogue to let me add a
> > printer I now get a help page telling me how to do it at the command line.
> 
> Hmm ... something must be amiss in your setup.  When I go to the
> Administration tab and click to add another printer the familiar cupsd GUI
> offers various protocols to choose from.  Have you set USE="X"?

That's my fault. I didn't read the display properly. Now, seeing straight(er) 
Find New Printers doesn't find any, and Add Printer just gives me the usual 
manual methods of declaring the printer.

Emerge -pv gives me this:
net-print/cups-2.3.3-r1::gentoo  USE="X acl dbus pam ssl threads usb -debug -
kerberos -lprng-compat (-selinux) -static-libs -systemd -xinetd -zeroconf" 
ABI_X86="(64) -32 (-x32)"

> > Even if I do manage to add the printer, cups reports that it isn't
> > responding. I take this to mean I'm not using the right protocol. I've
> > tried IPP, IPPS, HTTP and HTTPS, following that help page.
> 
> You haven't locked down the printer itself to limit which IP addresses it
> will allow connections from?

Not knowingly. I haven't seen anything on the printer to suggest I can do 
that.

> Have a look here in case there is some step you've missed out:
> 
> https://wiki.gentoo.org/wiki/Printing

Yes, I've done that.

> Cups usually captures informative logs and you can set increased verbosity
> for more detail.  What do these logs report?

Ah! I think it's a pam problem: permission denied. I am in the lp group 
though. Do I also need to be in the lpadmin group? I never have been before.

-- 
Regards,
Peter.





  reply	other threads:[~2020-10-30 11:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29 14:16 [gentoo-user] Network printer not being found Peter Humphrey
2020-10-29 19:25 ` Michael
2020-10-30 11:20   ` Peter Humphrey [this message]
2020-10-30 11:51     ` Michael
2020-10-30 16:49       ` Peter Humphrey
2020-10-30 18:23         ` Michael
2020-10-31 12:30           ` Peter Humphrey
2020-10-31 17:06             ` Michael
2020-10-30  1:44 ` William Kenworthy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9795641.nUPlyArG6x@peak \
    --to=peter@prh.myzen.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox