Re: [cups] One user unable to use lpr

Jörg Thümmler <[email protected]> Thu, 30 Nov 2023 08:04:08 +0100
Newsgroups gmane.comp.printing.cups.general
Message-ID <[email protected]>
Hi,

assume the "lpstat"-answers are from this user...

sounds like a user rights problem. Usually a user should have the rights 
for printing by beeing in group "users", but maybe there is something 
wrong in your cups config.

In cups.conf shoukd bve something like

<Policy default>
   JobPrivateAccess all
   JobPrivateValues none
   SubscriptionPrivateAccess all
   SubscriptionPrivateValues none
   <Limit Create-Job Print-Job Print-URI Validate-Job>
     Order deny,allow
   </Limit>
   <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job 
Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription 
Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job 
Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job 
CUPS-Get-Document>
     Require user @OWNER @SYSTEM
     Order deny,allow
   </Limit>
   <Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer 
CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default CUPS-Get-Devices>
     AuthType Default
     Require user @SYSTEM
     Order deny,allow
   </Limit>
   <Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer 
Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs 
Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer 
Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs 
CUPS-Accept-Jobs CUPS-Reject-Jobs>
     AuthType Default
     Require user @SYSTEM
     Order deny,allow
   </Limit>
   <Limit CUPS-Authenticate-Job>
     Require user @OWNER @SYSTEM
     Order deny,allow
   </Limit>
   <Limit All>
     Order deny,allow
   </Limit>
</Policy>

and

DefaultPolicy default

to allow users to print and to use basic cups functions ("user" has to 
be in the above "Required" entries).

In some configurations it's necessary for users to be in the "lp" group 
to print, the above will be different then (no "user" in the Require...)

Also your DefaultPolicy can be something different. Maybe it's an idea 
for testing to set it to "Allowallforanybody" to exclude user rights 
problems - set it back after testing ;-)

restart cupsd if you changed something in the configs (and backup them 
before changing ;-)

-- 
cu

jth


Am 29.11.23 um 21:06 schrieb Johnnie W Adams:
> I should have added this output:
> 
> lpstat -t
> 
> scheduler is running
> 
> no system default destination
> 
> lpstat: Forbidden
> 
> lpstat: Forbidden
> 
> lpstat: Forbidden
> 
> lpstat: Forbidden
> 
> lpstat: Forbidden
> 
> 
> On Wed, Nov 29, 2023 at 2:04 PM Johnnie W Adams <[email protected]> wrote:
> 
>> Hi, folks,
>>
>>       So I've got a new RHEL 8 server and one particular user can't print
>> with lpr, getting this error: "lpr: Error - scheduler not responding".
>> Both root and my own ID can.
>>
>>       Any thoughts?
>>
>> Thanks,
>>
>>       John A
>>
>> --
>> John Adams
>> Senior Linux/Middleware Administrator  | Information Technology Services
>> +1-501-916-3010 | [email protected] | http://ualr.edu/itservices
>> *UA Little Rock*
>>
>> Reminder:  IT Services will never ask for your password over the phone or
>> in an email. Always be suspicious of requests for personal information that
>> come via email, even from known contacts.  For more information or to
>> report suspicious email, visit IT Security
>> <http://ualr.edu/itservices/security/>.
>>
> 
> 
_______________________________________________
cups mailing list
[email protected]
https://lists.cups.org/mailman/listinfo/cups