Bug#697331: installation-reports: Printer not working / recognised - Fixed

[Brian Potkin <claremont102@gmail.com>]

On Sun 06 Jan 2013 at 06:53:46 +0100, Christian PERRIER wrote:

> Quoting de28jihem (de28jihem@scarlet.be):
> > 
> > The user was not in lpadmin group (checked with "id").
> > This caused problem to use the CUPS configuration menu (localhost:631).
> > 
> > Added the user in lpadmin (under root) :
> > > usermod -a -G lpadmin user1
> > 
> > Plugged in printer/scan.
> > 
> > Started a web browser, url "localhost:631" (the CUPS interface)
> > Select the "admin" tab; "add printer"; ... (almost all fields already filled in)
> > 
> > Printing ok (from mousepad editor & libre office document)
> 
> 
> Hmmmm, that brings the problem back in the scope of the installer,
> then. The initial group membership *for the first created user* is
> done in D-I (though the user-setup module) and the user is added to a
> predefined set of "useful groups".
> 
> Your experience brings the question of whether we should add lpadmin
> to this. However, I don't understand why one should be a member of
> lpadmin in order to *print*.

The problem encountered by de28jihem in setting up and administering a
print queue is not uncommon; #680195 gives another example.

The list of "useful groups" in passwd/user-default-groups has scanner
and debian-tor, both of which were added in recent times without any
fuss or controversy. There may be arguments against adding the first
created user to the lpadmin group but, at first sight, it appears to be
at least as beneficial as any of the existing default groups, especially
as the choice of installed tasks now includes a print server.

Regards,

Brian.