Re: [cups] lpform failing, password not recognized

Am 01.06.23 um 17:01 schrieb Johnnie W Adams:
> Hi, folks,
> 
>       From one of my users:
> 
> I was taught to issue a command similar to the following:
> lpform lineprint2 -Pls139 outputfile.txt
> 
> lineprint2 is a form
> -Pls139 designates the print queue ls139
> outputfile.txt is what needs to be printed.
> 
> When I issue this command, it prompts me thusly:
> Password for <user id> on localhost?
> It does not accept my password
> 
> When it fails, I get:
>   /usr/bin/lpr: Error - The printer or class does not exist.
> lpform error: /usr/bin/lpr -h returned error code 1
> 
>       I've done what I know to do for him. Do any of you have ideas?
> 
> Thanks,
> 
>       John A
> 

Hi,

no cmd "lpform" here. IMHO "lpform" is a script / program performing 
some formatting with outfile.txt and sends the output to the printer 
ls139 via cups. Maybe "lpform" is part of some special cups packages.

The given err msg I would interprete as cups says "the printer ls139 
doesn't exist on your system".

What do you get when running (as root)

	lpc status ls139

output should be something like:

ls139:
	printer is on device 'socket' speed -1
	queuing is enabled
	printing is enabled
	no entries
	daemon present

the "Password for <user id> on localhost?" otherwise is what you usually 
get if some authentification error occurs. I saw it, when cups 
(sometimes it does it, no clue why) changed a cups printer's entry (in 
fact a smb printer's) from

	AuthInfoRequired username,password
to

	AuthInfoRequired negotiate

in printers.conf. There may be a incorrect general setting in cupsd.conf

	DefaultAuthType Basic

is in mine and it may be more "secure" in yours...

Some info on this lpform script maybe interesting but mostly interesting 
are the /etc/cups/printers.conf and /etc/cups/cupsd.conf files I believe.

-- 
cu

jth

_______________________________________________
cups mailing list
[email protected]
https://lists.cups.org/mailman/listinfo/cups