Re: Bug#697331: installation-reports: Printer not working / recognised - Fixed
On Tue 08 Jan 2013 at 07:14:26 +0100, Christian PERRIER wrote:
> Quoting jswmb01x (jswmb01x@mobistarmail.be):
> >
> > Clarification :
> > Adding "user1" to the lpadmin group was required to add the printer in CUPS (otherwise after entering the user name and password the operation is "forbidden"), not for printing.
>
>
> Hmmm, well, then I would say this is cups that changed its behaviour
> and made it a requirement to have privleges in order to add a printer,
> even "plug n' play" toys. Which makes sense to me. Indeed, even on
> Windows, unprivileged users cannot add local printers to the system
> (but most Windows users don't notice as they always virtually work as
> "root" on their machines).
The requirement has been present for the past 10+ years when using the
web interface of CUPS to add a printer.
> That makes it less of a requirement to have the first created user in
> lpadmin, after more thinking.
>
> This bug could then even be "wontfix".
Given the existing status of using group membership in d-i to grant the
first created user limited privileges, I think the issue revolves round
whether there is something special about the lpadmin group which would
militate against adding it to the first user account.
A Cc: has been sent to debian-printing to allow them to comment on the
usefulness and wisdom of putting lpadmin in user-setup-udeb.
Regards,
Brian.
Reply to: